Have been asking about this problem for days and no one has answered me yet. For the past few days Android System has been using the majority of my battery. Always around 30% or more. I attached screens so you can see the processes running underneath "Android System"
Sent from my LG-D800 using xda app-developers app
You probably didn't receive an answer because there are COUNTLESS threads on how to find out for yourself what is causing your drain and how to fix it. People need to stop expecting to be spoon fed solutions. You're on a developers forum where there are guaranteed to be bugs and issues, If you can't deal with that, don't hang out here.
Someone had to be the asshole haha
The only solution I can think of, is to periodically close the apps you're using the least, Again though if this doesn't work then of course do the good old factory reset and try again. Anything past that and it's hardware issues.
Download something like Better Battery Stats and see if one of your apps is causing wakelocks. If you don't see any wakelocks, I'd say the next step is to check your CPU settings. Different CPU governors keep the phone awake longer than others before dropping back to deep sleep which could cause higher system drain. Beyond that, if you're rooted reflash whatever you're running, if not try a factory reset.
jellybear456 said:
Have been asking about this problem for days and no one has answered me yet. For the past few days Android System has been using the majority of my battery. Always around 30% or more. I attached screens so you can see the processes running underneath "Android System"
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
What Rom are you using(if any)?
I have the same problem and I'm on stock.
Sent from my VS980 4G using Tapatalk
tinymitch94 said:
The only solution I can think of, is to periodically close the apps you're using the least, Again though if this doesn't work then of course do the good old factory reset and try again. Anything past that and it's hardware issues.
Click to expand...
Click to collapse
I clear my recent apps almost every time i am done doing something on my phone. So I dont think that does anything for me.
Obaterista93 said:
Download something like Better Battery Stats and see if one of your apps is causing wakelocks. If you don't see any wakelocks, I'd say the next step is to check your CPU settings. Different CPU governors keep the phone awake longer than others before dropping back to deep sleep which could cause higher system drain. Beyond that, if you're rooted reflash whatever you're running, if not try a factory reset.
Click to expand...
Click to collapse
There arent that many wakelocks. But when there are its normally from Google Search. Is there a way to stop that? And I am using the Google Experience Launcher. Does that effect anything?
Walter21026 said:
What Rom are you using(if any)?
Click to expand...
Click to collapse
I am stock rooted with the Google Experience Launcher.
Also, If I were to factory reset(Which I hope I dont have to), would it be safe to do so even though I am rooted with TWRP installed? Like will there be a risk bricking/bootlooping my phone if I factory reset while rooted with TWRP? Should i factory reset using TWRP or in the settings menu on my phone?
I had the same issue over the past few days, and as simple as it seems, rebooting fixed the problem for me.
craighwk said:
I had the same issue over the past few days, and as simple as it seems, rebooting fixed the problem for me.
Click to expand...
Click to collapse
I have tried that to no avail.
jellybear456 said:
Also, If I were to factory reset(Which I hope I dont have to), would it be safe to do so even though I am rooted with TWRP installed? Like will there be a risk bricking/bootlooping my phone if I factory reset while rooted with TWRP? Should i factory reset using TWRP or in the settings menu on my phone?
Click to expand...
Click to collapse
Yes, you can even do the factory reset from within TWRP; just select the standard wipe option. I did it yesterday in prep for installing a new ROM. It does take awhile, but I had no problems and my internal "SD" memory wasn't touched.
rfarrah said:
Yes, you can even do the factory reset from within TWRP; just select the standard wipe option. I did it yesterday in prep for installing a new ROM. It does take awhile, but I had no problems and my internal "SD" memory wasn't touched.
Click to expand...
Click to collapse
So if I factory reset through TWRP will I lose root or TWRP itself?
Sent from my LG-D800 using Tapatalk
jellybear456 said:
So if I factory reset through TWRP will I lose root or TWRP itself?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Nope. It just takes you back to the starting blocks of whatever ROM you have loaded. For instance, if you're on stock it takes you back to Day 1 of owning the phone, but doesn't erase anything on the "Internal SD". If you've loaded another ROM, say Malladus or something, it will just take you back to the base of that ROM, with no mods or personal settings.
This is happening to a lot of different people on a lot of different devices. FYI.
Sent from my SCH-I605 using XDA Premium 4 mobile app
rfarrah said:
Nope. It just takes you back to the starting blocks of whatever ROM you have loaded. For instance, if you're on stock it takes you back to Day 1 of owning the phone, but doesn't erase anything on the "Internal SD". If you've loaded another ROM, say Malladus or something, it will just take you back to the base of that ROM, with no mods or personal settings.
Click to expand...
Click to collapse
So i will maintain root and TWRP if i factory reset using TWRP? Im stock just using GEL.
sbrownla said:
This is happening to a lot of different people on a lot of different devices. FYI.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your input. Just maybe we can solve it.
Sent from my LG-D800 using Tapatalk
jellybear456 said:
So i will maintain root and TWRP if i factory reset using TWRP? Im stock just using GEL.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
I don't know what GEL is.
I may have your answer. Use BetterBatteryStats. Check processes and wakelocks, pretty much everything. Battery Manager was telling me the same thing, but a random game was keeping it awake.
Sent from my LG-D800 using xda app-developers app
rfarrah said:
I don't know what GEL is.
Click to expand...
Click to collapse
The Google Experience Launcher. Pulled from the nexus and 4.4.
chrisphoenix7 said:
I may have your answer. Use BetterBatteryStats. Check processes and wakelocks, pretty much everything. Battery Manager was telling me the same thing, but a random game was keeping it awake.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I will look and post screens. Although its not being waked by anything according to Wake Lock Detector.
Sent from my LG-D800 using Tapatalk
Related
Does anyone else's battery history reset after a reboot? The percentage amount is fine but the up time and screen on time starts from scratch again. On 4.2 but this also happened on stock rooted 4.1.2.
Sent from my HTC Sensation using xda app-developers app
It's supposed to be that way. It would be rather pointless if they didn't reset.
Sent from my Nexus 7 using Tapatalk 2
It doesn't do this on my phone though? You can see the small gap where the system rebooted but it continues as its on the same charge.
Slightly annoying as sometimes a reboot is required or you need to boot to recovery and the history starts again still you lose track of what battery life you're really getting.
Sent from my HTC Sensation using xda app-developers app
gsmyth said:
It doesn't do this on my phone though? You can see the small gap where the system rebooted but it continues as its on the same charge.
Slightly annoying as sometimes a reboot is required or you need to boot to recovery and the history starts again still you lose track of what battery life you're really getting.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I haven't tested it but if thats the case , its ridiculous.. Battery stats should always start from unplugging time, otherwise what is the meaning of it? That must be a bug..
aLPaSLaN07 said:
I haven't tested it but if thats the case , its ridiculous.. Battery stats should always start from unplugging time, otherwise what is the meaning of it? That must be a bug..
Click to expand...
Click to collapse
Thanks, I haven't modded or changed anything apart from unlocking and rooting. Happened to notice it and thought I would ask about it, since my phone behaves differently. Everything else is fine though so its not a big problem, but would rather it worked correctly. Wondering if I should full wipe from recovery and reinstall apps one by one to see if it helps.
aLPaSLaN07 said:
I haven't tested it but if thats the case , its ridiculous.. Battery stats should always start from unplugging time, otherwise what is the meaning of it? That must be a bug..
Click to expand...
Click to collapse
Uptime is a measure of a system's availability without interruption. Time on AC power is also counted as uptime, and a reboot resets the clock on that, as it should. Uptime is not synonymous with time on battery- they are two separate concepts. A reboot, by its very nature, interrupts that availability of the system. Were the uptime not reset at this point, that particular metric would be utterly meaningless since it would be grossly inaccurate.
najaboy said:
Uptime is a measure of a system's availability without interruption. Time on AC power is also counted as uptime, and a reboot resets the clock on that, as it should. Uptime is not synonymous with time on battery- they are two separate concepts. A reboot, by its very nature, interrupts that availability of the system. Were the uptime not reset at this point, that particular metric would be utterly meaningless since it would be grossly inaccurate.
Click to expand...
Click to collapse
Update:
Well the battery history/time is now sticking after a reboot, i.e. showing 19hrs on the current charge (after both power down/up and reboot. Surely that's what its supposed to do? That's the way its worked on all android phones I've seen.
Sent from my Nexus 7 using xda app-developers app
gsmyth said:
Update:
Well the battery history/time is now sticking after a reboot, i.e. showing 19hrs on the current charge (after both power down/up and reboot. Surely that's what its supposed to do? That's the way its worked on all android phones I've seen.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
After double-checking, it looks like we're talking about two different things. What you were referring to as uptime is the time overlay on the graph, correct? If that's the case, then that is not uptime and you are correct in that it should only reset after charging. Uptime is displayed in Settings >
About tablet > Status.
Sent from my Nexus 7 using Tapatalk 2
najaboy said:
After double-checking, it looks like we're talking about two different things. What you were referring to as uptime is the time overlay on the graph, correct? If that's the case, then that is not uptime and you are correct in that it should only reset after charging. Uptime is displayed in Settings >
About tablet > Status.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Ah thanks, sorry for the confusion!
Sent from my HTC Sensation using xda app-developers app
This just started happening the other day. Randomly during the day it will not allow me to adjust the volume ( ie from vibrate to loud). The status bar moves when i move them but it doesn't actually do anything. Also when this starts happening, voice input no longer works. I cant do voice text voice searches etc etc.
I have to shut it down and restart it, then everything will work again. But it only lasts for a few hours and then i have to do it again.
I am stock and not rooted.
Thoughts?
It doesn't happen to me on my modded and tweaked Slim Bean Beta2. I would recommend doing a factory reset and see if that fixes your problem.
Sent from my Nexus 4 using xda premium
Maybe you have apps installed that control or manage audio
Sent from my GT-I9300 using xda premium
android88 said:
It doesn't happen to me on my modded and tweaked Slim Bean Beta2. I would recommend doing a factory reset and see if that fixes your problem.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Could i use this backup utility found here http://forum.xda-developers.com/showthread.php?p=36499906
factory reset my phone and then install that backup or would that defeat the purpose of resetting it.
I am not a pro at this obviously, i just do not want to lose all my apps and settings i have. Or would they just reinstall once i linked the phone back to my google account?
Benconquerer said:
Maybe you have apps installed that control or manage audio
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I did have one, but i uninstalled it and still having the same issues.
I'm having the same issue, stock ROM rooted with franco kernel.
Not only that, but the volume gets very low almost inaudible and I end up having to reboot the phone.
I don't have any audio apps installed, noticed this while watching YouTube.
Thus far have not found a solution
Sent from my Nexus 4 using xda app-developers app
now it is not happening anymore and hasn't happened since Saturday.
Weird.
Will repost later if it starts acting up again.
My nexus 10 is dying with displayed charge at or around 70%. I had lost the tablet and it was dead for months. Idk if that is relevant or not. It did take a full charge a few times after finding the tablet before the above stated issue occurred. The charger I'm using should be in good shape as it charges my Galaxy S4 w/o issue. Running CM 10.1.3 (Stable).
Thoughts? Thanks in advance.
Update: now the device is dying while showing charge level in the high 90% mark. Device now dies mid-boot even plugged in. Before it would stay on so long as I kept it plugged in. It will stay on if I go into cwm. That's the curious part.
Sent from my SGH-I337 using XDA Premium HD app
After doing some research I'm going to guess calibration to be the issue. What to do if calibration is so out of wack it thinks its charged when it's dead?
Update: I ran calibration after I managed to get it to 100%. A few minutes later it died. Curiously I put my tablet in recovery mode and it has stayed on for at least an hour now. However when I try to boot into CM it dies. Every retry it dies a little sooner in boot.
Maybe you could go back to stock via fastboot. If that doesnt work I think tour battery is dead.
Sent from my Galaxy Nexus using XDA Premium HD app
Actually I've been letting it sit idle in recovery mode. Its had at least 4 hours to drain now. Haven't been able to kill it yet so I am extra confused. I read the charge with an app and it was at 4400. The tablet is perfectly happy in recovery. I wiped my system partition and reflashed CM. This seemed to have an affect to a degree. Once the dalvik cache was rebuilt the tablet died again and went back to the odd behavior I mentioned. I would prefer to not return to stock unless it is absolutely necessary. I will if I have to but I would like to see if anyone else has seen this issue or has an idea on how to TS it as is.
For the Android junkie this would be a fun issue to trace down. I simply don't have the education. I just created my developer console account and am going through the documentation to create my first app. Clearly outside of Google Fu I'm relatively useless.
Sent from my SGH-I337 using XDA Premium HD app
Try wiping the battery stats from recovery, if yours lets you.
Have you tried wiping/factory reset and starting with a clean install? As part of all the rebooting, you may have corrupt file(s).
SmokinCharger said:
Have you tried wiping/factory reset and starting with a clean install? As part of all the rebooting, you may have corrupt file(s).
Click to expand...
Click to collapse
I think in going to have to. I've proved the battery is charged and CWM knows it. I'd like to do a titanium backup to preserve my game data but I don't see how if the darn thing dies mid-boot. May have to bite the bullet on this one
Sent from my SGH-I337 using XDA Premium HD app
dibblebill said:
Try wiping the battery stats from recovery, if yours lets you.
Click to expand...
Click to collapse
It didn't so I just wiped the whole /system partition (I believe that's where the battery bin exists) and flashed CM back. No good.
Sent from my SGH-I337 using XDA Premium HD app
my tablet died at 60,but it dont died since i flash other custom roms....
Sent from my Nexus 10 using XDA Premium 4 mobile app
hunforfee1 said:
my tablet died at 60,but it dont died since i flash other custom roms....
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why thank you. I'll have a look.
Sent from my SGH-I337 using XDA Premium HD app
Flashed full factory image
I used the image found here to completely wipe and reset all partitions and make the thing like it just came out of the box with no trace of mods left (that I'm aware of). It happily booted in and I got about halfway through initial setup and it died and returned to the same behavior.
What do I do now?
What ever this is is SERIOUSLY draining my battery...
Does anyone have any idea what 10425 is or what it does,?
I haven't installed any new apps besides ESET security.. Can it possibly be that?
Screenshots attached
Uninstall it then and see for yourself
Sent from my SM-G935F using Tapatalk
Damn. That's not good.
Sent from my SM-G935T using Tapatalk
I would try to factory reset, maybe just a fault installation/update?
Did you get the recent update yet? I use AT&T and just got mine today.
I thought a numbered process always had to do with a removed app, if you didn't uninstall any app prior to ESET (which drained my battery on my Galaxy S2 also) it probably didn't install well. Let us know if you got it fixed, just for future reference
skivnit said:
Uninstall it then and see for yourself
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
It wasn't eset... I cannot for the life of my figure out what it is
Juuls said:
I thought a numbered process always had to do with a removed app, if you didn't uninstall any app prior to ESET (which drained my battery on my Galaxy S2 also) it probably didn't install well. Let us know if you got it fixed, just for future reference
Click to expand...
Click to collapse
I updated a few days ago and there are no more updates to be had. On T Mobile
xcha0tic said:
I would try to factory reset, maybe just a fault installation/update?
Click to expand...
Click to collapse
Might have to... my phone is hot CONSTANTLY even when running no foreground apps
yanowman said:
Might have to... my phone is hot CONSTANTLY even when running no foreground apps
Click to expand...
Click to collapse
Try that def man, only time my phone got semi warm was when I first started it up and was restoring and transferring everything from my nexus.
An about a month ago switched to 7.1.2 from 6.0.1.
Stock rooted version. The phone is one and a half years old.
Since then I'm having random freezes that only pressing the power button and reboot will help.
I can't figure out what causes these freezes.
Anybody else having this ?
Sent from my Nexus 6P using xda premium
How did you update to 7.1.2 was it stock image ?
Yes. Stock image
Sent from my Nexus 6P using xda premium
Try a factory reset see if that helps really hard to say. Are you using substratum try removing overlays. If using custom kernel resore to stock. If it was me I would completely wipe my phone including internal. Then flash a fresh factory image to rule out any software related issues. Just make sure you back up all your pics etc.
I'm using stock kernel. The freezes are random. Can't figure out what triggers them.
The freeze can be while the phone connected to charger, lying on a table or when I on Facebook or something else...
Sent from my Nexus 6P using xda premium
Lior84 said:
I'm using stock kernel. The freezes are random. Can't figure out what triggers them.
The freeze can be while the phone connected to charger, lying on a table or when I on Facebook or something else...
Sent from my Nexus 6P using xda premium
Click to expand...
Click to collapse
There apps that you can get that will show you logs of what's going on in the background. Catlog or syslog are ones that I know of. They can be hard to understand but might give you some clues to what's going on. After the phone does it thing quickly check the log and see if any errors from apps and such that stand out.