Currently Being ModeratedJan 6, 2013 2:20 AM (in response to Summer Storm Pictures)
Day 2 and success, this time with 6-hours of sleep followed by instant wake-up.
The 6 Terminal commands set I assembled together (see my last post) seems to have worked--for me at least. If you decide to apply them, I strongly suggest you apply all 6 of them and in that order.
If day 3 (tonight) brings success as well, I'll follow-up post one last time.
My only "huh" comes from wondering why, with all the brainpower at Apple, how they couldn't come up with this.
Currently Being ModeratedJan 7, 2013 2:54 PM (in response to Summer Storm Pictures)
I ran these two days ago and so far I have not experienced the issue any longer. This might be promissing. I have a rMBP with Thunderbolt display and several USB devices running off the monitor USB ports. I have so far tested with machine plugged, unplugged, lid closed, open and extended periods of sleep (overnight) with good resuts. Thanks for the post!
Currently Being ModeratedJan 8, 2013 12:25 PM (in response to Rodney Gracia)
I too can honestly say I ran these commands 2 days ago and have no experienced any issues. Great work Summer Storm!!!This is very exciting and disappointing at the same time. Exciting that we might have a solution. Disappointing that apple couldn't figure this out.
Currently Being ModeratedJan 8, 2013 1:09 PM (in response to brferreira8)
Well it was definitely a group effort. Someone else suggested the pmset commands as did someone else suggest the page that detailed their use. All I did was to assemble them in a logical order that made sense...and then hope.
I am on day 3 now without problems. I hope to hear from others too. There looks to be 3 of us (including me) so far.
Also, something to note that should be obvious--if one ever does a power management reset either by using a utility like Mountain Lion Cache Cleaner, or manually, by shutting down and then holding down the shift-control-option-power buttons--everything will once again default back to the original settings, thus requiring another reset using this "coctail" of pmset commands once again. I know this just now as I did this using Mountain Lion Cache Cleaner.
I really was at my wits end and honestly was not looking forward to exchanging my MBPr with a new one--not at all. Worse yet, I was actually going to hold out as long as possible so that when I did do so, I'd get the next iteration of this model rather than just a switch-out to the same one. Worst case scenario, sell this to Gazelle and use the money toward a replacement/upgrade.
There definitely does seem to be a disconnect--or worse, a compartmentalization--between the engineers and the AppleCare/technical support staff, and it's not exactly good to witness the AppleCare staff being shown up like this.
Currently Being ModeratedJan 8, 2013 2:38 PM (in response to jstefanop)
I too decided to run these prompts too after taking my mbp to Apple a few days ago and them saying that I can send it out and they can run a plethora of diagnostics on the hardware to see if anything is wrong. Things have been running smooth as of now, but its only been 6 hours, which the mbp has only been asleep for 3, will keep you guys updated on how it goes, but from the rest of you, it seems very promising! Thank You very much Summer Storn for posting this find!
Currently Being ModeratedJan 8, 2013 5:59 PM (in response to shawnunder7)
I too tried these command and have not had a failure since, although I want to give it another test cycle or two that normally brings out the fault before declaring it good. (I've had false hope on it before). I'm running a recent, but not latest Mac Book Air.
Currently Being ModeratedJan 8, 2013 6:34 PM (in response to obscurebug)
What I'm finding a pleasant surprise is that this solution isn't going to be limited to just the MacBook Pro "Retina" model but to the Air as well.
Hopefully I'll report a successful day-4 tomorrow as well.
Currently Being ModeratedJan 9, 2013 7:51 AM (in response to Summer Storm Pictures)
Day 4: Closed my MacBook Pro 15-inch "Retina" last night and 6-hours plus later, I opened it up. It instantly woke up and was not "groggy" at all.--going right to the log-in screen.
Anyone else who is testing, please let us know of your succeess and/or failures.
By the way, for newcomers who do not want to scroll back and search for this set of Terminal commands, here they are:
sudo pmset -a hibernatemode 3
sudo pmset -a autopoweroff 0
sudo pmset -a autopoweroffdelay 36000
sudo pmset -a standby 0
sudo pmset -a standbydelay 36000
sudo pmset -a acwake 0
(The 36000 represents 10-hours in seconds and can be adjusted to your preference)
To check to be sure they applied correctly:
Currently Being ModeratedJan 9, 2013 1:30 PM (in response to Summer Storm Pictures)
I usually don't put my Retina MacBook Pro in to sleep mode, but when I do, I would notice that it would take some time to start-up again (~10 seconds).
After running the Terminal commands, I no longer experience this "lag time" to wake-up. I have no idea what the commands do, but they seem to work for me. Really nice job!
Currently Being ModeratedJan 12, 2013 12:19 AM (in response to jstefanop)
@jstefanop: very good analysis!
To set a few checked points clearly:
- black screen after wake up isn't related to any external display;
- is not limited to Retina;
- is not coming of any file corruption;
- not solved by any sort of system install.
It looks like a simple logic problem. Suggesting customers to reinstall a system is just…
Currently Being ModeratedJan 12, 2013 3:21 AM (in response to jstefanop)
It seems like the pmset commands work, but I don't see this as a real solution for the problem.
If I understand these commands correctly, they disable standby (hibernation after sleep mode, which writes the memory to disk and powers off the memory) and autopoweroff. Setting the standbydelay and autopoweroffdelay in these commands should not have any effect, as you disable them in the commands before anyway.
No wonder that the Macbooks wake up very fast now, as they keep the memory alive and don't hibernate to the disk anymore, but they also use more battery during sleep this way.
It's a nice workaround and should work for all of us I suppose, but the problem still exists.
By the way: I only had the problem of not waking up when the charger was connected, so I used these commands with -c instead of -a, which only applies when the charger is connected. Worked fine for me.
Currently Being ModeratedJan 13, 2013 12:04 PM (in response to Summer Storm Pictures)
@Summer: if you confirm your sequence of pmset kills this bug of [...secret word under NDA], then you should be carefull not to use
System Preferences > Energy Saver
since it may corrupt again the settings saved within the SMC.
If you have a chance to reproduce the initial bug, it would be a very good point to catch what
Then you will be able to compare to the settings you entered through a Terminal and see where
the error is.MacOS X 10.4.11 ⟶ 10.7
Currently Being ModeratedJan 20, 2013 6:00 AM (in response to jstefanop)
I've also had issues with sleep mode. Since shutting down bluetooth my problems have gone. The machine wakes instantly on opening the lid.
(I, like others, have reset the time for powernap to 6 hours)
Currently Being ModeratedJan 26, 2013 8:22 PM (in response to jstefanop)
Hmm, im now having another issue that seemed to arise sometime this week. I use the laptop moderately at night. I'd say from 8PM-Midnight, so about 4 hours straight. After about 2-3 hours the mbp literally will randomly freeze. Now im not talking about lagging, i mean full blown frozen, doesn't respond to anything. Have to power cycle the laptop and everything will go fine, but then once again the next day it will happen again.
Currently Being ModeratedJan 27, 2013 12:34 AM (in response to Summer Storm Pictures)
Has anyone tried running the pmset cmds and let it set for more than 10 hours? It looks like all you're doing is telling it not to sleep or standby for 10 hours, all it's doing is blanking the screen. This doesn't really fix anything so you may as well just set the energy saver setting to never sleep.