-
All replies
-
Helpful answers
-
May 9, 2014 11:05 AM in response to comfortablynumb002by frame_of_mind,I want to have a case where the computer goes to standby, and only after a couple of hours it goes to hibernation. Can anyone tell me if it is possible to do that.
That's what the MacBook Air is supposed to do under normal operation. If we knew the answer to this question, then this thread would be closed.
-
May 17, 2014 12:40 AM in response to frame_of_mindby alessio85,The problem seems to be fixed after the last update.
Two days and o suspicious wake up.
-
Jun 3, 2014 8:30 AM in response to alessio85by Perewernykruczenko,Not entirely. I have upgraded XQuartz to the latest v2.7.6 and installed all OS updates avalable as of May 27, 2014. Yet, after using Inkscape for a couple of hours and closing the lid, my laptop woke up after three hours of hybernation and failed to go into the deep sleep mode. The log was filled with usual "Wake reason: ?".
Everything was normal after that. However, I did not run Inkscape. Since I use Inkscape only sporadically, I can't tell for sure if Inkscape is the actual culprit or not. So far, both my incidents occurred after using it though.
-
Jun 10, 2014 10:14 PM in response to Perewernykruczenkoby kutlan,there is a fix released just for this case. did any one tried?
http://support.apple.com/kb/DL1748?viewlocale=en_US&locale=en_US
-
Jun 11, 2014 1:44 PM in response to kutlanby frame_of_mind,Unfortunately the issue persists even after the update.
-
Jun 13, 2014 5:50 AM in response to frame_of_mindby Mike Angelichio,Unfortunately, my computer is now worse. Freezes upon lifting the screen.
-
Jun 14, 2014 3:39 PM in response to rcolonescuby ondrafromczech,Hi,
I have MacBook Pro 13" retina, i5, 16GB, 256SSD. I have it one mont and I am dealing this issue with apple support maybe 14 days.. We tried everything you described here - SMC reset, PRAM, NVRAM reset, systemconfiguration folder deleted, safe boot etc. Then they told me to erase and reinstall system, maually restore all data and install apps again.. This is exactly what I hated about windows. I guess it won't help anyway so I am not going to do that. I will try to uninstall Avast but that's a stupid solution :/ I like when it goes to standby mode and in 3 hours to hibernation. It makes sense.
The biggest problem for me is that wakes up when my mac is on the cover in my bag and it almost burned!!
Hope Yosemitee will resolve this but it is still too far..
-
Jun 15, 2014 11:13 PM in response to rcolonescuby onmomo,"Wake reason ?" issue is still not resolved for me after the recently released MBA firmware upgrade. Avast is not installed.
Ubuntu here I come...
16/06/14 04:52:40.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 673 us
16/06/14 04:52:40.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds
16/06/14 04:53:05.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:53:05.000 kernel[0]: Wake reason: ?
16/06/14 04:53:05.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:53:05.000 kernel[0]: AppleCamIn::wakeEventHandlerThread
16/06/14 04:53:05.000 kernel[0]: AppleHSSPIController::HandleMessage Device Wake by Host
16/06/14 04:53:05.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 180466 us
16/06/14 04:53:05.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 2 milliseconds
16/06/14 04:53:05.000 kernel[0]: ARPT: 111987.630522: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
16/06/14 04:53:05.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:53:05.000 kernel[0]: AppleCamIn::wakeEventHandlerThread
16/06/14 04:53:10.000 kernel[0]: AppleCamIn::handleWakeEvent_gated
16/06/14 04:53:10.000 kernel[0]: AppleCamIn::handleWakeEvent_gated
16/06/14 04:53:57.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:53:58.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 673 us
16/06/14 04:53:58.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds
16/06/14 04:54:23.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:54:23.000 kernel[0]: Wake reason: ?
16/06/14 04:54:23.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:54:23.000 kernel[0]: AppleCamIn::wakeEventHandlerThread
16/06/14 04:54:23.000 kernel[0]: AppleHSSPIController::HandleMessage Device Wake by Host
16/06/14 04:54:23.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 181174 us
16/06/14 04:54:23.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 2 milliseconds
16/06/14 04:54:23.000 kernel[0]: ARPT: 112066.069968: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
16/06/14 04:54:23.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:54:23.000 kernel[0]: AppleCamIn::wakeEventHandlerThread
16/06/14 04:54:28.000 kernel[0]: AppleCamIn::handleWakeEvent_gated
16/06/14 04:54:28.000 kernel[0]: AppleCamIn::handleWakeEvent_gated
16/06/14 04:55:15.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
16/06/14 04:55:16.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 703 us
16/06/14 04:55:16.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds
-
Dec 22, 2014 11:47 PM in response to rcolonescuby paulmeyers42,Did anybody find a solution to this? I'm running Mavericks 10.9.5 on a late 2013 Macbook Pro Retina 13" and seeing the same issues.
-
Dec 23, 2014 8:00 AM in response to paulmeyers42by MicroDev,Changing the sleep modes fixed this for me under Mavericks. There's been a bunch of people offering different settings but this is what did it for me:
sudo pmset -b standby 0
sudo pmset -b standbydelay 0
sudo pmset -b hibernatemode 25
Under Yosemite, the default settings seems to work okay and I have not experienced the problem again. This is also while running Avast and other background daemons.
-
Dec 23, 2014 9:27 AM in response to MicroDevby paulmeyers42,Thanks. Since you're setting standby to 0, that basically disables the standby mode right?
-
Dec 23, 2014 9:52 AM in response to paulmeyers42by MicroDev,Basically these settings force the system to hibernate, rather than sleep, immediately (standbydelay 0). This writes the memory condition to disk and removes power (see man pmset 'hibernatemode = 25'). For that to work, standby must be set to 0. The -b switch only applies these settings to the battery power settings.
-
-
Dec 29, 2014 9:50 AM in response to MicroDevby paulmeyers42,I tried changing the standby delay to 6040800 for all and that seemed to do the trick, thanks.
-
Mar 13, 2015 10:59 PM in response to spmudirajby Andreas Kahl,Thanks for all the tips. With my MacBookPro, the problem now seems to be resolved. I followed a variety of tips and let the computer alone over the night in standby. This morning I reopened it and battery was still at 100% - great. Before that, the battery would have been at 10%, the laptop would have been very warm from all the wakes.
What I did:
- Uninstall XQuartz
- sudo pmset -a standby 0
- sudo pmset -a standbydelay 0
- sudo pmset -a hibernatemode 0 (I do not want SafeSleep - this simply writes 8GB to my flash and takes a lot of time)
Here are my current settings:
pmset -g
Active Profiles:
Battery Power -1
AC Power -1*
Currently in use:
standbydelay 0
standby 0
womp 0
halfdim 1
hibernatefile /var/vm/sleepimage
darkwakes 0
networkoversleep 0
disksleep 10
sleep 1
autopoweroffdelay 14400
hibernatemode 0
autopoweroff 1
ttyskeepawake 1
displaysleep 10
acwake 0
lidwake 1
