Why do I get a grey screen and a loading bar every time I open my laptop?

Okay everyone, I finally got a reponse back. According to Apple, it is working as intended... frustrating, but I guess we'll have to live with it. Here is Apple's reply to my bug report:

28-Feb-2013 02:45 PM Apple Developer Bug Reporting Team :

Engineering has determined that this issue behaves as intended based on the following information:

After 4 hours of inactivity, your system may enter a deeper, lower power sleep state. It takes longer to recover from that than a shorter sleep does.

If this is still an issue, or you have questions regarding the resolution of this issue, please update your bug report with that information.

We are now closing this bug report.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.

That's not as intended : if i unplug the battery charger i got no grey screen and awake from stop is super fast.

This is a bug introdeced by the last firmware.

-A

Yes it is. Like it or not, this hibernation option was put in and enabled due to some EU power conservation standard. If you don't like it, simply open up a Terminal window and type in sudo pmset autopoweroff 0 and hit enter. Then put in your admin password to process the command. Once you do that, the hibernation option will be turned off and the laptop will go back to only sleeping when you close the lid.

Ok, thanks but why only if the battery charger is connected ?

Because that's how it set. Do pmset -g in Terminal and look at the settings.

Autopoweroff is the only recognized hibernation option in the AC Profile.

Standby is the only recognized hibernation option in the Battery Profile.

I don't know why Apple decided to have two naming conventions for this deeper hibernation, all I know is that Standby enabled only works in Battery Profile and Autopoweroff enabled only works in AC Profile. By default, Standby is disabled (you'll see Standby 0 when you do the pmset -g) and update DL1609 along with OSX update 10.8.3 released 2 days ago introduced the new Autopoweroff setting, which only works in AC Profile. So, when your charger is connected the system sleeps for 14400 seconds (i.e. 4 hours), the system will enter a deeper hibernation state. The same behavior would happen on battery after 4200 seconds of sleep if you enabled Standby by using sudo pmset standby 1. Anyway, disabling both of these options keeps that hibernation from happening. Simple as that.

Thanks !!!!!

heatwaveo8 wrote:

...

After 4 hours of inactivity, your system may enter a deeper, lower power sleep state. It takes longer to recover from that than a shorter sleep does.

Total poppycock. Unless it is something exclusive of the 2012 hardware.

My very beloved MBP, specs below, will soundly sleep for 8-12 hours or more and wake up instantly afterwards. No hibernation and NO fancy fiddling with the command line options on my part. Yeah, sure, battery wil have drained 10-12% or more, but let me repeat: NO HIBERNATION, INSTANT ON. No matter which Lion it is running, and all firmware patches have been applied.

Courcoul,

Me, too.

Even when connected to my Apple Thunderbolt Display - everything sleeps normally and wake-ups are quick, not going into hibernation.

Clinton

I agree, maybe it's hardware related, my old MBP 2010 have no "problems" .

-A

That's because you're not on ML. To my knowledge all MBPs with minimum 10.8.2 above 12C60 OS builds will exhibit this behavior. If you can do a pmset -g in Terminal and you see Standby and Autopoweroff listed, your system supports this feature. Until November 2012 when DL1609 was released which implemented this new EU power conservation standard, the Autopoweroff option wasn't in PMSET and Standby is disabled by default.

If you have the Standby option, make sure you're sitting on hibernatemode 3 and then enable it via sudo pmset standby 1 and let it sleep for the 4200 seconds that the default delay is set for while on battery and you'll see it enter hibernation. For the systems that have Autopoweroff as an option, this function is the same but for the AC power profile.

Now, since this is a EU required change that Apple had to implement, it's possible that the year models affected are only 2012 and newer.

And apparently it is... This is the description for the update off Apple's website.

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.

Ok, but why i get this only if i unplug the power cable.

I mean : if the computer is connected to the power supply i have no problems : close open, start stop immediately super responsive. If is not connected to the power supply the same super fast.

The behaviour just when the mac is closed and i unplug the power cable : i listen a mechanical sound from the body ( kind of superdrive sound ??) and the computer seems to go in stop, just open and it take time to awake.

That's strange. And : after last os update 10.8.3 i have no green screen till now.

?????

-A

OMG! Are you not listening to what I'm saying!??!

It's the way you're doing it, that's all. If you were to leave the system plugged in and open it, you'd get the same CD/DVD drive ejection sound and you'd see the same screen. When Standby or Autopoweroff is enabled, the ACWAKE being disabled seems to be getting ignored, so what happens is that when you unplug the power from it after it's entered hibernation, it actually triggers a wakeup of the system. The same thing would happen if you were to enable Standby and let it hibernate on battery power and then plug in the AC adapter, you'd hear and see the same thing. That's the behavior... I've explained this in like 5 or 6 threads about this same issue that people are finally starting to see because they obviously didn't notice it back in November when DL1609 was pushed out.

Hi, sorry,understand.Thanks.

Ya, sorry, don't misunderstand my tone, maybe I was a bit short, but I kinda ran out of ways to say the same thing and it seemed like you still weren't getting it. lol

Anyway, trust me, this is your issue. I've been working on it with Apple for 4, almost 5 months now... ever since it came out at the end of November.

Thanks again, at the moment i agree but that's absolutely boring behaviour.

Cheers.

-A