FelixRaven
Level 1 (4 points)
Notebooks

Q: My MacBook Pro retina late 2013 batteries drain in sleep mode

Hello There!

I have a late 2013 MacBook Pro which recently (I think after the El Capitain update whihc came before the last one) started to seriously drain the battery in sleep mode. (About 20% / day compared to the usual 1-2 % / day.)

I went through some logical steps:

  • I turned off every application before entering sleep mode
  • checked whether if it is completely turned off, does it still have power loss? No.
  • I checked the energy saving settings, nothing prevents my Macbook to enter sleep mode, power nap is turned off.

 

What else I noticed: if I didn't open my MacBook Pro for days, then before it had a different starting screen (I had to type in my password twice, but now only once.)

This led me to an assumption: does something prevents my MacBook to enter stand by after a while?

I didn't find anything in settings that affects this.

What could went wrong?

Thanks,

Gabor

MacBook Pro (Retina, 13-inch, Late 2013), OS X El Capitan (10.11.5)

Posted on Jun 25, 2016 3:04 AM

Close
FelixRaven

Q: My MacBook Pro retina late 2013 batteries drain in sleep mode

  • All replies
  • Helpful answers

Page 1 Next

  • by Esquared,

    Esquared Esquared Jun 25, 2016 3:10 AM in response to FelixRaven
    Level 6 (8,533 points)
    Mac OS X
    Jun 25, 2016 3:10 AM in response to FelixRaven

    Please have a look at this topic, and see if it contains any suggestions you haven't tried yet:

    2015 Macbook Pro Retina battery drain after El Capitan Install

  • by FelixRaven,

    FelixRaven FelixRaven Jun 25, 2016 3:16 AM in response to Esquared
    Level 1 (4 points)
    Notebooks
    Jun 25, 2016 3:16 AM in response to Esquared

    Oh, I forgot to mention, that I tried this too (not the hardest parts, but those I don't intend to...)

  • by FelixRaven,

    FelixRaven FelixRaven Jun 25, 2016 3:18 AM in response to FelixRaven
    Level 1 (4 points)
    Notebooks
    Jun 25, 2016 3:18 AM in response to FelixRaven

    I mean resetting the printers. I tried all other stuff.

  • by Esquared,

    Esquared Esquared Jun 25, 2016 3:32 AM in response to FelixRaven
    Level 6 (8,533 points)
    Mac OS X
    Jun 25, 2016 3:32 AM in response to FelixRaven

    Resetting the printer system isn't exactly complicated, so give it a try.

     

    Other things to try:

    reboot in Safe Mode (and to normal mode again) OS X El Capitan: Start up in safe mode

    reset SMC Reset the System Management Controller (SMC) on your Mac - Apple Support

  • by FelixRaven,

    FelixRaven FelixRaven Jun 25, 2016 5:07 AM in response to Esquared
    Level 1 (4 points)
    Notebooks
    Jun 25, 2016 5:07 AM in response to Esquared

    Yeah, resetting is easy, but I think setting all the printers I contact to in different offices is a different story. (Many of them are older printers which aren't exactly easy to install.)

    If all the settings remain with reset, please inform me!

    If Apple phone support can't help on Monday, I'll give it a try though. Thanks & regards,

    Gabor

  • by FelixRaven,

    FelixRaven FelixRaven Jun 27, 2016 12:36 AM in response to Esquared
    Level 1 (4 points)
    Notebooks
    Jun 27, 2016 12:36 AM in response to Esquared

    Hello! Finally, I did everything, but no use. 10 % drop overnight. :-(

  • by Rysz,

    Rysz Rysz Jun 27, 2016 9:31 PM in response to FelixRaven
    Level 7 (21,001 points)
    iPad
    Jun 27, 2016 9:31 PM in response to FelixRaven

    Keep the MacBook connected to a charger overnight. There's a lot of background maintaince, syncing and updating activity that the OS takes care of at night.

  • by FelixRaven,

    FelixRaven FelixRaven Jun 27, 2016 11:39 PM in response to Rysz
    Level 1 (4 points)
    Notebooks
    Jun 27, 2016 11:39 PM in response to Rysz

    Hello Rysz!

    Thanks, but really? Each **** night?

    Until this extreme 10 % power loss over night started, the daily loss was 1%

    10% would mean my Mac would reinstall the OS each night.

    So I don't believe this is the case.

    The case is I think, El Capitain manages sleep very poorly, and needs a complete refurbishment.

  • by Esquared,

    Esquared Esquared Jun 28, 2016 12:16 AM in response to FelixRaven
    Level 6 (8,533 points)
    Mac OS X
    Jun 28, 2016 12:16 AM in response to FelixRaven

    10% certainly isn't normal, not even for El Capitan. My MBPr loses a few percent per night. 

     

    So let's see if we can solve this one. Can you show us part of the logs in Console that are produced during the night? Don't post the whole thing: a few dozen lines should be enough to get an idea.

     

    As a further trouble shooting step, log out before you put the MBP in sleep mode. Let us know if the power loss still occurs then.

  • by FelixRaven,

    FelixRaven FelixRaven Jun 28, 2016 12:25 AM in response to Esquared
    Level 1 (4 points)
    Notebooks
    Jun 28, 2016 12:25 AM in response to Esquared

    Hello, yes, of course. Please specify what logs you need, and how to reach them!

    Thanks!

  • by Esquared,

    Esquared Esquared Jun 28, 2016 12:33 AM in response to FelixRaven
    Level 6 (8,533 points)
    Mac OS X
    Jun 28, 2016 12:33 AM in response to FelixRaven

    Simply open Console, and select 'All messages' (if necessary). In the right frame scroll to the point where the MBP was supposed to enter sleep mode. Copy a few dozen lines below that and paste them in a reply.

     

    Also: in the search field (top right) type the word 'sleep'. That should give you a much shorter list: copy&paste that too. And do the same for the word 'wake'.

     

    And finally: when in battery mode, open Terminal and type the command "pmset -g" (without the quotes. Also copy/paste those results.

  • by FelixRaven,

    FelixRaven FelixRaven Jun 28, 2016 2:26 AM in response to Esquared
    Level 1 (4 points)
    Notebooks
    Jun 28, 2016 2:26 AM in response to Esquared

    Hello Esquared!

    I entered sleep mode (hopefully) by closing the display of my MBP, then I woke my computer up with opening it.

    Here are the last lines from the console, with the first one after waking it:

     

    2016. 06. 28. 11:13:45,406 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fab70f60850 {name = _NSDoNotDisturbEnabledNotification}

    2016. 06. 28. 11:13:45,413 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>:    NC Disabled: NO

    2016. 06. 28. 11:13:45,418 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>:   DND Enabled: YES

    2016. 06. 28. 11:13:45,418 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>: Updating enabled: NO   (Topics: (

    ))

    2016. 06. 28. 11:13:46,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:13:46,332 WindowServer[182]: device_generate_desktop_screenshot: authw 0x7fd4a508dc00(2000), shield 0x7fd4a48a4c00(2001)

    2016. 06. 28. 11:13:46,332 WindowServer[182]: device_generate_lock_screen_screenshot: authw 0x7fd4a508dc00(2000)[0, 0, 0, 0] shield 0x7fd4a48a4c00(2001), dev [1440,900]

    2016. 06. 28. 11:13:46,611 WindowServer[182]: no sleep images for WillPowerOffWithImages

    2016. 06. 28. 11:13:50,000 kernel[0]: Sandbox: coresymbolicatio(871) System Policy: deny(1) file-write-create /System/Library/Caches/com.apple.coresymbolicationd

    2016. 06. 28. 11:13:50,217 coresymbolicationd[871]: /System/Library/Caches/com.apple.coresymbolicationd/data does not exist, resetting cache

    2016. 06. 28. 11:13:50,217 coresymbolicationd[871]: Attempt to create [/System/Library/Caches/com.apple.coresymbolicationd/data] failed. No such file or directory

    2016. 06. 28. 11:13:50,217 coresymbolicationd[871]: Unable to open storage at /System/Library/Caches/com.apple.coresymbolicationd/data

    2016. 06. 28. 11:13:50,217 com.apple.xpc.launchd[1]: (com.apple.coresymbolicationd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

    2016. 06. 28. 11:13:51,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:13:51,988 CommCenter[284]: Telling CSI to exit low power.

    2016. 06. 28. 11:13:52,000 kernel[0]: Setting BTCoex Config: enable_2G:1, profile_2g:0, enable_5G:1, profile_5G:0

    2016. 06. 28. 11:13:52,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:13:52,155 sharingd[311]: 11:13:52.155 : Starting AirDrop server for user 501 on wake

    2016. 06. 28. 11:13:52,000 kernel[0]: en0: BSSID changed to 00:1f:cf:10:3c:f8

    2016. 06. 28. 11:13:52,000 kernel[0]: en0: channel changed to 4

    2016. 06. 28. 11:13:52,319 WindowServer[182]: CGXDisplayDidWakeNotification [590233005250]: posting kCGSDisplayDidWake

    2016. 06. 28. 11:13:52,319 WindowServer[182]: handle_will_sleep_auth_and_shield_windows: Deferring.

    2016. 06. 28. 11:13:52,440 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fab70c2e790 {name = _NSDoNotDisturbDisabledNotification}

    2016. 06. 28. 11:13:52,441 imagent[345]: <IMMacNotificationCenterManager: 0x7fedea51a150>: notification observer: com.apple.FaceTime   notification: __CFNotification 0x7fedea609cf0 {name = _NSDoNotDisturbDisabledNotification}

    2016. 06. 28. 11:13:52,459 imagent[345]: <IMMacNotificationCenterManager: 0x7fedea51a150>:    NC Disabled: NO

    2016. 06. 28. 11:13:52,459 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>:    NC Disabled: NO

    2016. 06. 28. 11:13:52,467 imagent[345]: <IMMacNotificationCenterManager: 0x7fedea51a150>:   DND Enabled: NO

    2016. 06. 28. 11:13:52,467 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>:   DND Enabled: NO

    2016. 06. 28. 11:13:52,467 imagent[345]: <IMMacNotificationCenterManager: 0x7fedea51a150>: Updating enabled: YES   (Topics: (

        "com.apple.ess",

        "com.apple.private.ac"

    ))

    2016. 06. 28. 11:13:52,467 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70d3c600>: Updating enabled: YES   (Topics: (

        "com.apple.private.alloy.icloudpairing",

        "com.apple.private.alloy.continuity.encryption",

        "com.apple.private.alloy.continuity.activity",

        "com.apple.ess",

        "com.apple.private.ids",

        "com.apple.private.alloy.phonecontinuity",

        "com.apple.madrid",

        "com.apple.private.ac",

        "com.apple.private.alloy.phone.auth",

        "com.apple.private.alloy.keychainsync",

        "com.apple.private.alloy.fmf",

        "com.apple.private.alloy.sms",

        "com.apple.private.alloy.screensharing",

        "com.apple.private.alloy.maps",

        "com.apple.private.alloy.thumper.keys",

        "com.apple.private.alloy.continuity.tethering"

    ))

    2016. 06. 28. 11:13:52,468 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70c101e0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fab70c66430 {name = _NSDoNotDisturbDisabledNotification}

    2016. 06. 28. 11:13:52,472 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70c101e0>:    NC Disabled: NO

    2016. 06. 28. 11:13:52,477 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70c101e0>:   DND Enabled: NO

    2016. 06. 28. 11:13:52,477 identityservicesd[299]: <IMMacNotificationCenterManager: 0x7fab70c101e0>: Updating enabled: YES   (Topics: (

        "com.apple.madrid"

    ))

    2016. 06. 28. 11:13:52,983 helpd[386]: Could not find access page in directory /Applications/WebDrive.app/Contents/Resources/en.lproj/WebDrive Help

    2016. 06. 28. 11:13:52,987 helpd[386]: Could not find access page in directory /Applications/WebDrive.app/Contents/Resources/en.lproj/WebDrive Help

    2016. 06. 28. 11:14:00,000 kernel[0]: Sandbox: coresymbolicatio(873) System Policy: deny(1) file-write-create /System/Library/Caches/com.apple.coresymbolicationd

     

    I think, I have to leave it sleep for a longer season in order to make you see if there is a problem with entering standby. Actually it is my guess, that somehow my MBP does not enter to standby from sleep.

     

    Here is the filtered sleep lines:

    2016. 06. 27. 9:58:58,570 GoogleSoftwareUpdateAgent[3111]: 2016-06-27 09:58:58.569 GoogleSoftwareUpdateAgent[3111/0xa42cb000] [lvl=2] -[KSAgentApp setupLoggerOutput] Agent settings: <KSAgentSettings:0x636fd0 bundleID=com.google.Keystone.Agent lastCheck=2016-06-25 09:01:04 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/holicsgabor/Library/Google/GoogleSoftwareUpdate/TicketSt ore/Keystone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration logEverything=0 logBufferSize=2048 alwaysPromptForUpdates=0 productIDToUpdate=(null) lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>

    2016. 06. 28. 11:04:11,000 kernel[0]: ACPI: sleep states S0 S3 S4 S5

    2016. 06. 28. 11:04:26,298 GoogleSoftwareUpdateAgent[372]: 2016-06-28 11:04:26.289 GoogleSoftwareUpdateAgent[372/0xa42cb000] [lvl=2] -[KSAgentApp setupLoggerOutput] Agent settings: <KSAgentSettings:0x70e5f0 bundleID=com.google.Keystone.Agent lastCheck=2016-06-27 07:59:01 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/holicsgabor/Library/Google/GoogleSoftwareUpdate/TicketSt ore/Keystone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration logEverything=0 logBufferSize=2048 alwaysPromptForUpdates=0 productIDToUpdate=(null) lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>

    2016. 06. 28. 11:10:11,351 AirPlayUIAgent[384]: 2016-06-28 11:10:11.350997 AM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification

    2016. 06. 28. 11:10:12,696 WindowServer[182]: no sleep images for WillPowerOffWithImages

    2016. 06. 28. 11:10:29,752 WindowServer[182]: handle_will_sleep_auth_and_shield_windows: Deferring.

    2016. 06. 28. 11:13:45,264 AirPlayUIAgent[384]: 2016-06-28 11:13:45.264197 AM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification

    2016. 06. 28. 11:13:46,611 WindowServer[182]: no sleep images for WillPowerOffWithImages

    2016. 06. 28. 11:13:52,319 WindowServer[182]: handle_will_sleep_auth_and_shield_windows: Deferring.

     

    Here are the filtered wake lines:

    2016. 06. 28. 11:04:12,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:04:12,813 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:12,824 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:16,993 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:16,997 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:17,000 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:17,003 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:17,006 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:17,008 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:17,316 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:17,463 apsd[78]: Attempt to set push wake topics without dark wake enabled: ()

    2016. 06. 28. 11:04:20,523 apsd[78]: Peer [pid=316] requested push wake but lacks APSPushWakeEntitlement

    2016. 06. 28. 11:04:38,890 com.apple.photomoments[564]: Photomoments process awakened.

    2016. 06. 28. 11:05:01,823 airportd[61]: -[CWXPCConnection performScanWithChannels:ssidList:legacyScanSSID:includeHiddenNetworks:mergeScan Results:maxAge:maxMissCount:maxWakeCount:maxAutoJoinCount:interfaceName:waitForW iFi:waitForBluetooth:token:priority:reply:]: !!! SCAN request received -0.6230 seconds after previous scan request from 84 (locationd)

    2016. 06. 28. 11:10:11,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:10:12,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:10:29,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:10:29,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:10:29,575 sharingd[311]: 11:10:29.575 : Starting AirDrop server for user 501 on wake

    2016. 06. 28. 11:10:29,738 WindowServer[182]: CGXDisplayDidWakeNotification [387662645048]: posting kCGSDisplayDidWake

    2016. 06. 28. 11:13:45,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:13:46,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:13:51,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:13:52,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    2016. 06. 28. 11:13:52,155 sharingd[311]: 11:13:52.155 : Starting AirDrop server for user 501 on wake

    2016. 06. 28. 11:13:52,319 WindowServer[182]: CGXDisplayDidWakeNotification [590233005250]: posting kCGSDisplayDidWake

     

    And here are the results of the command in terminal:

    Active Profiles:

    Battery Power -1*

    AC Power -1

    Currently in use:

    standbydelay         10800

    standby              1

    halfdim              1

    hibernatefile        /var/vm/sleepimage

    powernap             0

    disksleep            10

    sleep                15 (sleep prevented by AddressBookSourceSync)

    autopoweroffdelay    14400

    hibernatemode        3

    autopoweroff         1

    ttyskeepawake        1

    displaysleep         15

    acwake               0

    lidwake              1

    Holicss-MacBook-Pro:~ holicsgabor$


    Thanks for your help!

    Kind regards,

    Gabor

  • by Esquared,

    Esquared Esquared Jun 28, 2016 2:46 AM in response to FelixRaven
    Level 6 (8,533 points)
    Mac OS X
    Jun 28, 2016 2:46 AM in response to FelixRaven

    It's hard to tell from these reports what's going on. The last bit suggests that at the moment the command was entered, AddressBook was synching, but that doesn't necessarily mean anything (only if this ALWAYS is the sleep preventer).

     

    The trick is to find some kind of pattern in these log entries: an error message of some kind that keeps repeating itself time and time again. But you'll have to leave it in (failed) 'sleep mode' a bit longer than this to find a possible culprit.

  • by FelixRaven,

    FelixRaven FelixRaven Jun 28, 2016 2:49 AM in response to Esquared
    Level 1 (4 points)
    Notebooks
    Jun 28, 2016 2:49 AM in response to Esquared

    OK, thanks, tonight I will leave it in sleep mode and I'll come back with the same reports.

Page 1 Next