Related
My Evo battery is draining at a rate that is all together too fast. I took it off the charger about 3.5 hours ago and it has drained about 30-40%. I have not made a call nor used the net at all save for the receipt of 3-4 emails. I had a rooted phone but I reset the phone back to complete unrooted stock. I have not even so much as installed an app. What can I do about this?
turn off your mobile data when not in use. This will save tremendous amounts of battery.
if you search the forums you should find countless threads on battery and how to find out what is draining your battery and to extend life.
not sure why you would unroot unless you were exchanging it at sprint store but it greatly limits what you can do to help prevent battery drain. If you dont want to mess with much jsut use a rooted stock rom and it is pretty much the same thing as being unrooted but you keep the extra rooted benefits.
your best bet on non rooted device make sure mobile data, 4g, auto orientation, bluetooth etc are turned off. do the HTC battery condition/charge trick. and turn off background sync.
my suggestion is to re root and look into undervolted kernels and many other battery saving tricks found using search!
hopefully it helps some.
I had the same problem OP.
Turns out my radios weren't update.
Head over to the developer section and download the newest radios and stuff.
I've seen significant improvement of my battery life by using Collin_ph Battery Tweak 1 that was offered by Myn's when I flashed his/her's rom. I had my BF take his Evo to work after he come home complaining that the charge would only last about an hour or two and behold, he got through the whole day without having to charge his battery. This is after listening to music at work for 8 hours also. I HIGHLY recommend this tweak for ROOTED PHONES as I and everyone else I've recommended loves their Evo now and have no complaints...I'm at work right now and I'm at 79% and when I usually get home the battery is either still green (full) or orange (med) charge. I'm not sure if this tweak can be used with other mods but I'm very happy with this tweak as it has made my phone perfect now~~
Could be a Rogue app running killing your battery or radios not updated like stated above.
I recently started having the same issue. Advice such as turning of data and the GPS aren't helpful since the device functioned fine with GPS and data on before. Also if the battery was draining at a slower rate on the current radio before, you shouldn't need to update it, should you?
Seems that either something is making the Evo use more juice than it was before or that the battery is not holding the same capacity it used to. For some reason Phone Idle and Cell Standby have been using quite a bit more juice than they used to.
I don't like some of the software mentioned to try and locate anything that could be using more juice since those programs seem to use quite a bit themselves. Either way, what could be doing it that would come up as Phone Idle or Cell Standby in the included battery monitor? Wouldn't anything else come up under Android System?
The battery draining that quickly is not normal even with background sync, GPS (idle), 4g, data, or anything else on. There is another issue which must be solved. To troubleshoot so far I've tried another battery (same thing happens) and now I'm trying with everything turned off. If I can isolate what was causing my sudden rapid battery drain, I'll update everyone. This just started a couple nights ago for me. I think I'm on the latest radio, but I'll check.
Last post sums up my problem perfectly. I have an extended battery that lasts half the time it has over the last 4 months. Started with the radio updates. running myk
Use the battery usage functions of 'spareparts' to determine what's consuming cpu or preventing the phone from sleeping.
Can't fix the problem until you've isolated what's at fault.
Turning off mobile data will indeed fix a problem of some app trying to access the network, but it won't solve the actual cause.
bcarter2000 said:
turn off your mobile data when not in use. This will save tremendous amounts of battery.
Click to expand...
Click to collapse
I think juice defender does this automatically when the screen is off.
In the case of my phone, and I believe the OP's, we don't have any rogue apps or things running in the background. I know this phone like the back of my hand. I have completely uninstalled unnecessary apps like facebook, twitter, all things like news and weather are on manual update, i don't keep 4g or gps on, and I use wifi at home. I turn off 3g in terrible reception areas. I'm not a new user who doesn't understand the basic ways to save a little battery. I'm pretty sure the OP isn't either by his post. I use my phone the same every day. My chinese extended battery would last me easily from morning to bedtime with 20 to 30 percent to spare. Now I can't get near that after the radio updates. Since it's been well known that something is weird with these current updates, I've downgraded to 1.77 to see if that helps. My phone was sleeping fine though, so I don't know how much it will help. Always some BS with this phone.
Log out of gtalk and latitude. Those two seem to kill battery.
Bielinsk said:
Log out of gtalk and latitude. Those two seem to kill battery.
Click to expand...
Click to collapse
I appreciate it. I really do. But that is exactly the things I'm saying are already off. GTalk is turned off immediately on my phone from the jump and latitude has never been opened. It's got to be radios. I guess I'm not really asking a question, I'm just telling the OP he isn't alone.
cruecu said:
I appreciate it. I really do. But that is exactly the things I'm saying are already off. GTalk is turned off immediately on my phone from the jump and latitude has never been opened. It's got to be radios. I guess I'm not really asking a question, I'm just telling the OP he isn't alone.
Click to expand...
Click to collapse
this is the thread with flashable .zips of alllll the radio updates ever out for the EVO.
http://forum.xda-developers.com/showthread.php?t=715485&highlight=radio
if you are having trouble after a radio update, just try some of these other radios and see if that helps
Your best bet would be to root your phone again and give one of the SBC kernels a shot. I'm running CM 6.1.2 along with Zendroid 1.1.0 BFS AVS SBC and I can easily get 16+ hours with HEAVY use. And when I say heavy use, I mean hundreds of sms, dozens of calls and lots of websurfing. You will love the SBC kernels. Give it a try.
PS. My name is HondaCop and I approve this message.
We can offer suggestions until we're blue in the face.
First off, the OP needs to provide specifics of what's installed on the device, including rom, kernel, radio, etc, not to mention the hardware version itself.
Assuming it's not the known pri /rom conflict, then determination needs to be made as to what's actually consuming cpu - see first sentence above.
Need to use a systematic approach to troubleshoot this, otherwise it's a waste of time.
hgelpke said:
My Evo battery is draining at a rate that is all together too fast. I took it off the charger about 3.5 hours ago and it has drained about 30-40%. I have not made a call nor used the net at all save for the receipt of 3-4 emails. I had a rooted phone but I reset the phone back to complete unrooted stock. I have not even so much as installed an app. What can I do about this?
Click to expand...
Click to collapse
That sounds like a very weak cellular signal is forcing the radio to keep searching for it, draining the battery very quickly.
One way to somewhat alleviate this problem is to force roaming, to connect to a provider with a better signal.
"Roam Control" app does this (Market).
gpz1100 said:
We can offer suggestions until we're blue in the face.
First off, the OP needs to provide specifics of what's installed on the device, including rom, kernel, radio, etc, not to mention the hardware version itself.
Assuming it's not the known pri /rom conflict, then determination needs to be made as to what's actually consuming cpu - see first sentence above.
Need to use a systematic approach to troubleshoot this, otherwise it's a waste of time.
Click to expand...
Click to collapse
Dude....This is the best post in this thread...
Sometimes I wonder how far android users went in school....is scientific method lost these days? By no means am I qualified to help here..so my flamesuit is on for the post but damn.."my ****z broke...halp" won't cut it in a developer forum...
"it works on my machine"....words to die by.
d3x502 said:
....is scientific method lost these days?
Click to expand...
Click to collapse
What's that??????
d3x502 said:
Dude....This is the best post in this thread...
Sometimes I wonder how far android users went in school....is scientific method lost these days? By no means am I qualified to help here..so my flamesuit is on for the post but damn.."my ****z broke...halp" won't cut it in a developer forum...
"it works on my machine"....words to die by.
Click to expand...
Click to collapse
Actually,
some android users looked at the posting date, saw that the op hasn't updated in over 24 hours, wanted to complain about it, decided against it, posted quickly the most useful idea they had.
All that while doing real science.
Edit: The 4.2.2 update seems like it fixed this wakelock from taking over. That's just my personal experience so let me know if yours is different from mine after the update.
I've searched and tried to find a solution to my problem, but I can't find anything. My main kernel wakelocks are sns_async_ev_wakelock and sns_periodic_wakelock and the time they both register is massive. This has been happening for at least a week, or at pretty much the entire time I started monitoring my wakelocks. Does anyone have any idea what these might be attached to? I originally thought they were pertaining to social networking services, so I promptly deleted the Facebook app and for a day it seemed to fix it. But then the wakelocks came back and were even worse.
Have others come across this problem and does anyone know what might be causing it? They've been preventing my phone from going into deep sleep and I would really like to reduce or get rid of them.
Updated info: I have determined that the game Asphalt 7 is at least one app responsible for massive sns wakelocks. As long as the game remains as a "recent app" it will continue to wake the phone up. Angry birds is another game possibly responsible for the wakelock as well as reddit sync. Anyone else that uses these apps regularly us encouraged to report back your findings. Using the phone prompts sns wakelocks, but the amount of time the phone contributes is identical to your talk time, so your phone is triggering a fake wakelock since the device isn't supposed to be in deep sleep while you're on the phone anyways. Right now the only fix I know of for the listed apps is to manually clear them from "recent apps".
Please include the rom and kernel you're using. So far it seems like a new kernel doesn't actually fix the problem when you're on the stock rom. So anyone on CM or PA, do you have this wakelock after having a game like asphalt 7 or angry birds sit in recent apps?
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
madd0g said:
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
Click to expand...
Click to collapse
Well I'm getting this on Franco's. I think it has something to do with the phone. [ I mean talking/calling on phone]
@OP,
Do you get this only when you call someone or get a call. In bbs, try a custom ref. setting and monitor for 1 hour where you were not getting/calling anyone and see if it is going down drastically. Also is the msm_hsic wakelock present for you a lot? [The custom kernels like franco, faux and others have fix for this, taken from patch commits done by qualcomm]
What were you doing with your phone in that time, were you making calls, texting, etc?
Sent from my Nexus 4 using xda premium
madd0g said:
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
Click to expand...
Click to collapse
Currently full stock. And it looks like it's still present even with Franco's kernel
Hrithan2020 said:
Well I'm getting this on Franco's. I think it has something to do with the phone. [ I mean talking/calling on phone]
@OP,
Do you get this only when you call someone or get a call. In bbs, try a custom ref. setting and monitor for 1 hour where you were not getting/calling anyone and see if it is going down drastically. Also is the msm_hsic wakelock present for you a lot? [The custom kernels like franco, faux and others have fix for this, taken from patch commits done by qualcomm]
Click to expand...
Click to collapse
I talk on the phone for maybe an hour every day, so I would be surprised if it was associated with the phone since the wakelock time has been increasing this whole week while my phone time is relatively constant. Although I'm just taking the phone off the charger now and won't use it for calls for the next 2 hours, so I'll report back with what kind of wakelocks I'm getting as well was the apps I've used. As for msm_hsic_host wakelock, it is present but not as prevalent as the sns wakelocks. As you can see from the first picture I'm only getting about 20 minutes for that wakelock compared to the 4 hours of the others. If I remember correctly I ended the day with almost 5 hours for both sns and then an hour and a half for msm_hsic. So sns slowed down a bit and msm_hsic ramped up, but it didn't come close to overtaking sns
steviewevie said:
What were you doing with your phone in that time, were you making calls, texting, etc?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I was using it pretty normally. Had around an hour of talk time (cumulative over the day), texting throughout the day, streaming pandora for a little, checking emails, playing a game for a bit, and on sites like xda, reddit (through apps), and facebook (through chrome).
So far I haven't had any sns wakelocks today (well, nothing compared to what I recently had). The hisc wakelock is dominating now which seems more "normal". I only talked on the phone for a grand total of 3 minutes today so maybe that has something to do with sns. Currently charging it so I'll start getting new stats (the ones I'm posting now were taken a few hours ago), but this time I'll try to use the phone more as well as keep everything else the same. My use today has been streaming pandora, checking emails, reddit, xda, facebook, but no games (maybe that also comes into play). I'll keep updating
I'm getting massive sns kernel wakelocks too. No phone calls.
Xylon + Franco r30
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
I'm getting massive sns kernel wakelocks too. No phone calls.
Xylon + Franco r30
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, yesterday I started getting sns wakelocks after I was on the phone for a while, so that might be part of it. Of course there might have been another reason behind it if you get a lot of wakelocks without the phone. Forgot to get a screenshot
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
floepie said:
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
Click to expand...
Click to collapse
No, I never used Reddit sync. However, it could be related to a general sync problem
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
No, I never used Reddit sync. However, it could be related to a general sync problem
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ha. It's not a sync program whatsoever, not in the sense that it syncs anything to the contents of your phone. It does sync in the sense that it keeps track of your "read" articles.
floepie said:
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
Click to expand...
Click to collapse
I only use Reddit News. My sns wakelocks for today match the time I was on the phone, almost identically. This has been the case for today and yesterday which leads me to believe that the phone calls are NOT responsible for this runaway wakelock (as others have been saying). I didn't use my Nexus 4 very much this weekend, and the two major functions I used it for were phone calls and checking email sporadically. Others seem to report substantial wakelocks even without calls, so this has to be attributed to some app or setting that we're missing. Although I'm more inclined to think it's a problem with an app (or apps) because limited use seems to result in limited wakelocks, and if it was a system setting then it would be fairly constant. Has anyone gotten low sns wakelocks after not using their phone much in a day (like not using very many apps)? And thanks for the input so far
Async could stand for asynchronous, the CPU functions asynchronously but, I have no clue whether that wake lock is really cpu related.
Sent from my Nexus 4 using xda app-developers app
Ace42 said:
Async could stand for asynchronous, the CPU functions asynchronously but, I have no clue whether that wake lock is really cpu related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think it might be but I'm not completely sure.I found out last night that the game Asphalt 7 was responsible for a couple hours of wakelocks. However, in the system battery stats it registered as 0s for keeping the phone awake while android os registered the 2 hour jump I saw after playing the game. I played for a few minutes and jumped back to the home screen and didn't touch the game for those 2 hours. I'm not sure why, but having the game in my recent apps triggered those wakelocks, and the second I swiped it out of recent apps the wakelocks stopped. Either the app is bad or maybe the system isn't handling it correctly. I'll be trying other apps to see what the results are.
Sent from my Nexus 4 using xda app-developers app
I use redditsync and also had a 7hour snsw wake lock overnight... Gonna keep an eye on it and hope it was a one off (or an update gets pushed out)
cyberkid2002 said:
I use redditsync and also had a 7hour snsw wake lock overnight... Gonna keep an eye on it and hope it was a one off (or an update gets pushed out)
Click to expand...
Click to collapse
Alright, so that's two people getting wakelocks from redditsync. What happens when you clear redditsync from your recent apps? Does the wakelock continue or does it stop? This definitely sounds like the system isn't handling some of the open/recent apps correctly. No idea what links these apps together though
I am using Franco 62 with stock ROM and it turns out that Angry Birds Seasons can cause these wakelocks as well. Glad I'm not the only one with this issue.
I have never had these wakelocks previously (only the famous msm_hsic_wakelock). Yesterday after I installed a couple of apps (most are just theme-ing apps with no sync) and flashed custom kernel (Franco.r53); and ever since then these two wakelocks are continously appearing in my BBS stats, almost preventing my phone from entering deep sleep AT ALL. So I thought it was the kernel's problem; flashed back stock kernel and the problem still persists.
It's really weird as I previously NEVER had these two wakelocks.
By the way, I'm on stock ROM (rooted, unlocked)
chy1991 said:
I have never had these wakelocks previously (only the famous msm_hsic_wakelock). Yesterday after I installed a couple of apps (most are just theme-ing apps with no sync) and flashed custom kernel (Franco.r53); and ever since then these two wakelocks are continously appearing in my BBS stats, almost preventing my phone from entering deep sleep AT ALL. So I thought it was the kernel's problem; flashed back stock kernel and the problem still persists.
It's really weird as I previously NEVER had these two wakelocks.
Click to expand...
Click to collapse
Thanks for the update. But, it begs the question as to whether you uninstalled the new apps one by one to hone in on a possible culprit?
floepie said:
Thanks for the update. But, it begs the question as to whether you uninstalled the new apps one by one to hone in on a possible culprit?
Click to expand...
Click to collapse
I'm suspecting something else, will update if it's solved.
UPDATE:
This is really weird, I have uninstalled what I installed yesterday and the problem persists, so I decided to try something else (as it was the another differences factor compared to pre-problem).
My WiFi was disconnected in middle of the night and I thought it could be causing it.
I turned my WiFi off, turn it back on and the problem is gone. This is really weird, as I have rebooted many times prior to trying this solution (and even flashed back to Stock Kernel).
Really random or just plain unlucky? I have even reinstalled the apps that I thought are causing the problem, but still fine so far. Gotta leave it overnight again to judge.
Right, no matter what, I'm getting battery drain in stand by. No sync, Google now disabled, no mail, no location reporting/history etc. and yet I'm getting weird battery readings. In the pic below you can see, I'll let it idle for a couple of hours and the battery will drain. Then I'll use the n10 and the levels will spike. BBS shows that the n10 is awake for about 4 hours but the partial wakelock and kernel wakelock nothing untoward. I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
yets said:
I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
Click to expand...
Click to collapse
You can unroot and relock your device. Rooting should not be a warrenty issue.
See: " [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE"
http://forum.xda-developers.com/showthread.php?t=2001868&highlight=unroot
Features mentioned among many: "* Unlock/Re-Lock your Bootloader"
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
EniGmA1987 said:
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
Click to expand...
Click to collapse
Is it worth getting in touch with Google? I've had it since just after xmas? I'm about to factory reset it for the second time this week.
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
EniGmA1987 said:
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
Click to expand...
Click to collapse
I'd rather not factory restore it, this is my second time doing it. I'm starting from the beginning like it's a fresh install, just using the Google apps only to see if there are issues there and then adding more until I'm comfortable.
I want to root the tablet only as a last resort as I'm attempting to see if it is an app or it is the battery. I'd rather not brick it or void warranty only to find out it is the battery and then be unable to get a replacement.
There must be somebody that has similar problems?
So, factory reset, this is after 24 hours; This is not kosher. Stock apps. Only thing syncing if you can call it that was Google now. No syncing or anything. Purely from stock apps with updates. Stock battery graph says that it's not awake but stats say it's awake for 19 hours.This doesn't even come close to advertised idle/stand by time. Surely I should return it? I was adamant that I wouldn't complain but I didn't pay so much money for it to come out with this as stock performance.
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
EniGmA1987 said:
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
Click to expand...
Click to collapse
Thanks. To be fair I think if purchasing such an item, you shouldn't have to become a developer/hacker to study such an issue. Haha! I've used Google now when I first got the tablet and not understanding what it was had it enabled and get there was no battery drain to such an extent.
Fair play to Google, they've agreed to send me out a new one. It reached a point where I couldn't enjoy using the tablet and everything was a test to see what could be causing the issue.
I won't bad mouth Google, as I understand that things do become faulty and these items are complex enough. On another note I called up the RMA team in American (I googled the wrong number) and the two ladies were more than helpful. I don't know how anyone has problems with them. Maybe it was my British accent that did it!
So, I've got a replacement and so far it is not displaying the same issues. It got me thinking about when my original problem started and I think it started when it was updated to 4.2.2. This model comes stock 4.2.1 and it's prompting me to update. Should I bother? Was I just unlucky? Is there a specific way to ensure that the update is a clean update?
yets said:
... This model comes stock 4.2.1 and it's prompting me to update. Should I bother? ...
Click to expand...
Click to collapse
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
3DSammy said:
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
Click to expand...
Click to collapse
Yeah, I kind of did that when I factory reset it, I just loaded up the stock apps, desynced everything, logged out of everything that wouldn't be used, disabled Google Now and location settings, rebooted and it was still iffy. Before I sent it back I left it for a day and the battery stats were going up and down like a roller coaster. Could it of been a faulty battery? I would like to update but I'm so wary of the problem coming back.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
You may have been unlucky. I have had great battery on all 4.2.2 some ROMs/kernels make a difference.
Sent from my Nexus 10 using XDA Premium HD app
So, after a few days my new Nexus 10 started displaying exactly the same issues as before and I had just about ruled everything out. I used BBS again and looked at the stats, with PowerManagerService being the main culprit but the numbers in Partial wake locks just didn't match. There were very little wakelocks but something was still draining. I looked at the CPU and for most of the CPU was running at 200hz in deep sleep. I just couldn't figure it out and looked at the Running apps and there was only a few but one remained constant throughout all my tests and that was the Settings app. I took a punt and stopped it and cleared it from recent apps. Lo and Behold, the drain has disappeared and the battery doesn't drop at all in idle.
Excuse my noobiness, I didn't know that Android treated Settings as a separate app? On my Samsung S3, this isn't the case, once you leave settings it closes it and suspends it causing no drain.
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
EniGmA1987 said:
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
Click to expand...
Click to collapse
Sorry, didn't make myself clear. BBS was saying that tablet was running at 200mhz preventing it from deep sleep and that thing causing it was having the System Settings app not closing. Hope that makes sense and helps people in the future.
Well that is certainly an interesting find. If you restart the tablet and dont open settings does the tablet sleep fine?
Yes, if you restart it and avoid going into settings, it sleeps happily only waking sync if you have any. It has been idling for about 10 hours without dropping.
I've attached a picture and if you compare to the one I posted at the start of the thread you can see a clear difference. There was a point where I forgot to close Settings and you can see the drain (middle of the graph).
Somehow I don't think this is normal. It dropped almost 30% at home while I was at work. Google now is disabled but groove IP running. No apps that should be sucking battery, but its mostly the android OS. Any thoughts?
Sent from my Nexus 10 using xda app-developers app
Probably the exact same thing as the guy above me. Doesnt look like you are deep sleeping one bit.
Hi - newbie here hoping to get to the bottom of my battery drain problem.
Somewhat unusually I think, I am seeing problems only when I have wi-fi switched on. It took me a while to realise as I have wi-fi at work and home and I wouldn't normally have turned wi-fi off as I always understood that 3G uses more power.
I tried installing BetterBatteryStats but I am not rooted so it is only giving limited information. What it does tell me is that I am draining the battery at a rate of 9% or so an hour on wi-fi and about 1.4% on 3G. This is with very light or no actual use of the phone. The top two wakelocks by a big margin are msm_hsic_host and PowerManagementService.WakeLocks.
I have virtually nothing running according to my running processes list - mainly the Google ones like Google Play Services, Google Keyboard.
I couldn't put my finger on exactly when this started but it was towards the end of 2013. I did have the really bad drain with Google Play for a few days until the next Android update came. What I'm seeing now is not as bad as that was. I couldn't say whether I had a period after that update when things for a while were better than they are now but my feeling is that things have never been great since the 4.4 updates.
Does anyone have any suggestions please? Am I going to have to root to get better info to debug this problem?
OK, I'm too having this problem and couldn't find any concrete solution for this.
Without full use of batterystats application, the information that you provide don't help much.
Could be many things.
Unleashed by my Nexus 4
So not sure if this has already been posted and / or discussed elsewhere. Did a quick search and didn't find anything.
I was having pretty decent battery life on my s7 edge, but still getting random wakelocks that were only stopped by a restart. I was using package disabler to disable bloatware etc.
Usually it would show up as Android OS which was causing the stay awake. Device would not go into deep sleep when this was happening.
A bit of playing around and I noticed once the wakelock started I could get it to stop by restarting the phone or turning off bluetooth. I use android wear so turning off bluetooth wasn't an option.
Some googling led me to this thread http://forum.xda-developers.com/nexus-6p/help/bluetooth-causing-wakelock-t3237226
Mentions gas buddy app causing wakelock due to polling location via bluetooth (beacons...?), and some sort of bug or bad programming being the main culprit. Anyway, point being once I removed gas buddy everything was great and I had no more extended wakelocks for no reason.
I hadn't seen anyone post it in here, and clearly it does have the same issues on our phones. I see a lot of people talking about bad battery life, so hopefully this helps.
Keep in mind that gas buddy isn't the only app which has issues like this - it just seems to be the most common one. Check your apps as while it might not report it that way, but could be the root caused of wakelocks and subsequent bad battery life.
mrja22 said:
So not sure if this has already been posted and / or discussed elsewhere. Did a quick search and didn't find anything.
I was having pretty decent battery life on my s7 edge, but still getting random wakelocks that were only stopped by a restart. I was using package disabler to disable bloatware etc.
Usually it would show up as Android OS which was causing the stay awake. Device would not go into deep sleep when this was happening.
A bit of playing around and I noticed once the wakelock started I could get it to stop by restarting the phone or turning off bluetooth. I use android wear so turning off bluetooth wasn't an option.
Some googling led me to this thread http://forum.xda-developers.com/nexus-6p/help/bluetooth-causing-wakelock-t3237226
Mentions gas buddy app causing wakelock due to polling location via bluetooth (beacons...?), and some sort of bug or bad programming being the main culprit. Anyway, point being once I removed gas buddy everything was great and I had no more extended wakelocks for no reason.
I hadn't seen anyone post it in here, and clearly it does have the same issues on our phones. I see a lot of people talking about bad battery life, so hopefully this helps.
Keep in mind that gas buddy isn't the only app which has issues like this - it just seems to be the most common one. Check your apps as while it might not report it that way, but could be the root caused of wakelocks and subsequent bad battery life.
Click to expand...
Click to collapse
Related question: How are you determining wakelocks? Are you rooted?
Sent from my SM-G935T using Tapatalk
GiancarloMorr24 said:
Related question: How are you determining wakelocks? Are you rooted?
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I am not rooted. This makes the whole wakelock detecting a whole lot harder.
I simply use cpuspy and watch when the phone isn't going into deep sleep, but rather idling at the lowest cpu speed. This usually means a wakelock so I head over to the battery section in settings and look at what is listed there for stay awake times. this is what lead me to android os, and then bluetooth (as android os aggregates a lot of different services into it's stats)