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

Hi Palmz43, don't get me wrong but it's good to hear the problem persisted even with a new macbook.

Can you recall when the problem started with the new MBP? Did it have the problem out of the box?

To be sure the problem is with the MBP update 2.0 I'm trying to find proof that the problem isn't with the MBP update 2.0. So i'd like to know if your new MBP had this update installed when you got it, and if the problem was present at that time.

I can't tell you because the computer had all of the updates out of the box. The only updates I had to do was for iPhoto and iMovie...

I have the same problem... June 2012 MBP. The grey screen started about a month ago. Went to the Genius Bar and they determined all hardware was good. They reset the power settings and said the next step was a reinstall of ML 10.8.2. The grey screen was back 4 hours later. I did a reinstall of ML that night and the problem was gone for about a week, until the software updates started. I did another reinstall of 10.8.2 and stopped the automatic install of updates. I have MBP 2.0 update showing in the App Store, but I am holding off on installing it. I am on day 3 without the grey screen, and if I make it more than a week, I will assume that is the culprit.

Skitchone,

Thank you for your post, very interesting.

I seem to match your problems (including a period in between where the MBP would not enter slepp mode on idle which has now ceased?) and time spent with very nice people on Applecare line to no effect.

I am now just turning off the power before putting to sleep for long periods (overnight) so it wakes instantly and will wait for next firmware update hoping this is solved.

Can I just confirm you are on MPB like myself (not Retina) and what is MBP 2.0 Update - is this the same as 10.8.2?

I currently show no updates available in Apple Store?

Skitchtone,

I also have the MacBook Pro June 2012 and I'm pretty sure that MBP 2.0 Update is the problem because I never remember having this issue before updating to that.

- Daniel 

Mike,

I have the MBP 13" from June 2012 which is not Retina. I have Mountain Lion 10.8.2 installed. The update I am talking about was orgianlly installed in the background when it was first released. It looks like this (from Apple support page):

MacBook Air and MacBook Pro Update 2.0

About MacBook Air and MacBook Pro Update 2.0

This update includes graphics performance and reliability enhancements and improves compatibility with some USB devices.
This update is recommended for all Mac notebooks introduced in June 2012.

Hi guys,

Its great to see all the comments from everyone. At least we are not alone.

I also have the MBP 15" standard (not retina) and it is 10.8.2.

As 'mikethebike2010' said i disconnect the power before leaving it over night, this speeds up the wake up alot!

It's a start atleast.

I check the app store for updates most days, but nothing.

Hopefully apple will become aware of the problem and send us a well deserved update.

Tom 🙂

Thank You!

It is good to know I am not alone. I have a mid 2012 13" MBP non-retina with this exact same problem. I have been looking for postings since I started having this problem (over a month now--not exactly sure when it began) and for some reason didn't find the thread until today. I have the exact same problem everyone else does. When connected to power mbp goes to sleep normally after closing the lid, but after 4 hours it stops sleeping (indicator light goes out). Eerily like the 14400 seconds indicated in AutoPowerOff Delay in the system power settings. I don't know what this means or what the connection may be, just something I discovered while poking around. When I open the lid--gray screen, cd drive sounds like it's starting, progress bar, pointer appears (won't move), brief spinning beach ball, and after 35-40 secs I am able to enter my password. I have been working with Applecare and have jumped through so many hoops trying to find the cause (and cure) to no avail. I have reinstalled 10.8.2 twice. I have created a seperate clean hd partition and installed 10.8.2 there. Still the same problem. Finally I was told it was probably a logic board issue and went to the local genius bar, had it replaced last week, and am still having the same problem. This only happens when I am connected to power. When I take the magsafe off (after 4 hours--indicator light out), the computer resumes sleep mode (wierd). When I am on battery power there is no problem. Oh, by the way, I recently noticed when I press my power button now, my computer freezes (don't know if it's related or when this began). Anyone else notice this problem, too? So glad to have found this thread. I am so relieved it is not just me. When I call Applecare Wednesday (I am working someone in level 2 support, I call him directly and he doesn't work again until then) I will advise him of this thread (he said he couldn't find anything about this problem). Will let you know what I find out. Obviously this is a real problem affecting a number of users.

Just wondering...Usually when I see these threads there is some action from users with lots of points like Dale on the first page (level 6 15K points) that have something useful to say. But his input had nothing to do with our problem. Obviously he wasn't paying attention or reading closely, and no other heavy hitter has commented since. What's going on? Why isn't anyone else paying attention?

Okay, did some research and after resetting pram power button now works properly. Also reinstalled ML 10.8.2 on second partition, did NOT install update 2.0, and now sleep is functioning correctly when I use this as startup disk. Thank you skitchone. I think you solved my problem. Man, this thread is hard to find. Took me a while again. Now it's bookmarked. Will show it to Applecare guy tomorrow. I hope Apple fixes this problem soon.

I've found that you can leave hibernate settigns alone. Using Terminal (in utilities), enter this:

sudo pmset -a autopoweroff 0

This will give you this message:

"WARNING: Improper use of the sudo command could lead to data loss

or the deletion of important system files. Please double-check your

typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort."

Type your admin password, then press enter. If you want to check that it's taken, enter pmset -g into terminal.

