2012 mbp - slow wake up from sleep after last mbp update

Excellent – really pleased! Interesting that it was already off on battery power. On mine it was on one AC and battery. Still, we have the same settings now, and great that it works.

Email sent to Apple, so will let you know...

This is exactly the problem I have been having with our mid 15" 2012 Macbook Pro non retina. So far there have been 3 trips to the Apple store repair shop. They ran full diags for 2 days with no trouble found, replaced the charger and then the motherboard. The problem still exists.

Our problems started right after the update talked about in this thread (which we told Apple).We even took a video of the issue and showed it to them.

Thanks for vindicating me, I was convinced it was the update that changed something.

This is a problem with all 2012 MacBook Pros that have applied the update DL1609 via Software Update. This update is called MacBook Air and MacBook Pro Update 2.0. The only fix that exists for this is to reinstall OSX and just not install this update when it shows in the available updates list in the AppStore. Just hide it until this issue is fixed by Apple.

If your OSX 10.8.2 version is anything after version (12C60) then you will have this problem. The problem is as follows. With the system asleep with clamshell closed, plugging and unplugging the power cable causes the system to wake up and go back to sleep. Additionally, leaving the system plugged into power for over 4 hours will cause the system to go into hibernation, but only when plugged in. If it's not connected to AC power while sleeping for that long, it will not enter hibernation.

Please call Apple and complain about this problem. I have been working with them for over a month and a half trying to get them to fix this and it's a major hand-holding process because they didn't initially understand the issue. Add to that the fact that they insisted that this problem doesn't exist and it just made it that much harder to get them to see the issue.

You need to call them AppleCare and let them know you're having this problem. Along with that, email the rep you're working with links to every Apple Support Forum thread you can find on this. Trust me, there are several with this same exact problem.

Glad autopower off is working for so many people. However, you'll notice you still have a slight issue – if you unplug your MBP from the AC adaptor before opening the lid, the light on the front will illuminate fully as the machine enters a darkwake. If you now open the lid, you'll find the screen stays dark, and won't turn on for about 40 seconds. Of course, the computer is still running far better than before chainging autopoweroff to 0, but I wasn't totally happy...

