I'm at my wit's end here. There's no indicated partial wakelock by much of anything, but somehow my phone has a drain of around 30 mA when idle. It seems like this is off by something like a factor of 10 from what it should be.
Does anyone have a conclusive fix to this mysterious battery drain?
I'm on ARHD 6.1.2 w/ Revolution HD theme, with no applications that visibly are hogging CPU or partial wake locks, currently just wiped the entire phone and in the process of calibrating the battery, but for some reason it seems to be draining way too fast.
I'm not sure whether this is going to become an issue again, but I've always run into the problem every so often and a solution would be very much appreciated.
Are you using the recommended radio for that ROM? Radios make a big difference to battery life.
I assume you didn't do anything dodgy like restoring system data via Titanium Backup after you flashed your current ROM...
Also, you checked the MD5 of the ROM zip before flashing?
Is the drain constantly ~30mA when idle? does it ever reach the normal ~5mA it should when idle?
Check the drain in Airplane Mode to see if it's a Radio issue.
Flashed proper RIL for the radio I run, airplane mode is a steady 1 mA.
This has happened before, I'm not sure if it's the result of uncalibrated battery or just a bad ROM.
Currently calibrating on ARHD 6.1.2, seems mostly smooth sailing with <10 mA drain idle.
I run an Inspire so I use the latest GB radio/RIL released for the Inspire.
Related
I believe I may have a radio battery drain issue. The battery consumption on idle seems too fast for me, averaging around 5%/hour. Battery stats reports cell standby at over 40% constantly, and nothing I have done has made a difference.
Only things I have done is perm root, gfree, clockwork, hboot, and baconbits. Also have setcpu with screen off profile. Have not flashed any radios yet or run the ril matcher. Though I am considering trying it to see if it makes any difference.
Only other notable thing is that battery drain is reduced when on wifi calling, but cell standby still consumes the most power, next is wifi. Battery drain on wifi calling on idle is about 3.4%/hour, better but still seems high to me.
Would the RIL matcher do anything if I ran it with stock ROM and stock radio? My current radio version is 26.03.02.26_M
Any ideas? Could it be bad radio hardware? Or is this normal?
--MrAnt--
I don't see the stock radio doing that, maybe if you flashed a different radio. But this is stock, and it's supposed to work efficiently on your device.
Make sure gps or wifi and all of that aren't on. Try buying titantium backup pro where there's a freeze app function so apps can't launch in the bg.
Sent from my HTC Vision using XDA App
I'm with you on this one.
I had the stock radio, and was getting battery use on standby of about 50-60%. I've now flashed the gingerbread test rom radio, and I'm currently at 35% battery/standby and falling.
With the stock I was dropping 1-2% a MINUTE
Im using the stock radio and i have about 45% battery drain from cell standby, is there anyway to lower this? i have tasker and apndroid but i cant tell if there working. but i use my phone a lot throughout the day and im thinking maybe activating/deactivating it is wasting more battery then just leaving it on. Any suggestions on a radio i should try? and do you just flash radios in CWM? and btw im running CM7 2.3.3
Kevin001111 said:
Im using the stock radio and i have about 45% battery drain from cell standby, is there anyway to lower this? i have tasker and apndroid but i cant tell if there working. but i use my phone a lot throughout the day and im thinking maybe activating/deactivating it is wasting more battery then just leaving it on. Any suggestions on a radio i should try? and do you just flash radios in CWM? and btw im running CM7 2.3.3
Click to expand...
Click to collapse
I downloaded the radio from this thread http://forum.xda-developers.com/showpost.php?p=11666760&postcount=1 and renamed to PC10IMG.zip
Booted into bootloader and flashed it..that was it! Radio updated in less than 2 minutes!
You flashed the newest radio from the gingerbread test rom, 26.08.04.16? Did you run the RIL matcher? Might try this out this weekend.
--MrAnt--
Hi all!
Since a few months ago, my Desire has been having two major issues:
- Huge battery drain in 2 to 5h time (unable to identify application responsible, powertutor reports android system or os - can't remember -, while built-in battery usage monitor reports either display or cell standby - the second appears especially when the phone is idle and supposedly sleeping). The few times I enabled airplane mode, I got double battery time, though it doesn't come close to former normal battery time.
- 3G connectivity loss, when going through no signal areas or when the phone is forced to switch between GPRS and 3G and vice-versa.
Regarding the second issue, I've already tried to enable GSM (auto-PRL) and the result is practically the same as having 3G enabled. Only factory resetting after enabling the former setting and choosing GPRS only, in Settings works in no signal downtime.
Nothing I've tried takes care of the battery draining issue, even hard-resets. I've already flashed different roms from Eclair to Gingerbread, from unrooted stock to root stock-based: no real change.
So after this rambling, my question what is more likely either some hardware malfunction or a software bug in the android system or in some application?
Anyway, I'll try to use systempanel or watchdog to try pinpointing the culprit.
Thank you.
Flash latest radio
Also worth thinking about the kernel, I had a similar thing to you, and it was because I flashed a different kernel to the one packaged with the rom.
I would also try a full wipe, ie cache, data, system etc. in recovery and installing something clean eg oxygen rom.
The suggestion above about the radio is definitely worth trying also I would check that your current ril is compatible with your radio version:
http://forum.xda-developers.com/showthread.php?t=902752
Hello! Sorry for not answering sooner.
I have been running the latest radio for at least one month, and it hasn't changed that much the issue.
Also, at some point, I did try another kernel, having seen that suggestion elsewhere in the forums. It also didn't change much.
Finally, I have also tried flashing and using the clean oxygen gingerbread rom. The battery time improved a bit, but didn't go back to normal.
Still, after seeing the results of systempanel monitoring, I will try flashing oxygen rom again because, perhaps with 2.3.4, whatever the issue is, it might have been fixed.
Try to calibrate your battery:
1.) Load phone till full when on
2.) Turn off and load to green led
3.) Turn completely on, turn off and load until green led appears
4.) Boot into recovery, wipe battery stats and now use phone as normal
No warranty for any damage.
Sent from my HTC Desire using XDA App
Did it start when you flashed something new?
Hello!
That is possible. However, I have flashed and formated the phone many times since then and there has been no change.
Also, I have been monitoring the cpu usage through systempanel as suggested in some other threads, throughout the last weeks and in average, there's no installed application going further than 10% cpu usage consistently. When seeing the history of usage, at the top I have the system process, which has an average consumption of 0.2% over one week.
So, the phone seems to be working normally, but when using the currentwidget app to see the current drawn from the battety in each instant, at the best I get 50-70 mA, at the worst I get 700-800 mA. On average, 300-500 mA consistently.
I think something is draining the battery consistently much more than normal and also causing the baseband or the radio subsystem to crash, when switching from 2G to 3G or vice-versa.
I have done everything suggested in this thread, except for flashing a new clean oxygen rom and I've got no result.
What could be causing this: some hardware problem?
Thank you for your patience.
Maybe try the battery in someone else's desire, that you know functions ok, and their battery in yours? Perhaps the battery is dying?
Since I haven't been able to find anyone with an HTC Desire and I can't be certain if the problem is with the battery itself, I'll just send my Desire for repair to HTC.
Hopefully, they'll find and solve whatever the problem is.
Thank you all, anyways.
Please can I get some assistance, I cannot for the life of me figure out what has happened.
LeeDroid 3.3 latest.
I have gone from 48h standby to 14h. During use it's depleted in a matter of hours, it's incredibly low in relativity to what I'm used to.
I was on LeeDroid 3.0.2 previously and battery life was VERY long, I loved it - going back to this version doesn't help and the battery issue remains, and therefore it also remains on the newest build.
Previously I was running a bucket load of apps/games with normal 50% brightness, I have resorted to deleting apps/keeping tasks closed but to no avail. The Statistics for battery usage seem to look similar to how it used to be before, with display taking up a large chunk.
I tried the battery trick today but it hasn't helped. My phone has already gone to 98% (40m uptime) with screen turned off + SetCPU set at powersave/lowest mhz while screen is off.
I hope you can help, Thanks.
This does happen sometimes, not sure what causes it but a wipe and reflash sorts it out for me.
What kernel are you using? Have you made any recent changes before massive drain started happening?
Try monitor the current using current widget. If it's normal, around 1-4ma during standby, perhaps, your battery need calibrated. If it didn't resolve your problem, then, maybe the battery is dead.
ErOR22 said:
What kernel are you using? Have you made any recent changes before massive drain started happening?
Click to expand...
Click to collapse
I dont think this is the problem because when it happens to mine it just happens by itself after a few weeks of having the ROM installed with very few extra applications which I install immediately.
anyone know if the proximity sensor is classed under display? could be that thats stuck on. got any apps that use or used the proximity sensor? or maybe the touch screen is stuck on.
have you tried removing the SD card? see if its something on there.
Well I reinstalled Leedroid with the recommended rom and although the battery life is nowhere near what it was previously... its at a respectable 22h or so... enough to give me time to actually find a fix...
Theres no apps, nothing, just the rom and its apps so I will try it without SD card also, i dont understand how to check for proximity sensor though
Thanks
Hello Mates,
I am using Wildpuzzle ROM v0.8, which is having many problems in its stage.
The camera fails to operate sometimes. But I do managed to make it working using an external application.
The major issue remains of the BATTERY.
Its been a disaster for me to use it when EDGE 'on'. When the downloading is taking place, this phone starts draining the battery within 30sec for each percent. Presently i get the battery backup of around 120mins max on data usage.
One more issue lies in, the battery wont get charged beyond 71%. I need to reboot so that it shows somewhere more than 90%.
I have tried to reflash the v0.8 rom but facing similar problem again.
Will Radio update be a better option?
Can you recommend any better Sense Enabled Froyo?
Is this the bug in the ROM itself?
Help me, with your suggestions.
Thank You.
Recalibrate your battery. Just perform a search on XDA, there are many guides. It cant be a bug with WildPuzzle because I have personally tested it extensively, and this issue didnt exist.
Only after a fresh flash of a ROM, I get very bad battery life, but this is normal in all ROms I have tried. After 1-2 charge - discharge cycles, it fixes itself.
But because you are facing issues like it doesn't go beyond 71%, then jumps to 90% etc - Your battery definitely needs recalibration.
Hi everyone,
I just flashed ARHD 7.0.2 on my Desire HD last night and I'm experiencing the following problem:
The CPU remains at 99-100% all the time, the battery drains excessively fast and the phone gets really hot.
Using "Watchdog Lite", I detected that when the CPU does not stay at 100% (after a battery-pull), the "Phone" process uses 0,0% of CPU.
However, for some reason, after a while it will jump up to 80-90% and stay there, causing the CPU to go berserk.
I suppose the heat-issue comes from the fact that the cpu works all the time at 100%.
The battery drain issue comes also from the CPU.
However, I do not know why the Phone process would suddenly go crazy and use that much cpu - and keeps doing it until the battery is dead.
I'm thinking it is because the ARHD 7.0.2 ROM is actually a stock Sensation XL base and thusly requires another RIL than the one that was on it before that.
Before flashing another RIL or radio I would like it very much if somebody could confirm that the fact that the Phone process goes crazy like that could very well be linked to the fact that the RIL and Radio don't match.
It seems obvious, but I don't know enough of the inner workings to verify this, so therefor: this thread
Thanks in advance to all!
sstm
The RIL should be pretty standard between HTC devices so that shouldn't cause any issues. Did you do a full wipe before the install?
Hello TransientMotion,
Yes I did a full wipe, I even cleared the battery stats for good measure.
I even formatted my SD-card to make sure nothing remained from some app somewhere.
The phone is as if I'd have bought it fresh out of the store with ARHD 7.0.2 on it (and rooted of course)
It's just weird to see that the "Phone" process is using this much cpu, even when on Airplane mode.
Thanks for you reply,
sstm
It may be worth trying out an earlier version of the rom just to see what happens. I used 6..3.1 before I switched over to ICS and never had any major problems with it. If that works fine then try newer versions until you get glitches again or it works without the drain
Hey,
I just found out that it is Llama (kebabApp 'location aware' application) who is causing the problem.
Whenever I leave an area and then re-enter it, the CPU goes berserk and stays that way as if some loop can never be interrupted.
I didn't have this problem on ARHD 6.3.1, but I didn't have the same Llama configuration on it either so I tried the Llama config on ARHD 6.3.1 and it did the exact same thing: cpu 100% and slowness all over.
So conclusion: Llama config is the culprit.
Anyways, thanks for you help TransientMotion.
sstm