Currently Being ModeratedDec 2, 2012 3:34 PM (in response to JohnNY123)
Yes, I know I am trending a little toward the harsh side and so far I have not ignited any flame-back, which means this is a good group seriously looking to solve a real-world problem that can't hide in the shadows anymore.
I applaud your jump from the Win-world. Overall the Apple flavored world is much better, mainly because at least up to the last couple years or so, the hardware was both innovative and reliable. But, beginning around 2008, the Q-C problem was beginning to evidence itself. For me, I'd rather suffer drinking Apple-flavored Kool-Aid than deal with a kludged together windows machine. What I won't stand for though is to pay far above market price for a premium advertised piece of equipment with "pro" actually in its title, and then to suffer what I could get for much less money on the "dark side."
Apple has lots and lots of cash--lots of my cash. They can afford to throw a few bucks at quality control, both on the hardware and programming side. They are fortunate to be able to curate a closed gadget ecosystem with relatively few models and/or variations. They need to stop putting out things not much further along the development process than beta.
Anyway, my ranting speaks for itself and I sincerely want to be as happy as the day I pulled my MBPr from the box.
Currently Being ModeratedDec 3, 2012 4:00 AM (in response to Summer Storm Pictures)
Agreed. I'm still a Mac newbie, so I'll keep the faith that they'll release a patch for this. If it goes ignored/unfixed, then the Apple gets a bite out of it.
More important though, which I think we both refer to, are the underlying problems at Apple (or any company) that cause this type of thing in the first place (poor testing, poor QC, etc). They certainly have the power and cash to improve the situation. If not, they risk becoming just another technology company in the crowd....instead of one of the premier innovative companies.
Currently Being ModeratedDec 3, 2012 6:12 PM (in response to chocobanana)
That's my 5 cent.
After a lot of experiments with "pmset" command, I found the same way to solve this problem: set "autopoweroff" to "0" with -a flag. And all it without any mention in "man pmset".
But, as I tried later "sudo pmset -b autopoweroff 1", it gave nothing.
So, when autopoweroff is "1" for both modes (AC and batt.), hibernate works as it should.
When autopoweroff is "1" only for battery power, computer newer hibernates in both modes. In other words, now it's not possible to hibernate mac when it's on battery and leave it in sleep mode without hibernate when it charging.
I'm sure, it's a bug in pmset utility.
Currently Being ModeratedDec 4, 2012 4:42 AM (in response to chocobanana)
A simple search will reveal this has been picked up in quite a lot of places:
Perhaps this whole "baked in" concept is coming back to bite them in the backside? If an update goes bad where there's no way to fix it other than a complete system replacement, that can't be a good thing.
Also, because it's taking so long to wake up, lately I find myself apologizing to colleagues when I bring out my MBPr to show them something. Some have even said without an apology, variations of "What's taking so long? I thought this was all RAM" etc. This can't be a good thing either.
Worst, it also makes me feel like an idiot for spendig so much money. My mid-2010 17-inch MBP with a hard drive treated me better. Oh how I wish I hadn't sold that thing off to Gazelle...(sigh)
Currently Being ModeratedDec 4, 2012 1:11 PM (in response to Summer Storm Pictures)
Yikes! Thank god I got my Macbook Pro 15" working to the point where I'm OK. I set autopoweroff and hibernatemode to 0, and the computer is behaving how I want it to now....with the one exception of momentraily waking and then re-sleeping when the AC power is plugged in or unplugged. I can deal with that hiccup until a fix comes out.....
Best wishes to everyone else who's trudging through this. It seems that different machines are affected differently and no one fix suits all.....so if I hear/see anything valuable, I'll post it back to this thread.
Currently Being ModeratedDec 4, 2012 6:23 PM (in response to egsl)
Hi egsl....I set hibernatemode to 0 to stop the computer from writing the safety sleep disk image when I close the lid (therefore making it sleep instantanteously again) and also to stop it from reading it when I open the lid (thus waking instantly). With the patch problems, this behavior was screwed up and autopoweroff alone didn't fix it.
Hopefully if Apple patches this (correctly), I can set both back the way they were and resume normal operations without tinkering with these settings.....but for now this does the job.
Currently Being ModeratedDec 5, 2012 1:29 AM (in response to Monsignor Paolo)
I personally am aware of the tradeoff for turning off hibernation. But I find much more valuable the ability to have instant sleep as opposed to first having the hibernation file to be written before sleeping.
Currently Being ModeratedDec 5, 2012 4:13 AM (in response to chocobanana)
Agreed chocobanana....I save my stuff constantly anyway and never slam the lid with unsaved app data. If it crashes or completely loses power under these circumstances then I won't lose anything anyway and the rapid sleep and wakeup time are more important to me. When Apple fixes this, I'll set all parameters back the way they were and hopefully they'll work. I heard there's a next OSX update in the works and released to beta testers, and maybe it will address this. Or make it worse! :-)
Currently Being ModeratedDec 6, 2012 8:22 AM (in response to JohnNY123)
@JohnNY123 To make things even more interesting, this other niggle seems to also be specific to certain machines, including, at least, my 2012 MBP.
I checked out to see if my 2010 MBP does this quick wake up-sleep cycle and it does not...
Currently Being ModeratedDec 6, 2012 8:28 AM (in response to chocobanana)
Yes @chocobanana......I would imagine that just what you mention is a total nightmare for a hardware/software manufacturers to figure out...especially when the machines affected span over years because Apple might have made different hardware/software/firmware tweaks over the years to these machines that are now tying into this sleep scenario. It must keep the developers and testers awake at night trying to figure out all the possible options and fixes.
Currently Being ModeratedDec 9, 2012 3:58 PM (in response to JohnNY123)
That's weird, i haven done any sudo command to solve this problem but for me connecting and disconnecting ac when my MBP is asleep results in waking up for 20 seconds, then going back to sleep.
So I think it has to do with something else. As of the autopoweroff command I haven't tried it yet, but il give it a try.
Just to know, what does the autopoweroff set to 1 mean exactly?
Hope this gets fixed in the next update