Battery Life and Radio info!

[Guest Arthur Hucksake]

Just thought I would share my over night findings, I have been switching between Radio types. I'm using the latest Modaco r3.1 btw.

When I upgraded the rom originally I always felt there was something going slightly wrong with the battery life. I had the same on one of the Froyo roms also which was accounted for by the display battery usage, but then

when the display was off it never came into it.

Upgrading roms I noticed that the battery life usage for the Android system was something crazy like 96% and it never seemed to last aslong as it use to.

I was using Radio 32.36.00.28U_4.06.00.02_2 I believe.

Well, last night I went back to the older radio 32.30.00.28U_4.05.00.11 and under my battery usage now Cell Standby is at 47%, Phone Idle 45% and Android system just 6%.

Much better, just what it's meant to be.

So basically, some people who were blaming the rom.... it isn't, it's HTCs retarded radio releases.

- D -

[Guest BlackLine7]

I am having battery problems since Richard Trip included a 8mb hack to his kernel. At the time I was already using a newer radio. I think it was the 36 one.

Is there any changelog for the radio updates. What do we loose if downgrade to 30?

P. S.: on xda AdamG posted an older radio (26) and also an older HBOOT 0.66! Just wanted to share.

[Guest lenik]

I have unlocked TW version of Desire and I've rooted it to 1.15 and had wonderful battery life (about 3~4days on one charge), then upgraded to MCR r3.1 and noticed discharge rate about 10%/hour, it ate the whole battery in just few hours. Tried to go back to 1.15 -- no difference, so now I have 1.21 with no modifications and have to recharge every night and hope it will live through the day. The phone is quite warm, when I touch it on the back.

Today I went out and drove about 70km to the another region with slightly different cellular provider. And here's what I notices on my JuicePlotter -- FLATLINE since 18:30 to 20:50 -- almost exactly the time I was not at home. Phone went totally, surprisingly cold. After I came back home the battery drain started again. Currently my radio version is 32.36.00.28U_4.06.00.02_2 and I wonder if there are any ideas how to fix the battery situation, except moving closer to my friend's home =)

Edited June 13, 2010 by lenik

[Guest spammyspam]

FWIW I'm on radio 32.30.00.28U_4.05.00.11 and my battery life sucks.

[Guest 1uk3]

I was having a massive battery drain issue also with the MoDaCo ROM but just installed SetCPU for Root and everything now seems fine when I have it set to underclock when in standby. Been connected to Wi-Fi and auto sync etc for 4 hours now and battery is still showing as full :)

I've never used the stock ROM so have no idea what the battery consumption is like when using that compared to the MoDaCo one.

I'm using Radio 32.36.00.28U_4.06.00.02_2 but might try using another if that seems to be the battery drain issue.

Edited June 13, 2010 by 1uk3

[Guest Namtaffy]

Well I have tried all the custom and stock roms and have come to the conclusion that there isn't much of a difference between them regarding battery life. Setcpu seems to help a little if using Richards kernel. But basically if I use my phone it uses battery! Lol if I use WiFi it uses more battery, gps - even more, task the processor by running games etc. I have gotten used to the idea I have to charge it when its low! So I just do that and use my phone to the max

[Guest encrypt]

Did you guys try the latest radio? 32.37.00.32U_4.06.00.16_2

It would be good if someone could compare all the radios for all to see which is the best radio at the moment...

[Guest kevinof]

I don't think its related just to the radio. I have just gone from R3 to R3.1 and have noticed a massive increase in battery life. I took it off charger at 8am yesterday and its still going with 30% left at 9:29 the next day. This is with mail update every 15 mins, some browsing etc. On R3 I couldn't get more than 12 hours on a charge.

FYI - my radio is 32.30...

Just thought I would share my over night findings, I have been switching between Radio types. I'm using the latest Modaco r3.1 btw.

When I upgraded the rom originally I always felt there was something going slightly wrong with the battery life. I had the same on one of the Froyo roms also which was accounted for by the display battery usage, but then

when the display was off it never came into it.

Upgrading roms I noticed that the battery life usage for the Android system was something crazy like 96% and it never seemed to last aslong as it use to.

I was using Radio 32.36.00.28U_4.06.00.02_2 I believe.

Well, last night I went back to the older radio 32.30.00.28U_4.05.00.11 and under my battery usage now Cell Standby is at 47%, Phone Idle 45% and Android system just 6%.

Much better, just what it's meant to be.

So basically, some people who were blaming the rom.... it isn't, it's HTCs retarded radio releases.

- D -

[Guest pina]

took off the charger saturday night, around 3, battery was at 51%. Sunday morning, around 11, still 49% left. Radio version is 32.30....

[Guest Arthur Hucksake]

I don't think its related just to the radio. I have just gone from R3 to R3.1 and have noticed a massive increase in battery life. I took it off charger at 8am yesterday and its still going with 30% left at 9:29 the next day. This is with mail update every 15 mins, some browsing etc. On R3 I couldn't get more than 12 hours on a charge.

