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.
Related
Hey guys,
I have been trying to solve this on my own for two days now, but I would like to consult the forum now.
So, I was running Pink Sense 1.8 for about 2 weeks with setCPU profiles and was getting satisfactory battery life. I had re-calibrated the battery info maybe 2 weeks before flashing the Pinky ROM (as described here: http://forum.xda-developers.com/showthread.php?t=755903).
All of a sudden, without any app installation or change to either the ROM or software/hardware settings I started getting horrible battery life. The battery would drain completely for less than 6 hours with GPS, 3G, and WiFi off.
*Another strange thing (which I don't know if it was related to my battery issue or not) was that when I would plug the charger it would turn the screen on but switch to the default clock app instead of the HTC sense homescreen. If I pressed home or back it would disappear. This would happen randomly and not always.
So, I figured it's time to jump ROMs and I decided on LeeDroid. I wiped cache, etc. and flashed the ROM. Out of the box the battery life was again pretty crappy (the battery was virtually disappearing in front of my eyes). I found some threads where it was suggested to disable market notifications and that slowed the battery drain a bit but it's still crappy.
I just charged it fully, 3G and WiFi off, and was with the screen off for 99% of the time and it still drained 18% battery in 1hour and 25 mins.
So, my question is - what the hell is going on???
Should I wipe battery info? Should I install a non-WiFi n rom? What more can I do?
I would really appreciate help and advice.
p.s. I am running the latest radio too.
wich radio have you the .23 drains the batery with my desire try with the .30_2
the battery life is better.
did you try reboot your phone maybe your optical joystick dead and drain your battery.
load any new apps recently?
cr1960 said:
load any new apps recently?
Click to expand...
Click to collapse
As I said, the problem appeared with absolutely no new apps installed and persists after flashing a new ROM.
How do I know if my optical joystick is dead? It still works if that's what you mean (although I don't like using it).
I will try flashing the 30_2 radio, thanks for that suggestion.
slyn4ice said:
How do I know if my optical joystick is dead? It still works if that's what you mean (although I don't like using it).
Click to expand...
Click to collapse
If it works he's not dead
after flashing your radio and if the battery still drain check if the rom you use has his own rules for the cpu freq. if you are in that case don't use cpufreq or something like that because of conflicts.
PS: Sory for my bad english
Sithlord31 said:
If it works he's not dead
after flashing your radio and if the battery still drain check if the rom you use has his own rules for the cpu freq. if you are in that case don't use cpufreq or something like that because of conflicts.
PS: Sory for my bad english
Click to expand...
Click to collapse
Thanks, I just flashed the 17_2 radio. It doesn't look like LeeDroid has any requirements for cpu frequencies. I will post an update after an hour.
slyn4ice said:
Thanks, I just flashed the 17_2 radio. It doesn't look like LeeDroid has any requirements for cpu frequencies. I will post an update after an hour.
Click to expand...
Click to collapse
There seems to be no change with 17_2 radio. 15% drop for 1h45m. I will go through a charge/recharge cycle and if nothing has changed I will flash the 30_2 radio.
Some people had the same effect. It happens when you flash your ROM while the phone is connected to power/charging. The battery stats simply get messed up.
An easy indication for this is if you charge the phone fully while powered on, LED is green, as soon as you unplug the charger the battery drops to some 90%.
The fix is easy too. If the phone is fully "charged" while on, disconnect the charger and switch it off. Then plug the charger in again. The LED should turn orange again and the remaining percentage will be charged. Wait until you have a green LED and your problems are hopefully gone.
Look out for the battery calibrating thread here for more info.
Hope that helps...
Mac
mmaacc said:
Some people had the same effect. It happens when you flash your ROM while the phone is connected to power/charging. The battery stats simply get messed up.
An easy indication for this is if you charge the phone fully while powered on, LED is green, as soon as you unplug the charger the battery drops to some 90%.
The fix is easy too. If the phone is fully "charged" while on, disconnect the charger and switch it off. Then plug the charger in again. The LED should turn orange again and the remaining percentage will be charged. Wait until you have a green LED and your problems are hopefully gone.
Look out for the battery calibrating thread here for more info.
Hope that helps...
Mac
Click to expand...
Click to collapse
Thanks for the suggestions. I always thought it would be better to flash with the ac adapter plugged.
I have tried the method you described above but it hasn't really solved any of the problems.
The battery drain is now at least manageable - i had 50% drop while sleeping for 6 hours (at least it didn't drain it completely). I am going to flash the 30_2 radio and try again.
slyn4ice said:
Thanks for the suggestions. I always thought it would be better to flash with the ac adapter plugged.
I have tried the method you described above but it hasn't really solved any of the problems.
The battery drain is now at least manageable - i had 50% drop while sleeping for 6 hours (at least it didn't drain it completely). I am going to flash the 30_2 radio and try again.
Click to expand...
Click to collapse
If you have access to a spare battery, maybe you can try that too?
Normally when I have unexplained problems with the phone, the last drastic step I would take is to wipe everything, data/app/cache. Do a nandroid backup first so that if that doesn't solve your problem you could always get back all your setups.
You could also try Titanium to help save your setup. But I would be careful with what I restore. The last thing I would want is to get the messed up setting back in.
I have noticed also whenever I flash a new rom, the battery seems to get worse. So I would always do a recalibration. The proper step is here:
http://forum.xda-developers.com/showthread.php?t=755903 (and wipe the battery status on the last power up before using).
Lastly, I would use as stock as possible first to see if it is things that I introduce that cause the problem.
pehkblui said:
If you have access to a spare battery, maybe you can try that too?
Normally when I have unexplained problems with the phone, the last drastic step I would take is to wipe everything, data/app/cache. Do a nandroid backup first so that if that doesn't solve your problem you could always get back all your setups.
You could also try Titanium to help save your setup. But I would be careful with what I restore. The last thing I would want is to get the messed up setting back in.
I have noticed also whenever I flash a new rom, the battery seems to get worse. So I would always do a recalibration. The proper step is here:
http://forum.xda-developers.com/showthread.php?t=755903 (and wipe the battery status on the last power up before using).
Lastly, I would use as stock as possible first to see if it is things that I introduce that cause the problem.
Click to expand...
Click to collapse
I think I can definitely confirm the radio is the problem. There is barely any battery drain in airplane mode (1% drain per hour with WiFi on). I am back to 32.43.00.32U_5.09.00.20 but it seems to drain battery faster than before.
Now that I think back, this battery problem started when i switched to the newer 32.47.00.32U_5.10.05.23 radio. No matter what I do now though even after rolling back to older radios it's still a problem. Damn it.
slyn4ice said:
I think I can definitely confirm the radio is the problem. There is barely any battery drain in airplane mode (1% drain per hour with WiFi on). I am back to 32.43.00.32U_5.09.00.20 but it seems to drain battery faster than before.
Now that I think back, this battery problem started when i switched to the newer 32.47.00.32U_5.10.05.23 radio. No matter what I do now though even after rolling back to older radios it's still a problem. Damn it.
Click to expand...
Click to collapse
Don´t know (because i never updated radios above .20 and have no problems with battery)...but...maybe flash a original ruu rom...and root again
maybe this help...with kind regards..Alex
Alex-V said:
Don´t know (because i never updated radios above .20 and have no problems with battery)...but...maybe flash a original ruu rom...and root again
maybe this help...with kind regards..Alex
Click to expand...
Click to collapse
that doesn't help, ive tried it already
TieT said:
that doesn't help, ive tried it already
Click to expand...
Click to collapse
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings and ... got a 5% drop in battery for 10 hours on standby (wifi off, setCPU set to 245Mhz when screen is off). This is unbelievable.
Anyways, here are lenik's blog posts about it:
http://lazydroid.com/2010/06/battery-life-improved/
http://lazydroid.com/2010/06/back-to-1-21-...ry-consumption/
I hope this helps other people out there!
slyn4ice said:
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings and ... got a 5% drop in battery for 10 hours on standby (wifi off, setCPU set to 245Mhz when screen is off). This is unbelievable.
Anyways, here are lenik's blog posts about it:
http://lazydroid.com/2010/06/battery-life-improved/
http://lazydroid.com/2010/06/back-to-1-21-...ry-consumption/
I hope this helps other people out there!
Click to expand...
Click to collapse
VERY nice results! Do you think that these RIL settings should work on any network/carrier?
It's very odd because today I noticed my battery performance dropping large, BUT before it was always great. I am also on LeeDrOiD 2.1, and while at home, with WiFi + BT on AND connected to my router + handsfree, I lose only about 3-4% an hour.
Today when I left the house and went shopping, I was in the store for 1.5 hrs and I had lost near 15%! I had even turned off Wifi so it wasn't trying to scan APs. Very very strange...
Anyways, I want to maybe try these RIL settings if it will work on any carrier. Does anyone know if I can edit build.prop while in recovery, or do I have to edit it in the ROM .zip then reflash the entire ROM?
Thanks for the post and hunting down a solution slyn4ice, I'm glad that it has helped you out big time!
*** EDIT *** - After looking more into my JuicePlotter graphs, I notice that the battery life gets killed when I am using APN / 3G / HSPA network. I would have thought Wifi would take more power, but that seems not to be so. I DID have "Network Mode" set to "WCDMA only" (in Mobile Network Settings) because I heard it might save battery not having to switch back and forth from EDGE to 3G, but I guess that didn't help...I've since switched it back, but need a lot of charging before I can test again.
Does anyone else notice that when they're on 3G/H the battery drops MUCH quicker than if you were connected to Wifi instead? This is just my last hurdle towards a PERFECT ROM!
Thanks in advance all!
3G uses waaay more power than WiFi. After all, the data usually travels long distances and needs to be amplified. This effect is pronounced especially if in the limit zones of 2G/3G coverage and you have 3G preferred, the phone boosts the power to maximum to maintain 3G.
Gsm Auto (PRL) prefers 2G if 3G coverage is too low. WCDMA Preferred tries to maintain 3G connection even if it means sacrificing battery life.
If you are constantly in good coverage zones, no problem, but to the people living on the edges of proper 3G coverage it meas a big hit to battery life, especially if the mobile data is used. This partly explains why some get superb battery life and others far worse.
Jgruar said:
3G uses waaay more power than WiFi. After all, the data usually travels long distances and needs to be amplified. This effect is pronounced especially if in the limit zones of 2G/3G coverage and you have 3G preferred, the phone boosts the power to maximum to maintain 3G.
Gsm Auto (PRL) prefers 2G if 3G coverage is too low. WCDMA Preferred tries to maintain 3G connection even if it means sacrificing battery life.
If you are constantly in good coverage zones, no problem, but to the people living on the edges of proper 3G coverage it meas a big hit to battery life, especially if the mobile data is used. This partly explains why some get superb battery life and others far worse.
Click to expand...
Click to collapse
Amazing explanation and reaffirmation of my thoughts Jgruar (JuicePlotter confirms it). I guess from my old WinMo days, I always remember Wifi being the power hog. I actually did change it back to GSM/Auto since that was the only change I made lately, but I thought I'd chime in while my device was charging back up, hoping for a reply just like that!
Thanks a bunch!
scar45 said:
VERY nice results! Do you think that these RIL settings should work on any network/carrier?
It's very odd because today I noticed my battery performance dropping large, BUT before it was always great. I am also on LeeDrOiD 2.1, and while at home, with WiFi + BT on AND connected to my router + handsfree, I lose only about 3-4% an hour.
Today when I left the house and went shopping, I was in the store for 1.5 hrs and I had lost near 15%! I had even turned off Wifi so it wasn't trying to scan APs. Very very strange...
Anyways, I want to maybe try these RIL settings if it will work on any carrier. Does anyone know if I can edit build.prop while in recovery, or do I have to edit it in the ROM .zip then reflash the entire ROM?
Thanks for the post and hunting down a solution slyn4ice, I'm glad that it has helped you out big time!
*** EDIT *** - After looking more into my JuicePlotter graphs, I notice that the battery life gets killed when I am using APN / 3G / HSPA network. I would have thought Wifi would take more power, but that seems not to be so. I DID have "Network Mode" set to "WCDMA only" (in Mobile Network Settings) because I heard it might save battery not having to switch back and forth from EDGE to 3G, but I guess that didn't help...I've since switched it back, but need a lot of charging before I can test again.
Does anyone else notice that when they're on 3G/H the battery drops MUCH quicker than if you were connected to Wifi instead? This is just my last hurdle towards a PERFECT ROM!
Thanks in advance all!
Click to expand...
Click to collapse
From what I understand you need to update RIL settings in the ROM and then flash the modified ROM. I just edited the /system/build.prop file in the Leedriod zip file and saved (didn't resign or anything). Flashed the ROM through ROM Manager recovery (I also tried flashing it through the normal recovery but it failed on the "verifying image" stage - I guess because I didn't resign the archive).
As far as the options themselves - only the last two should be carrier specific. I haven't researched anything about them, so I have absolutely no idea what they actually do. "lenik" just copied them from an official Softbank ROM.
God, i just checked JuicePlotter and i dropped 1% for 1h10m (everything off except the radio + setCPU to ~400Mhz when screen off). This is just crazy ... awesome ))))
Is the setting rom specific, or will it work om opendesire?
Sent from my HTC Desire using XDA App
slyn4ice said:
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings
Click to expand...
Click to collapse
LeeDroid ROM (LeeDrOiD_V2.1_A2SD+_.zip) build.prop includes:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
but no:
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
Just checked.
I'm running CM6.1 RC2, and the past couple of days I have experienced excessive drain, mainly in the first 50%. I attached a picture of the issue. I went to spare parts battery history to see the network usage, since in the about phone battery usage cell standby was 84% of the battery usage, and under network usage there was just an entry for 0, using the most network. When I clicked on '0' the settings application crashed. Yesterday it dropped 35% in 2.5 hours, before it slowed down. It was ridiculous, never used to have this problem, and the battery is only a couple of weeks old so it has to be software. Today it is at 53% after 7.5 hours, which is pretty decent, but at around 70% I disabled 3g and background data to save some energy for a few hours. Is there any way of figuring out what is causing this, or should I reflash? Could it be a CM6.1 RC2 bug? Anyone else having this issue? Thanks in advance
BTW I have no idea why the dialer was so high in usage I only had like MAYBE 15 minutes total of voice calls in 2 hours. The 0 is what I'm concerned about.
Anyone? Bump? No one else is having the issue? Still happening to me on RC3.
I've been getting that problem too.
I used to have battery life of up to 4 days (Mostly standby), now I'm lucky if I get 1.5 (Same usage).
I went in to spare parts and it crashed for me too.
Battery drain here too since cm 6.1
Sent from my T-Mobile myTouch 3G Slide using XDA App
Well '0' is he system's ID, 0 is root. In the graph the blue is bytes sent, red is bytes received. Have you checked other usage like CPU usage? That might be a better indicator of what's using your battery. Then from there you can start to narrow it down to a specific process or app. I'm using the latest nightly and don't have that issue, never have. I use a bit more battery than I think I should but nothing crazy.
Do you have wifi or bluetooth on? Those drain your battery like no other.
I havent used wifi at all today, unplugged at around 6:30, it's 3:45 now and I'm at 63%, but from around 9:50 to 11:45 and then from 12:20 to 2:20 I had airplane mode enabled since the time without a signal was at 70%, very low signal area. So it seems like for only 4 hours or maybe 5~ of non airplane mode time I should be at above 63%. I only had wifi on for a half an hour today. I'm considering going back to stock for a few days just to see the battery life comparison, and then nandroiding back to CM6.1. I always end up going back to AOSP-based roms in the end. I don't have a data plan on my phone at the moment, getting it today I'm pretty sure, so could all of the blue be from the phone continuously trying to access a website? But other people said they have the same issue and I'm assuming that they have data plans, so that can't be too much related. Hmm.
I also checked cpu usage and such like you suggested, there were a lot of things listed but all but two of them were too small to even have a bar. The two that did have a bar visible were minuscule to put it lightly, so that can't be an issue. Battery use in the about phone area always has cell standby at the top, normally between 40 and 80%. It would seem like there is way too much cell communication going on, moreso than normal. Cell standby stays at the top in even high signal areas, so it's not the signal levels. Kind of stumped here.
Well if the cell is in standby then it's linked to a tower and awaiting activity. Every now and then it 'checks in'. If it's doing that too often then that could seriously drain the battery. You're right though, I'd just switch back. Trouble shooting the exact issue wouldn't be worth the time. Maybe try flashing it again later, could have just been a corrupt download that didn't flash properly.
After conditioning my battery religiously (full to empty with every charge cycle) I am back up to about 15 to 16 hours from full battery to system shut down which is way better than the 10-12 hours I was getting when I first loaded RC2. CR_OTA ROM gave me up to 24-30 hours off of one charge with the exact CPU/2g/3g/wi-fi "routine" as I am using with RC2. Tracked battery usage with System Panel app and RC2 has a steady and even drain pattern ... an even diagonal line down the graph (100% to 0%). Cell standby uses a ridiculous 40% of the battery from full charge! On the stock ROM System Panel app shows plateaus throughout the day when the phone screen is off/sleeping where battery use is virtually non-existent. I'm going to load RC3 today and track the cell standby and battery usage. This time I am not going to use setCPU and just let the ROM run as the CM team designed it to be used and see if anything has changed. I tried this with RC2 and the battery still trended absolutely evenly from 100% to 0%. I can live with a 16 hour battery cycle for the CM ROM because it is very smooth and never has a glitch. The stock ROM is smooth as well but it has some buggy behaviors that I just cannot stand for and it does not run the latest GAPPS.
I've noticed i have exacly the same problem(was actually gonna post it when i found this thread)
Needless to say that on eclair my battery lasted ~48 hours constantly, not its drained in max 24...
The highest I have EVER gotten was 24 hours, and that was on a cm6.1 nightly build, pre RC2. I loaded cr_mod and experienced a HUGE drain. I had airplane mode on, just to test, and it dropped 7% in an hour, in AIRPLANE mode, with no screen on time. I went into spare parts and looked at the usage, and sure enough, "running" was at the top, with 99% of the time spent without sleeping. This has never happened before though, so I can probably attribute that to my modifications. I deleted a few apk's and de-odexed it before I flashed it, and I have a feeling something I did corrupted something else, so I'll flash plain old cr_mod and see where that leaves me. I should probably get back into the habit of full charge/drain every cycle. I used to do that until my battery started lasting longer than I was awake for, so I always had to plug it in at around 15 to 30%. I'll run some more "trials" and see what's going on.
Also, on an unrelated note, I love the stock rom, I always love the sense UI, but I hate HTC_IME compared to the froyo Latin_IME, is there any way at all I could port the froyo Latin_IME to the eclair stock rom?
Edit: also, I flashed dumfuq's OC kernel over cr_mod, could that have been the culprit to the battery drain?
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
KCRic said:
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
Click to expand...
Click to collapse
Actually, by process of elimination, the kernel was the issue. I remember hearing about there being a bug in the older dumfuq kernels with something idle being null, I really don't remember but it had something to do with sleeping. I flashed pure CR_mod and then 3.5 dumfuq and I experienced the same issue where it wouldn't sleep. I flashed 4.0, but I think it's too soon to determine whether or not the same issue with sleep is occurring.
I tried doing what you said with LatinIME.apk, I even imported the lib file from /system/lib on CM6.1, but the it was nowhere to be found in the system when I booted. It wasn't under keyboard settings, and HTC_IME was gone. I figured it was an incompatibility between froyo and eclair, since the stock sense rom is eclair and the LatinIME.apk is from a froyo ROM. Do I have to something more than just adb push the apk and lib file? I also tried installing it with a file manager, and no surprise, problem parsing the package. It's a system apk so I didnt expect it to be able to install via a file manager. Do I have to use adb install instead of adb push? I'm wondering if htc IME is so wired into the system that it won't work that way. What if I rename LatinIME.apk to htcime.apk or whatever the name of HTCime is and see if that works, because the system may be is treating that as the stock android keyboard, rather than a third party one, because it is labeled touch input in settings, just like LatinIME in aosp roms.
I'll experiment some more I guess
edit: Nevermind, 4.0 is draining as well, albeit less rapidly. Ah well. I guess I'll have to go back to CM6.1 if I want to do overclock. Shame, I love sense so much.
ANOTHER edit: nevermind, you were right, it isn't the kernel at all. It happens when I turn wifi off. I'm assuming that's because I don't have a data plan so it's continually retrying a server that it can't access. I don't know why it didn't do this on the stock HTC kernel, but I'm pretty sure it's the issue. If I turn wifi AND mobile data connection off, it stays at normal drain as well. Well, I'm at 11% and my battery app is estimating roughly 1 hour and 20 minutes remaining, so I don't know if that's GOOD, but I'll give it a good full charge tonight and run it tomorrow. I hopefully will have data activated tomorrow so I can really test it.
Hey guys new to the slide forum but not new to the site. I come from the G1 thread and we had the similar problem. How is your battery life on a 2.1 ROM? I have my phone rooted with a Sense ROM and it has 2.2 and i do see a bad battery drain as well. I remember froyo ROMs battery life may not be the greatest yet. I remember that was always a big problem over there and it looks like it still hurts here. Have you tried setcpu settings?
Maybe this information will help, i forgot to mention last time i posted that i'm not using a HTC device, i'm using Samsung Galaxy S, and there are more ppl with this problem on our forum aswell, so maybe someone can use this information correctly, i mean, it's either a program that's doing this or some strange freaky froyo process that not everybody has? or idk..
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
KCRic said:
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
Click to expand...
Click to collapse
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
MusicMan374 said:
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
Click to expand...
Click to collapse
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
KCRic said:
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
Click to expand...
Click to collapse
Yeah that'd be cool. It must have something to do with that, since it's the cell radio sucking battery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I flashed 6.1.0 stable, battery drain seems to be slightly less. I'm still at around 5 or 10% below where I was at this time on stock, with 9.5 hours off the charger, current level 57%. Although, I did use airplane mode for almost 2 hours, so really I'm like 10 or 20% below where I should be. I just can't figure it out, cell standby is at like 80% usage in this ROM. It's ridiculous, is it the polling intervals or something? How can it be so much less battery efficient than stock?
I flashed 6.1 RC2 with a low battery and had trouble with battery life. TMO's service was acting very strange for a couple of weeks and my cell standby was consuming a lot of juice. Flashed 6.1 RC3 with a well conditioned full battery. At first I used no setCPU just to see how things would go ... 11 hours from full battery to empty. Added setCPU to RC3 and got 27+ hours out of a full charge. Either TMO fixed it's towers or RC3 was better with cell standby because my network usage was not cranking overtime like it had been. Finally, I flashed 6.1 stable with setCPU and I average around 22 to 24 hours on one charge.
One observsation - when I first flashed RC2 I was really into my phone again. I was constantly tweaking it and flipping through options, testing apps, digging new Gapps, etc. ... bottom line I was just using my device waaaaay more than usual and I think that played a huge role in my (supposed) poor battery performance. All seems to be well with 6.1 stable.
So I hve been going nuts trying to figure out why my phone keeps rebooting. I'm in another country so getting a replacement isn't an option for me and it seems it hasn't helped some people anyways (After a while it comes back).
THe only constant I see is that the CPU usage after maybe 30 seconds after the phone comes on stays at 95-100% all the time. Only thing that makes sense is that the phone is shutting itself down before it melts down.
This kinda makes sense since it seems the more I try to do the more random the reboots become.....and battery life is beyond horrible. I did the steps to increase battery life and battery life is making this phone virtually unusable off AC power (EXample: Leaving from my Brother in laws apartment and travelling 10 floors down to my car results in 89% battery left. Phone is dead within the hour if i use it and 3 or 4 if leave it idling.
I tried killing all the tasks that te phone starts up with but nothing change the CPU usage. I thought maybe it was the kernel but I flashed the latest one from this thread: http://forum.xda-developers.com/show...RI+version+PRL [the undervolted version]. Not sure if that would help (THe info in this forums is so scattered and disorganized it makes my head spin.....and I'm a techie).
Also try flashing the combo package of the latest radio, PRI, NV etc and that doesn't work also....CPU usage is still through the roof.
I just got this a few days ago. I'm currently on:
HBoot 2.10 [s-off]
H/W 0004
Basband 2.15.00.11.19 [I was on this before I was rooted]
Kernel version 2.6.32.27-SBC-net-4.2.2-less-havs [email protected] #19 [Just flashed] ROM myn's Warm TwoPointTwo 9RLS 4)
Software: 3.3-.651.3
PRI Version: 1.90_0003
PRL Version: 60662
Can I get some help from people smarter then me. I'm at the end of my rope and I'm not convinced a handset swap is going to fix my issue esp. since this was BNIB straight from Sprint and other people who've had this issue and had a new phone seem to somehow have it later.
If i leave it alone it will reboot on its own eventually. If i switch from airport to turning on the cell data, reboot, turning on wifi......reboot, toggling 4g.......reboot, After a few web page searches......reboot, open up an application.....reboot.
This isn't temperature related as far as I can tell.....The app I have monitoring temp has seen this happen at 25 degrees and sometimes less.
PLEASE HELP
Ok.. firs tthings first..
when your phone is unstable and rebooting, dont use an undervolt kernel. Undervolt kernels provide less power to the CPU at set frequencies.
In my case, I discovered undervolting CAUSED reboots, because my phone couldnt handle anything under 950mv... there is such a range in the quality of the components that theres no way to always say yes, undervolting this much will work with every phone.
so 1: Use stock kernel ( for whatever rom your using.. also use a well established rom, not one of the 'hey, last night i got bored and made this' ones.. it may work, but it may be so buggy its what is causing your crash )
2: do a fresh install. run the phone with 0 apps added, see if it has the same issue. If it does, may be the phone itself. If it doesnt, its one of your apps.. install one at a time, and see if it improves.
and you made two posts why?
Didn't know they would move it. Posted in the wrong forum and they moved it as well. lOL. My bad.
I've been on a stock kernel up until I started trying different kernels. I will try the other one then.
My CPU usage is the problem I think. I have both memoryusage and system monitor and both report the same thing.....95-100% usage constantly. If I could resolve that then maybe my phone would work properly.
Didn't know they would move it. Posted in the wrong forum and they moved it as well. lOL. My bad.
I've been on a stock kernel up until I started trying different kernels. I will try the other one then.
My CPU usage is the problem I think. I have both memoryusage and system monitor and both report the same thing.....95-100% usage constantly. If I could resolve that then maybe my phone would work properly.
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
Sometimes the battery works great, lasts a couple days. And sometimes, I get strange spikes where the battery drains extremely quickly (see attached images).
I have tried:
1. New device - I swapped my unit yesterday
2. Hard reset - restore all factory settings (and erase everything) off the phone
3. Battery cycle - i.e. let the battery run out entirely, recharge it from scratch
I have also tried diagnosing the issue via the stock battery app, GO Power Master, and BetterBatteryStats, but I don't see anything out of the ordinary when the battery usage spike occurs. Maybe there is some process running wild, but it doesn't seem to do anything...
Has anyone had similar issues? The only non-Google Play store app I have installed is Visual Voicemail - the apk I downloaded from this board.
You have tried everything I would normally suggest, but might have noticed something. Your sharp drop coincides with that red band on your signal bar. The red part signifying no cell tower signal. The sharp drop seems to start there. Is your phone stuck searching for cell towers when it has already re-established a signal? The earlier dip in the battery also has a red bar under it.
Also battery performance is not linear. If you are at 50% after 24 hours, you will not necessarily get another 24 hours. I am alwaysfinding myself at 50% after 18 hours and think, "Cool, I've found the right kernel" but sure enough I'm still plugging it into charge at 24 hours!
I know you say you normally get two days (which is very good) but this is all I can think of.
I use a powerful automation app called Tasker. With it you can set any phone setting to any phone condition. I've just checked, and it is possible to set a profile based on signal strength. With this you could specify a weak or no signal to do any manner of things, from play a notification sound, to turn off 3G and auto-sync. Set an exit task and it will also turn 3G and auto-sync back on when signal strength is healthy again. Might be worth a try.
Edit: If you have root access, Tasker supports the app 'Quick Boot Plus' as a plugin. With this you could set Tasker to reboot your phone if it is out of signal for more than 'x' seconds. I know it might not be very practical, but it would tell you if you we are looking at the real culprit.
Another edit: Scratch that. You could set Tasker thatif it sees no signal for 'x' seconds, turn on airplane mode, wait 'y' seconds, turn off airplane mode. No need to buy a plugin.
Thanks, wnp_79 - appreciate the thoughtful response!
Yes, that's a good point - there is a drop in battery starting with the red line for the signal. I take the subway to/from work in the morning and evening. But I don't see any problems connecting after I get outside (i.e. it doesn't seem to be searching for signal).
Perhaps next time I can try setting airplane mode on/off when I notice the battery draining quickly - and see if that helps the issue. If it does, clearly it's a signal issue.
I like the Tasker idea, I will give that a try! Thank you for the suggestion.
I wasn't by any means expecting another 24 hrs, but that drain of "50%" occured over a span of like 3 hours... with no screen usage (i.e. the phone was just sitting next to me at the desk, supposedly "idle").
Whatever you do, don't cycle your battery deeply unnecessarily.
Sent from my HTC One X using Tapatalk 2
Thanks tsleng, will keep that in mind.
I guess I am surprised other people haven't seen this issue. Maybe it's something specific to my software...
I've got this issue but it's down to my signal. At home it's fine and battery last's me well but as soon as I get to work my battery starts to dip due to Vodafone having poorer signal. Bad signal is killing my battery too bad we can't change radio's as of yet due to no S-OFF.
what happens when we can s-off? i mean what adv will we encounter regarding with the issues that we are having?
mohaimed said:
what happens when we can s-off? i mean what adv will we encounter regarding with the issues that we are having?
Click to expand...
Click to collapse
Well S-OFF, we can unlock bootloader without having to use HTCDev meaning we can revert back to stock easily and without it tampering the status. We can lock it back to it's original state.
We can flash kernels without having to use fastboot.
We can flash radios. By flashing other radios we can improve our signals if one radio is bad, an improved signal is friendlier on the battery.
I get a weird spike too but mine causes the phone to die. Also mine was done overnight when I was sleeping. (see attachment) I'm not really sure what I can do. I hope this was a one time problem...but i'm not so sure. I'm still under warnty and this is my second HOX
neocryte said:
Sometimes the battery works great, lasts a couple days. And sometimes, I get strange spikes where the battery drains extremely quickly (see attached images).
I have tried:
1. New device - I swapped my unit yesterday
2. Hard reset - restore all factory settings (and erase everything) off the phone
3. Battery cycle - i.e. let the battery run out entirely, recharge it from scratch
I have also tried diagnosing the issue via the stock battery app, GO Power Master, and BetterBatteryStats, but I don't see anything out of the ordinary when the battery usage spike occurs. Maybe there is some process running wild, but it doesn't seem to do anything...
Has anyone had similar issues? The only non-Google Play store app I have installed is Visual Voicemail - the apk I downloaded from this board.
Click to expand...
Click to collapse
You have the LTE version of the one x Maybe they can help you there:
http://forum.xda-developers.com/forumdisplay.php?f=1538