[Q] 100mA battery drain while on STANDBY !! ARGH !!

[chareos12]

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

 

[swine...]

Flash a RUU and start from fresh?

http://forum.xda-developers.com/showthread.php?t=695667

 

[chareos12]

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...

 

[chareos12]

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.

 

[Smultie]

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 !!

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

 

[chareos12]

Oh... damn, I just succeeded with starting RUU flash.
Oh, well. Let's see how it goes.

 

[chareos12]

Flash a RUU and start from fresh?

http://forum.xda-developers.com/showthread.php?t=695667

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...

 

[zHk3R]

SetCPU

Helps my battery time.

 

[chareos12]

SetCPU

Helps my battery time.

... 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.

 

[chareos12]

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...

 

[swine...]

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]

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...

... and with WiFi off, it's 3% / 30 minutes. CRAZY.

 

[chareos12]

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.

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

 

[Smultie]

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!

 

[swine...]

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

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

 

[chareos12]

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...

 

[th3]

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)?

 

[chareos12]

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)?

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 ?

 

[th3]

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 -

 

[th3]

weird...
IF it is the bug you are talking about, how could it survive trough 4 OpenDesire releases and a jump back to RUU ?

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 -