Recently updated to macOS Monterey, Waking up by the screen in the middle of the nightclub,It feels weird,Have been before,But the screen will only light up when there is a notification,Now I light it up without any reason,The hardware is still that hardware,Then it should be the software's pot。
Checked it online,First I found Apple's official tutorial:https://support.apple.com/zh-cn/guide/mac-help/mchlp2995/mac
Very detailed,But obviously it is of no use...
So continue to dig,Really found the reason,Use the command pmset -g log | grep DarkWake You can see,During your sleep,Your Mac is not resting...
1 2 3 4 5 6 7 8 |
2021-11-09 01:21:32 +1000 DarkWake DarkWake from Deep Idle [CDN] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using AC (Charge:100%) 0 secs 2021-11-09 01:21:32 +1000 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%) 2021-11-09 02:00:44 +1000 DarkWake DarkWake from Deep Idle [CDN] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using AC (Charge:100%) 0 secs 2021-11-09 02:00:44 +1000 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%) 2021-11-09 03:14:07 +1000 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using AC (Charge:100%) 0 secs 2021-11-09 03:14:07 +1000 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%) 2021-11-09 03:53:30 +1000 DarkWake DarkWake from Deep Idle [CDN] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using AC (Charge:100%) 1 secs 2021-11-09 03:53:31 +1000 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%) |
Look at the output,These are more typical,Mostly like this,A DarkWake, A wake, Two are just connected,Then the problem arises, DarkWake wakes up the computer in the background to update data,But somehow,Peripheral is triggered,Which led to a global wakeup。
One of my laptop loses power by 10% overnight。
Anyway,I don't want this feature, Just that PowerNap,to me,I hope it can save me more power,So there are probably so many solutions:Turn off network access to wake up,Turn off PowerNap... but here comes the problem,On m1 device,In fact, there is no PowerNap option... (obviously,Apple is confident in its battery life,But they ignore the power of bugs)
So for the function of PowerNap,We can only start from the command line,First use pmset -g Command to view current status,turn up powernap Value,if not 0 ,Description is enabled,Use the command sudo pmset -a powernap 0 Turn it off。
Simultaneously,There is another one tcpkeepalive ,This should not be the default 0 ,Also turn off,It determines whether your rmbp should keep tcp connection during sleep-obviously,If you keep it, you need to wake up regularly to connect to the Internet... sudo pmset -a tcpkeepalive 0 ,Executing this command will cause the terminal to prompt:
1 |
Warning: This option disables TCP Keep Alive mechanism when sytem is sleeping. This will result in some critical features like 'Find My Mac' not to function properly. |
Probably it means that some functions will be restricted if it is turned off,In fact, the system function cannot be connected to the Internet when it sleeps.,I believe someone stole your Mac,It doesn't even connect to the internet。
Anyway,Two commands down,The problem should be solved,But in the information I'm looking for,Another one is "Turn off optimized power charging",Just the "Optimized battery charging",But I’m not sure if this will also cause awakening,And the old one before me 15 The inch is indeed bulging with two batteries,I decided to try driving it first,If it still wakes up,Turn it off again。
Anyway,that's it,If you read this article I didn’t come to update,That shows that the above scheme is effective :)
References:
- https://discussions.apple.com/thread/252061187
- https://apple.stackexchange.com/questions/253776/macbook-pro-13-with-retina-display-consumes-10-battery-overnight-with-the-lid-c
- https://discussions.apple.com/thread/252276065
Original article written by LogStudio:R0uter's Blog » After upgrading macOS Monterey, the device wakes up frequently in the middle of the night after sleeping
Reproduced Please keep the source and description link:https://www.logcg.com/archives/3528.html
too strong,Thanks for the tutorial sir,I encountered the lock screen,Click on the cross below,The screen cannot be blacked out immediately. Instead, the screen will turn black after a short period of time.,This tutorial is awesome! ! !
Thanks R0uter for the fast reply.
Yeah, I also was searching for very long time for a fix but nothing really helped out.
Mostly I also have it on the cable and when I know I don´t use it the next few hours I shut it down to save my battery.
Maybe someday a fix from Apple will come but I´m not really sure because I had this issue also under MacOS 12
Thank you anyway 🙂
HEY Router,
it doesn´t worked for me.
I use the current MacOS Version 13.3.1
My PMSet are:
System-wide power settings:
SleepDisabled 0
Currently in use:
standby 1
Sleep On Power Button 1
SleepServices 0
hibernatefile /var/vm/sleepimage
powernap 0
networkoversleep 0
disksleep 10
sleep 1 (sleep prevented by powerd)
hibernatemode 3
ttyskeepawake 0
displaysleep 2
tcpkeepalive 0
lowpowermode 1
womp 0
Overnight I lose around 10% of battery. 🙁
No external devices are connected.
When I use the command: “pmset -g log | grep DarkWake”
I got this answer from the terminal:
2023-04-15 23:02:22 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:81%) 45 secs
2023-04-16 00:31:57 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:79%) 45 secs
2023-04-16 02:07:36 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:77%) 45 secs
2023-04-16 03:13:31 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/Maintenance Using BATT (Charge:75%) 45 secs
2023-04-16 04:48:44 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:75%) 45 secs
2023-04-16 06:24:12 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:73%) 45 secs
2023-04-16 07:59:21 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:71%) 45 secs
2023-04-16 09:34:34 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:70%) 45 secs
Maybe you can help me? 🙂
Kind regards
Thomas
Sry man, I ve done some research for you but no luck. This one
due to AOP.OutboxNotEmpty
looks like persist. Some ppl work, but some don’t, really have no idea.For me, now I m using m1 mac so even it still eating my battery, it lasts long enough and now I m more plug it in as a desktop tho 😆
Sry not helping….