Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

A1MB1G

macrumors 6502
May 13, 2020
290
99
Run this command
Code:
pmset -g log | grep -i "wake from"
in terminal and show us the result here
Happened again overnight last night. Tried turning on my laptop this morning and no power, 0% and full battery drain. I've tried resetting everything, still same issue. Here's the output from the above command you suggested:

2020-10-23 08:01:19 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:86%) 2274 secs

2020-10-23 08:51:29 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.PowerButton/User Using BATT (Charge:77%)

2020-10-23 11:52:59 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:100%) 45 secs

2020-10-23 12:25:41 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:100%) 49 secs

2020-10-23 12:26:30 -0400 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%) 930 secs

2020-10-23 12:42:59 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:100%) 45 secs

2020-10-23 13:23:41 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:100%) 1821 secs

2020-10-23 13:54:02 -0400 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%) 603 secs

2020-10-23 14:04:12 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:100%) 11 secs

2020-10-23 16:33:55 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:100%) 2327 secs

2020-10-23 18:07:58 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:90%) 2927 secs

2020-10-23 19:16:39 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.LidClose/Maintenance Using BATT (Charge:76%) 10 secs

2020-10-23 20:57:15 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.SleepTimer/SleepTimer Using BATT (Charge:76%) 0 secs

2020-10-23 20:58:12 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.SleepTimer/HibernateError Using BATT (Charge:76%) 12 secs

2020-10-24 06:57:55 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.RTC/Maintenance Using BATT (Charge:76%) 16 secs

2020-10-24 07:00:09 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.RTC/SleepService Using BATT (Charge:74%) 0 secs

2020-10-24 08:13:10 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/UserActivity Assertion Using BATT (Charge:73%) 3986 secs

2020-10-24 09:26:03 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.PowerButton/User Using BATT (Charge:55%)

2020-10-24 10:51:13 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.KeyboardTouchpad/User Using BATT (Charge:39%) 2784 secs

2020-10-24 13:19:49 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:24%) 25 secs

2020-10-24 13:21:04 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:22%) 142 secs

2020-10-24 13:58:22 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.KeyboardTouchpad/User Using BATT (Charge:22%) 2065 secs

2020-10-24 14:32:54 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:59%) 45 secs

2020-10-24 15:13:26 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:95%) 4252 secs

2020-10-24 16:24:26 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:100%) 45 secs

2020-10-24 17:04:26 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:100%) 9856 secs

2020-10-24 19:48:49 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/UserActivity Assertion Using BATT (Charge:100%)

2020-10-24 20:23:50 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:91%) 10 secs

2020-10-24 22:23:53 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.SleepTimer/SleepTimer Using BATT (Charge:90%) 0 secs

2020-10-25 06:30:06 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.RTC/SleepService Using BATT (Charge:88%) 3 secs

2020-10-25 08:24:50 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.RTC/Maintenance Using BATT (Charge:87%) 10 secs

2020-10-25 09:30:03 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:87%) 2537 secs

2020-10-25 12:54:17 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:74%) 2238 secs

2020-10-25 13:31:43 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:64%) 15 secs

2020-10-25 16:02:50 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:63%) 1080 secs

2020-10-25 16:21:06 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:56%) 12 secs

2020-10-25 17:07:21 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/UserActivity Assertion Using BATT (Charge:55%) 1878 secs

2020-10-25 19:15:07 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.SleepTimer/SleepTimer Using BATT (Charge:46%) 0 secs

2020-10-25 19:16:18 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.SleepTimer/HibernateError Using BATT (Charge:46%) 11 secs

2020-10-25 23:45:02 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.RTC/Alarm Using BATT (Charge:44%) 15 secs

2020-10-25 23:45:24 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:44%) 15 secs

2020-10-26 02:45:26 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.SleepTimer/SleepTimer Using BATT (Charge:43%) 0 secs

2020-10-26 08:00:09 -0400 Wake Wake from Standby [CDNVA] : due to EC.RTC/Alarm Using BATT (Charge:42%) 31 secs

2020-10-26 08:00:47 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:42%) 10 secs

2020-10-26 08:58:35 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:42%)

2020-10-26 15:42:44 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.Bluetooth/Maintenance Using BATT (Charge:100%) 42 secs

