macOS Monterey 12.3 Beta 2 Appears to Fix Bluetooth-Related Battery Drain Issue During Sleep Mode

[JippaLippa]

I'm using monterey on my M1 Mac Mini, but it still doesn't feel completely usable (without frustration that is).
Hopefully 12.3 will be ready by the 8th, when I'll get a Mac Mini PRO.

 

[Wokis]

Agreed with the notion that this needs to go into a fast release hotfix, not some March/April feature patch.

 

[RoelJuun]

I’m still having lots of issues with external displays, docks and Time Machine. Hope this release might fix some of it…

 

[Alwis]

Either that, or Apple ignores the feedback.

In the past I have reported so many bugs to Apple, I can not even count them. Only once I got feedback to clarify the issue. In all other cases nothing and most of the bugs are still present, even years after reporting them. So I tend to "Apple ignores feedback", at least feedback concerning software (the new MacBooks show, that they listened to some of the Feedback regarding their hardware).

I noticed this bug the first time I woke my iMac after updating the OS. Usually it takes a short moment to switch on the screen after hitting the key on the keyboard. In this case it was switched on instantaneously. As Apple has a long history with sleep related bugs a looked into the log files and it was obvious.

Every Developer at Apple using bluetooth devices should have been able to find this bug even without doing some serious testing, absolutely unbelievable, that this got shipped.

And yes, software got more complex in the past 10 years. But we are talking about a company with a profit of tens of billions, they should be able to implement some serious testing during software development.

The times of "it just works" are long gone.

 

[Tyler O'Bannon]

They need to fix this now. This has been a problem. I don’t know why they don’t release a quick 12.2.1. Update to fix this.

 

[pshufd]

They need to fix this now. This has been a problem. I don’t know why they don’t release a quick 12.2.1. Update to fix this.

The software development process isn't that great for single fixes. You have a development line and releases fork off of that. If you make multiple forks, you have to apply the fix to all of the lines and also test them all. So instead you have the mainline and you fork a release and then you apply changes to the release and mainline along with the accompanying testing.

 

[creativesmith]

The software development process isn't that great for single fixes. You have a development line and releases fork off of that. If you make multiple forks, you have to apply the fix to all of the lines and also test them all. So instead you have the mainline and you fork a release and then you apply changes to the release and mainline along with the accompanying testing.

Yes, the process. But someday, if Apple becomes a big company with lots of employees and buckets of cash, maybe then they'll— nah.

 

[pshufd]

Yes, the process. But someday, if Apple becomes a big company with lots of employees and buckets of cash, maybe then they'll— nah.

Engineers really don't like to do one backport much less two. I worked for a company with more software engineers than Apple and there are just a bunch of process tasks that are unpleasant to do, especially in the context where you don't get any rewards for doing so.

 

[creativesmith]

Engineers really don't like to do one backport much less two. I worked for a company with more software engineers than Apple and there are just a bunch of process tasks that are unpleasant to do, especially in the context where you don't get any rewards for doing so.

Good point. Those who efficiently, thoroughly and passionately push through those tasks should be rewarded.

 

[dwsolberg]

This should be fixed in a 12.2.1 update. It's silly to leave a bug like this for what will likely be a month or two for 12.3.

 

[jimmysofat6864]

I've been having this problem since Big Sur I was wondering why nobody brought it up. Also, does this also fix the Wi-Fi battery drain as well because I'm pretty sure it was a combination of Wi-Fi and Bluetooth that drained the battery.

 

[aleksdj]

Monterrey 12.2.1 didn't resolve any problem about battery draining at all, I totally lost my battery to 0% after 3 days with the macbook m1 pro slept and with the lid closed...

Hundreds of darkwake ups:

2022-03-12 17:13:13 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 45 secs
2022-03-12 17:13:58 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:14:00 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 20 secs
2022-03-12 17:14:20 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:14:22 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 27 secs
2022-03-12 17:14:49 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 3 secs
2022-03-12 17:14:52 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 29 secs
2022-03-12 17:15:21 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:15:23 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 45 secs
2022-03-12 17:16:08 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:16:10 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 45 secs
2022-03-12 17:16:55 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:16:57 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 23 secs
2022-03-12 17:17:20 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:17:22 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 30 secs
2022-03-12 17:17:52 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:17:54 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 8 secs
2022-03-12 17:18:02 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:18:04 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 16 secs
2022-03-12 17:18:20 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:18:22 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 28 secs
2022-03-12 17:18:50 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:18:52 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 10 secs
2022-03-12 17:19:02 +0100 Sleep                   Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:22%) 2 secs
2022-03-12 17:19:04 +0100 DarkWake                DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:22%) 9 secs
2022-03-12 17:19:13 +0100 Wake                    DarkWake to FullWake from Deep Idle [CDNVA] : due to UserActivity Assertion Using BATT (Charge:22%)

I'm pretty tired of this problem, I JUST REALLY WANT TO BE ABLE TO SLEEP MY PORTABLE WITHOUT ANY POSSIBILITY OF WAKES OR DARKWAKES OTHER THAN A MANUAL USER INTERACTION!!

 

[Alwis]

For me it fixed the bluetooth issue. But a week or so ago the „Dark wake“ issue started again in the middle of the night. I could not figure out the reason but a reboot solved it.

Just the way Apple software currently is.

 

[jimmysofat6864]

I thought going to 12.2.1 fixed it but then I left my Mac in sleep for another day and the battery drained again. I tried going back to Big Sur and even Catalina but still same issue. Hopefully 12.3 fixes this once and for all. Tested on 2015 MBP 13.

 

[pshufd]

I thought going to 12.2.1 fixed it but then I left my Mac in sleep for another day and the battery drained again. I tried going back to Big Sur and even Catalina but still same issue. Hopefully 12.3 fixes this once and for all. Tested on 2015 MBP 13.

I've found some Monterey bugs backported to Big Sur. Sometimes you can't escape unless you go back to older versions before the updates.

 

[jimmysofat6864]

I've found some Monterey bugs backported to Big Sur. Sometimes you can't escape unless you go back to older versions before the updates.

I even tried it on Catalina and last time I remembered it wasn’t affected so I have no idea how far back I should go. The odd thing is that it seems to only affect my 13 inch mbp 2015 and air 2015. My 2015 15 mpb on Big Sur doesn’t seem to have this issue or at least to this extent.

 

[pshufd]

I even tried it on Catalina and last time I remembered it wasn’t affected so I have no idea how far back I should go. The odd thing is that it seems to only affect my 13 inch mbp 2015 and air 2015. My 2015 15 mpb on Big Sur doesn’t seem to have this issue or at least to this extent.

Might be a firmware update then. I don't know how to undo those.