Related
Have read some other threads from other phones but can't get to the bottom of this:
When looking at the battery stats in the settings menu, it reports that the phone is almost always awake, and there is a very minimal difference between awake and up time in the battery statistics.
What could be causing this? A ROM problem? I'm on Leedroid 3.3.3 R5. This seems to be one of the only problems with my phone at the moment. Even though this problem persists, I can still get a day's work with the phone, so not all that critical at the moment, but it would be nice to solve it..
Thanks
Just out of curiosity I checked my awake time and it's on about 80%. I've no idea really. It might be awake due to background apps running. But would be nice to have some light shed upon this. I will look around for something similar.
http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=android+awake+time
http://www.nimdae.com/?p=396
Searched for this and didn't find it in the forum. My phone is not rooted.
I've had this phone maybe a week after launch and this issue has just started happening in the last 4 days or so. It typically seems to happen after charging and unplugging the phone. The stock battery usage app, Settings--> Applications--> Battery usage, shows no battery drain at all while showing the phone as Awake the whole time and Screen on the whole time.
The reality is that the phone was just sitting on the kitchen counter with the screen off and I hadn't touched it the entire time. Rebooting only sometimes seems to make it snap back to reality, there are times when I'll reboot or pull the battery and nothing happens, it just continues to give a false readings.
Anyone else experiencing/experienced this?
Leaving my OP in place, but I have rewritten the description with much more detail and pics here
http://forum.xda-developers.com/showthread.php?p=25401417#post25401417
I suggest skipping to there.
I am looking for general tips here. E.g., not asking you to diagnose my specific problem so much as give me ideas of what else to check or try.
Lately I have had unexplained (to me) battery drain. Yesterday I lost about 25 percent in an hour while the phone idled. It is not a constant thing, though. I can go an hour and loose 1 percent then loose massive amounts in the next hour.
Now, i have searched, but I have not found anything that applies to me.
I have:
Tried a different radio
Tried a different kernel
Reflashed my rom
Phone is entering deep sleep according to cpu spy
There are no unusual or excessive wake locks according to better battery stats
No apps are using a lot of battery.
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Ideas?
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Zepius said:
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Click to expand...
Click to collapse
beren28 said:
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Click to expand...
Click to collapse
So I don't think I can blame it on that.
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
can you give us screen shots of battery stats?
Herman76 said:
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I do, and on reflection it is a possible culprit since I added it recently.
Didn't occur to me since it was producing no wakelocks and the battery stats did not showing as using much battery.
I shall turn it off for a bit and see if that helps. (unless there is some other way to test if it is the problem first.) I am off to the search button!
Zepius said:
can you give us screen shots of battery stats?
Click to expand...
Click to collapse
This is from yesterday when i set it down unused for about 90 minutes. The amount of wakes seems liek a lot, but it is similar to what i see when i have far far less drain, so I don't think that is the problem. I didn't get the app list screen, but out should screen as the only major drain with about 2 minutes.
I know it is shows poor signal strength, so immediately after that shot I put it in airplane mode, turned of sync, and rebooted. The battery continued to drain and graph had the exact same slope under those conditions. (Forget to get a pic though.)
Sent from my jitterbug using tapatalk.
System panel paid version with monitoring enabled is the best for tracking apps using CPU.
OK, still working on this.
To recap:
When the screen is off, and no apps are running I sometimes get inexplicable battery drain. This is occurring under conditions when I should be experiencing little or no drain at all. I say this becuase:
The screen is of and no bakground apps are running
the phone is NOT awake and IS entering deep sleep (as confirmed by cpuspy)
there are no unusual kernel or partial wake locks
there are no apps listed as using unexpected ammounts of battery
This is not a universal problem. The phone *often* behaves as expected. I can leave the phone off for an hour and see a 1% or 2% drain, and I am happy with that. However, sometimes, randomly, it goes nuts on my.
This graph from a few weeks ago shows what I mean. Look in the green box. The phone is sleeping, and the screen is off. The graph starts as a flatline, then, all of a sudden, it begins to drop precipitously.
Here is a graph that shows the battery dropping at the same rate whether the phone is awake or sleeping:
I have gone the following to try and narrow the problem down:
Done a completely fresh install of my Rom including a system wipe.
Tried two kernels (the aokp default and several relases of Franco's
Tried a different radio
Activated and installed a new sim card
I have come to suspect that the problem is network related. When the problem starts, sometimes going into airplane mode and back and/or toggling 2g only temporarily fixes the problem.
I suspect that something is happening with my connection to T-Mobile that keeps the network running and draining power. This is pure speculation, but it is all I can think of.
I installed juice defender (which I had not been previously running) and noticed the that, sometimes, it didn't turn of data when it should have. I also noticed the following two things happen:
I do not believe it is a rom problem, since if so, someone else would be reporting this. It might be an app problem, but if so the app is draining battery without a wake lock and while the phone is in deep sleep.
It is not exchange (as was suggested in this thread) since it continues when I ev my exchange account.
I have no idea what else to do or try.
Since it happens at random and takes a while to identify, uninstalling one app at a time to test for that could easily take months to narrow down a misbehaving app.
I know it is not a hardware issue since last month I got this:
That was with AOKP and Franco (earlier versions obviously)
I have google searched till my fingers bleed.
I am a long way form being an expert, and I suspect I may have overlooked something obvious.
Please, any thoughts??
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
derekwilkinson said:
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
Click to expand...
Click to collapse
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Here is that chart for last night.
I had about 1 hour and 30 minutes screen on time with 65% left when I went to bed. When I woke up, phone was dead.
RogerPodacter said:
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
Click to expand...
Click to collapse
Mine often does that. But sometimes it doesn't. It is the fact that it happens seemingly at random that makes it so annoying and hard to track down.
I would replace the battery
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
arw01 said:
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
Click to expand...
Click to collapse
The thought has occurred to me, but unfortunately, no, I don't have a friend I can swap with. And really, since I have had the phone less than 3 months, the battery *shouldn't* be bad, but yeah, defective products happen.
If I cannot find any other cause I will likely order a new battery and see if that fixes it.
beren28 said:
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Click to expand...
Click to collapse
1. yes battery calibration does make a difference.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"? Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
derekwilkinson said:
1. yes battery calibration does make a difference.
Click to expand...
Click to collapse
You are incorrect. But, in any case, I DID calibrate the battery just to cover bases in the case that I was wrong.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"?
Click to expand...
Click to collapse
We'll of course it can. That is kinda my point. If I go one app at a time waiting for it to "run a process at random" I am talking literally MONTHS of testing. I would have to wait many hours, if not days after installing or uninstalling an app to be sure whether or not it made a difference, then move on the the next. This is simply not an option. I started this thread in hopes that a realistic and doable solution might exist that I was unaware of.
Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
Click to expand...
Click to collapse
I am asking because there may be a solution that I am unaware of that doesn't require me to put my entire life on hold for months. It is possible that there is no such solution, but I asked in case there was one.
Sorry to have put you out so much.
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
skadebo said:
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
when i did a complete quote and re flash i did not setup the exchange account, but the issue continued.
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Sent from my jitterbug using tapatalk.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
My battery also drains at a rate similar to yours however I'm on the CDMA version. Hopefully you can figure out what's going on with yours.
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Checkout this thread to see if the gsiff_daemon is your problem. tl;dr when the system is hot and tearing through the battery, go to system settings -> Developer options -> and check Show CPU usage. If gsiff_daemon is the top or second highest on the list, then that is your problem. To solve it for the moment, use system tuner, or something else, to kill gsiff_daemon. There is no permanent cure at the moment, other than to delete gsiff_daemon. Both of those fixes require root, the non-root fix is to reboot.
If gsiff_daemon is not on the list, then something else is the problem, but Show CPU Usage should give you an idea of what system process is running hard.
Samsung Push problem
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
dansushi said:
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
Click to expand...
Click to collapse
Interesting, I installed "micro cpu monitor" shows thin line at top of screen showing both cores.
I haven't had this happen for some time now but after playing with google play and maps downloading offline maps etc I noticed my 2nd core pegged out.
Having seen this in the past & ignoring it I now realize that majorly drains the battery as well as it getting warm.
A simple reboot seems to be the only thing that fixes it. Clearing ram and closing recent screens dies nothing to clear the "cpu jam".
If left alone, it always shows the culprit as "android system"
As to what part of "android system" I don't know.
But until we figure this out for good, that little micro cpu monitor. App is sweet for peace of mind to know all is well or whether a reboot is needed. For what it's worth, I also noticed that after the event, that my auto rotate to landscape was mysteriously unchecked?
If it jams again, I'll have to see if it gets unchecked again, unknown if there is a relation.
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
That happened to me too. But for me, flashing another rom fixed it.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Swaggernaut said:
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No there is a cwm flashable fix floating around here for that
Galaxy SIII via XDA premium
do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?
Contact sync?
i noticed this today and while troubleshooting, noticed contact sync from google says "sync is currently experiencing problems..." maybe?
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
I read the thread about gsiff_daemon culprit. I had it listed as a possible battery drain culprit. The thread says the issue may happen after a hot reboot...which I did have. Killing gsiff_daemon was not immediately effective. I renamed the file so it wouldn't get used...like the thread recommended. I had to reboot to get normal battery drain back and have yet to see the issue again. But i wont know for some time...or maybe when/if i get a hot reboot...which is really rare. Do yourself a favor, and buy better battery stats. Its a must have tool...and it's not expensive.
I wonder if this problem has been solved with latest lj7 jellybean from sprint
Sent from my SPH-L710 using xda app-developers app
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
eatonjb said:
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
Click to expand...
Click to collapse
My experience with froyo/gb/ics is that things have been getting progressively better over the years. But with each so called UPGRADE of an OS or even APPS, we often have to deal with bugs or incompatibilities. I am eager to upgrade to a stock based JB soon, but wisdom says, for 20 things improved, there will be 5 things broken....or hurting in some way. Early adopters suffer the most as usually these issues get ironed out...most of them.
BUT...these stuck drains...wake locks etc., it seems they will happen when they do no matter how many issues get fixed. Over the years, I've had random standby drains caused by Maps/Nav. Maybe it's ok for months, then after a particular update, it's back...and unpredictable. The YES...a reboot, just like with a PC, is a quick short term workaround.
Finally, with the App CURRENT WIDGET, there is a provision to watch for high drain in standby. It watches MilliAmp (ma) readings over time..to determine if you have a rogue drain. That's different than monitoring the CPU. (Some drains do not cause much CPU activity) BUT UNFORTUNATELY, that app won't work with our S3's because of a lack of hardware support. Works great with HTC and many others. It's a bummer because I used to use it and have my HD2 reboot if a 15min consecutive high drain was recorded in standby....thereby saving the battery and usually killing the bug.
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app
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.