prezzy77 wrote:
Hi all.
I am having the same issue on my 2012 Non-retina MPB.
I reported the issue to my mac protection support in November.
After some diagnostics at the rapair shop I had my disk fully wiped and it was the 12C3012 that was the supposed culprit (with no explanation).
From that time it ran OK.
But a cuple of weeks ago I ran software update again and the issue came back.
I again spoke to apple care, but this time to more technical people.
This time I had a very straight response: it's supposed to do this.
The 12C3012 adjusts the power/sleep behaviour to make the power drain profile compliant with an EU directive.
It's "The European Commission's Ecodesign Directive (2005/32/EC) for reducing the environmental impact of energy-related products (ErP for short)".
It specifically relates to Lot 6 (standby and off-mode- EC 1275/2008)
You can read a bit more about it on: http://www.powerint.com/green-room/agencies/ec-eup-eco-directive
So the only "bug" in this whole thing is that there is no mention of this behaviour being introduced.
Hope this answers some questions.
Mick
This part is correct and no one is contesting that. However, there's still a bug with the setup they introduced. The bug is as follows.
Hibernation is only entered when on sleep for 4 hours AND power adapter is plugged in. Without the power adapter plugged in, the system never enters hibernation which is not what pmset shows. Hibernation is when the system state in RAM is written to hard disk in the hibernation file and then all power is shut off (that's why the system loses very little power when it's in this mode but a lot more when it's in simple sleep (the mode where the system state is resident in RAM and the system keeps RAM powered up). Now, why would anyone think that it makes logical sense to enter this mode when you're plugged into ac power but not when you're on batter. Stupid reason... the system doesn't need to maximize battery power in this state because it is connected to a valid power source. So, just as pmset indicates, hibernate should be entered when both batter and ac profiles are in use. That would maximize the battery life the most AND provide less power drain to the ac power source coming in.
Now, second bug. The system wakes from sleep when the ac adapter is plugged in or unplugged from the system. More than likely it does this to switch pm modes and know when it's on the ac power profile or when it's on the battery profile. There's one glaring issue with this. By doing this, it defeats the purpose of the system entering the deeper hibernation and maintaining better battery life because now it has to wake up, switch profiles, and start counting down again before it can enter hibernation. That's a problem because now it'll waste battery power while in sleep (because it has to power the RAM) before it can enter hibernation. So, again, why wake it? Stupid... Let it remain in hibernation once it enter that state until the user triggers a clamshell open or a power button press. How hard is it to code the pm settings like this? Here's another problem this type of behavior leaves the system susceptible to. The system doesn't know when the ac adapter is unplugged from the wall or from the laptop, meaning that if there's a power outage or something interrupts power to the adapter, the system again wakes up to switch power profile modes. Now imagine if power was unreliable (like it can be in the EU countries). Now you have a laptop that's constantly switching modes, causing power loss in the battery, causing more wear and tear on the battery, and also causing wear and tear on the hard drive having to spin up and down all the time on non-SSD equipped systems.
Like I said, Apple engineers didn't think very dynamically and clearly when they wrote OSX's PM abilities. Back to the old drawing board for them I guess.