MacBook switches to hibernation during sleep

sudo pmset acwake 0

@bruclin...Yes, my wake and go back to sleep time is about 20 seconds too. But as I said, I'm ok with that....for now.

You can find a lot of interesting info about these settings here:

http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/ man1/pmset.1.html

I don't know exactly what autopoweroff=1 does.....but I know having it at 0 fixed most of my problem for now. :-)

Hey all. I just got a new Macbook Pro: 2012, 13 inch, Mountain Lion, non retina display. I'm coming from a 2007 Macbook Pro so it isn't my first Mac.

I'm having the same problem:

If I close the lid, the MBP sleeps normally. If I leave it on battery power over night or for an extended period of time, it just sleeps and wakes up fine as all Macs SHOULD.

However, if I close the lid, plug it in to the AC and leave it for a while to recharge (like overnight), it goes into Hybernate mode. Which of course takes much longer to wake up.

Looks like this is a known problem with no solution yet.

If I don't see a solution in the next week or so, I guess I'll take it in for service and see what they say.

Cheers from Nashville, Tn.

The following is from an "off-the-record" conversation with an Apple senior tech who was a bit more forthcoming:

This is a known issue with the engineers at Apple.

That's the good news.

The bad news is that it is a problem that is "baked in" if you will--at the factory assembly level--and that's from where any fix will have to come.

It is similar to an issue with a previous model of MBP's a few years back with a bad NVIDIA chipset. Adjustments had to be made at the factory assembly level to fix that issue.

Same here. Your only solution is to get a completely newly built replacement right off the production line--where adjustments have been made.

Fortunately for those of us who custom ordered their original machine, this will be automatic, but for those with "standard" configurations, you will need to be certain that any replacement is newly built at the factory, not from the warehouse.

Hope this helps.

Thanks so much for the info! Sounds like I'll just have to live with it for the life of my machine. Sounds like way too much of a pain to try to convince support people about the details of this issue even after they revamp their production line. :\

Yes, thanks for the info.

That's a bummer, but I guess I do have a work-around. I use mine during the day for work with an external monitor. So, I can just let it charge while I use it during the day and leave it on battery power over night.

But after the holiday craziness is over, I will take it down to the local Apple Store and start the complaint process so I can hopefully get a new, working unit in the upcoming weeks/months.

@Summer....Thanks for the update.

I would have to agree with @Kenneth on this one...Convincing Apple that I want a new machine due to this issue sounds like a tall order unless I end up barking up just the right tree.....and doing it long and hard at that. And even then....I imagine that this would have to be acknowledged (somehow) as an "official" issue before they would do anything. I could be wrong having never dealt with Apple on an issue like this...but I can't see them easily conceding on this one and handing me a new Mac.

What this doesn't explain is why the machine worked perfectly at one point, and then broke after an OS update. Which leads me to believe that it could very easily happen again in the future if a bug slips into another update.

So for me, I won't bother with digging for a replacement. After I made the setting changes mentioned earlier in this thread, the machine is working satisfactorily for me now considering my usage style. I don't have a need for hibernation mode, so shutting it off permanently is fine with me.

I have this exact same probelm and the exact same MPB (mid 2012, I bought mine in June). I took it in 7 times now. They replaced the RAM twice, hard drive+cable, logic board, top case (sleep sensor), and battery, plus wiping the drive and reinstalling the OS a couple times...to no avail! Since they can't replicate it in-store, they basically don't believe me and say they won't replace it or repair it further. [I've posted this story on a couple related threads]

I was hoping that it was just an update bug but if it's like Summer says and I need an entirely new system...gah. The guys at my local retial store are sick of me coming in, so maybe I'll give apple a call. I was told 3 times that I was going to get a replacement computer "if this fix doesn't work" and I have yet to get one. I'll be sure to update if I do.

Hmmm. I have an appointment to call support tomorrow. I'll post the outcome.

Mine is very easy to recreate:

1) Close the lid and let it go to sleep

2) Plug it in to charge it

3) Wait overnight

It goes into hibernate mode 100% of the time, although I'm not sure how long it takes.

If they won't help me because they can't recreate it, I will start timing how long it takes to hibernate. But hopefully it won't get to that.

Mine is failing just like yours, but they're unable to recreate it...I'm assuming because they're not leaving it untouched and plugged in. As others have mentioned, it does not hibernate on battery.

I was just going to give up and live with it, but after a heated exchange with the store manager today, I'm determined to prove him wrong, lol.

I haven't timed the sleep to hibernation, but I know it's roughly 3-4 hours. I'm going to camp in the apple store for 4 hours with my computer plugged in and have one of the "geniuses" open it. Since I can recreate it like this 100% of the time, I am confident they'll have a hibernation screen staring them in the face.

Fortunately, I have the time to kill and the determination to make snarky managers eat their words.

I sure hope you have better luck than me!

That's really too bad! That's one of the 2 or 3 biggest benefits of owning a Mac: Open lid, work, close lid, repeat.

Exactly the point of basically this entire conversation. More than anything else, all of us who threw a lot of cash at Apple for a "pro" piece of equipment--we didn't "settle" when we bought, why should we settle now?

Apple more than pitched this "instant-on" feature--not only with the MBPr, but with the Air as well. This is a selling point--other than the high-res screen.

These machines run on RAM. They are fast. There's no excuse for this "instant-wait" issue.

I owned a 17-inch mid-2010 MBP with a hard drive--and it truly was "instant-on." I miss that machine greatly and at one point seriously considered returning this MBPr to get TWO of those 17-inch models for what I spent on the MBPR.

Never again will I jump in first for a new model. Just like the iPhone 4S and potentially the 5S, and my second iteration 17-inch MBP I owned, I will from now on wait until the mid-model.

I fear, more than anything else, that just like when Steve Jobs left Apple the first time, which was followed by mediocrity, now that Steve's vision no longer drives innovation, Apple will slide into mediocrity once again.

Oh, and the absolute added insult to injury? This MBPr "creaks." Yes, the so-called all-in-one unibody design actually creaks like an old 2007 when I pick it up from one side or another.

Mac 101

Sorry if I missed this earlier, but do you have the Retina version? I have the non-Retina version.

Yes, my 2007 15" MBP has been solid as a rock! The only reason I got a new one was because that monitor is flickering and starting to cause problems. I've read it cost $400 - $600 to fix it and there is no guarantee it would work like it used to. But I have thousands of hours on that MBP for personal use, and professional use as a Photographer and it has served me well without even one hiccup.

I've gone 2 or 3 months without even rebooting that machine and the only reason I rebooted is to perform software updates.

AAAHHHHHHHH! Apple support is telling me this issue is a FEATURE called Powernap!

I explained that what I've read about Powernap doesn't make sense, but they insist this is a FEATURE!

HAHAHAHAHAHAHAHAHA!