I made a TimeMachine backup, then booted up in recovery mode (hold cmd R while restarting). I then erased the hard drive, reinstalled the OS, then restored from Time Machine, just unchecking the box for "settings" (don't know if this bit is necessary, but wanted to try). With the laptop up and running again, I went to updates in the App store. There were three at this time – Safari, Camera RAW, and "MacBook Air and MacBook Pro Update 2.0 2.0". I set the two other updates going, but hid the "2.0 2.0" one (holding ctrl and clicking anywhere but on the update button).

My laptop is now running exactly as it should be. The only issue I had with turning settings off seems to have been losing my printers. All other settings are reset, but it's not an problem for me.

Here's the interesting bit... now I haven't applied the update, there is NO mention of autopoweroff or autopoweroff delay in pmset! Also, acwake is still at 0, but it seems to actually work now (as in my MBP doesn't wake when the AC is connected or disconnected). I've passed all this on to my Apple Senior Technician, so I'll let you know if I hear anything back... To me, it's as if this update is meant for the Retina and Air MBPs that have Power Nap, but is causing problems with our mid-2012 MBPs.

Glad to hear that this is an issue with the 2.0 update. Hopefully Apple will do something about this...

So glad I found this thread. Another thing I noticed along with the slow start up with gray screen and vertical progress bar is that it ha started going black in the middle of me working on it, I guess this it's just randomly falling asleep. I have a mbp mid 2012 btw

Software OS X 10.8.2 (12C3103) ... I don't know exactly what this means but maybe this mac is apart of the batch that's having trouble. I am in no way tech savy so I am intimidated when it comes to going and changing things in the cpu, hopefully Apple will fix this soon.

I don't think Apple will be fixing this problem anytime soon. I talked with a rep for a couple of days and linked all the threads that are popping up and he said that there is nothing wrong.

According to the engineer the update made it so that when plugged in or sleeping the computer would go into hibernation. I told him that my MBP does not go into hibernation when it is sleeping after 4 hours and only does it when it is plugged in. He had nothing to say...

Looks like the only fix to this problem is to reinstall OSX and hide the Apple 2.0 graphics update.

I was having this issue,

"With the system asleep with clamshell closed, plugging and unplugging the power cable causes the system to wake up and go back to sleep. Additionally, leaving the system plugged into power for over 4 hours will cause the system to go into hibernation, but only when plugged in. If it's not connected to AC power while sleeping for that long, it will not enter hibernation."

I got in touch with a technician who has told me the 2.0 update is what's making this happen and it's suppose to happen. He said while the computer is closed and plugged in it goes into hibernation, when you wake the computer from sleep it's common to hear the hard drive and see the load bar.

He also said apple did this to meet the energy standards of Europe.

Ya, except for one problem. The PM settings say that it should enter hibernation after 4 hours of sleep both on battery power and while plugged in. Currently it only works when it's plugged in. THAT right there is a problem! Apple needs to fix that because that's a big issue. If it's set to hibernate during both instances and it only does it in one, that's not right. New behavior intended or not (the plug/unplug thing during sleep) doesn't matter, the fact that this additional issue is there leads me to believe the idiots didn't program it right, much less test it thoroughly to make sure it behaved as intended.

Debra is correct - setting the autopoweroff to 0 is all you have to do. I had the same problem with the gray screen and scrolling bars after waking from deep sleep, and now, moving the setting from 1 to 0, the computer never goes into deep sleep, and it wakes immediately when I open the lid.

As noted in another reply, this does not fix the root of the problem; it is a workaround, but, despite AppleCare's warning, I doubt that any other "side effects" will appear because of this change.

It is a feature! 😁

Just received an interesting call from AppleCare. He said he closed my case number, because he got engineer feedback that this phenomenon was actually a feature in order to comply with the new European standby regulations. I think he was referring to this one: 1275/2008. He said furthermore all Apple Computers from 2012 on are affected (Can anyone confirm this?).

I asked him to reopen the case however because I encouter an actual problem due to this feature: When the MBP hibernates after 4 hours and I unplug it, it will wake and ask for my Filevault password (full disk encryption). In this low level state the MBP will not realize that the lid is actually closed and wait forever. That is actually somewhat dangerous because spinning harddisks might take damage if I put the computer in my back and start travelling.

Yep, the powerup issue when someone plugs/unplugs the laptop from power when these hibernate states are enabled is the cause of a lot of issues. If you don't mind, I'm going to take your additional info on this and also forward it to my corporate relations guy there so he can send it to his escalations team as well on the preexisting case he's working for me.

let me know if you need a case number or something

So I did my time on the phone today with AppleCare for the very same reason, the safe sleep debacle. After the rep told me there was no issue, I pointed him in this thread's direction and others, got on to a senior advisor, who sent a note to engineering, who then returned a response and confirmed this is a "feature" to conform to the European standard. The tech rep pointed me to this KB

http://support.apple.com/kb/HT1757?viewlocale=en_US

I told him that was ridiculous, why should I in the US be penalized for some ridiculous new EU standard. Also, one of the things I loved about the MacBook PRO before was the instant on from sleep, not my two year old Windoze work laptop comes up from hibernate faster than my Safe Sleep MacBook PRO that has WAY better specs.

And then there is the inconsistency of the battery and AC performance. If this is to save power, then why not have it do it in battery mode too? If I leave it in regular sleep on battery power for 7 days and deplete the battery some percentage, I am still going to have to plug it in the wall to recharge that lost energy, so its pay me now or pay me later, but you got put the juice in and pay me at some point in time.

It would be so easy to use the Time Zone in the system settings to see if the person was in the EU and should conform, and if not, ignore it. The Senior Tech rep said the only option is to log it on apple.com/feedback and that perhaps if enough people sent in their displeasure the engineers would review it, in the meantime, I guess I am doing the hack to "fix" my MacBook PRO. Thank goodness for the people that figured out how to fix Apple's mess up in this case, thanks

Ya, I fixed mine by hiding the 2.0 Update in System Updates, lol.

Regardless, I've actually enabled Standby on my 12C60 10.8.2 build of OSX and the behavior with Standby enabled is actually oposite of this. I now enter hibernate after 4200 seconds of sleep but only on battery. If I'm plugged in, it won't enter hibernation. The thing is, with this option enabled like that, the system now has that same wake up behavior when you plug/unplug it from power. I honestly don't have a problem with the deeper sleep hibernation. I just can't stand the waking up crap that doesn't need to happen and defeatus the purpose of the system entering hibernation in the first place. Why a Mac (in all it's advanced OS glory... ya right) has to wake up from hibernation to switch PM modes when you remove it's power source when Windows has been entering hibernation for years and never has to do anything to know what mode of PM it's in. That's just laughable that Apple can't do something as simple as this, but everyone there bashes Windows. lol to the max!