Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
goentillsundown said:
Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
Click to expand...
Click to collapse
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
suljo94 said:
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
Click to expand...
Click to collapse
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
Looks like faulty battery, try change the battery with new one and see what will happend
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
Thant said:
Looks like faulty battery, try change the battery with new one and see what will happend
Click to expand...
Click to collapse
in the OP he said that he did that already
suljo94 said:
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
in the OP he said that he did that already
Click to expand...
Click to collapse
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Thant said:
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Click to expand...
Click to collapse
Surely if it's the light sensor it would be irrelevant if it was turned off or on though, same with the CPU. I'm going to spend some time getting power into it today, charge, then put in freezer to cool it, and repeat.
Once some power is into it I'll start with suggestions, one at a time, and get some screen shots up, and logs of the current drain.
Thanks for the help so far, would be good to get it going again, instead of having a $350 paper weight.
An update:
Changed the recovery from Philz recovery to an older CWM recovery program, and now possibly just through coincidence the battery isn't super heating to the point it needs to live in the freezer to charge.
I have restored to stock ROM, and have a couple of pictures of the battery history, which are neither here nor there, apologies as I wiped a lot of things off, including my WLD pictures from the ARHD ROM.
I purchased trickstermod and had a look into the CPU settings, and nothing seemed out of the ordinary. Also turned on the dev options of graphic CPU usage on the homescreen - not really showing unusual signs of anything. About to flash the original recovery on and email HTC to see if they might feel sorry enough to accept it as a straight manufacturing defect, without evidence of where we purchased it (as it was a second hand phone off the net).
subscribing to this thread - I have the exact same issue. I have installed CM11 and ParanoidAndroid. Torched and Bubba kernel... turned off lots of stuff.
I have whatsapp, soundcloud and facebook as the only background running apps. not sure what's the issue
sensors drain battery
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Laccee said:
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Click to expand...
Click to collapse
I have checked all the sensors in the testing menu by dialing *#*#3424#*#* and they all turn off and on as required properly. I noticed yesterday that I've actually burnt out the charging system as it has got too hot at one point, so no use pursuing anymore. I will stick with my HOX until it too breaks in some way. Received an email back from HTC saying "Not under warranty, not our problem" after asking if they had had any phones with similar issues pass through.
I'm currently on stock MM with root and xposed but this issue started before I even upgrade to MM and I have cleared data and caches since the MM upgrade. Basically what happens is any time I open any app which actually uses location services (and have either GPS or network based location turned on) the phone reboots itself. When the issue started, it only seemed to happen when the battery level was also below about 40% but it slowly crept upward and now does it even with 100% battery and charging cable attached. Does anyone think there is a software explanation ? Are there any logs for location services or for the reboot I could look at which actually survive the reboot? I seem to remember last_kmsg being useful for random reboots but I don't seem to have that file on my phone (maybe something which has changed since I was really paying attention to Android dev stuff back in the ICS days). I'm hoping my issue isn't caused by a hardware defect but if that is the case I would like to know for sure.
6Eric said:
I'm currently on stock MM with root and xposed but this issue started before I even upgrade to MM and I have cleared data and caches since the MM upgrade. Basically what happens is any time I open any app which actually uses location services (and have either GPS or network based location turned on) the phone reboots itself. When the issue started, it only seemed to happen when the battery level was also below about 40% but it slowly crept upward and now does it even with 100% battery and charging cable attached. Does anyone think there is a software explanation ? Are there any logs for location services or for the reboot I could look at which actually survive the reboot? I seem to remember last_kmsg being useful for random reboots but I don't seem to have that file on my phone (maybe something which has changed since I was really paying attention to Android dev stuff back in the ICS days). I'm hoping my issue isn't caused by a hardware defect but if that is the case I would like to know for sure.
Click to expand...
Click to collapse
Never heard about this, long shot but might wanna try a different battery and see. Other than that I'm stumped
I am having the same issue, I open Google maps and the device reboots changed the location to battery saving and it doesn’t reboot, I guess is a marshmallow issue
Forgot I posted this, turned out the battery had gone bad so couldn't supply enough power. Replaced the battery for like $8 and it was fixed.
Hey everyone,
So i have a stock HTC 10, no custom rom or whatsoever and the battery drain suddenly got very bad. Android OS is on 49% and Android system on 28%. Battery drained 8% over the last hour with 3 mins SOT. I've set back the phone to factory settings and didnt install anything back on it, turned stuff like the GPS location to power saving mode but nothing seems to help. Tons of forum posts also didn't help. I don't want to put a custom ROM on it for now, so i can always send it back to HTC.
One thing that i keep noticing is my CPU usage. Im checking this with the stock android CPU checker and the load is 12.13/13.28/13.68 with only the systemui active. I have forced all apps to stop once but there was no solution. This problem is occuring since mid august. Hopefully somebody is known with this problem.
Edit: running wakelock detector atm
blackjezzx said:
Hey everyone,
So i have a stock HTC 10, no custom rom or whatsoever and the battery drain suddenly got very bad. Android OS is on 49% and Android system on 28%. Battery drained 8% over the last hour with 3 mins SOT. I've set back the phone to factory settings and didnt install anything back on it, turned stuff like the GPS location to power saving mode but nothing seems to help. Tons of forum posts also didn't help. I don't want to put a custom ROM on it for now, so i can always send it back to HTC.
One thing that i keep noticing is my CPU usage. Im checking this with the stock android CPU checker and the load is 12.13/13.28/13.68 with only the systemui active. I have forced all apps to stop once but there was no solution. This problem is occuring since mid august. Hopefully somebody is known with this problem.
Edit: running wakelock detector atm
Click to expand...
Click to collapse
I experienced something similar, funnily enough it was the charger cable causing it. Not sure how or why but as soon as I swapped from the faulty HTC official cable to another cheaper cable the drain stopped. Worth a try
timbohobbs said:
I experienced something similar, funnily enough it was the charger cable causing it. Not sure how or why but as soon as I swapped from the faulty HTC official cable to another cheaper cable the drain stopped. Worth a try
Click to expand...
Click to collapse
I tried another cable, didnt solve the problem unfortunately.
I'm having a very similar issue. Battery drains way quicker in the last few months (20% in 30 minutes) just from web browsing. A factory reset didn't help me either.
I'm trying safe mode now to see what happens (hold the power button, then tap and hold the "power off" option).
Long story short, I have been experiencing a severe battery drain with any ROM I try for the last month or so. Some ROMs seemed not to have it until first reboot, then the drain showed up.
Installing BetterBatteryStats showed me there was a "fingerprint wakelock" active 100% of the time. This was a bit strange, because my fingerprint sensor doesn't even work most of the time (sometimes it works after installing a ROM, sometimes after a few reboots, but it always stops working eventually for no apparent reason).
But searching around, I came across this page, where the following step is suggested:
mv "/vendor/bin/hw/[email protected]" "/vendor/bin/hw/[email protected]"
By renaming the corresponding file on my current ROM (/vendor/bin/hw/[email protected]) and restarting the device, I got rid of the battery drain and it now shows a healthy deep sleep time! I suppose that kills the fingerprint sensor, but since it wasn't working anyway, no harm done.
Just posting it for posterity and reference to whoever wants to try, I have no idea if anyone else has the same issue. (now I'll go hunt down PowerManagerService wakelocks, which seem to be the next big thing eating battery)
First, thank you for your guide. After updating from 7.1.2 to 9 i experienced a severe battery drain issue as well and this solved it. Actually, the fingerprint sensor never worked on android pie for me (crdroid 5.3). I would like to add some information that may be usefull to people.
This battery drain was caused by the fingerprint sensor and can be diagnosed by cpu spy where you will see your phone not going into deep sleep at all (interactive mode kernel, no idea for performance or gaming modes), and better battery stats showing finger print sensor being responsible for a big part of kernel wake lock when the screen is off.
Renaming the file can be done either if you are rooted on the phone or ( as i have noticed many apps like netflix refusing to work on rooted phones, making it inplactical to having your phone rooted ) using adb usb debugging to rename the files. if you are not allowed to rename the files, remount the phone and try again, remounting will automatically mount it in ReadWrite, while sometimes the first time will mount only as read.
If the problem is fixed the cpu spy app will show a much larger time spent in the lowest clock state in interactive mode and actually phone spending time in deep sleep.
PS: DO NOT hunt down the power wake locks as stated in your post, as those are active when your screen is on, and those should be on.
A long time ago for an unexplained reason my phone froze at 17%. It hold more power then that, but Android is frozen at that number. When the device is off and I first plug it in then it only shows 17%.
It's been like this for a year. I've done various things, like factory reset. Tried draining and fully charging battery many times. No luck. I was told I should get the battery replaced. I may still do that.
I just recently installed twms. I noticed it actually has the proper battery %. What is making twms check different then Android?
I have the last version of Android for pixel 3 xl. My phone is rooted but I don't have any mods installed. Is there something I can do to have Android read the battery the same way that twms does? Would a new kernel fix this? Please point me in the right direction?
I do not know what Twms is but it seems something wrong with rom itself. Did you tried wiping everything and clean flash stock rom ? Maybe some files gets corrupted.
Also can you try any battery app that report battery voltage ? If it is reported correctly at least you can say battery is ok..
icanrule said:
A long time ago for an unexplained reason my phone froze at 17%. It hold more power then that, but Android is frozen at that number. When the device is off and I first plug it in then it only shows 17%.
It's been like this for a year. I've done various things, like factory reset. Tried draining and fully charging battery many times. No luck. I was told I should get the battery replaced. I may still do that.
I just recently installed twms. I noticed it actually has the proper battery %. What is making twms check different then Android?
I have the last version of Android for pixel 3 xl. My phone is rooted but I don't have any mods installed. Is there something I can do to have Android read the battery the same way that twms does? Would a new kernel fix this? Please point me in the right direction?
Click to expand...
Click to collapse
I am having the same problem as you, only in my case I am stuck at 1% when I restart in TWRP if it shows me the correct percentage, I have tried with different roms (custom - stock) and different kernels I still have the same problem.
I have noticed that when accessing the root of the system (any rom) in the address or path "sys/class/power_supply/battery" and I open the "battery" file with a text editor there if I see the real value of the load of my battery
I have been meaning to post an update to this thread. I found a workable solution for me with tasker. You can download it for free at (https://taskernet.com/shares/?user=...GsgjEQmPWd4nGTxTaKorB2&id=Project:BatteryInfo)