View Single Post
Old September 2nd, 2013, 01:35 PM   #410 (permalink)
Clueless Senior Member
GuitarG20's Avatar
Join Date: Jun 2012
Location: Texas
Gender: Male
Posts: 1,797
Device(s): Nexus 5, HTC One XL (retired)
Carrier: AT&T

Thanks: 888
Thanked 864 Times in 420 Posts

Originally Posted by Hadron View Post
Number of wakelocks is part of the story. The time awake is the key. In the last 10.5 hours my Android System has had 1441 wakelocks, has woken the phone 168 times, and kept it awake for less than 4 minutes. Google Services has had 336 wakelicks & woken it 96 times, but kept it awake for 7 seconds. When things went bad for me Google Play Services had actually kept it awake for 10.5 hours!

Good luck
Like Hadron said, waking up is one thing, but keeping awake is the kicker.

Waking the phone up for a couple of milliseconds could be something as simple as making sure your calendar is up to date and your contacts are synced. It's really when your phone is being held awake that the battery starts to get zapped.
The FAQ page has the answer to every question you could ever have about the forums, ever!

See something you don't think should be here? Use the report
GuitarG20 is online now  
Reply With Quote
The Following User Says Thank You to GuitarG20 For This Useful Post:
ChrisH76 (September 3rd, 2013)