Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2020 13" MacBook Pro not sleeping
- Thread starter boylerman
- Start date
- Sort by reaction score
I'm sorry to hear that... mine has been behaving lately. Just out of curiosity, do you have Intel Power Gadget installed? I did a wipe and clean OS installation, which solved the problem. I then reinstalled Power Gadget and I was again having sleep issues - since I removed Power Gadget, the problem has not recurred. It's anecdotal and very thin evidence to be sure, but that's the only thing I can connect the problem to.
Good luck!
[automerge]1592615983[/automerge]
How do you see the log files?
If you just paste that command in terminal (Applications > Utilities > Terminal) it will spit out the sleep and wake logs with timestamps.
Did people ever get this resolved? Did anyones problem disappear when the got a new machine? I am quickly approaching the time when I can no longer return my computer for a new one.
I am very unhappy with this problem in my computer and I want it resolved so if I put my computer to sleep it wakes up with the same charge as it had before it entered sleep. I lose like 40% in 6 hours!
I am very unhappy with this problem in my computer and I want it resolved so if I put my computer to sleep it wakes up with the same charge as it had before it entered sleep. I lose like 40% in 6 hours!
I have not had the problem resurface since I reinstalled macOS fresh. I did not have the machine replaced. I have had at least a few trouble-free weeks. Fingers crossed...
One thing I did that, at least for a short few trial has worked, is to uncheck “Allow Bluetooth devices to wake this computer” box. I haven’t yet tried it overnight so I’m keeping my fingers crossed.
I do have Bluetooth AirPods that should not disturb it, but maybe they are. I hope this is it. I like using my computer in bed and just letting it sleep when I go to sleep (not wanting to charge it until it’s further rundown).
I had my computer replaced because of this problem, and the replacement computer also had the same issue. I reinstalled the OS, and the problem has not completely gone away for me - it seems to be hit or miss. It has become an exciting part of my day to reach into my laptop bag each morning to discover how much battery power I have!
This morning, my battery was down to 58% when I opened up my MacBook Pro. I ran the Terminal command herb2k shared, and I got this:
So it appears that the MacBook Pro didn't "wake up" throughout the night, but it still consumed 42% of the battery life during this time?
2020-06-29 23:09:39 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:100%) 7 secs
2020-06-29 23:09:44 -0400 Wake Requests [*process=powerd request=TCPKATurnOff deltaSecs=43255 wakeAt=2020-06-30 11:10:39]
2020-06-29 23:09:46 -0400 Assertions PID 238(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000928a [System: PrevIdle DeclUser IntPrevDisp kDisp]
2020-06-29 23:09:46 -0400 Assertions PID 238(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000928a [System: DeclUser IntPrevDisp kDisp]
2020-06-29 23:09:46 -0400 DarkWake DarkWake from Deep Idle [CDN] : due to EC.ARPT/Maintenance Using BATT (Charge:100%) 9 secs
2020-06-29 23:09:46 -0400 WakeDetails DriverReasonataFrame - DriverDetails:0800450000281a1540003106cc7b11399034c0a8012a1467f1ac0000000
2020-06-29 23:09:46 -0400 WakeTime WakeTime: 0.793 sec
2020-06-29 23:09:46 -0400 Kernel Client Acks Delays to Wake notifications: [RP05 driver is slow(msg: SetState to 2)(326 ms)] [IOBluetoothHostControllerUARTTransport driver is slow(msg: SetState to 1)(332 ms)]
2020-06-29 23:09:57 -0400 Wake Requests [*process=powerd request=TCPKATurnOff deltaSecs=43241 wakeAt=2020-06-30 11:10:39]
2020-06-30 10:03:48 -0400 Assertions PID 238(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd00009298 [System: DeclUser IntPrevDisp kDisp]
2020-06-30 10:03:48 -0400 Assertions PID 238(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd00009298 [System: DeclUser IntPrevDisp kDisp]
2020-06-30 10:03:48 -0400 Wake Wake from Deep Idle [CDNVA] : due to EC.ARPT/Lid Open Using BATT (Charge:58%)
2020-06-30 10:03:48 -0400 WakeTime WakeTime: 655.934 sec
2020-06-30 10:03:48 -0400 Kernel Client Acks Delays to Wake notifications: [RP05 driver is slow(msg: SetState to 2)(323 ms)] [IOBluetoothHostControllerUARTTransport driver is slow(msg: SetState to 1)(332 ms)] [AppleIntelFramebuffer driver is slow(msg: SetState to 2)(375 ms)] [AppleIntelMEClientController driver is slow(msg: SetState to 1)(368 ms)]
So it appears that the MacBook Pro didn't "wake up" throughout the night, but it still consumed 42% of the battery life during this time?
That's what it looks like. You can try to disable tcpkeepalive (pmset -b tcpkeepalive 0) and see if that helps, if not, it means something is draining your battery while it's not in use.
That is really frustrating... the problem disappeared for me after a fresh macOS reinstall, then returned after I installed Intel Power Gadget. Once I uninstalled Power Gadget, the problem went away again. It has not happened since. That’s over a month ago now.
It may be a coincidence, but do you by chance have Power Gadget installed? That’s the only thing I was able to connect the issue with.
I have the Intel Power Gadget installed but it currently not active. I will use the uninstaller.pkg to get rid of it and see if that makes a difference.
After last update of Intel Power Gadget I found that my Mac never sleeps even when this app is not launched. An uninstalling helped to fix it.
My experience was the same. As soon as I removed Power Gadget, the issue disappeared for me completely.
I'll be testing it out soon...but I can't take any chance tonight as I'll be traveling tomorrow morning and need it fully (or close to fully) charged. I really hope you two are right!
I posted a new thread about this because I couldn't find this one but I'm glad I found it again.
I had it drain from 53% to 45% after 10 hours overnight, before dying immediately to 0%. I also have Intel Power Gadget installed, and was running it before closing the lid (I don't remember if I closed the program or not). Think I'll also remove it and see if it happens again.
Just curious, does it happen every night for any of you if you have Intel Power Gadget installed, or only some nights?
[automerge]1594447859[/automerge]
Do you know which version? I currently have version 3.6.0 installed, while the newest is 3.7.0. The old versions on intel's site are dead links, so we're stuck with the newest one.
I had it drain from 53% to 45% after 10 hours overnight, before dying immediately to 0%. I also have Intel Power Gadget installed, and was running it before closing the lid (I don't remember if I closed the program or not). Think I'll also remove it and see if it happens again.
Just curious, does it happen every night for any of you if you have Intel Power Gadget installed, or only some nights?
[automerge]1594447859[/automerge]
Do you know which version? I currently have version 3.6.0 installed, while the newest is 3.7.0. The old versions on intel's site are dead links, so we're stuck with the newest one.
Last edited:
For me, it did not happen every night; it was seemingly random. The only thing I could connect the problem with is the Intel Power Gadget app (version 3.7.0) directly from the Intel website. It seemed to happen whether or not I had Power Gadget running when putting the computer to sleep. However, I also use iStat Menus and I had Power Gadget linked to iStat, so it would display the CPU/iGPU clock speeds in the menu bar. So, in that respect it was always running.
Again, problem completely gone after uninstalling Power Gadget.
On my prior machine (2017 15" Pro), I always had Power Gadget installed and linked to iStat Menus displaying CPU clock speed and I never had a problem with that computer losing charge while in sleep mode. However, I am not sure what version of Power Gadget I had installed on that computer. Maybe this is a problem Intel can fix with an update?
Uninstalled it yesterday night. I'll try a few days without Intel Power Gadget and report back if it happens again. Still drained ~8% overnight, which isn't the best standby time. I did however wake up today to a kernel panic, first time that's happened.
Mine still didn’t sleep even with the Intel app uninstalled. I don’t know what to try.
[automerge]1594496149[/automerge]
Mine happens every night. I’m getting very frustrated that my new computer can’t be put to sleep.
It’s not good for the battery to run all the way down so if I don’t plan to use it for a while, I must shut it down. This is a real pain.
Last edited:
I’ve never gotten to the bottom of this issue. My replacement laptop still demonstrates this behavior more often than not. I have completely uninstalled Intel Power Gadget, but it didn’t resolve for me. My next step is a complete drive wipe and reinstall from scratch.
He there,
I have the same issue with my new MBP 13" 2020 — battery goes from 100 to 0 during the night or less while should be in sleep mode.
I've spent a day already looking into that, reading forums and googling different parts of logs from
What I've found out by now is that in most cases it's more or less related to network requests. And in most cases it helps to switch off
By now, I'm testing switching off Find My Mac option — during the 10 mins test it resulted in that I don't see
I have the same issue with my new MBP 13" 2020 — battery goes from 100 to 0 during the night or less while should be in sleep mode.
I've spent a day already looking into that, reading forums and googling different parts of logs from
pmset -g log and log show --style syslog | fgrep "Wake reason"What I've found out by now is that in most cases it's more or less related to network requests. And in most cases it helps to switch off
tcpkeepalive for battery mode (for those who interested the command is sudo pmset -b tcpkeepalive 0 and sudo pmset -b tcpkeepalive 1 to revert, but PLEASE USE ONLY IF 100% SURE) that is not a good solution as it could block some apps and features from working.By now, I'm testing switching off Find My Mac option — during the 10 mins test it resulted in that I don't see
Wake Requests … process=mDNSResponder in pmset logs every single minute, that as I believe is the main reason for this issue. I'm going to test it with 100% battery this night, will post an update afterward.
I just created another thread but stumbled on this thread. I noticed my Mac wasn't sleeping properly.
(AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.RTC (Alarm) appears to be waking it every 2 hours.
Also:
2020-07-13 11:20:49 -0400
Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 1
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 1
NetworkClientActive 0
Listed by owning process:
pid 3703(Webex Productivity Tools): [0x000137b600019f50] 03:08:01 PreventUserIdleSystemSleep named: "Cisco Webex Meetings(Mac)"
pid 211(coreaudiod): [0x00015ff10001a24f] 00:16:21 PreventUserIdleSystemSleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridlesleep"
Created for PID: 511.
pid 211(coreaudiod): [0x00014dee0001a235] 01:33:12 PreventUserIdleSystemSleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridlesleep"
Created for PID: 9894.
pid 211(coreaudiod): [0x00015ff10005a251] 00:16:21 PreventUserIdleDisplaySleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridledisplaysleep"
Created for PID: 511.
pid 211(coreaudiod): [0x00014dee0005a238] 01:33:12 PreventUserIdleDisplaySleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridledisplaysleep"
Created for PID: 9894.
pid 164(hidd): [0x000157bb0009a3ad] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100002e53 name:AppleUserHIDEventSe product:MX Keys eventType:3"
Timeout will fire in 600 secs Action=TimeoutActionRelease
Kernel Assertions: 0x104=USB,MAGICWAKE
id=506 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14400000 owner=IOUSBHostDevice
id=509 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14420000 owner=Logitech BRIO
id=510 level=255 0x100=MAGICWAKE mod=2020-07-11, 2:24 PM description=en0 owner=en0
id=539 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14410000 owner=Jabra Engage 75
id=541 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.0d300000 owner=IOUSBHostDevice
id=543 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14300000 owner=IOUSBHostDevice
Idle sleep preventers: IODisplayWrangler
(AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.RTC (Alarm) appears to be waking it every 2 hours.
Also:
2020-07-13 11:20:49 -0400
Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 1
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 1
NetworkClientActive 0
Listed by owning process:
pid 3703(Webex Productivity Tools): [0x000137b600019f50] 03:08:01 PreventUserIdleSystemSleep named: "Cisco Webex Meetings(Mac)"
pid 211(coreaudiod): [0x00015ff10001a24f] 00:16:21 PreventUserIdleSystemSleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridlesleep"
Created for PID: 511.
pid 211(coreaudiod): [0x00014dee0001a235] 01:33:12 PreventUserIdleSystemSleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridlesleep"
Created for PID: 9894.
pid 211(coreaudiod): [0x00015ff10005a251] 00:16:21 PreventUserIdleDisplaySleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridledisplaysleep"
Created for PID: 511.
pid 211(coreaudiod): [0x00014dee0005a238] 01:33:12 PreventUserIdleDisplaySleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:f803:0:{AC10-41B5-3539374C}.context.preventuseridledisplaysleep"
Created for PID: 9894.
pid 164(hidd): [0x000157bb0009a3ad] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100002e53 name:AppleUserHIDEventSe product:MX Keys eventType:3"
Timeout will fire in 600 secs Action=TimeoutActionRelease
Kernel Assertions: 0x104=USB,MAGICWAKE
id=506 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14400000 owner=IOUSBHostDevice
id=509 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14420000 owner=Logitech BRIO
id=510 level=255 0x100=MAGICWAKE mod=2020-07-11, 2:24 PM description=en0 owner=en0
id=539 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14410000 owner=Jabra Engage 75
id=541 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.0d300000 owner=IOUSBHostDevice
id=543 level=255 0x4=USB mod=1969-12-31, 7:00 PM description=com.apple.usb.externaldevice.14300000 owner=IOUSBHostDevice
Idle sleep preventers: IODisplayWrangler
What version of power gadget did you have. Is this only an issue with the newer version?
This may be a stretch...but there are a bunch of us with iPad Pros (both ‘18 and ‘20) with the new Magic Keyboard and we are having the same issue with battery drain when closing the case. For us, it appears the backlight on the keyboard either doesn’t go out or comes back on during the night and causes the same percentage battery drain that you are seeing. I know we are using 2 totally different OS’s but aren’t the new keyboards the same? I wonder if it is a keyboard issue. Seems like a software issue to me, but seems strange we are having the same problems at the same time. Some of us also had a problem that the backlight wouldn’t come on at times. Fix is to unmount iPP from MK and reboot, easy but frustrating. Apple just swapped out my keyboard and I will see if that helps. At least the iPP doesn’t get hot like the MBP!