Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
So like 2 people who still use DVI?

Meanwhile most of us using USB-C are still stuck on ****** YPbPr mode and washed out displays.

Way to go Apple!:rolleyes:

So make me the 3rd person who still use DVI? I get you have high end monitor with USB-C, but some people are still using their old functional monitors? I really don't see the reason for me to change my 10 years old monitor, I mean it works just fine...
 
And now I update (from RC2 11.2)

FYI- bluetooth appears to be fixed. Went two days without a disconnect, even some time at a BT congested coffee shop with it.

Would've cut in and out about 15-20x in that timeframe, on 11.0.1 previously on my M1 air.

RC3 build = GM. 20D64 is build number for both.
I wish I could say the same, as soon as I connected my AirPods Pro to my M1 MBP, my magic keyboard started lagging and only stopped when I took out my APP and put them back in their case. The only other peripheral I have attached is my Magic Mouse 2. I’m really hoping it was just a fluke.
 
Why wouldn't you just reinstall what works?
I guess I'll have to if this update doesn't fix things. The longer I leave it, the more work to reconcile with the small bit of work I've got done since going from Catalina to Big Sur. TBH, I wish I still had a SuperDuper backup of my Mojave set up, since late Mojave builds have been the fastest and most stable of recent years, for me at least.
 
Not sure yet about the Bluetooth fix. My son has had all sorts of Bluetooth issues with his 2020 13" MacBook Pro (10th generation Intel), so hopefully it's now fixed.

With my M1 MacBook Air, I never had any bluetooth issues, but I've been having all sorts of external monitor issues with the HDMI monitor not waking up after the M1 MacBook Air goes to sleep. I have to disconnect the physical cable from the M1 and then plug it back in and then pound on the space bar on the external keyboard for the monitor to finally be detected by the M1 MacBook Air and the 4K image to come up. The DP1.4 (5K) connection on this monitor doesn't work with the M1 at all (the M1 MacBook Air doesn't even detect that the monitor is connected), whereas the same monitor works fine via DP1.4 with the 2020 13" MacBook Pro (10th generation) with the true 5K image.

I opened a case with Apple on the external display issue back in December, and after about a month of trying to tell me it was the monitor's issue they finally admitted the issue with the M1 laptops. They never committed to fixing it, but kind of intimated that it could be fixed at one point. Unfortunately, it's not fixed in 11.2. It's pathetic really.
 
Progress bar stuck at about 70% for at least an hour (or maybe even two) since the update started. I already had this happened going from 11.0 to 11.1, literally bricked my M1 Air, struggled to do a clean wipe install and here we are again.
 
It took about an hour to download and install but it's working fine. Too early to tell if I get skipping on Bluetooth speakers and mouse lag on Bluetooth mouse.
Do let me know if that is lag. I havent update yet too.
 
The number of times this update reboots and goes blank just to wake up again and start the process bar tells me there’s some deep stuff being updated. Probably some low-level Firmware. I’ve never seen anything like this before. It also spins fans like crazy in the 2020 13” MacBook Air (10th generation) while updating.

If your think your Mac is off because the screen is black, don’t do anything. Leave it alone. It’s doing some crazy low-level crap. After about 4 or 5 reboots, I finally got to the screen that says 9 minutes left. It took about 30 min to get here from the time it downloaded the update. About 15 minutes preparing update and another 15 minute rebooting, going black, waking up, rebooting again, showing progress bar, going black, showing progress bar again, rebooting again, etc.
Crazy is the right word. A mess of black screens (of arbitrary duration) and various solitary progress bars is a terrible way of keeping a user informed.
 
But does it actually fix the problem of turning a 2017 iMac into a porridge-eating snail? Will it make my computer usable again?
Did you made a clean install? Boot from external USB, erase internal HD and install a fresh OS. Then install your software again and configure as a new machine. I’ve always do follow this procedure (since Mac OS 6... long long time ago)
 
Finally, Safari no longer randomly closes in between.
And more importantly: Finally, my iMac (27" Mid 2015) no longer crashes regularly with a kernel panic! It's annoying that Big Sur can only be used on the iMac after its second update. After all, a regularly occurring kernel panic is not considered a "small bug".
 
What’s wrong with it?
Try this for issues with Music App

 
That's slightly different. Mojave, Catalina, and Big Sur are receiving security updates, no earlier OS is. Apple's repeatedly demonstrated incompetence with OS development has meant for some years that the safe option is to wait until the .6 before installing the new shiny.
I had done that for years - install the .6 version of the previous OS when the new OS was released in the fall. Except this year - so far I have resisted going from Mojave to Catalina after the release of Big Sur due to the many comments here about how bad the final version of Catalina still is.
 
My only problem with Big Sur 11.1 (clean install) on MBP 15" 2016 was with kernel panic which crashed my machine few times during sleep so I downgrade back to Catalina and no problems at all.

I did Apple HW diagnostic and the result was no problem so I assume the problem lies in Big Sur.

panic(cpu 0 caller 0xffffff801f77ecde): nvme: “Fatal error occurred. ID=0x843 ARG1=0x4c0e ARG2=0xfc ARG3=0xfe EDD0=0x10600000 EDD1=0x100000 EDD2=0x0 EDD3=0x1cf00000 EDD4=0x0 EDD5=0x0 EDD6=0x0 EDD7=0x0 NANDV=0x2, DRAMV=0x2, SSDC=256GB. FW Revision=9.134.01\n”@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.40.12/Common/IONVMeController.cpp:5471
 
Cursor stuttering/choppy animations still present on integrated graphics. MacBook Pro 16 inch.
 
After a few hours use, it seems to me that 11.2 is not working my M1 mini so hard.

I run folding@home in the background to soak up all the available CPU to assist Covid research.

11.1 was idle around 5% and folding was running at around 640%
11.2 the figures are idle 15% and folding around 580%

I'm doing nothing different in terms of usage, its almost as if its 'lost' a whole CPU
 
Bluetooth Audio dropouts with Flip4 continues in 20D64. No fix for that. Appalling, Apple.
 
The 11.2 update did not solve the HDMI issue of M1 Mac mini. It is even much, much worse than with the 11.1 when connecting a display through the HDMI - besides the massive picture ghosting (which was before as well), the picture is flickering extremely ("HDMI of Mac mini M1 - Apple HDMI to DVI Adapter - Apple Cinema HD 23-inch Display/first generation").
 
Update took very little time.
I left the room after hitting the update button and it was all ready when I returned after 15 mins (m1 MBA)

First impressions - opening apps seems marginally faster
Overall CPU load is also (probably) better than before.
The CPU temps are around 4-5C lower than before while driving a 4K monitor and runninga zoom call and bunch of other windows open.

Too early to say for sure but seems to be an improvement over 11.1
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.