-
All replies
-
Helpful answers
-
Nov 30, 2013 12:24 PM in response to rcolonescuby alessio85,A friend of mine suggested me this software: http://www.jinx.de/SmartSleep.html.
I have not tired yet.
-
Nov 30, 2013 12:54 PM in response to Hermespdxby dr-grim,Ahhh.... that could be it.
I used to run Avast - I am now running Avira for anti-virus.
That could have been the trigger that fixed it...
Anyone else tried that?
-
Dec 1, 2013 1:23 AM in response to dr-grimby rcolonescu,Uninstalled Avast yesterday and hapilly reporting first night of proper "sleep". Opened the lid this morning with 100% battery.
Will give it a few more nights before declaring it fixed.
-
Dec 1, 2013 3:35 AM in response to rcolonescuby Hans Kohlmeyer,I do not have Avast installed and still have the issue. I use ClamXav for anti-virus. I had the issue even after a clean install (MBA 2013).
Apple need to fix this. It never happened on previous OS X releases, only with Mavericks. It is an OS bug.
What puzzles me is that once in a while the systems deep sleeps, even with all SW running as usual.
-
Dec 1, 2013 8:07 AM in response to rcolonescuby xes13,I agree with Hans Kohlmayer ... this did not happen in previous releases of OS X.
-
Dec 1, 2013 12:07 PM in response to xes13by VAXMaster95,I don't believe this issue is linked to any 3rd party software. I have the "self-waking" issue and I don't use Google Drive or Dropbox; my AV is Norton.
Applying the prior mentioned "band-aid" of:
sudo pmset -n standbydelay 604800
has avoided the self-waking issue for on my 2013 Air (i7/128GB). There is slight penalty for battery but it is rather small (~5% drop per 24 hours).
-
Dec 2, 2013 1:53 AM in response to rcolonescuby Hermespdx,I agree with most opinions here---essential system bits such as power management should never fall prey to third party software like this... the bug is in OS 10.9. Until Apple offers a solution, workarounds listed above intended only to keep Maverick's sanity in check.
-
Dec 2, 2013 6:45 AM in response to rcolonescuby jasonlancaster,Confirmed that uninstalling Avast fixes this problem for me. After doing so, I reset my delay using:
sudo pmset -b standbydelay 600
100% upon opening computer both this and yesterday AM. Thanks for the suggestion.
-
Dec 2, 2013 2:11 PM in response to jasonlancasterby Swedish Frog,I had Avast too; I've uninstalled it and we'll see if that fixes the problem. A few people here say they have the problem without Avast, but does anybody have this problem who doesn't have some kind of AV installed?
-
Dec 2, 2013 2:35 PM in response to Swedish Frogby fskirschbaum,I did not and do not have any AV software installed and did not remove any software to fix the issue.
-
Dec 3, 2013 1:11 AM in response to jasonlancasterby rcolonescu,Reporting third day of deep sleep after uninstalling Avast.
This is definitely a Mavericks issue since everything worked well on Mountain Lion. For those not using Avast, experiment with other memory reisdent apps, the OS seems to be too sensitive to wake requests.
-
Dec 3, 2013 6:11 PM in response to rcolonescuby Swedish Frog,Removing Avast seems to have fixed the problem here, too.
Does anybody care to link to this discussion over at the Avast user forums?
-
Dec 16, 2013 5:03 AM in response to rcolonescuby MarkNew,I have the same problem as well on my MBAir mid -13. But this issue started only a few weeks ago, and I've owned my mac since early summer, so I'm thinking that it might be a third-party software-issue after all?
I'm trying to think which of the apps that I've installed that could have caused it, and Avast is one of the later additions. Also, NoSleep. I've uninstalled both just now. I had no issues with Dropbox.
Could someone tell me exactly how I go about this "sudo pmset -b standbydelay 600" procedure? If it's necessary to do that command? I'm not very good at using the terminal (I know how to open it, that's about it). Thanks!
-
Dec 16, 2013 7:23 AM in response to MarkNewby jasonlancaster,MarkNew, you should uninstall Avast. As many have mentioned, this tends to fix the problem. If you want to tweak some terminal settings you can but it won't actually fix the problem. To do that, you paste that command into terminal.
-
