Hi guys,
as per topic title, I'm experiencing a monstruous battery drain.
In the last few weeks I devoted a lot of time in understanding how to get more juice, with very good results.
I removed (and noticed developers) every power hungry app I had. I recalibrated my battery.
Suddenly, all of this became futile, because of this 100mA battery drain while phone is in standby, EVEN with everything (wifi, radio, gps, bluetooth, everything) off.
Like the phone itself takes 100mA to just stay in standby.
Now, this is way, way higher than "healthy" (5-8mA from users experience here on xda), and means 5-6% battery lost every 30 minutes. Doing NOTHING.
What I did:
I'm using OpenDesire since 4.0.23 , upgrading to every stable version. Today I'm at 4.0.32
Also, I upgraded the radio to latest version, 32.48.00.32U_5.11.05.14
and I noticed very good improvements.
Then, I flashed the RIL.
And the battery drain began.
Today, no matter what radio I flash, which revision of OD I revert back... Nothing seems to change, the battery drain stays.
I tried to:
- full total wipe/factory reset, always. Only app installed is CurrentWidget, to measure draining ; NO settings restored with Titanium Backup
- EVERY radio since 32.41.00.32U_5.08.00.04 ; flashed by Clockwork Recovery, phone only ; every time I tried the latest radio, I both tried without and with the suggested RIL
- OpenDesire from 4.0.23 to 4.0.32 ; Tried 4.0.23 and 4.0.28 with EVERY radio ; other OD releases tried only with stock radio (32.44.00.32U_5.09.05.30_2) and latest
- Umounted sdcard; reformatted sdcard; different sdcard; no sdcard at all
- restore my nandroid backup, made before all of this, which brings me back to my stock sense days... but with the hipotethic radio mess, and the same battery drain issue.
I don't really know what else to test.
I can't just get rid of this horrible 100mA battery drain.
Anyone has hints, suggestions, solutions ?
As of now, my Desire is ... barely a phone.
Thanks
Flash a RUU and start from fresh?
http://forum.xda-developers.com/showthread.php?t=695667
Uhm... if that's the full package, with rom and radio, may be worth the try.
I hope it's doable without Windows. Only linux here...
Oh, great... I'm having issue "waiting for bootloader".
I launch RUU
phone reboots
stops on HTC screen
RUU on PC gives error 171.
Edit:
Appearently, it's very important that the phone is recognized by Windows as "MY HTC" in system resources.
So, I did:
- install HTC Sync. Reboot. Plugged in the phone. This gets installed the necessary drivers.
- DISABLED WINDOWS 7 AUTOMATIC DRIVERS SEARCH. I think this is a windows update thing, don't really remember... I'm a linux guy ^_^
- Reboot phone in bootloader (pressing power while keeping pressing VOL- ) ; then, Windows will come up with an unrecognized device called "Android 1.0"
- Manually installed drivers under c:/programs/HTC Sync/HTC Drivers.
- Started RUU
- phone rebooted. Bad windows sound told me drivers dailed. So I went there... and the "HTC bootloader" driver appeared. Then I manually installed "MY HTC" to that device... and RUU finally started !
Also, I *HAD* to start RUU from normally booted phone. Otherwise, it failed the "minimum 30% charge" check.
chareos12 said:
Oh, great... I'm having issue "waiting for bootloader".
I launch RUU
phone reboots
stops on HTC screen
RUU on PC gives error 171.
Read here and there, solution seems
unplug & replug phone leaving as is
(note - unplugging the phone exposes the white bootloader screen, wuth RUU option only ; replugging pops up again HTC screen)
restart RUU
but isn't working:
RUU on PC can't read the phone, and gives error 170.
DAMN !!
Click to expand...
Click to collapse
Having the same problem (100 mA drain/hour in standby) ever since I started experimenting with roms/radio etc.
Going back to complete stock hasn't helped me though
Oh... damn, I just succeeded with starting RUU flash.
Oh, well. Let's see how it goes.
swine... said:
Flash a RUU and start from fresh?
http://forum.xda-developers.com/showthread.php?t=695667
Click to expand...
Click to collapse
Successfully done...
but the 100mA battery drain in standby is STILL THERE
I begin to think just flashing 1-2 radios made some mess7damage that can't just be solved with another radio flash...
SetCPU
Helps my battery time.
zHk3R said:
SetCPU
Helps my battery time.
Click to expand...
Click to collapse
... and I used it myself.
But here I'm talking about the barebone power usage, no cpu spikes, no software installed.
No phone should dry that amount of power by being on total unusage.
SetCPU is awesome, but doesn't help here.
Also trying safe mode (pwr on while pressing menu)
...
7% / 60 minutes.
This means 3-4% / 30 minutes, or 50-60mA / 30 minutes.
Oh, I had WiFi on.
Trying with WiFi off now...
Well that's some crazy battery use mate.
I have currently installed:
* OD version .32
* Radio .30_2
I have installed other ROMs before for testing, and I have tested all the radios newer than the 30_2 one. All bar the very latest one 32.48.00.32U_5.11.05.14, as I have no need for it.
I have Current Widget set to update every 1 min, and not create a log or text file when I test my use.
With the screen off for 1 min, and then turned on, Current Widget shows either 4mA or 5mA, which is my standby power consumption!
After trying what you have with the RUU I don't know what else to suggest, but wish you luck.
#Edit# Since taking the phone off charge at 8am, I have lost 6% of battery. But so far today I have only sent one message.
chareos12 said:
Also trying safe mode (pwr on while pressing menu)
...
7% / 60 minutes.
This means 3-4% / 30 minutes, or 50-60mA / 30 minutes.
Oh, I had WiFi on.
Trying with WiFi off now...
Click to expand...
Click to collapse
... and with WiFi off, it's 3% / 30 minutes. CRAZY.
swine... said:
Well that's some crazy battery use mate.
I have currently installed:
* OD version .32
* Radio .30_2
I have installed other ROMs before for testing, and I have tested all the radios newer than the 30_2 one. All bar the very latest one 32.48.00.32U_5.11.05.14, as I have no need for it.
I have Current Widget set to update every 1 min, and not create a log or text file when I test my use.
With the screen off for 1 min, and then turned on, Current Widget shows either 4mA or 5mA, which is my standby power consumption!
After trying what you have with the RUU I don't know what else to suggest, but wish you luck.
Click to expand...
Click to collapse
Thanks mate.
Question: have you ever DOWNGRADED a radio ?
If so, did you take any particular precaution ?
Also,
Just to be sure I tried everything possible, before sending my device to repair (risking many days without it, or even they discover my rooting here and there...)
may I ask you HOW do you flash the radio ?
My procedure:
- basic: I rooted via unrevoked 3.21 - all right with root permissions and got ClockWork recovery installed and working
- I (re)boot in Clockwork
- I go to Install zip from sdcard option
- I choose the radio zip file, all downloaded from the xda thread
- I apply and confirm the radio (file name is NOT update.zip ... is this an issue ?)
- phone starts to work. A progress bar apperars, fills only by 1/10th, 1-2 seconds, then suddenly process is complete and asks to reboot from menu. So I press back, and reboot.
- Phone don't reboot. It just sits 15-20 seconds saying "flashing radio" or something, but showing no progress bar. Then phone reboots. Almost immediately, reboots again
- Phone reboots back to os usable state. radio version is changed in system infos.
If I made something wrong, or something is missing or wrong in my procedure, maybe I can still solve all of this
chareos12, as you probably know by now: I got the exact same problem.
Updating/replacing radio roms/normal roms/RIL/RUU etc has nog helped me thus far.
I have one question however, what program do you use to monitor mA usage/hour?
(Nvm, found it, Current Widget, duh.... Mine is at 87mA at the moment....)
Secondly, I will follow this topic closely and help you wherever I can.... Let's fix this!
chareos12 said:
Thanks mate.
Question: have you ever DOWNGRADED a radio ?
If so, did you take any particular precaution ?
Also,
Just to be sure I tried everything possible, before sending my device to repair (risking many days without it, or even they discover my rooting here and there...)
may I ask you HOW do you flash the radio ?
My procedure:
- basic: I rooted via unrevoked 3.21 - all right with root permissions and got ClockWork recovery installed and working
- I (re)boot in Clockwork
- I go to Install zip from sdcard option
- I choose the radio zip file, all downloaded from the xda thread
- I apply and confirm the radio (file name is NOT update.zip ... is this an issue ?)
- phone starts to work. A progress bar apperars, fills only by 1/10th, 1-2 seconds, then suddenly process is complete and asks to reboot from menu. So I press back, and reboot.
- Phone don't reboot. It just sits 15-20 seconds saying "flashing radio" or something, but showing no progress bar. Then phone reboots. Almost immediately, reboots again
- Phone reboots back to os usable state. radio version is changed in system infos.
If I made something wrong, or something is missing or wrong in my procedure, maybe I can still solve all of this
Click to expand...
Click to collapse
I think I always downgraded when trying the new batch of radios But really, yes I have changed version number up and down, and the one I found the best performer was the radio 30_2. But that may only be for me, even though a lot of other users report that it is also good. I did find much higer battery use on the 32.47.00.32U_5.10.05.23 radio, but after returning to 30_2 all was well again.
I would say the way you are doing it would be fine. And no it does not need to be called update.zip. I'm busy right now working, but will check back later if I think of anything extra. ;P
Exactly, CurrentWidget. That also reports the same mA variations as dmesg, so I take as trustable.
Yeah, let's hope it's fixable !
I fear sooo much repairing centers...
I'm no expert but it should be -2mA if in standby with everything off (including the display) and >80mA with display on. >30mA ish drawn is not possible with all hardware off/idle except by the display. That's unless you have the "Android System" bug I had where it consumes 10-30% CPU just resting.
What current discharge reading do you obtain with same everything except display on (black background)?
th3 said:
I'm no expert but it should be -2mA if in standby with everything off (including the display) and >80mA with display on. >30mA ish drawn is not possible with all hardware off/idle except by the display. That's unless you have the "Android System" bug I had where it consumes 10-30% CPU just resting.
What current discharge reading do you obtain with same everything except display on (black background)?
Click to expand...
Click to collapse
Consider that right now I'm on the stock Sense...
disabling everything (any sync/background data), wifi off and then airplane mode on, sensor off, gps off, led notifications disabled, display brightness manually on the exact 50%, black background, ONLY widget across the 7 pages is CurrentWidget - which is also the only installed app... + Estrongs file manager ...
175-185mA.
Which is
your normal 80mA + mine sick 100mA ...
as I said before, it is like the bare phone drains 100mA battery for just staying barely alive.
oh,
12 minutes uptime
Android System is accounted for 17 seconds (4636 menu)
but then, going in settings battery infos, I read
CPU total 49s
CPU foregroung 20s
Android system - usage 70%
Display - 22%
weird...
IF it is the bug you are talking about, how could it survive trough 4 OpenDesire releases and a jump back to RUU ?
The Sense ROM you have is totally default with nothing added except CurrentWidget?
You need to go barebones to figure out what is happening here. The 80-115mA baseline is from many users at 0% brightness on a black background. You need to also log your CPU usage with something like OSMonitor, System Panel or Show CPU Usage to see if Sys, Usr or IO are experiencing abnormal load. In apps like OSMonitor, see the debug errors it is showing you under Messages.
On some ROMs it has been my experience that the cell network, accelerometer and/or touchscreen goes haywire causing large battery drain in idle or use. Consistent network locations and network provider search was a key problem. That made me lose 5-10 hours from my usual battery life. There was no way that I could fix it except changing ROMs and starting from scratch. I reverted back to a clean HTC 2.2 ever since with no such oddities.
----------------------------------------------
- Sent from HTC Desire via Tapatalk -
chareos12 said:
weird...
IF it is the bug you are talking about, how could it survive trough 4 OpenDesire releases and a jump back to RUU ?
Click to expand...
Click to collapse
Admittedly, the existence of it after the change to stock RUU also had me confused. Providing you did complete wipes, that should have wiped out any soft bugs.
----------------------------------------------
- Sent from HTC Desire via Tapatalk -
Hey guys,
the strangest thing since i'm using android happened to me right now.
I realized that my DHD starts to lag after 2-3 days, a reboot fixes it, (USB debugging always enabled) but that's not the problem :=)
so i wanted to restart!
all apps stopped working unexpectedly....
really everything, launcher, there are masses of popups coming up, no idea what really happened.
the only thing i know, htc sense seemed to work (i was so intelligent to try to start launcherpro, which created a default shortcut, so then everything including launcher pro stopped working, no chance to to anything (usb connection not detected... nothing)
popups just reoccur directly after clicking them away. no idea at all.
i found this:same problem on another phone @xda
but there hasn't been a solution too.
so i just wanted to tell anyone out there experiencing the same with a dhd.
u're not alone.
i'm reflashing. (another rom, it was revolution hd 3, but i think its not rom related - but i have to mention, the stock rom - used for 2 months before- never had anything similar - rev. hd was just in use for a few weeks now (1 or 2).
howdi
cV
update:
guys this really suckz, i dont know whats different with my DHD and the combination of revolution HD rom, but this is the second time this happened!
the first time, i realized (not as written above) i was using rev. HD 2.1
now it was on 3.0
i know, there's a 3.1 out there, but i really dont want to test it.. something's really strange here? (same error happened another time :===/)
I suggest you to reset your Desire HD
thanks,
hennailiao said:
I suggest you to reset your Desire HD
Click to expand...
Click to collapse
... directly flashed a new rom (there was no other possibility)
thanks for the response, i hoped that somebody can exchange some experience with this problem to prevent it in the future
greets,
Problem solved on my HTC HD2
Just solve the problem on my HTC HD2 applications force to stop error, no need to soft of hard reset required no need to update or re-install ROM, Go to Manu >Rome Manager ( My version is v4.8.1.3 > Utilities > TAP ON Fix permissions ( Fix file system permissions, this often fixes force close problems) after waiting few minutes reboot and enjoy ...............
Good Afternoon,
I flashed my phone with a bunch of stuff a few weeks ago, and it's been running spectacularly, but the past few days, I've been having some issues getting my phone to boot completely. ADW would keep force closing, and my phone would randomly reboot, and I'd sometimes need to battery-pull to restart it from being frozen completely. Also, my volume buttons no longer work, and the screen occasionally goes 4-split screen from the keyboard opening ( I'm assuming flex ribbon ). Now today, after the the splash screen, the phone screen just goes black and stays like that. From reading around, I think I know what the problem is, but I was wondering if anyone more knowledgable could give some insight as well, specifically, if there's any chance it could be a software issue and **crosses fingers** not a hardware issue. I attached what I could get of the adb logcat.
Also, if it helps, here's some info about my phone:
Rooted & S-Off, with newest radio
Rom: nickmcminn60's XM-8 Vr 1.1
Kernel: Miguel's
Mods: darktremor A2SD & ?Firerat's? Custom MTD Partition
Any help or advice would be much appreciated.
1) don't use Miguel's kernel with these latest builds.
2) did you fix permission with rom manager to help with fc's.
3) I don't think this will fix the screen issues, that's is mostly hardware related.
Sent from my fingertips using Android.
Thanks for the help! I hadn't done fix permissions yet, as last time it somehow broke my rom. Unfortunately, I tried doing a nandroid backup first, yesterday morning before trying fixing permissions, and after my phone finished and rebooted, the phone just froze, and I couldn't reboot into recovery ( my volume buttons don't work ), and after a few reboot attempts, my screen died. I'm going to try ADBing into it tonight if I can.
In case I can get it fixed though, what kernels should I be using instead? I tried drowningchild's, but I seemed to have fewer issues with Miguel's.
Use stock cm kernel when using cm roms if using sense I believe nbetcher has a good kernel
Sent from my fingertips using Android.
Greetings.
My problem is quite curious - and so far I was unable to find exact case on those forums :
When I installed ICS on my DHD ( Blackout ICS, AospX BR4 BR5, also tried JB - Jellytime beta 14) and installed WIFIX
some time after turning WiFi cellphone slowdowns (any button pressed takes minutes to react) and after a while everything comes to complete halt
Sometimes it occures few seconds after turning on wifi , sometimes it gets after performing any actions ,and there is 100% chance that it will get stuck when going to sleep ( Few times tested it while listening to MP3 - suddenly music stopped and everything was dead).
When I go back to my original software, everything is working as intended - A pity as I really like ICS and JB
When I was flashing those roms always did Data wipe , Cache wipe and Dalvik wipe, not to mention that I saw Blackout install doing format on my partitions.
Overclocking and Underclocking don't change anything on the phone.
Edit : Installed Rom : Nik Project X v4.1 - insteald of hanging, it now resets itself every so often when wifi is on. After few restarts , it have problem with turning on WiFi
Dont flash wifix.
Include format all partitions except sd card.
Chech battery cover.
Reset router.
Sent from a dream.
same problem
Hi,
I have the same problem as you. Have you solve it?
After installing ICS, whenver i turn on my wifi and surf/download, it will restart
But if i turn off my wifi, no issue. It won't restart for whole day.
I'm running ViperX 3.3 at the moment. Was running ViperX 3.2 before this and 2.7 before that. Once I installed 3.2, my phone ran well for a few days and I was quite pleased because I've been having tons of issues before that. And one fine day, it just powered down during use. Upon rebooting the device, it got to my home screen and shut down within 5-10 seconds. Tried that a couple more times and it didn't work so I just ran a fresh install of my ROM, with factory reset, clearing cache and dalvik as well. Got to setup screen and powered down again. Tried it again, worked for half hour and powered down again. Got annoyed, flashed cm10 nightlies, but had issues with logging into my google account, would give me the 'unfortunately google account manager has stopped working', I went to accounts and it was saved there but play store would display a 'error retrieving data' sort of message. Removed my sim, switched it to a backup phone and ran viperx3.3 again, left it for 2-3 days and when I noticed that it wasn't powering down, I switched back. Ran smooth for a day. It just shut down again. I have absolutely no idea what to do now.
Another odd thing that I've noticed since installing ViperX 3.2/3.3 is that my clock speed has been capped at speeds under 1.5 (1.3, 1.4, 1.2, changes every time I freshly install my ROM). Haven't messed around with overclocking/undervolting at all. Clock speeds are set to 1.5 max and the 54 min but if I change the min to 1.5, it stays at 1.2/1.3/1.4.
Please help. I've tried searching extensively but can't seem to find any threads similar to this.
Have you see this thread??
However, try to install ViperX 3.3.4 and check if you have the problem
Guich said:
Have you see this thread??
However, try to install ViperX 3.3.4 and check if you have the problem
Click to expand...
Click to collapse
I was running 3.3.3 just now and it powered down, I just tried reflashing without wiping but it powered down. I'll try with wipe this time but I'm pretty sure it will power down within the day if not soon as I'm done. Going through that thread you just posted to see if anyone else has faced similar issues.
EDIT: Happens after reflashing with wipe as well.