I read through various forums that MacOS 11.1 beta 2 solves the Bluetooth connection issue. I haven't tried it myself. I did notice Bluetooth drops when I paired with my Magic Mouse 2. I also heard that this might be an issue with Big Sur itself because some people are having the same issues on Intel Macs.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I’ve reverted - giving up for now on these machines.
- Thread starter turbineseaplane
- Start date
- Sort by reaction score
1) Obviously some who buy one with possibility of return will not return but just keep. 100% of those who buy two with the intent of returning one will return one. More wasteful.
2) Intent matters.
@senttoschool
I really hope 11.2 solves the issues I’d had. I’m starting to wonder if the Mini I had was a lemon unit
I really hope 11.2 solves the issues I’d had. I’m starting to wonder if the Mini I had was a lemon unit
Last edited:
Scenario 1 could also have people buying two to directly compare them side by side and decide.
On point 2, intent really doesn’t matter to Apple if you keep one either way. If you don’t keep any, or you could have maybe reached that decision without buying and returning one of the units, then yes, I’m with you.
If you are Apple you’d rather someone buy and try both and keep one though, if the alternative there is buying nothing (just one scenario of course)
I hope folks here realize that we could talk about this from umpteen angles and none of it will change what people actually do.
Anyhow..
Well none of it will change what you do. I’m not sure you can extrapolate your behaviour to everyone else on the planet.
M1/Apple def has flaws like brand new microphones not being compatible. The computer is lightning fast but isn’t compatible with some software and connections I have tried. Frustrating to say the least but I have tried to go to Windows and have purchased super gamer computers that don’t perform a fraction of what the m1 performs with. As someone who used the computer for recording not many microphones work perfect a lot of issues.
So he expected a 4K webcam when it lists 720 P on the specs... I wasn’t criticizing anyone. It’s unreasonable to expect something other than exactly what is listed on your purchase. Should I be upset if I order a 13” MacBook and it doesn’t come with a 16” screen? I’m sure someone here would ?♂️
It does. I'm on it since day 1 I got my MacBook Air and didn't experience any Bluetooth issues... Everything is running fine...
I wonder if this is a different issue than Intel Mac mini has with Bluetooth? Mine just has short range so if I put my computer under my desk it gives me problems with the mouse. If it’s on or next to my desk everything works fine. It’s not a dealbreaker for me and I absolutely love my mini. I’ve had way more issues with my Windows PC
Hey, I am as shocked as everyone else is that we can now state that an Apple laptop is better value than it's direct Wintel counterpart without qualifying the statement or using "except" or "but". ?
I've been reading this thread - out of curiosity - and the above mentioned (BT devices not working on booting) got me confused. I have been using an iBook in 2005 and an Inten iMac from 2007 and onward, and I was pretty damn sure that I could use my wireless Apple Keyboard + Magic Mouse to - for example - reset SMC or anything alike with hitting certain keys at startup.
Do I remember that incorrectly?
I honestly don't know but it's possibly feasible that drivers for known devices, like native wifi/BT card, Apple keyboard or magic mouse could be loaded pre-boot (after all the drivers must be loaded for the laptop keyboard) so that input can be made by them.
But it's not really feasible for drivers for every known Bluetooth input device to be loaded in this way. There are just too many.
It is technically possible to include some basic drivers as a part of the initial bootloader to allow input from a wireless keyboard or mouse. However, you would have to fit that into a finite amount of space with everything else needed for the initial boot of the machine. With the M1 Macs, Apple has made yet another change to how the machine boots, and I'm not sure anyone outside of Apple fully knows how this new setup works, or what drivers can be loaded prior to actually launching Mac OS.
Just want to chime on the return discussion.
Senior staff at Apple Stores have actively said to me on multiple occasions to return the computers if they are not right, as their goal is satisfied customers. As a happy customer we always go back to Apple.
But yes we pay for the convenience in the price.
Senior staff at Apple Stores have actively said to me on multiple occasions to return the computers if they are not right, as their goal is satisfied customers. As a happy customer we always go back to Apple.
But yes we pay for the convenience in the price.
I suspect that apart from only apple knowing, that they will only ever provide limited support for bluetooth at UEFI (or whatever it's called in M1) because of security concerns. Not saying no support, but some functionality may always be limited or unsupported.
To be clear: it's a great policy and I fully support. If you're not happy, return it. If something doesn't work the way it should, return it.
I think the only thing people have commented on is using that policy to just play with a new toy for a few weeks with no intention of keeping it.
The apple apologists here are so funny... while others like me are more willing to solve and discover issues FOR Apple. Cheerleading the brand and "it's good as it is, take it or leave it" is not going to make the issues disappear.
So I also have the problem with waking up my external monitors on my M1 Mac Mini. Originally, it was the LG monitor connected to the HDMI port. I suspect this is maybe fixable through hardware, so I went to purchase a HDMI 2.0 cable as I was using a HDMI 1.4 cable, and viola! The monitor is good now...
BUT!!! BUT!! My the other monitor connected to USB-c (also LG) starts to experience this wake-up issue after I changed the cable for my previously mentioned monitor. It had no issue before.
So, my uneducated guess tells me, the M1 Mac Mini has some sort of bandwidth limitation issue (!?) and that results in monitors (if more than 1) not getting the proper information from the computer.
Therefore, if there's no software update for this, the only way in my eyes that this is somehow fixable, is to play around with different ports using different cables and hubs and adapters. Maybe it will be working then.
(no bluetooth issue on my part, only no instant connection when I turn on the mac)
So I also have the problem with waking up my external monitors on my M1 Mac Mini. Originally, it was the LG monitor connected to the HDMI port. I suspect this is maybe fixable through hardware, so I went to purchase a HDMI 2.0 cable as I was using a HDMI 1.4 cable, and viola! The monitor is good now...
BUT!!! BUT!! My the other monitor connected to USB-c (also LG) starts to experience this wake-up issue after I changed the cable for my previously mentioned monitor. It had no issue before.
So, my uneducated guess tells me, the M1 Mac Mini has some sort of bandwidth limitation issue (!?) and that results in monitors (if more than 1) not getting the proper information from the computer.
Therefore, if there's no software update for this, the only way in my eyes that this is somehow fixable, is to play around with different ports using different cables and hubs and adapters. Maybe it will be working then.
(no bluetooth issue on my part, only no instant connection when I turn on the mac)
Last edited:
@yolo355355
Glad to hear it wasn't just me - thanks for reporting that.
I also share the desire to constructively work through some of this stuff instead of just "defending Apple" as too many are keen to do (no clue why).
Glad to hear it wasn't just me - thanks for reporting that.
I also share the desire to constructively work through some of this stuff instead of just "defending Apple" as too many are keen to do (no clue why).
Here is why: you titled the thread this:
I’ve reverted - giving up for now on these machines.
Even if you said I'm ABOUT to give up, you would have more pulling for you. But you are still here at message #95 of this thread. So you do care about a resolution.New technology mixed with old technology has growing pains. Early adopters pave that way. For years we've heard HDMI cables don't matter. Now they do as @yolo355355 discovered. Last year when I bought my Intel Mini, I went through several monitors before I landed on the LG that Apple used to sell, it was the only one that worked properly and it came with a special cable and only worked on USB-C (Thunderbolt) not HDMI.
This stuff is never in the manuals and takes loads of trial an error. I defend Apple and New Technology because there are so many external variables to consider.
TL;DR: I defend Apple and New Technology because there are so many external variables to consider.
You do you.
I have given up on these for right now, for my usage needs, but we do still have one in the house that I will use to continue to track all this.
That’s why I’m still here.
I enjoy the discussion and the learning even if I don’t personally use one day to day.
The M’s are phenomenal- but not for everyone quite yet, depending upon what you do and what you already have, etc (obviously)
cheers
Every time someone mentions returning an Apple product, the peanut gallery shows up rending their clothes and demanding that we all stop and think of the poor stockholders! I think your reasoning is sound, I’m still holding off on a new Mac, I’ve got my 4 month old iPad Pro to hold me over. Problem is, now I like the pencil and the touch screen, now I just want a larger iPad running Mac OS. Anyway, good on you for trying it out, I think it makes sense to wait.
I have terrible Bluetooth performance on my M1 MacBook Pro with Magic Mouse Gen1.
Seems you have 5 courses of action
1. Do nothing
2. Return to Apple
3. Un pair / reset / re pair all BT devices
4. Update to 11.1 beta 2 Big Sur
5. Uncheck "wifi networking" and "Wifi calling" in location services
That last one was mentioned in another thread I think. I'm not having this issue as I don't use BT with my M1 (I could have it, dunno though), but my mate has it on an intel machine and it only started when he updated to Big Sur. He was on the phone to Apple and their answer was Number 3. It's working for him atm...
I have random M1 MBP Bluetooth disconnects with MM2 and am running a 3 year old LG 4K monitor. I get occasional wake from sleep issues as well as the occasional reboot.