Random sleep mode after Mountain Lion install

netreg: wow, you're right! i hadn't figured that out but that does work consistently - logging in before unplugging seems to do the trick. not sure what that tells us. also, doesn't help the times it comes unplugged accidentally. i like the magsafe adapters but they do practically fall out.

i sure wish i could edit my old comment. please everyone disregard my "some more clues" post from 22 august - my speculation hasn't held up, i think i was completely wrong about being related to the new "power messages" or whatever they're called that apps have to send now. completely separate issue i'm afraid.

are we all having fun doing free tech support? :\

Pressing control/shift/power also triggered the error on my computer. I then brought it to the mac store and luckily my 14-day warantee was still valid. They gave me a new computer; otherwise they would have had to send it to be repaired. They hadn't seen the sleep error before, but I was so thankful for this post.

APPLE! Please answer even ONE of the following questions:

WHERE ARE YOU AT ON THIS ONE?

There hasn't been even a whisper from your representatives here...FOR THE LAST YEAR!

Why are people who bought your products doing all of the work to figure out the problems that came with them?

Do you realize that we are working with limited resourcess and you are far better equipped to correct this problem?

Do you value the people on this thread?

Do you realize that the people at your "genius" bars are not equipped to deal with the problems on these devices?

Why are we not getting straight answers FROM YOU?

Is this problem beyond your ability to correct?

Do you have any suggestions?

Fuentecito wrote:

APPLE! Please answer even ONE of the following questions:

WHERE ARE YOU AT ON THIS ONE?

There hasn't been even a whisper from your representatives here...FOR THE LAST YEAR!

Why are people who bought your products doing all of the work to figure out the problems that came with them?

Because this is an Apple Users community.

Hey Csound,

You're right, but it is also...hosted by the mother company. Regardless, no moderators, no representatives period. You think they arent seeing what we write? The idea is to get this issue fixed for all the users that have this problem.

So if genius bars don't have the answer and there is nothing coming from Apple directly, please tell us what you suggest. Where is the appropriate place to cry for help?

Apple.com/feedback

In case nobody in the past year has done it, I shared our concerns and frustration with Apple via feedback. Perhaps we will hear something before this time next year.

Yeah I did the same yesterday via feedback as well. Hope Apple will eventually respond when enough people report the issue.

Also replied on feedback site. Everyone should do this. Better yet, if someone has an in with Lifehacker/reddit/engadget or other loud mouth geek forums, post it there. Maybe it would garner more attention haha. Its not like this is severe crippling behavoir, but it is annoying, and I think even more annoying is that no one from Apple has responded.

Expirobo, thanks for the suggestion r.e. resetting the SMC and NV Ram (we used to call it PRAM.) I tried with high hopes but it had no effect. Fortunately I had better luck with pmset. I'll elaborate in my next post.

Thanks isspin! pmset seems to have done the trick for my 2013 MBA.

I ran these commands to determine what my current settings were before making any changes:

pmset -c -g

pmset -b -g

I discovered that "sleep" was set to "1", meaning 1 minute. I have no idea how it got that way -- I don't seem to have any visibility into the value in System Preferences.

I found I could not set separate values for -c (charger) and -b (battery). Setting a value for -c set both values, while setting one for -b had no effect.

Since the problem was intermittent I will grow more confident over time. If the issue recurs I'll post again.

To sumarize, this eliminated the problem for me at least for now:

sudo pmset -c sleep 0

Hey Everyone

I'm one of those who suffered of the same problem last year with my MBP late 2011. I solved the problem that time and wrote about it on this thread, but seems it didn't work to others.

The solution that time was just reinstalling OSX without formatting. That just fixed the issue which was caused by a widget I used to have on OS 10.7 and older. The widget was called "Deepsleep" and it seems that the developer stopped releasing compatible versions for the new Mountain Lion.

Two weeks ago, I wanted to use that widget, so I went to its official website, downloaded the latest version there and installed it. Then the same sleep/hibernation problem was back.

I uninstalled the widget cos I realised that it was the reason for sure and reinstalled Mac OS again, but this time it didn't solve anything. I desperately headed to the Deepsleep's website and searched the support page there and found out a hint to return the a default setting that was causing the whole problem for me.

According to a PDF I downloaded from there I entered the following on Terminal:

pmset -g | grep hibernatemode

That is to check the "hibernatemode" value on the machine

then

sudo pmset -a hibernatemode X

with X replaced by the value of the hibernate mode to set. My choice was 3 according to a page I found online http://etherealmind.com/osx-hibernate-mode/

You can find even more result if you just Google this "mac hibernatemode desktop laptop"

I've been using my Mac normally and closing the lid to sleep several times a day for more than a week, and it's waking up just normally as I open it. I even happen to sleep it while the battery was lower than 5%, the Mac in that case went to hibernation mode after a while and woke up successfully.

Hope that works for you all.

Ayham

So this has been 2 weeks since I put my solution and no one else has given any feedback if it was any good or not.

Any thoughts?

I was experiencing this issue with my brand new mid-2013 13 inch air, and I just brought it to the genius bar.

I showed the tech the issue, reproducing it by sleeping the computer (with control-shift-power).

He deleted the sleep image and swap files, restarted the computer, emptied the trash, and it seems to have fixed the issue!

to get to the sleep image and swap file...

Open terminal:

-type "open /var"

-this will open the /var folder in finder, navigate to the "vm" folder

-delete all the files in this folder.

-you'll need to restart to empty the trash