FYI - my radio is 32.30...

If your feeling brave, try the latest radio and see how battery life fares.

32.30 seems to be about the best so far, not sure whats going on with HTC and their crappy radio updates tbh.

One thing that I have noticed though, on the latest radio. My mobile data is permanently locked to HSPDA. It use to be a case of it saying 3G at the top until I use net access but now there is always the

little H there. Not sure whether that's the radio or MCR 3.1 though.

Edited June 14, 2010 by Arthur Hucksake

[Guest Jagdish]

I saw this thread and wanted to check somethin...

about 2 weeks ago i flashed pays rom BS (over from XDAs) and wanted to flash the 32.37.00.32U_4.06.00.16_2 radio as well, see if it improves anythin. i experienced a nasty battery drain to the extent that it made me switch to Pauls 3.1, flashed Richards V11 kernel (seems to be the one working for meh) and reverting back to older version of radio(32.30.00.28U_4.05.00.11), using setcpu my battery still appeared to be draining quite fast, yesterday, after reading this thread i decided to flash the newest of radio versions, went back to 32.37.00.32U_4.06.00.16_2 again and well, 10 hrs later, during the night (after unplugging the device from the charger before bed time) its on 90%, meaning 10+ hrs took only 10% with no use woots o' ever...

thats a major improvement and has anything to do with the radio, coz thats the only thing i changed...

hope my experience helps anyone!

Edited June 15, 2010 by Jagdish

[Guest lenik]

hope my experience helps anyone!

thanks! :)

Edited June 15, 2010 by lenik

[Guest Jagdish]

your experience will be much more helpful, if you specify exact radio versions instead of "old", "new" and "newest" :)

Noted and changed accordingly :)

Just as a side note, battery life now seems awesome, i got to bout 50% with heavy-moderate usage after 24 hrs!

Edited June 15, 2010 by Jagdish

[Guest pina]

I noticed that the alarm clock does use a lot of battery power. Only lost about 3% during night (radio ON). Then during an hour, my alarm went on at least 5 times, because I kept snoozing it. The battery lost in 1 hour about 10%... Saw it perfectly in juice plotter.

Edited June 15, 2010 by pina

[Guest lenik]

Just a short follow up to the previous messages. I've been struggling with poor battery life (read: 10%/hour) last week, and finally I have found a solution. I have picked stock RUU from local cellular provider, unpacked it, made an upgrade.zip and flashed it. Battery discharge curve became flat and horizontal (using "Juice Plotter").

Using stock RUU image I've tried to flash a few different radio images (32.30.00.28U_4.05.00.11, 32.36.00.28U_4.06.00.02_2, 32.37.00.32U_4.06.00.16_2), but did not see any significant difference, so I decided to use 32.36.00.28U_4.06.00.02_2 for now and maybe investigate this later when I have more time.

Unfortunately stock ROM has some disadvantages, so currently I'm looking into building a joint ROM from one of rooted images, but including some settings I've found in local stock RUU. Hopefully this will fix the issue completely, because now I'm getting less than 1% discharge in an hour in standby mode and this is pretty much enough for me.

[Guest spammyspam]

Unfortunately stock ROM has some disadvantages, so currently I'm looking into building a joint ROM from one of rooted images, but including some settings I've found in local stock RUU. Hopefully this will fix the issue completely, because now I'm getting less than 1% discharge in an hour in standby mode and this is pretty much enough for me.

That's astonishing. I lose at least 5-10% per hour standby on my stock ROM. I've rooted now so will have a play, but I don't see myself getting anywhere near 1%.

Perhaps this is network dependant?

[Guest BDrift]

I was just thinking ... the standby times on the HTC website are listet at like 300+ hours and we are struggling to achieve like 100 hours (1%/hour). Funny how far off the numbers are ^^ even if I enable flight mode I'm not getting close to 1% every 3 hours.

[Guest lenik]

I was just thinking ... the standby times on the HTC website are listet at like 300+ hours and we are struggling to achieve like 100 hours (1%/hour). Funny how far off the numbers are ^^ even if I enable flight mode I'm not getting close to 1% every 3 hours.

last night I've lost about 3% for 8 hours, while the phone was receiving some messages while on standby. it's not very precise, but rough calculation gives about (100/3)*8=264 hours. my place it not the ideal in terms of reception and processing of the messages took its' toll, so I can easily imagine than in the ideal reception conditions the standby phone can easily reach 300hours+, however in the real life, when neighbours sometimes vaccum the floor or microwave theirs sausages, it's more likely going to be closer to 180-200hours or less.

if you worry your android system does not behave well, try *#*#4636#*#* and then "Turn Off" radio in the phone settings, my phone gives absolutely horizontal line in this mode (for some reason I don't trust "airplane mode" to switch off the radio completely).