2020-10-26 16:24:28 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:100%) 5347 secs

2020-10-26 18:01:25 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.LidClose/Maintenance Using BATT (Charge:82%) 15 secs

2020-10-26 18:09:35 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:81%) 1237 secs

2020-10-26 19:57:42 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:73%)

2020-10-26 21:06:17 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:43%) 45 secs

2020-10-26 21:43:52 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:86%) 9355 secs

2020-10-27 00:19:47 -0400 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%)

2020-10-27 00:39:12 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:100%) 66 secs

2020-10-27 01:13:45 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:100%) 3836 secs

2020-10-27 02:57:01 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:100%) 3770 secs

2020-10-27 04:00:03 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:100%) 45 secs

2020-10-27 04:39:34 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:100%) 4722 secs

2020-10-27 07:58:22 -0400 DarkWake DarkWake from Deep Idle [CDNPB] : due to EC.RTC/Maintenance Using AC (Charge:100%) 97 secs

2020-10-27 07:59:59 -0400 Wake DarkWake to FullWake from Deep Idle [CDNVA] : due to HID Activity Using AC (Charge:100%)

2020-10-27 08:17:45 -0400 DarkWake DarkWake from Deep Idle [CDNP] : due to EC.ARPT/Maintenance Using AC (Charge:100%) 45 secs

2020-10-27 08:21:13 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.USBC/Maintenance Using BATT (Charge:100%) 45 secs

2020-10-27 08:53:34 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:100%)

2020-10-27 15:39:45 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.Bluetooth/Maintenance Using BATT (Charge:100%) 45 secs

2020-10-27 16:36:31 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:100%) 1063 secs

2020-10-27 17:25:02 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:98%) 995 secs

2020-10-27 20:00:06 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.SleepTimer/SleepTimer Using BATT (Charge:93%) 0 secs

2020-10-28 05:42:47 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.RTC/Maintenance Using BATT (Charge:93%) 16 secs

2020-10-28 07:30:09 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.RTC/SleepService Using BATT (Charge:91%) 0 secs

2020-10-28 08:00:01 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.RTC/Alarm Using BATT (Charge:91%) 30 secs

2020-10-28 08:56:03 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.RTC TDM0 TDM1 XHC1/Notification Using AC (Charge:85%)

2020-10-28 16:01:45 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.RTC/HID Activity Using BATT (Charge:91%) 1556 secs

2020-10-28 16:34:09 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:82%) 1540 secs

2020-10-28 17:20:59 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:71%)

2020-10-28 21:39:36 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:51%) 80 secs

2020-10-28 23:41:02 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.SleepTimer/SleepTimer Using BATT (Charge:50%) 0 secs

2020-10-29 07:30:05 -0400 DarkWake DarkWake from Standby [CDN] : due to EC.RTC/SleepService Using BATT (Charge:49%) 2 secs

2020-10-29 08:00:01 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.RTC/Alarm Using BATT (Charge:48%) 30 secs

2020-10-29 08:01:21 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:49%) 7 secs

2020-10-29 08:56:47 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:49%)

2020-10-29 15:24:00 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.Bluetooth/Maintenance Using BATT (Charge:100%) 46 secs

2020-10-29 15:49:32 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:100%)
 

A1MB1G

macrumors 6502
May 13, 2020
290
99
Have you tried this:
Code:
sudo pmset -b tcpkeepalive 0
?
I have tried that command, didn't seem to help resolve the issue. I'm starting to wonder whether my laptop isn't going to sleep because of the Kuzy cloth I use over the keys when closing the lid. As far as i know, it the screen shuts off when i close the lid but I'm going to try the next few days without the cloth just to see.
 

Henriiiii

macrumors newbie
Mar 29, 2020
9
2
I think I’m suffering the same. Found a lot of way on google and none of that works, even brought it to the apple Genius Bar they couldn’t tell what the problem is. Saw some threads said it’s a bug since Mojave. So I think all we can do now is to hope apple solve it on the next MacOS upgrade.
 

A1MB1G

macrumors 6502
May 13, 2020
290
99
So I shut my laptop closed today at 2:07PM left it in my bag. Came back to it at 6:36PM to see that 28% of my battery had drained down from 100% to 72%. Here's what was in the log. Hoping someone can direct me to what might be the issue:

2020-11-04 14:07:49 -0500 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:100%) 16097 secs

2020-11-04 14:07:54 -0500 Wake Requests [*process=powerd request=TCPKATurnOff deltaSecs=43255 wakeAt=2020-11-05 02:08:49] [process=powerd request=UserWake deltaSecs=64325 wakeAt=2020-11-05 08:00:00 info="com.apple.alarm.user-visible-com.apple.remindd.time-alarm,375"]

2020-11-04 14:07:54 -0500 PM Client Acks Delays to Sleep notifications: [com.apple.apsd is slow(2981 ms)] [mDNSResponder is slow(5006 ms)]

2020-11-04 18:36:05 -0500 Kernel Client Acks Delays to Sleep notifications: [AppleIntelFramebuffer driver is slow(msg: SetState to 1)(1417 ms)] [powerd is slow(5013 ms)] [AppleUSBVHCIBCE driver is slow(msg: SetState to 1)(320 ms)] [IOBluetoothHostControllerUARTTransport driver is slow(msg: SetState to 0)(448 ms)] [AppleIntelFramebuffer driver is slow(msg: SetState to 0)(544 ms)] [RP01 driver is slow(msg: SetState to 0)(1008 ms)]

2020-11-04 18:36:06 -0500 Wake Wake from Deep Idle [CDNVA] : due to EC.LidOpen/Lid Open Using BATT (Charge:72%)
 

A1MB1G

macrumors 6502
May 13, 2020
290
99
I'm starting to get really annoyed with this problem. Last night I made sure to close all open apps, closed the lid with 89% battery remaining. Opened the lid today at 1:40PM and only had 6% battery life left. Here's a snippet from the log:

2020-11-06 22:16:18 -0500 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:89%) 55481 secs
2020-11-06 22:16:23 -0500 Wake Requests [*process=powerd request=TCPKATurnOff deltaSecs=43255 wakeAt=2020-11-07 10:17:18] [process=powerd request=UserWake deltaSecs=207816 wakeAt=2020-11-09 08:00:00 info="com.apple.alarm.user-visible-com.apple.remindd.time-alarm,406"]
2020-11-06 22:16:23 -0500 PM Client Acks Delays to Sleep notifications: [com.apple.apsd is slow(2965 ms)] [mDNSResponder is slow(5006 ms)]
2020-11-07 13:40:58 -0500 Kernel Client Acks Delays to Sleep notifications: [AppleIntelFramebuffer driver is slow(msg: SetState to 1)(1298 ms)] [powerd is slow(5013 ms)] [AppleHPMIECS driver is slow(msg: WillChangeState to 2)(302 ms)] [AppleHPMIECS driver is slow(msg: WillChangeState to 2)(302 ms)] [AppleUSBVHCIBCE driver is slow(msg: SetState to 1)(315 ms)] [AppleIntelFramebuffer driver is slow(msg: SetState to 0)(548 ms)] [RP01 driver is slow(msg: SetStat

I'm now contacting tech support as this should not be happening on a new 2020 Macbook Pro. If anyone has any other suggestions, please let me know.

Thanks
 

brianmowrey

macrumors 6502
Oct 5, 2020
419
133
I'm now contacting tech support as this should not be happening on a new 2020 Macbook Pro. If anyone has any other suggestions, please let me know.
Letting Support do their job is the best bet.

Still, I'm surprised you seem not to have looked at what your pmsets actually are? Maybe your standby delay has been set to a crazy high amount. It's pmset -g to show.

Screen Shot 2020-11-05 at 16.53.23.png
 

A1MB1G

macrumors 6502
May 13, 2020
290
99
Letting Support do their job is the best bet.

Still, I'm surprised you seem not to have looked at what your pmsets actually are? Maybe your standby delay has been set to a crazy high amount. It's pmset -g to show.

View attachment 1490870
Mine is currently set to the following (how do I change it - don't think I saw the command in this thread to adjust the delay?)


Currently in use:

standbydelaylow 10800
standby 1
halfdim 1
hibernatefile /var/vm/sleepimage
proximitywake 0
powernap 0
gpuswitch 2
disksleep 10
standbydelayhigh 86400
sleep 1 (sleep prevented by sharingd)
hibernatemode 3
ttyskeepawake 1
displaysleep 2
tcpkeepalive 1
highstandbythreshold 50
acwake 0
lidwake 1



Any ideas/suggestions?
 

brianmowrey

macrumors 6502
Oct 5, 2020
419
133
Mine is currently set to the following (how do I change it - don't think I saw the command in this thread to adjust the delay?)



Any ideas/suggestions?
Yeah, those are weird!

The Restore Defaults button in syspref > Energy Saver should fix them all.

hibernatemode is usually 25 (which powers off RAM) for a retina MBP. So that's one reason you have the same fast sleep drain issue as a lot of pre-retina MBPs which default to hibernatemode 3.

Second is your standbydelays. Standby refers to beginning whatever your "hibernatemode" is. Your standbydelayhigh is 24 hours. So until you hit 50% your MBP is basically at regular, high-powered sleep. Standbydelaylow takes over once the battery gets below 50%. Your standbydelaylow is 3 hours.

So the combo of not even going into standby until the lid has been closed for 3 hours and then keeping the RAM powered on is draining battery.
 

tommiy

macrumors 6502
Dec 11, 2015
412
127
Interesting discussion. I just looked at my 2017 MBP and the figures are the same as @A1MB1G has quoted. My Standbydelayhigh is 86400 and I have never changed it myself. Interesting to see if resetting changes it. I'm not game to touch anything on my machine while using it for work in this environment.

I just checked my 2013 Mac Air and it only has one sleep setting of 10800. It battery drain is like 5% in a week while asleep.
 

A1MB1G

macrumors 6502
May 13, 2020
290
99
Yeah, those are weird!

The Restore Defaults button in syspref > Energy Saver should fix them all.

hibernatemode is usually 25 (which powers off RAM) for a retina MBP. So that's one reason you have the same fast sleep drain issue as a lot of pre-retina MBPs which default to hibernatemode 3.

Second is your standbydelays. Standby refers to beginning whatever your "hibernatemode" is. Your standbydelayhigh is 24 hours. So until you hit 50% your MBP is basically at regular, high-powered sleep. Standbydelaylow takes over once the battery gets below 50%. Your standbydelaylow is 3 hours.

So the combo of not even going into standby until the lid has been closed for 3 hours and then keeping the RAM powered on is draining battery.
Thanks for the details. I reset the energy saving settings and when I checked pmset -g command, it reverted back to 86400 for standbydelayhigh and 10800 for standbydelay low. I've now changed them both to 3600.

With respect to the Hibernate Mode, I noticed you have your's set to 3 instead of 25. Should I change mine to 25 instead?
 

tommiy

macrumors 6502
Dec 11, 2015
412
127
Here is a good explanation of the settings.

hibernatemode is set to 0 for plain sleep (desktops), 3 to store a copy of memory to disk and keep memory powered up (laptops), or 25 for full hibernation in which memory is powered down too.

Further down the Q&A there is this response that explains the hibernate options and that 3 is normal and 25 can only be set by pmset.
 
Last edited:

tommiy

macrumors 6502
Dec 11, 2015
412
127
I'm guessing that the 86400 for standbydelayhigh is so that the laptop wakes extremely fast when within the time period. It does seem that many come as default of this. My reset option in energy saver is greyed out and yet my setting is the same. Typically my MBP in this mode will use 15-20% of the battery in 24hrs. As compared to my Air which has one sleep setting at 10800. I'd suspect changing the settings and making it hibernate earlier will fix the use providing there is nothing continuously waking it up.
 

tommiy

macrumors 6502
Dec 11, 2015
412
127
Just checked my mbp setting and 'man pmset' is basically what is in the electriclight article. The man page also states that hibernate 25 is only set by pmset and not else where. There are references to european countries so perhaps the defaults could be linked to the country settings as well? I'm just guessing there but would seem to make sense.
 

brianmowrey

macrumors 6502
Oct 5, 2020
419
133
Just checked my mbp setting and 'man pmset' is basically what is in the electriclight article. The man page also states that hibernate 25 is only set by pmset and not else where. There are references to european countries so perhaps the defaults could be linked to the country settings as well? I'm just guessing there but would seem to make sense.
Right, it's a big mess. The pmset man has clearly been updated since 2012 since it refers to standbydelayhigh, but, it's just obvious that the language about hibernatemode 25 is eight years old. hibernatemode 25, aka "standby" (as in the Mac OS X feature) was the default for everything referred to in the Apple kb up to 2017.

*edit: I'm now officially confused about whether hibernatemode 3 is post-2013 standby! I've found other articles calling standby and safe sleep the same thing. Which, if ithey are, means pmset doesn't allow us to customize whether RAM stays powered on in any coherent way and there's no way to discern what the default "safe sleep" attitude to RAM is between models...
 
Last edited:

brianmowrey

macrumors 6502
Oct 5, 2020
419
133
With respect to the Hibernate Mode, I noticed you have your's set to 3 instead of 25. Should I change mine to 25 instead?
I would see how well your battery holds up with just the standbydelay timer change first...
 
Last edited:

tommiy

macrumors 6502
Dec 11, 2015
412
127
Yeah it is just a mess. I'll wait until on on holidays to play around. Given all the issues with Catalina i replaced my Mac as the daily driver with a XPS13 just recently rather than retaining an apple. It been much better than the MBP in regards to speed and reliability and sleeps and wakes up reliable. My MBP randomly kernel panics on wake from sleep even after the logic board has been replaced. So overall, the only issue that i have with the battery usage now is to remember to charge the thing every few days or simply shut it down completely.
 

brianmowrey

macrumors 6502
Oct 5, 2020
419
133
My MBP randomly kernel panics on wake from sleep even after the logic board has been replaced. So overall, the only issue that i have with the battery usage now is to remember to charge the thing every few days or simply shut it down completely.
Right, and I wouldn't be surprised if Catalina changed your machine's pmsets OR the SMC behavior that those pmsets refer to as a short-term for just such a stability issue that Apple doesn't want to document for us.

I went back to look at pmset man in High Sierra, which is before the edits to add standbydelayhigh. The language for hibernatemode 3 is the same: will power memory during sleep.

However, it's possible that pmset "standby" simply sidesteps 3 on all machines (ie retina MBP) that support the Mac OS X feature "standby", in which case hibernate mode is a half-useless value in those machines, and all I can know for sure is what my Mac does!
 
Last edited:

tommiy

macrumors 6502
Dec 11, 2015
412
127
It is interesting. I'll try changing my settings and see what makes a difference. As I said its no longer a daily driver due to Catalina so no real impact on my work I guess if things do not work out.
 
  • Like
Reactions: brianmowrey

tommiy

macrumors 6502
Dec 11, 2015
412
127
I changed by high and low timeouts to 7200 last night. It lost 4% of battery in 7.5hrs of sleep. Hibernate is still set to 3. I'm not sure if this is better or worse. The initial feeling is that it is alot better but I will try tracking a few nights then return to normal and see what happens.
 

A1MB1G

macrumors 6502
May 13, 2020
290
99
I made two changes. Adjusted the timeouts for both to 3600, kept hibernate mode at 3 but also changed HyperAdvisor on my Parallels Desktop VM to "Apple" and so far it's been 2-3 days with the laptop properly going into hibernation mode and virtually no battery drain when waking from hibernation.
 

A1MB1G

macrumors 6502
May 13, 2020
290
99
@A1MB1G can you provide your settings from pmset? I thought a 4% drop in 7.5hrs was ok.
My settings are as follows:


Currently in use:

standbydelaylow 3600
standby 1
halfdim 1
hibernatefile /var/vm/sleepimage
proximitywake 0
gpuswitch 2
powernap 0
disksleep 10
standbydelayhigh 3600
sleep 1
hibernatemode 3
ttyskeepawake 1
displaysleep 2
tcpkeepalive 1
highstandbythreshold 50
acwake 0
lidwake 1
 
  • Like
Reactions: tommiy

brianmowrey

macrumors 6502
Oct 5, 2020
419
133
I made two changes. Adjusted the timeouts for both to 3600, kept hibernate mode at 3 but also changed HyperAdvisor on my Parallels Desktop VM to "Apple" and so far it's been 2-3 days with the laptop properly going into hibernation mode and virtually no battery drain when waking from hibernation.
That's super. I'm glad the standbydelay change was helpful even if my conceptions of pmset defaults were three years out of date, haha
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.