I know that there are several threads about battery life in the General forum, but I decided to create a new one, cause I want this thread to take a different direction, and actually help the owners, which are having problems with kernel wakelocks as me.
So... here it goes. I decided to make a test by using my phone mainly as a PHONE ! From the screenshots you will be able top see exactly what I did with the phone for the last 60 hours. Just to mention that my phone ISN`T ROOTED. Wifi sleep policy set to ALWAYS ; auto brightness ; power saver on except 30 minutes when I wanted a brighter display at direct sunlight ; Auto Sync on BUT - almost everything set to sync off or manual, except weather, gmail (mail and contacts) and one more mail sync using the mail app. Used some internet, made some photos, listened to some music, checked mail after notifications, refreshed blinkfeed couple of times just to go through the smartphone headlines, checked battery usage and software update like 100 times lol - and there are the 2+h of screen on. I don`t use facebook, twitter etc.
And now comes the most important part and the reason I started this thread in the first place. I got like 4 hours of held awake time. In the screenshots provided you can see where these hours exactly came from. I`m absolutely sure that HTC One can manage to achieve like 3 full days of normal phone usage if it wasn`t for those sick wakelocks I`m getting (and I`m sure most of you are getting too). I know all of you have read that "7 hours screen on time" and saw the screens from some guys with 7+ hours screen on. If you pay close attention you will see that their devices worked for more than 10 hours and they got less than 10 minutes of Held Awake time. What I`m trying to figure out is how they achieved such thing.
One more thing I would like to point out if someone decides that 4 hours of held awake time are something normal for a 60h usage. Keep in mind that phone lost 1% per hour while I was asleep, which I don`t think is something normal, cause I read alot that people are loosing like 3-4% for 10 hours during the night (someone even mentioned 1%).
So basically please use this thread to discuss any wakelocks (mainly kernel related) you have and ways to get rid of them. There are alot of threads going on in xda about almost every single wakelock I`m experiencing, but I think the info is different for every phone out there. I tried almost every suggestion, but without any good result.
Here are some screenshots from Gsam Battery Monitor, BetterBatteryStats, and Battery in Setting.If you like to see a detailed info please use the dropbox link. I won`t discuss every single screenshot I made, but just want to point out two interesting things I noticed. Although facebook app is TOTALLY disabled in my phone, I still have it as a working process that is causing wakelock as you can see in screenshot 13 in dropbox folder. And also I have turned every single option in Maps to off, except first option (Google`s location service) in Settings>Location.
https://www.dropbox.com/sh/k7reupon5dcy42p/a4VNWyJLGJ
P.S. I`ve heard that with 4.2.2 some things are fixed, or at least not causing so many wakelocks, but we`ll have to wait and see.
So... here it goes. I decided to make a test by using my phone mainly as a PHONE ! From the screenshots you will be able top see exactly what I did with the phone for the last 60 hours. Just to mention that my phone ISN`T ROOTED. Wifi sleep policy set to ALWAYS ; auto brightness ; power saver on except 30 minutes when I wanted a brighter display at direct sunlight ; Auto Sync on BUT - almost everything set to sync off or manual, except weather, gmail (mail and contacts) and one more mail sync using the mail app. Used some internet, made some photos, listened to some music, checked mail after notifications, refreshed blinkfeed couple of times just to go through the smartphone headlines, checked battery usage and software update like 100 times lol - and there are the 2+h of screen on. I don`t use facebook, twitter etc.
And now comes the most important part and the reason I started this thread in the first place. I got like 4 hours of held awake time. In the screenshots provided you can see where these hours exactly came from. I`m absolutely sure that HTC One can manage to achieve like 3 full days of normal phone usage if it wasn`t for those sick wakelocks I`m getting (and I`m sure most of you are getting too). I know all of you have read that "7 hours screen on time" and saw the screens from some guys with 7+ hours screen on. If you pay close attention you will see that their devices worked for more than 10 hours and they got less than 10 minutes of Held Awake time. What I`m trying to figure out is how they achieved such thing.
One more thing I would like to point out if someone decides that 4 hours of held awake time are something normal for a 60h usage. Keep in mind that phone lost 1% per hour while I was asleep, which I don`t think is something normal, cause I read alot that people are loosing like 3-4% for 10 hours during the night (someone even mentioned 1%).
So basically please use this thread to discuss any wakelocks (mainly kernel related) you have and ways to get rid of them. There are alot of threads going on in xda about almost every single wakelock I`m experiencing, but I think the info is different for every phone out there. I tried almost every suggestion, but without any good result.
Here are some screenshots from Gsam Battery Monitor, BetterBatteryStats, and Battery in Setting.If you like to see a detailed info please use the dropbox link. I won`t discuss every single screenshot I made, but just want to point out two interesting things I noticed. Although facebook app is TOTALLY disabled in my phone, I still have it as a working process that is causing wakelock as you can see in screenshot 13 in dropbox folder. And also I have turned every single option in Maps to off, except first option (Google`s location service) in Settings>Location.
https://www.dropbox.com/sh/k7reupon5dcy42p/a4VNWyJLGJ
P.S. I`ve heard that with 4.2.2 some things are fixed, or at least not causing so many wakelocks, but we`ll have to wait and see.