[Guest lenik]

I lose at least 5-10% per hour standby on my stock ROM. I've rooted now so will have a play, but I don't see myself getting anywhere near 1%.

Perhaps this is network dependant?

here are some thoughts. last week, while wrestling the battery drain, I have noticed that the back bottom part of the Desire is quite warm. not the battery, but more likely a processor or radio module. when I switched radio off, the warmth was gone as well as the battery drain. I have tried different radio and system ROMs and had no improvement at all, except, as I said, when I drive about 50km away, everything suddenly become normal.

also, at the same time, a friend of mine have got another Desire from local provider and it was working perfectly until he flipped "Use wireless to determine location" check box. In 5 minutes he started to complain about the same problems -- warm back side and enormous battery drain. Unchecked the check box and everything was back to normal. This made me think there are some incompatibilities between networks and operators and this might pretty much result in radio module disconnected and connected back every second or so, sucking juice from the battery at the alarming rate.

Next my move was, obviously, to disable "wireless location" services. Still no results.

Then, thanks to my friend, I've got the firmware update from the local provider and found some parameters in build.prop, which were quite different from the ones I had. I have carefully merged "ro.ril.*" sections of the config files and rebuilt new firmware update image. Which, more or less, solved the problem.

Still, there's a question about how different radio versions behave regarding the battery use, but it's not critical and I can check this later.

Summing it up,

1) turn off the radio to see if this problem is really radio-related

2) disable "wireless location" feature and

3) get build.prop from someone's phone with good battery life (belonging to the local provider) and try to use his radio settings in your new firmware image.

Edited June 19, 2010 by lenik

[Guest spammyspam]

3) get build.prop from someone's phone with good battery life (belonging to the local provider) and try to use his radio settings in your new firmware image.

I've downloaded the firmware for my operator. Can you explain what I should do from here? I'm running MCR 3.1.

In the meantime I'm going to use the radio that shipped with the operator's rom. I've actually skipped over it after rooting.

[Guest squrl]

Then, thanks to my friend, I've got the firmware update from the local provider and found some parameters in build.prop, which were quite different from the ones I had. I have carefully merged "ro.ril.*" sections of the config files and rebuilt new firmware update image. Which, more or less, solved the problem.

I think this should be definitely brought to Paul's attention...

[Guest FloHimself]

Then, thanks to my friend, I've got the firmware update from the local provider and found some parameters in build.prop, which were quite different from the ones I had. I have carefully merged "ro.ril.*" sections of the config files and rebuilt new firmware update image. Which, more or less, solved the problem.

Which ro.ril keys of build.prop have you changed. Can you please post values you've changed?

Edit: Whats your preferred network type setting in info menu (*#*#4636#*#*) ??

Edited June 21, 2010 by FloHimself

[Guest lenik]

I've downloaded the firmware for my operator. Can you explain what I should do from here? I'm running MCR 3.1.

if the firmware you've got is RUU_*.exe package, you have to extract rom.zip first, then extract system.img and unpack system.img to find /system/build.prop file. then pull /system/build.prop from your device and carefully compare. if there are any differences in "ro.ril.* section -- carefully merge them or replace, then push resulting build.prop to your device and see what happens. wrong parameters may result in bad reception or other problems, so it's a good idea to keep a copy of your original build.prop file.

[Guest lenik]

Which ro.ril keys of build.prop have you changed. Can you please post values you've changed?

I think the following three lines made a difference:

ro.ril.oem.ecclist=110,118,119

ro.ril.enable.a52=0

ro.ril.enable.a53=1

I've checked MCR3.1 and these lines are different, based on the carrier/country.

If you simply copy mine into your build.prop file, it will most probably not work.

Update: and maybe these two too:

ro.ril.fast.dormancy.timeout=3

ro.ril.enable.sbm.feature=1

Whats your preferred network type setting in info menu (*#*#4636#*#*) ??

"WCDMA only", since there's no GSM in Japan, afaik.

Edited June 21, 2010 by lenik

[Guest FloHimself]

I think the following three lines made a difference:

ro.ril.oem.ecclist=110,118,119

ro.ril.enable.a52=0

ro.ril.enable.a53=1

I've checked MCR3.1 and these lines are different, based on the carrier/country.

If you simply copy mine into your build.prop file, it will most probably not work.

Update: and maybe these two too:

ro.ril.fast.dormancy.timeout=3

ro.ril.enable.sbm.feature=1

"WCDMA only", since there's no GSM in Japan, afaik.

According to http://androinica.com/2009/12/14/hack-for-...er-2g3g-speeds/

and other posts these are 3G/2G related features and could really have an impact on battery life.

Would you mind testing the setting "GSM/CDMA auto (PRL)" or "CDMA auto (PRL)" instead of "WCDMA preferred"? This should improve standby times because the phone don't contantly searches for a higher data rate on low carrier signal.