acwake 0 but it wakes up when I plug charger in/out, acwake 0 but it wakes up when I plug charger in/out, acwake 0 but it wakes up when I plug charger in/out

You might have issues with the charger, bad connector/cable, receptacle. Take it to the Apple store and have it checked out. If it is a faulty charger/connection you don't want it possiblby cause further damage

If you have AppleCare I would take advantage of that, there are number of things that have gone awry, and this sounds like a hardware problem, if possible see if you can borrow a computer from someone. I've heard of Apple doing loaners for time crunch repairs, as well as it could be a fairly quick fix. I would be backing up multiple times of day..just in case.

Go in to Apple, be very nice to the folks, and ask what they might be ablr to do for you, they tend to be very accomaodating. Be careful as to using different PUS's as they are not all the same some are 45 awtt, 60 watt, 85 watt. MBP 15 uses 85 watt, under pwering with a 45/60 watt can cause issues from not providing enough current, thus creating a possible problem augmentation.

Maybe there is someoe in the community that might have some suggestions on this issue that might give a fix of sorts.

Best of luck

Did you get a fix for this? I am having the same problem. Was it a hardware issue that needed to be replaced?

thanks

This is a problem with all 2012 MacBook Pros that have applied the update DL1609 via Software Update. This update is called MacBook Air and MacBook Pro Update 2.0. The only fix that exists for this is to reinstall OSX and just not install this update when it shows in the available updates list in the AppStore. Just hide it until this issue is fixed by Apple.

If your OSX 10.8.2 version is anything after version (12C60) then you will have this problem. The problem is as follows. With the system asleep with clamshell closed, plugging and unplugging the power cable causes the system to wake up and go back to sleep. Additionally, leaving the system plugged into power for over 4 hours will cause the system to go into hibernation, but only when plugged in. If it's not connected to AC power while sleeping for that long, it will not enter hibernation.

Please call Apple and complain about this problem. I have been working with them for over a month and a half trying to get them to fix this and it's a major hand-holding process because they didn't initially understand the issue. Add to that the fact that they insisted that this problem doesn't exist and it just made it that much harder to get them to see the issue.

You need to call them AppleCare and let them know you're having this problem. Along with that, email the rep you're working with links to every Apple Support Forum thread you can find on this. Trust me, there are several with this same exact problem.

is this confirmed? I am having the same problem with my computer (Mid 2012 MBP) and it's driving me bonkers. Help!

Yes, it's confirmed. I've been working with Apple on this for over 3 months. Please call AppleCare and report it/complain about it. The more calls they get, the more it'll drive them to fix it.

I discovered I have this issue last night. I'd noticed it happening but thought I was imagining it until I actually paid full attention.

My MBP definitely wakes on AC change despite having the setting set to off. It shows up as a darkwake entry in the logs.

I've also noticed that the logs show other darkwake occurences which appear to have stopped when I turned off "wake for network access" in Energy Saver Preferences. I'm doing testing on this before today and tomorrow so it's still TBC.

Why it would be switching on in the middle of the night for maintenance or network access when it's sleeping and I am too is beyond me. If I put it to sleep I want it to stay that way!

I've also logged a support call with Apple and have an in-store appointment on friday to, at the very least, log the issue as a problem.

BigGee42 wrote:

I discovered I have this issue last night. I'd noticed it happening but thought I was imagining it until I actually paid full attention.

My MBP definitely wakes on AC change despite having the setting set to off. It shows up as a darkwake entry in the logs.

I've also noticed that the logs show other darkwake occurences which appear to have stopped when I turned off "wake for network access" in Energy Saver Preferences. I'm doing testing on this before today and tomorrow so it's still TBC.

Why it would be switching on in the middle of the night for maintenance or network access when it's sleeping and I am too is beyond me. If I put it to sleep I want it to stay that way!

I've also logged a support call with Apple and have an in-store appointment on friday to, at the very least, log the issue as a problem.

That right there is 100%+ the reason why a lot of people don't know of this issue yet. They don't pay attention closely enough. You cannot imagine how long it's taken me for Apple to finally realize where the problems are with this behavior change they made.

I can also confirm the source of this issue is the Firmware Update 2.0.

I performed an erase and install of OS X 10.8.2 last week and re-applied all updates EXCEPT the firmware update 2.0.

I also restored all my content and Apps from Time Machine.

Once done, I tested the AC adaptor connection and the MBP no longer wakes when the AC adaptor is connected or disconnected.

I went into the store to explain the issue and they noted that their store models do the same thing. They recommended I call AppleCare and log it as a problem, which i'll be doing shortly.

DL1609 is not a firmware update. If it was, reinstalling an older version of the OS wouldn't fix this. Anyway, it's going to get harder and harder to get around this issue since the changes in DL1609 are also included in the 10.8.3 update, which blows. Please raise some **** with AppleCare when you call them. Thanks in advance.

I'm with you, it's a software update rather than a firmware update.

You're right, the firmware would remain unchanged even with an OS re-install because it's the underlying code to control the hardware.

With regards to Applecare, I sure will!

Any fix? Same issue here with md101 mid 2012

Not yet. The OS X 10.8.3 update includes this change. I logged a call with AppleCare and they advised there is no fix for it. I'm gonna log it again and record it as a problem with the 10.8.3 update.