QUOTE(destEX @ Oct 7 2013, 09:49 PM)
i can't diagnose for you now because either the statistics was reset or you really don't have any problem with wakelocks, the stats will reset when you plug in the usb cable and plug out or when your battery level reaches more than 90%, is facebook app still listed as wakeup more than 500 times? fb app wakes up a lot but it doesn't cause any significant wakelocks at the cpu wakelock if you noticed.
powermanagerservice or any power manager related services is normal, it shows up as wakelock when you are charging your phone because a phone does not go into deepsleep when it is being charged. so it satisfies the term 'wakelock'
android system at 1m 35s is too insignificant right now. if you have problems with battery draining plz consult this thread again.
anything more than 30 mins after a day's use (12hr+) is significant enough to pay attention to.
Finally found the culprit for the significant overnight battery drain. To recap, I initially thought it was the facebook app that was causing this drain as it calls up more than a few hundred wakelocks overnight. But as destex has mentioned, it was highly unlikely the major cause of the CPU wakelocks because I still had my battery juice drained from 38% to 28% between 11pm to 4am with all forms of data connection off and fb notifications set to minimum
Ran wakelock detector at 4 am again and found the culprit - it's the NLP wakelock under Google services. A quick search reveals that NLP relates to some network locator and was then pinpointed to location services.
Solution from XDA forum and it worked for me so far
- Disable location services in settings
- open your wifi settings, go to advance then uncheck 'always allow scanning'
- open google now, disable location services there (xda forum even suggested to remove web history but in my experience, not necessary and I think web history is integral to the user experience of google now. Without it, its pointless)
After that, my battery juice was a rock solid 21% all the way till 830am this morning.
Seems like this issue affects android 4.3 significantly
This post has been edited by kuntakinte: Oct 8 2013, 09:17 AM