Need Some Help: MacBook not sleeping when closed

Discussion in 'macOS High Sierra (10.13)' started by Hoosier317, Jul 18, 2017.

  1. Hoosier317 macrumors 6502a

    Hoosier317

    Joined:
    Sep 21, 2016
    #1
    So, I did a clean install of High Sierra on my early 2013 13" Retina MacBook Pro. I then installed NoSleep, which I sometimes used when plugged in and I have a process running that I don't want interrupted. It had issues however and would never stay in the menu bar for long. Also, with Sierra it would light up blue when activated...but in High Sierra it just goes from grey to a darker grey. That's all okay though. I can go without it (it hasn't been updated since 2013). Here is my real issue:

    I uninstalled it. I've removed the application itself and I can't find any traces of it in Library/Application support now. The problem is that my MacBook is continuing to run after I close the lid while on battery power even though I have the "Energy Saver" settings set to their default. It isn't sleeping. So each time I come back to use it the battery is drained or completely dead.

    Any ideas?
     
  2. Hoosier317 thread starter macrumors 6502a

    Hoosier317

    Joined:
    Sep 21, 2016
    #2
    Hmm....testing something out. Even though I had removed the application, I just noticed it was still appearing in my System Preferences and it was toggled to prevent sleep while on battery power.
     
  3. LarryJoe33 macrumors 6502a

    LarryJoe33

    Joined:
    Jul 17, 2017
    Location:
    Boston
    #3
    You are not alone. Use terminal to set hibernation mode to 0. That will fix it.

    https://forums.developer.apple.com/thread/78911
    --- Post Merged, Jul 18, 2017 ---
    Sorry, I quickly read your issue and assumed it wasn't waking up from a closed lid. My bad. Hope you resolve this.
     
  4. Hoosier317 thread starter macrumors 6502a

    Hoosier317

    Joined:
    Sep 21, 2016
    #4
    Yep, what I mentioned in my second post solved. I'm not sure why it's still there after I uninstalled it though. At least it's working correctly now.
     

Share This Page