Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have tried all of that. I gave up. I literally tried everything - clean install, hibernation modes, new battery, etc. I literally lose 20% overnight. If I didn't charge it, then it would be dead in a day and a half or so.

I give up. I guess it's just an old machine and maybe Apple didn't build the tools for this model year into High Sierra to make it really go to sleep. That's all I can think of.

Please keep me posted if you find a solution.

I know it's not a direct comparison, but for the sake of discussion, my '18 13" MBP loses 1-2% of battery during 8-9 hours of sleep. That's with Power Nap and 'Wake for network access' turned on. I really hope you find a solution as that must be mega frustrating!
 
I know it's not a direct comparison, but for the sake of discussion, my '18 13" MBP loses 1-2% of battery during 8-9 hours of sleep. That's with Power Nap and 'Wake for network access' turned on. I really hope you find a solution as that must be mega frustrating!

That's actually pretty normal. I would take that.
 
open terminal and type the following and restart

sudo pmset -a autopoweroffdelay 30
sudo pmset -a standbydelay 15


this forces MacOS to go into hibernation mode after sleeping for 30secs (default was 8hrs, thx apple)

hibernation mode setting (0,3,25) makes no difference but it was set to 3 (default) in my case.

used to lose ~30% of battery per 8hrs on a '12 15" rMBP with brand-new battery running sierra (should do the trick on newer OS's)

now it just hibernates and loses nothing, you know it's hibernating if it takes 2 extra secs before powering on.

just make sure standby and autopoweroff are enabled (which they are by default)

one caveat: if account is pw-protected and you wake up os by pressing a key for example, be sure to enter the pw and log in before putting the computer to sleep again, as not logging in and pressing esc for example causes it to just sleep without hibernating for some reason, at least that's what happens in my case

my power settings below for what's worth

__

System Power Settings:

AC Power:
System Sleep Timer (Minutes): 180
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 180
Wake on AC Change: No
Wake on Clamshell Open: Yes
Wake on LAN: No
AutoPowerOff Delay: 30
AutoPowerOff Enabled: 1

Current Power Source: Yes
DarkWakeBackgroundTasks: 0
Display Sleep Uses Dim: Yes
GPUSwitch: 2
Hibernate Mode: 3
PrioritizeNetworkReachabilityOverSleep: 0
Standby Delay: 15
Standby Enabled: 1


Battery Power:
System Sleep Timer (Minutes): 60
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 15
Wake on AC Change: No
Wake on Clamshell Open: Yes
AutoPowerOff Delay: 30
AutoPowerOff Enabled: 1

DarkWakeBackgroundTasks: 0
Display Sleep Uses Dim: Yes
GPUSwitch: 2
Hibernate Mode: 3
Reduce Brightness: No
Standby Delay: 15
Standby Enabled: 1
 
Hello Guys, same issue here on MBP 2017.

Reset SMC, went to Safe Mode, disabled all options wake on BT, disabled notifications in Sleep mode, power nap disabled on battery,



System-wide power settings:

Currently in use:

standbydelay 10800

standby 1

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 0

gpuswitch 2

disksleep 10

sleep 1 (sleep prevented by sharingd)

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 1

ttyskeepawake 1

displaysleep 2

tcpkeepalive 0

acwake 0

lidwake 1

Set tcpkeepalive to 0.

Logs during sleep mode from today's night:
Sep 9 02:09:34 MBP syslogd[39]: ASL Sender Statistics

Sep 9 02:09:34 MBP com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Sep 9 06:54:33 --- last message repeated 1 time ---
Sep 9 06:54:33 MBP syslogd[39]: ASL Sender Statistics
Sep 9 06:54:33 MBP CleanMyMac X HealthMonitor[371]: objc[371]: __NSFrozenArrayM object 0x7fdaa0f45140 overreleased while already deallocating; break on objc_overrelease_during_dealloc_error to debug
Sep 9 06:54:34 MacBook-Pro-Jakub awdd[143]: Diagnostics Report
Sep 9 06:54:34 MBP com.apple.xpc.launchd[1] (com.apple.bsd.dirhelper[1245]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.bsd.dirhelper

Do you have any solution? Is above thing safe to restore?
 
Last edited:
You may have already checked. My 2 cents!

https://support.apple.com/en-us/HT201464#energy

Clear history and let it run overnight. Then see who is using Energy - it will show processes with energy impact. But importantly processes that prevent sleep. Culprit application should be in the list. If this doesn't work, check which application is in top 5 consuming CPU / Network / Disk and go from there.

One thing I observed in your earlier post, that you are using beta profile and running on beta? I never used that, but is this something to look into?
 
I am using version of official system. Today I left my MBP for 4 hours with 15% charged, opened and there was still 15% :)

I switched tcpkeepalive to 0 in pm for all, but what I have seen that once I open a lid there is always WIFI connected and on logon screen some notifications appears. It is normal when this option is set to 0

UPDATE: After this change all looks better. I left my MacBook Pro at 0:00 AM with 67% and after when I opened it at the morning it has 64%. Only 3% drain on battery.


I. Enable do not disturb mode in Sleep mode
II. Ser tcpkeepalive parameter to 0
 
Last edited:
Found this thread 4 days back and facing this problem since I purchased new 2018mbp.
When every other solution was looks like I already tried and submitted once to Apple care and they returned it with usual all is well report and reinstalled the Mac OS. Which did helped until i started using iCloud.
There is one comment above related to shutting off “findmymac” feature with some terminal command so it will deactivated it while laptop is in sleep. I am yet to try that command but simply turning “findmymac” off in icloud setting worked for me. Now there is almost no power drop. 1-2% is normal but it used to be around 80-90%. I recommend to try this. May be Apple fix it in future updates.
 
I have find my Mac disabled. Today 6% battery lost in sleep mode during night...not bad, but yesterday was better.

You mean 1-2% by night?
 
That's actually pretty normal. I would take that.
Just curious @LarryJoe33, I couldn’t see anywhere that you listed which MacBook Pro this issue is occurring on? I have a 2017 MBP wTB, and it consistently loses 5-10% battery every night in sleep mode. I was just curious if you have one of the newer models, or an older gen model?

Ok all my older gen MacBook pros I’ve had, I usually only lost 1-3 percent battery overnight, so to me it’s a bit irritating that the battery drains so much.
 
  • Like
Reactions: BigMcGuire
Just curious @LarryJoe33, I couldn’t see anywhere that you listed which MacBook Pro this issue is occurring on? I have a 2017 MBP wTB, and it consistently loses 5-10% battery every night in sleep mode. I was just curious if you have one of the newer models, or an older gen model?

Ok all my older gen MacBook pros I’ve had, I usually only lost 1-3 percent battery overnight, so to me it’s a bit irritating that the battery drains so much.
I have a late 2011 13" MBP. It's a classic at this point. It runs really well with the upgrades I have done, but the battery will literally deplete from 100% to 0% in 24 hours. Overnight I lose 30%. I gave up. I have tried everything including a clean install.
 
  • Like
Reactions: Painter2002
LarryJoe wrote:
"It runs really well with the upgrades I have done, but the battery will literally deplete from 100% to 0% in 24 hours. Overnight I lose 30%. I gave up. I have tried everything including a clean install."

So... what is "your solution"?
How are you handling it now, to prevent "the drain" ....?
 
LarryJoe wrote:
"It runs really well with the upgrades I have done, but the battery will literally deplete from 100% to 0% in 24 hours. Overnight I lose 30%. I gave up. I have tried everything including a clean install."

So... what is "your solution"?
How are you handling it now, to prevent "the drain" ....?
No "solution". I plug it in alot and have power bricks in several places - before I go to bed and when I get to work (I don't use it for work, it sits in my bag and drains).

I certainly don't shut it off and on every time I want to use it as you have so frequently suggested as a "solution".
 
I have a late 2011 13" MBP. It's a classic at this point. It runs really well with the upgrades I have done, but the battery will literally deplete from 100% to 0% in 24 hours. Overnight I lose 30%. I gave up. I have tried everything including a clean install.
You may have already said this, but have you replaced the battery recently? Could it be perhaps that the battery is going out? That gen of MacBook Pros most definitely should not be losing that much juice overnight. How does the battery last when you use it under normal usage?
 
You may have already said this, but have you replaced the battery recently? Could it be perhaps that the battery is going out? That gen of MacBook Pros most definitely should not be losing that much juice overnight. How does the battery last when you use it under normal usage?
Oh yes I have. Three times.
 
  • Like
Reactions: Painter2002
I started to have the same issue (20-30% overnight charge drop on MBP early 2015, High Sierra 10.13.6) about a month ago. Nothing helped it (including tcpkeepalive=0). I've noticed HibernateError(s) in `pmset -g log' and decided to reset /var/vm/sleepimage. And voila - it helped! Now it is about 1-2% overnight drop, as I used to have before.

So looks like it just could not go into standby at all in my case (while retrying every two hours according to my log). Check your log (`pmset -g log') for HibernateError(s) and if you see them there repeating you might have the same issue. Here is how I fixed it:

1. Turn SIP off (sleepimage was added to SIP starting from High Sierra, it seems, google "macos sip off").
2. Set hibernatemode to 0 (remember the old value `pmset -g', `sudo pmset -a hibernatemode 0').
3. Remove the file (`sudo rm /var/vm/sleepimage').
4. Restore hibernatemode to the old value (usually 3, `sudo pmset -a hibernatemode 3').
5. Turn SIP back on.
 
Last edited:
I've had the same issue for more than a year now. While reading through this thread, I thought of looking at the documentation for pmset and noticed the following:
ttyskeepawake - prevent idle system sleep when any tty (e.g. remote login session) is 'active'. A tty is 'inactive' only when its idle time
exceeds the system sleep timer. (value = 0/1)

Since my Terminal app (iTerm) is always open and for most of the time with a ssh session to one of my servers, I realised that could be the problem. Disabled the option with 'sudo pmset -a ttyskeepawake 0'. So far (touch wood) it seems to be resolved.
 
I had huge power draw spikes with iCloud Safari Bookmark Syncing, consuming about 50% of CPU time for a couple of minutes, repeating each 10 minutes or so.

Only disabling the feature helped - which won´t really work for anyone using several Apple devices and Safari to stay in sync firsthand. I use Firefox as main browser, though, and there syncing works very fast, reliable and without any discernable power drain.

iCloud sync in general in my experience seems to be unusually high in enegry consumption and duration. I limited it to mail, and contacts for backup purposes, as googlemail is somehow much more reliable in that regard

Maybe this may help some of you identifying specific power drain issues.
 
I've had the same issue for more than a year now. While reading through this thread, I thought of looking at the documentation for pmset and noticed the following:
ttyskeepawake - prevent idle system sleep when any tty (e.g. remote login session) is 'active'. A tty is 'inactive' only when its idle time
exceeds the system sleep timer. (value = 0/1)

Since my Terminal app (iTerm) is always open and for most of the time with a ssh session to one of my servers, I realised that could be the problem. Disabled the option with 'sudo pmset -a ttyskeepawake 0'. So far (touch wood) it seems to be resolved.
Well, I read this post and thought to myself, have I tried this? I must have? I tried everything. But what the hell. I ran it in terminal at 4:00AM this morning with the battery at 85% and closed the lid. Opened it at 4:00PM and it's at 69%. That's better for 12 hours believe it or not.
 
Well, I read this post and thought to myself, have I tried this? I must have? I tried everything. But what the hell. I ran it in terminal at 4:00AM this morning with the battery at 85% and closed the lid. Opened it at 4:00PM and it's at 69%. That's better for 12 hours believe it or not.

Mine is also not draining as fast as before, but still not how it used to be. Have you tried checking the pmset log? Charge it fully to 100%, put it in sleep mode and unplug power. Leave it for two hours and wake it up again. Run the following: sudo pmset -g log

There is a lot of information. You see every wake event and the reason why it woke up. I see a lot of mDNSResponder and com.apple.backupd-auto events. I've disabled the auto backup (time machine) and will check the log tomorrow again.
 
Mine is also not draining as fast as before, but still not how it used to be. Have you tried checking the pmset log? Charge it fully to 100%, put it in sleep mode and unplug power. Leave it for two hours and wake it up again. Run the following: sudo pmset -g log

There is a lot of information. You see every wake event and the reason why it woke up. I see a lot of mDNSResponder and com.apple.backupd-auto events. I've disabled the auto backup (time machine) and will check the log tomorrow again.
Been there done that. Mine is still not normal too.
 
Been there done that. Mine is still not normal too.
I thought I'd give an update on my situation... I upgraded my 2017 MBP to Mojave on Tuesday night, and the past two days I've charged it to 100% before going to sleep, and in the morning it only has lost 1-2% battery power.

It looks like this could largely be fixed in Mojave, and that the culprit of the 5% or more battery loss overnight is the High Sierra OS. So you may try upgrading to Mojave to see if this resolves your issue. If your model isn't compatible with Mojave, there are work-arounds, or you could try downgrading back to Sierra to see if the issue still continues there.
 
I thought I'd give an update on my situation... I upgraded my 2017 MBP to Mojave on Tuesday night, and the past two days I've charged it to 100% before going to sleep, and in the morning it only has lost 1-2% battery power.

It looks like this could largely be fixed in Mojave, and that the culprit of the 5% or more battery loss overnight is the High Sierra OS. So you may try upgrading to Mojave to see if this resolves your issue. If your model isn't compatible with Mojave, there are work-arounds, or you could try downgrading back to Sierra to see if the issue still continues there.

Sadly, no more updates for my machine. Unless there is a hack out there.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.