This setting turns off autopower off when both the AC adaptor is in, or it's running on battery power. This has solved the issue for me.

This thread has more on what happened:

https://discussions.apple.com/thread/4648868?answerId=20953288022#20953288022

Now this is weird.

I own a brand new MBP and on first use migrated my old Powerbook across to it from a backup drive (rumours out there that the older settings could have corrupted something.

I have shared the slow wake up when on mains power and left a few hours on my non R MBP.

I have also gone through a period where the MBP would NOT sleep if left on idle.

I changed Terminal command to a 24 hour delay on "Hibernate" (although Leodangers solution looks more elegant) but this did not help.

http://osxdaily.com/2012/07/11/mac-wont-sleep-heres-how-to-find-out-why-and-fix- it/

Infuriating!

I then got around to registering my machine with apple and up pops the mysterious MBP 2.0 Update which some have blamed for the current issue. It seems this can only be found on Apples product page when one has logge the serial no. (certainly didnt come up on a software udate enquiry?)
I had read online that all chnages were already incorporated in 10.8.2 but the page stated I should try to install and would be told by the installer if I didnt need it (together with a helpful list of firmware versions).

I installed MBP 2.0 (figured I had nothing to loose) and the installer simply got on with it.

No obvious changes to Firmware numbers I confess I could have missed something here.

I then tried to install 10.8.2 supplemental to be told my machine did not support this.

Aside from doing a couple of Time Machine Backups I have not changed anything else (too scared to muck around in Terminal any more!).

Machine now appears to be working properly and I am experiencing instand wake up after a nights sleep mains powered opening the lid.

I know this is not a solution as such but wanted to share a positive experience which could be quickly repeated by anyone else out there?

Let us know if it helps.

Do you have a Retina MBP? The issue seems to be with machines that are pre-retina, 2012. It appears that there are settings that work for he Retinals, but not the 2012s non-Retinas.

Presumably you can control Power Nap in your Energy Settings... I can't.

If I download that update, it won't work. Please post a link to the update, so others can try it... Glad it worked!

So, I thought I'd add my two cents to this thread. I have a new (for me) refurbished 15.4 MBP running 10.8.2, June 2012, that I've had for exactly a week. I'm coming from an older (late 2007) 15 inch MBP running 10.6.8. I noticed this problem immediately. I too am very happy to have found this thread as I was concerned there was some major mechanical issue with the hard drive. I did use migration manager to migrate over the settings from my old MBP, so was also a bit concerned something might have happened there. Here are my current pmset -g custom settings:

Battery Power:

lidwake 1

autopoweroff 0

autopoweroffdelay 0

standbydelay 0

standby 0

ttyskeepawake 1

hibernatemode 3

gpuswitch 1

hibernatefile /var/vm/sleepimage

displaysleep 5

sleep 5

acwake 0

halfdim 1

sms 1

lessbright 1

disksleep 5

AC Power:

lidwake 1

autopoweroff 1

autopoweroffdelay 14400

standbydelay 4200

standby 0

ttyskeepawake 1

hibernatemode 3

gpuswitch 2

hibernatefile /var/vm/sleepimage

womp 1

displaysleep 10

networkoversleep 0

sleep 10

acwake 0

halfdim 1

sms 1

disksleep 10

The settings in bold look a bit strange to me, based on the discussion so far. I'm very annoyed that Apple is ignoring this problem, and especially annoyed that a brand new computer should be set up this way out of the box. I'm reluctant to start chaning things myself, as I agree that Apple should fix the problem. So I'm adding to the chorus of discontent, and am considering contacting Apple Care with my displeasure.

I got a little lost in the discussion of the MBP 2.0 update. I'm assuming I have it. I did run App Store updates after getting the machine up and running, and frankly don't remember if I did that one or not. So am I understanding correctly that reinstalling 10.8.2 without doing MBP 2.0 update might do the trick? Of course, the machine came with no hard discs, so how would I go about doing that?

You can boot into recovery mode by holding Shift and R when you restart – this will allow you to do a fresh install of the OS. However, you'll have to watch out for the update, if that is the cause (it seems likely), and not install that.

To be honest, having been through the process over the last month, and tried many settings, reinstalls, resets etc, if you want the problem to go away, make the autopoweroff change in Terminal. You can easily put it back again when (if) an update comes from Apple. If in doubt, turn it back on after the next update to see if it's cured – it's what I'll be doing.

Enter Terminal (scray name, but it's fine, then do the sudo pmset -a autopoweroff 0 command. If you want to turn it back on, type sudo pmset -a autopoweroff 1

Mine was also a refurb (great way to get them a little cheaper). Approaching AppleCare is a good idea, but if you try some basic setting changes, it'll make it easier for Apple to narrow down the problem. It's not going to helps them if everyone goes in blindly after we've all spent so long narrowing down what appears to be the root of the problem.

We don't know that Apple are ignoring the problem – take a read through some of the posts here, and imagine trying to solve an issue based on them. Instead of being annoyed, try the setting tweak. If it works, be happy, and ask Apple why. If it doesn't, then you've not lost out anyway. Why not help Apple fix the problem... they're only human too (I assume).