Develop Bugs

[Q] Oxygen 2.0-RC6, Battery drain issues

Hey everyone,
I wanted to ask everyone for advice/opinion on my horrible battery life.
I have been trying out 2.0-RC6 for some time now and I love it, except the fact that the battery is drained in about 10 hours. I am coming from LeeDroid 2.2 and could go sometimes 2 days without charging.
I have searched forums, posts, what have you ... tried different kernels, radios. No joy.
I am now running a virgin RC6 with all caches wiped (S-OFF too). What it comes down to is a mysterious drain of about 100mA even when the phone is sleeping (radio on, bluetooth off, wifi off). Which makes no sense... I used to get really low drain with the laggy HTC Sense rom (about 5-10mA). Again - this is a clean rom there are no apps installed on it apart from a battery widget and setCPU.
Why i think it is the radio's fault is that when I do put the phone in airplane mode the power drain goes to 2mA. I have tried most radios, even flashed the 32.49.00.32U_5.11.05.27_RIL and for some reason the radio is still constantly drawing power.
So, I am stumped. I was wondering if any of you have found some tweaks that have worked for you. Have you experienced this kind of problem and do you have any advice as to how I can go about debugging this issue? I have very little knowledge about radios in general but i'm willing to learn.
There have been people with battery drain issues out there, but no one seems to know how to resolve them (or those issues simply go away when they flash a new rom, which hasn't happened for me).
I would appreciate comments from developers who know how to debug those issues and I think this will be of help to everyone.
Thanks

slyn4ice said:
Hey everyone,
I wanted to ask everyone for advice/opinion on my horrible battery life.
I have been trying out 2.0-RC6 for some time now and I love it, except the fact that the battery is drained in about 10 hours. I am coming from LeeDroid 2.2 and could go sometimes 2 days without charging.
I have searched forums, posts, what have you ... tried different kernels, radios. No joy.
I am now running a virgin RC6 with all caches wiped (S-OFF too). What it comes down to is a mysterious drain of about 100mA even when the phone is sleeping (radio on, bluetooth off, wifi off). Which makes no sense... I used to get really low drain with the laggy HTC Sense rom (about 5-10mA). Again - this is a clean rom there are no apps installed on it apart from a battery widget and setCPU.
Why i think it is the radio's fault is that when I do put the phone in airplane mode the power drain goes to 2mA. I have tried most radios, even flashed the 32.49.00.32U_5.11.05.27_RIL and for some reason the radio is still constantly drawing power.
So, I am stumped. I was wondering if any of you have found some tweaks that have worked for you. Have you experienced this kind of problem and do you have any advice as to how I can go about debugging this issue? I have very little knowledge about radios in general but i'm willing to learn.
There have been people with battery drain issues out there, but no one seems to know how to resolve them (or those issues simply go away when they flash a new rom, which hasn't happened for me).
I would appreciate comments from developers who know how to debug those issues and I think this will be of help to everyone.
Thanks
Click to expand...
Click to collapse
Try the 32.54.00.32U_5.14.05.17 radio and use a RIL designed for it also. For me this gives the best battery life. Also set wifi sleep mode to never by going into wifi settings, menu->advanced

[Q] Battery drain and 3G connectivity loss

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.

[Q] Normal Stability?

Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference

bump. should I post somewhere else?

Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!

I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App

I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies

[Q] ARHD 7.0.2 "Phone" process keeping CPU at 100%

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

Frequent "GPS Signal Lost"

So weird Issue.
Using Google Maps on MaximusHD 6 with the latest t-mo firmware (2.11) I get constant "GPS SIGNAL LOST" when obviously driving and using it as my nav since I got it. I'm in southern California with a pretty good LTE signal almost everywhere. The highways are pretty open so trees, mountains, buildings etc are ruled out as a probable cost.
Now today I noticed that I normally keep the phone locked/screen off when driving since it's connected over BT so there's no real need to look at it. During a normal 15-20min drive I would get the signal lost alert a lot. Upwards of 10 or so times on that single drive. While with my M8 it never happened especially when literally not 5min after getting out of the parking lot doing maybe 20mph down the street. I first I thought i messed something up since I took the phone apart to apply thermal paste to keep it from overheating.
However today on a drive back I kept the phone with the screen on. Never did it lose signal while the screen was on, but a minute after I locked the phone (screen off) did it lose GPS signal. I turned it back on and after driving 20min or so the signal wasn't lost.
So overall has anyone experience a similar issue? Full cellular coverage with frequent google maps alerts that the GPS signal was lost. Maybe a background gps process being killed or another coming up and hindering it.
Gonna wait for the Thanksgiving break to mess around with stock/custom roms and see if it's just something that can be fixed with a reflash.

I'm having the same issue, have you figured anything out? Have you tried using a different app besides google maps to see if it's the actual app doing it's power save feature, or the background powersaving process being started by the phone being screen off? Really interested because my phone starts burning up to extreme temps...

On the backup I had with the issue I narrowed It down to possibly a background process cutting it off once the screen turns back. Power saving was off and all that would stick while screen was off was maps, Google service, and social apps.
As for the cause I couldn't figure it out. I went with a stock from without issues. Then went back to custom roms and haven't had the issue again. Also I drastically lowered my app count. Barely use any apps not needed for basic functionality.
As for the temp issue you're having. I noticed gets warm just like any other device when using GPS. I have opened up the phone and applied a new thermal coat following off a thread around here.
I have another issue came up where the phone would seek out a GPS signal while battery saving was selected to even location turned off. Killed my battery in a heart beat. Hasn't happened again.
I would suggest you make a full backup and either flash a stock rom or redownload whatever custom rom your using. Do a trial run for a day or two with minimal apps and see if it improves.

Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.

shivadow said:
Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Android 6 should be released around here soon so maybe that'll improve/fix these issues. I wouldn't be surprised if Google services is causing this since it has in the past drained batteries and causes similar issues. If the kernel is involved then the issue has been seen on both stock and custom.

well it may be a setting from the maximums HD, try using other Rom and tell us if problem is solved, try HD Revolution or ViperOne.

Hi all, I got a Moto G3 and having issues with the gps no signal message, it is on and off, but more the time that have no signal. So have heard that Android 6 could be the guilty one.. Do any of you know if there is a fix yet? ?
Enviado desde mi Nexus 7 mediante Tapatalk