Q: MacBook switches to hibernation during sleep

Thanks. I'm giving it a go. By the way, is this what the app SmartSleep tinkers with out of curiosity? I had that installed but as things progressed with this failure of an EFI update, I deleted it along with ShouldISleep.

Also, will these Terminal commands "stick" on a reboot or thorough cleaning by Mountain Lion Cache Cleaner, for example, or will I have to occasionally do this again?

I won't know until probably tonight whether or not this new/added command works as I will be using my MBPr all day most likely. Maybe I'll take a nap myself this afternoon and see if it works. It is Saturday after all...

As for the two apps I mentioned, SmartSleep and Should I Sleep, after this issue, I am no longer comfortable with them. I prefer your SUDO commands and have noted them for the future.

Good to know the SUDO commands will stick now that I ran them. I too am more interested in instant-on over battery life.

I also switched off the "power nap" feature. I am not really interested (or comfortable) with my laptop going online when it's sleeping. I have an iPhone to let me know when important mail comes in.

My particular issue is that my sleep/wake-up, short term, say within an hour or so maybe, is that it'll wake up instantly. However, if I let it sleep more, that's when the "instant wait" happens. I am not entirely sure on the exact time the hibernation feature takes over, but tonight will be a good test (or the afternoon nap).

Thanks again. If this works, I'm going to throw it in the face of the AppleCare senior tech.

Hi Summer Storm Pictures,

What is your pmset for standby? 0 or 1? i think to turn off hibernate in battery mode, you need to set standby to 0 in pmset.

I used both Terminal commands suggested:

sudo pmset -a autopoweroff 0

sudo pmset -a hibernatemode 0

I won't know the results until I find time today to put it to sleep and perhaps catch a nice Saturday afternoon nappy myself. I will probably wake up even slower. Perhaps I should run these commands on myself?

In pmset, autopoweroff only applies when your Mac is being charged. If setting to 0, your Mac will not hibernate after sleep.

When running on batteries, you need to set standby to 0, then it will not hibernate after sleep.

I am not sure about hibernatemode, i think is best you leave as the default value 3.

I realize I may not be applying these Terminal commands correctly. Do I need to un-plug and apply them in battery mode so as to make them function in that scenario, then plug-in and re-apply them to stick them to that mode?

Well, I knew it was too good to be true. These Terminal commands had no effect on my MBPr. It was "groggy" waking up again after an hour and a half nappy.

So much for that. Thanks, though.

OK.   Was away for a day but now back to try to fix this....

Set to 'sudo pmset -a autopoweroff 0' tonight and will see what happens when I check in the morning.

I hope this works....this problem is getting kind of annoying...

Will report in morning....

Problem solved!  All I did was set 'sudo pmset -a autopoweroff 0' and the computer behaved as it used to.  It didn't go into hiberation while sleeping on AC power and it woke up instantly this morning without referencing any disk image.  Great!

Thanks everyone!  Hopefully Apple will issue a fix for this soon....

Even though it's now working the way I want it to with regard to sleeping and not hibernating by setting autopoweroff to 0, I should note the following....

When the computer is sleeping when plugged into AC power, unplugging AC power will wake the computer for about 20 seconds before it goes back into sleep mode on its own.  Same thing when plugging back into AC power when sleeping in battery mode.  It wakes up, then goes back to sleep after 20 seconds or so.

This is kind of annoying and it did not do that before.  I could plug and unplug AC power to my heart's content when the computer was sleeping in the past, and it never woke up for any of those actions.

Anyone have an idea how to fix this part of it?  Is there some 'wake' parameter that needs to be changed?

After dealing with this complete and utter fail, I have come to only one conclusion--it's time to contact AppleCare and just ask for a complete replacement MBPr. It seems really the only way to get the full undivided attention this issue needs. I don't know about anyone else out there, but I paid a lot of hard-earned money for this, and was promised above anything else, the instant-on capability. This was really my top priority and a feature they promised on-stage at the reveal. This is not what I have now. If enough of us demand replacement computers, perhaps the message will get through. It's squeaky wheel time.

@Summer Storm Pictures.....

I totally understand what you're saying.....and far be it from me to defend any hardware manufacturer, Apple or otherwise.  But they all make mistakes and all have their pros/cons.  For me, since I own multiple iPhone, iPads, iPods, etc, an Apple laptop was the next logicl choice to complete the ecosystem.  Even with its problems/idiosyncracies, Apple is still a superior overall experience for me and my family so I don't regret jumping over the fence to the Apple side.  That being said, I'm quite disappointed by this because it all boils down to one thing:  quality control.  This was entirely avoidable with proper pre-release testing.

I think Apple's main problem right now is that they're losing focus on one of their historical primary selling points: a great customer experience start to finish.  Whether it's bugs in OSX, hardware problems, putting exciting new products out that they can't ship for months, mismanaging their supply chain to miss holiday sales and **** off investors, bad OS patches, etc.....they're losing a very important competitive differentiating factor here.  I don't expect them to be perfect, but the things above are all solvable problems that they need to get attention on....quickly.

With regard to your laptop....you can certainly turn up the heat on them and go for a new machine, but my guess is that they'll first offer to re-install Mountain Lion for you, so I would be prepared for that.  If that doesn't work, then I think you have a pretty good case to raise holy **** and get a new machine because at that point all reasonable options would be exhausted.

Let us know in this thread how it turns out....I'm very curious to see how they handle it.

John

@chocobanana...

Yup.  It's a bummer.  Not sure how to fix that short wake up time after plugging/unplugging AC power, but I can deal with that until a fix comes out.  I don't plug/unplug often during the day.  My main goal until a fix was to stop the sleep-to-hibernation issue, which the autopoweroff change did.

I am going to call them though to follow up on my open case and raise some noise about this.  Apple has to learn that OS patches are supposed to fix problems, not introduce new bizarre issues.