the size of a build has nothing to do with the practical effects of any changes.
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.
Apple Releases macOS Big Sur 11.2.1 With Fix for MacBook Pro Charging Issue [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
the size of a build has nothing to do with the practical effects of any changes.
I gave up! Formatted Mac and currently installing Big Sur via internet.
I don't know if it's installing directly 11.2.1; I'll see when done.
I don't know if it's installing directly 11.2.1; I'll see when done.
Apple doesn't yet appear to have released a full 11.2.1 installer, so you'll need to update when you're done installing 11.2.
Is it me or is 11.2.1 noticeably faster than 11.2? Installed the new update on 3 computers and all 3 just feel that little bit more responsive.
I don’t want to speak too soon, but I’d agree. I’m still having a few issues, but I’m in better shape for sure.
Proper external monitor detection still broken, since Big Sur 11.1.
MBP 16, Dell S3220DGF monitor (1440p, 165hz)
Displayport is completely broken. Max 720p resolution, 60hz.
HDMI resolution and refresh rate is fine, but is stuck in YPbPr mode instead of RGB.
(bootcamp works fine)
MBP 16, Dell S3220DGF monitor (1440p, 165hz)
Displayport is completely broken. Max 720p resolution, 60hz.
HDMI resolution and refresh rate is fine, but is stuck in YPbPr mode instead of RGB.
(bootcamp works fine)
Just as a short update:
I managed to freshly install 11.2 directly from internet over wifi and then upgraded to 11.2.1.
Reinstalled all apps and drivers, certificates etc, reconfigured and restored data.
Now I have it back to where it was a couple of days ago. Whole process took about 6 hours.
I'm not sure if I'm imagining it or not, but it feels a bit snappier now.
Somehow I'm glad I did it, since this is the first fresh install since I got it almost three years ago.
Also fixed a couple of issues for me:
I'm being able to unlock again with Apple Watch and battery started charging again (but still faulty).
I managed to freshly install 11.2 directly from internet over wifi and then upgraded to 11.2.1.
Reinstalled all apps and drivers, certificates etc, reconfigured and restored data.
Now I have it back to where it was a couple of days ago. Whole process took about 6 hours.
I'm not sure if I'm imagining it or not, but it feels a bit snappier now.
Somehow I'm glad I did it, since this is the first fresh install since I got it almost three years ago.
Also fixed a couple of issues for me:
I'm being able to unlock again with Apple Watch and battery started charging again (but still faulty).
I heard something about having to rebuild the root permissions system... so - it's probably a valid reason. Although don't quote me on that.
For the record, this update almost hosed my 2017 15-inch MacBook Pro. MacBook Pro user since 2005, and Apple customer since 1988. Updates getting worse and worse. Glad they fixed the battery issue, but... woke my Mac today and it sat there on the Apple logo forever. Did SMC and PRAM resets twice. Same thing. Entered Recovery and ran First Aid on my "Big Sur" & "Big Sur - Data" volumes. No issues. Rebooted. Stuck on Apple Logo again. PRAM reset and SMC reset. Finally rebooted, unlocked the volume, then it asked me to login again. And then it ran me through the Big Sur setup wizard again, which wasted more time, even though I was already setup and it did remember my preferences. But made me go through Siri and crap again anyway. Then I found this new update and this article. I was not even told there was an update, so automatic updates are now turned OFF on my Mac. (Believe me, I am not a fan of this either.)
How does Apple believe that it's OK to have someone needing to start work on their Mac the next day and have an indefinite amount of time (> 1 hour) to deal with Apple's unpredictable and unannounced update from the previous day? Why can't Apple apply such security updates as hot-fixes and in the background? I'm a software engineer for over 20 years now, with experience in Swift and Objective-C (+ 10 other languages), and am appalled at how Apple has failed to stabilize its firmware, failed to use its System Integrity Protection technology to improve user experience and apply updates in patches in the background (as its SIP technology surely can do), and has taken more and more away from Mac power users and developers update after update. Now I can't even make Mail.app accessible (I am legally blind) by editing its MUIWebDocument.css, because the System volume is locked, even after disabling SIP. So Apple thinks we are all stupid and willing to tolerate this nonsense after paying top dollar for their products and support, over and over again.
I miss Steve Jobs. He was opinionated and believed he knew better than the customer, but at least he wouldn't tolerate this kind of crap in his products, and at least his opinions were mostly good for his customers. His successor doesn't. I'm afraid Steve was losing it when he appointed Tim Cook as his successor. Apple has taken away my Touch ID on the iPhone, and now I'm sad to say that the iPhone is now even less accessible than Android because of this. I can't enlarge fonts in apps, even though Apple has stricter user interface guidelines than Android (why does Apple even approve inaccessible apps in the App Store when they've provided all the developer tools to make those apps accessible?). And I just switched from Android to an iPhone 12 Pro Max. I cannot enlarge the fonts, and Face ID works only half the time for me, because I am visually impaired, and duh, I wear masks during COVID like everyone else. Because of Tim Cook's failed leadership, instead of putting the Touch ID sensor on the back like most of their competitors in the Android space, some defeatist moron in marketing decided that because they couldn't put it "in the screen," they would just eliminate it.
How does Apple believe that it's OK to have someone needing to start work on their Mac the next day and have an indefinite amount of time (> 1 hour) to deal with Apple's unpredictable and unannounced update from the previous day? Why can't Apple apply such security updates as hot-fixes and in the background? I'm a software engineer for over 20 years now, with experience in Swift and Objective-C (+ 10 other languages), and am appalled at how Apple has failed to stabilize its firmware, failed to use its System Integrity Protection technology to improve user experience and apply updates in patches in the background (as its SIP technology surely can do), and has taken more and more away from Mac power users and developers update after update. Now I can't even make Mail.app accessible (I am legally blind) by editing its MUIWebDocument.css, because the System volume is locked, even after disabling SIP. So Apple thinks we are all stupid and willing to tolerate this nonsense after paying top dollar for their products and support, over and over again.
I miss Steve Jobs. He was opinionated and believed he knew better than the customer, but at least he wouldn't tolerate this kind of crap in his products, and at least his opinions were mostly good for his customers. His successor doesn't. I'm afraid Steve was losing it when he appointed Tim Cook as his successor. Apple has taken away my Touch ID on the iPhone, and now I'm sad to say that the iPhone is now even less accessible than Android because of this. I can't enlarge fonts in apps, even though Apple has stricter user interface guidelines than Android (why does Apple even approve inaccessible apps in the App Store when they've provided all the developer tools to make those apps accessible?). And I just switched from Android to an iPhone 12 Pro Max. I cannot enlarge the fonts, and Face ID works only half the time for me, because I am visually impaired, and duh, I wear masks during COVID like everyone else. Because of Tim Cook's failed leadership, instead of putting the Touch ID sensor on the back like most of their competitors in the Android space, some defeatist moron in marketing decided that because they couldn't put it "in the screen," they would just eliminate it.
Last edited:
Give this a read (https://developer.apple.com/forums/thread/655506?page=18) and you'll find this issue is far more widespread then just 'a small number of 2016/2017 MBPs'.
My perfectly working MPB 2015 turned into a 'desktop' after an auto update and Apple refuse to take responsibility. The battery went from great health to now not holding any charge and being at 0% health, just like that! Many others are in the same boat, with perfectly functioning MBP's now with their batteries bricked and not covered as eligible models for Apples free battery replacement scheme.
Apple said I pay for a out of warranty battery replacement and also replace the logic board (CAD$800+).. I declined
Post a reply if this is you too
My perfectly working MPB 2015 turned into a 'desktop' after an auto update and Apple refuse to take responsibility. The battery went from great health to now not holding any charge and being at 0% health, just like that! Many others are in the same boat, with perfectly functioning MBP's now with their batteries bricked and not covered as eligible models for Apples free battery replacement scheme.
Apple said I pay for a out of warranty battery replacement and also replace the logic board (CAD$800+).. I declined
Post a reply if this is you too
My 2015 MBP had the bottom case replaced in the last month of AppleCare, and that helped it last a little more than another year before the battery started swelling up like mad again. I was told the out of warranty fix/replacement would cost me something like $650US. I also declined. Still debating on whether to fix it or sell it. I'm sure I can get something for it now, maybe. I'm also pretty sure if it's fixed again, it'll need to be "fixed" again in another 2 or so years.
Sounds like your battery is a hardware issue, different to the battery charging issue I believe is caused by firmware as part of the Big Sur update impacting older MBPs. Regardless, having a new battery replaced and to have it swell up within a year sounds dodgy. My MPB is still on the original battery since 2015, was in good health at 250 charge cycles and no signs of damage.. Until it bricked right after a Big Sur update.. hence I believe the firmware is to blame. Exact same issue and symptoms reported here https://support.apple.com/en-ca/HT212163 but Apple only specify certain 2016/2017 models as eligible for the fix.. Any others who are not eligible but facing the same 'Not charging over 1%, Battery Service Recommended' issue?
Last edited: