Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Follow the video to find file Mac-E43C1C25D4880AD6.plist
right button and edit
Go down an find:
Set DNDWhileDisplaySleeps to true
Set NotificationWake to false
Set TCPKeepAliveDuringSleep to false
Save as same name.plist on desktop and then copy and replace.
Restart
Hope will help
 
Follow the video to find file Mac-E43C1C25D4880AD6.plist
right button and edit
Go down an find:
Set DNDWhileDisplaySleeps to true
Set NotificationWake to false
Set TCPKeepAliveDuringSleep to false
Save as same name.plist on desktop and then copy and replace.
Restart
Hope will help

Thanks. This kills Find My Mac I assume?
 
Yeah I noticed a similar thing. Sierra was great. High Sierra very far from great. Mojave even worse.
I'm just not using sleep mode at the moment. Hopefully Apple find a way to make it work again.
This has been my solution as well unfortunately. I come from a time where you were supposed to always shut down the computer after your down with it, so it’s not a deal breaker. But it was convenient to use the sleep feature when it worked correctly on MacBooks without sucking the life out of the battery.
 
I'm not a fan of videos. I like clear concise directions. I've been trying to find them in this thread and must have missed them.

I have a rMBP mid 2015 running Mohave. I take it off the charger at 100% and by the next evening around 6PM EST its 47%. Battery health is good.
 
  • Like
Reactions: madjack84
Try this one.

Create a new account on your Mac. DO NOT sign in to iCloud.

See what your battery life is then. I have a 13" MBP Early 2015 on Mojave and I went from 10 - 20% overnight to 5% or less with iCloud off.

Doesn't that just suck ...
 
  • Like
Reactions: madjack84
I used the: 'sudo pmset -b tcpkeepalive 0' method. Shuts off Find My Mac, which I'm not happy about, but I can live with. In 'pmset -g log' I do not see any logging between the time I close the lid and the next time I open it. To me that means the power usage is minimal. Before I saw tons of logging related to mDNS Responder, Cloud Photos dark wake sync, etc.

Battery usage has improved with this method. I lost 4% battery overnight last night. 2% over eight hours today.

BTW, isn't it odd that the Cloud Photos Dark Wake Sync would exist when you have Enable Power Nap unchecked?
 
The last few days I've put my MBP to sleep as usual but woken up with a flat battery and the red battery symbol on-screen. This is a 2018 model which has also been a bit temperamental when it comes to waking up from sleep.
 
The last few days I've put my MBP to sleep as usual but woken up with a flat battery and the red battery symbol on-screen. This is a 2018 model which has also been a bit temperamental when it comes to waking up from sleep.
I had the problem weeks ago and it went away..Now it's crept back with a fury. I'm losing 2-3% per hour of sleep.
 
  • Like
Reactions: ascender
Updated my 2015 rMBP 13" to Mojave last week. I now have major battery drain while sleeping, looks like around 1 percent per hour of sleep. It used to lose almost nothing in every OS before Mojave.

Seriously bad!
 
  • Like
Reactions: madjack84
Been having stability issues waking up from sleep and restarting on battery power lately, so I did a summy fresh install of Sierra on an external HD using the Recovery OS, so my computer would update the smc/efi whatever the devil it updates during a fresh OS installation. Then I did a PRAM/NVRAM reset, enabled rootless mode to give Onyx access to my system folder and done the entire run of cleaning up system stuff, rebuilding caches, repairing permissions etc, and gave safe mode a run and restarted, and then disabled rootless mode.

My machine has since become stable as a rock, and I wanted to give exclusive hibernation mode (using sudo pmset -a hibernatemode 25 which didn't work for me in the past) a try while completely disabling standby mode. It works like it should this time around, and I'm now a happy camper.

Settings below

pmset -g
System-wide power settings:
Currently in use:
standbydelay 15
standby 0
womp 0
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
networkoversleep 0
disksleep 10
sleep 180 (sleep prevented by coreaudiod)
autopoweroffdelay 2
hibernatemode 25
autopoweroff 1
ttyskeepawake 0
displaysleep 180
acwake 0
lidwake 1


I'm almost tempted to test out standby mode once again to see how much battery power I lose when not resorting to hibernating before powering down, but nah. This is as a good as it gets.

I now have a brand-new battery, for which I have managed to put the kibosh on a ticking death senstence. It doesn't drain anymore, and I'm not risking going back to the mess I've finally dug my laptop out of.
 
I do, but I think just because I had just installed Mohave, I didn’t used to. I’ll kill it.

I reviewed your entire thread, as I have similar problems with power loss on my Mac Pro.

I don't have enough data points to tell if this "really" worked, but it seemed to help. I uninstalled Malware Bytes and it seems to save about 4-5 percentage points each night. I've only tracked it a couple of nights, but wondering if that's one of the culprits.

Might be worth a look (?).
 
  • Like
Reactions: billyboyHK
Check the pmset log - if there are any errors which prevent deep sleep. For example, like this:

$ pmset -g log | grep -i err | tail -1
2018-12-02 01:25:20 +0000 DarkWake DarkWake from Standby [CDN] due to /HibernateError: Using BATT (Charge:50%) 5 secs


After fixing it few months ago by resetting /var/vm/sleepimage (see my post here from Sep 15) I started seeing it again recently and the battery drain issue reappeared again as well. I should probably reset sleepimage again...

(MBP 13" Early 2015, High Sierra)
 
Yeap, after sleepimage reset it works fine again (only 1% overnight drop). I wonder - what makes it corrupted and why macOS (High Sierra 10.13.6 in my case) does not detect and reset it by itself...
 
OP:
I asked this in another thread, and I'll suggest it again.

If...
"It just sucks taking my machine out of my bag after a few days to find it dead..."

Then...
Why don't you just power it off BEFORE you put it into the bag, and reboot when you take it out?
What would you really be losing by doing this?

Love this reply because it is so obvious...and I'm guilty of it, too! I was wondering why my Mac was losing power while closed, and it really does make sense to turn it off, especially when you're not going to use it for awhile (although this is seldom).
 
Love this reply because it is so obvious...and I'm guilty of it, too! I was wondering why my Mac was losing power while closed, and it really does make sense to turn it off, especially when you're not going to use it for awhile (although this is seldom).

But it doesn't solve the underlying problem. I suppose it's analogous to saying you want to take your car on a cross-country trip, but you need to stop every four hours to keep it from overheating. That works, but it doesn't solve the problem.

Apple should solve this.
 
But it doesn't solve the underlying problem. I suppose it's analogous to saying you want to take your car on a cross-country trip, but you need to stop every four hours to keep it from overheating. That works, but it doesn't solve the problem.

Apple should solve this.

I had this issue but someone here helped me solve it using pmset. If you open terminal and while the charger is disconnected (ie. running only on battery) run pmset -g what does it show?
 
Zolos wrote:
"But it doesn't solve the underlying problem."

Agreed.
But... maybe there's actually no working solution "to the underlying problem" right now.

In that case, "use what works" ("solution" or not)...
 
I had this issue but someone here helped me solve it using pmset. If you open terminal and while the charger is disconnected (ie. running only on battery) run pmset -g what does it show?
I think this is what you're asking me to show (let me know). Thanks.

System-wide power settings:

Currently in use:

standbydelaylow 10800

standby 1

womp 0

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 0

gpuswitch 2

networkoversleep 0

disksleep 0

standbydelayhigh 86400

sleep 0 (sleep prevented by coreaudiod, sharingd, cloudphotosd)

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 0

ttyskeepawake 1

displaysleep 3

highstandbythreshold 50

acwake 0

lidwake 1
 
I think this is what you're asking me to show (let me know). Thanks.

System-wide power settings:

Currently in use:

standbydelaylow 10800

standby 1

womp 0

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 0

gpuswitch 2

networkoversleep 0

disksleep 0

standbydelayhigh 86400

sleep 0 (sleep prevented by coreaudiod, sharingd, cloudphotosd)

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 0

ttyskeepawake 1

displaysleep 3

highstandbythreshold 50

acwake 0

lidwake 1


The standbydelayhigh is set for 24 hours. I would do:

sudo pmset -b standbydelay 3600

and see if that makes a difference. That's one hour. Change it how you see fit of course.
IIRC I had to do both stanbydelayhigh and standbydelaylow. The difference, I believe, is standbydelaythreshold; yours says 50 = 50%. So you can say above 50%, hibernate in 3 hours and below 50% hibernate in 1 hour. Or whatever.

Anyway, give that a go, it make a huge difference for me.
 
I've been experiencing this problem since upgrading to High Sierra and then Mojave (10.14.3). (Sierra does not have this problem.) I have had a case open with Apple Care for months trying to resolve this. I was just told by Apple support that engineering is now looking at this as a real issue. Whether anything gets resolved is to be seen.
 
  • Like
Reactions: Zolos
Remember when apple made great software and products?! I miss those days...

Apple used to advertise that macbooks could sleep for 30 days. Remember that? And it worked until 2016 maybe? Not sure on the exact date, but at some point before then, the macbooks reliably consumed very little power while closed and then after that they just chew through battery.

Remember, the used to ADVERTISE 30 DAYS OF SLEEPING. I assume they don't anymore but I haven't checked the website in a while.

EDIT: They do still in the tech specs claim
  • Up to 30 days of standby time
But it seems like this has been broken or unreliable for several YEARS now!!

Apple BRING QUALITY BACK! I'm done with Apple products until they do.

I've been experiencing this problem since upgrading to High Sierra and then Mojave (10.14.3). (Sierra does not have this problem.) I have had a case open with Apple Care for months trying to resolve this. I was just told by Apple support that engineering is now looking at this as a real issue. Whether anything gets resolved is to be seen.
 
Remember when apple made great software and products?! I miss those days...

Apple used to advertise that macbooks could sleep for 30 days. Remember that? And it worked until 2016 maybe? Not sure on the exact date, but at some point before then, the macbooks reliably consumed very little power while closed and then after that they just chew through battery.

Remember, the used to ADVERTISE 30 DAYS OF SLEEPING. I assume they don't anymore but I haven't checked the website in a while.

EDIT: They do still in the tech specs claim
  • Up to 30 days of standby time
But it seems like this has been broken or unreliable for several YEARS now!!

Apple BRING QUALITY BACK! I'm done with Apple products until they do.

I still have the original iPad I bought when it was released. I stopped using it in 2012, but last year I charged and used it to test streaming videos over local network, left it to sleep and forgot about it.

Fast forward 9 months, I clicked the power/wakeup button (it was sleeping, not turned off) and lo and behold, it still had 40% of battery power left. Streaming videos and light browsing yields 5-7 days of use on a single charge, on a battery that's 8 years old.

Apple's Products specs have gotten better over the years, but sadly quality has not.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.