Increase Battery Life [WinMo registry tweaks - Need confirmation] - HD2 Android Q&A, Help & Troubleshooting and Genera

I added the other registry tweaks for power management as i realize i had changed these too. So if you've already done the SDcard tweaks, try adding the others as well
Hi all,
I know there are a ton of other battery life threads, but i wanted to start one because I need people to confirm if this helps.
I've been using Android (Darkstone Froyo v1) for the last 2 weeks, and for the FIRST week of usage, my battery life was TERRIBLE.
I would unplug my phone at 10am (it would only charge to 93%), have the phone on STANDBY (not make ANY phone calls/SMS/browsing, literally screen-off sitting at my desk), and my battery would drain from to 25% in 5 hours.
I would go from 93% to 25% from 10am-3:30pm. This would happen with making ZERO phone calls, ZERO texts, and ZERO browsing.
I found myself charging my phone twice a day just to be able to have Android.
I even tried setCPU with the recommended profiles in the other thread, but still was experiencing the same battery drain
I came across this thread a while back (as i was a heavy tweaker for WinMo , constantly searching for new performance tweaks), and I decided to give it a try.
I had a theory (and this is where I need your help to confirm) - since Android boots from the SDcard and initially boots from WinMo, does it still use any of WinMo's power management features?
I put the theory to the test and so far its been working great for me.
1. I installed BSB tweaks 1.6 and turned ON "Power Savings"
2. Installed Resco Registry to edit WinMo registry, and performed the below changes: (credits go to tomksoft from the original post: http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=4967373&postcount=1)
**EDIT**
added the other registry keys as well
HKLM\Comm\AsyncMac1\Params
DisablePowerManagement=0
HKLM\Comm\PPTP1\Params
DisablePowerManagement=0
HKLM\Comm\L2TP1\Params
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass\High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class\ High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class
DisablePowerManagement=0
(There are a couple of other tweaks from that thread, but these are the main ones i changed since they deal mostly with the SDcard)
**I forgot to mention that you should perform a SOFT RESET before booting back to Android after doing these changes**
After making the registry changes, i just rebooted my phone and loaded up Android.
(I still have setCPU installed as well with the recommended profiles from the setCPU thread)
Now I can get a FULL day use of my phone running Android.
Just yesterday I made about 10 phone calls, 10 texts, did a bunch of browsing and wallpaper downloads from Zedge, and still had 53% battery life by midnight.
So again, im not taking credits for the registry tweaks, i just remember noticing them a while back and decided to try it.
If anyone has battery life problems I suggest trying this out and reporting back.
Any feedback is welcome. hope this helps!
The only reason why i need confirmation is because I'm not sure how the whole Android/Linux bootup works. Ive read somewhere that booting to Linux/Android will "shutdown" all the other WinMo drivers/etc. That's why im not sure if any WinMo registry tweaks will even affect Android. But so far for me, after making these changes my battery life has significantly improved.
Fyi, my setup is:
ROM: Miri V17 6.5
Radio: 2.10.50.x
Android: Darkstone Froyo V1 ( july26th build - i like the barebone build without Sense)
zImage: zImage.FULLRAM (fixed the graphic issues with artifact fix)
I did a quadrant bench test and scored 1350. I'm using an A-DATA 8GB class 6 card btw
BSB Tweaks: http://forum.xda-developers.com/showthread.php?t=589305
Resco Explorer you need to buy, but there's a 10 day trial you can download:
http://www.resco.net/downloads/pocke...en_aio.arm.cab

I'll definitely give this a try. Right now my battery performance with FroyoStone is the same as your old setup. 5% drain per hour on standby with everything off except for gsm phone calls. It would be really nice to have this sorted out.

buzz killington said:
I'll definitely give this a try. Right now my battery performance with FroyoStone is the same as your old setup. 5% drain per hour on standby with everything off except for gsm phone calls. It would be really nice to have this sorted out.
Click to expand...
Click to collapse
cool, give it a try and let me know
I was the same with you, i would disable all sync, no Wifi/GPS/bluetooth on, just 3G enabled (i would even disable the data connection with APN switch from market)
but i was still losing about 10% battery per hour
now i'm about 1% or less per hour on standby, and its great!
and try combining the above registry tweaks with setCPU to see if it helps even more

12 hours on standby and 20% drain. Is that about average? Using froyostone sense.

i will give these a test. i'm interested in seeing how they help in winmo too.

Bakedbread said:
Any feedback is welcome. hope this helps!
The only reason why i need confirmation is because I'm not sure how the whole Android/Linux bootup works. Ive read somewhere that booting to Linux/Android will "shutdown" all the other WinMo drivers/etc. That's why im not sure if any WinMo registry tweaks will even affect Android. But so far for me, after making these changes my battery life has significantly improved.
Click to expand...
Click to collapse
Thanks for the tips, I'm gonna try this out now!
Little info, from what I know the reason you boot winmo in the first place is to initiate the drivers, which android is not doing yet. Pretty sure that means that they stay on once you boot android, but everything else in the wince kernel shuts down.
It makes sense that this should work. For example, every dev recommends turning off the 'auto backlight' setting in winmo and it has an effect on the battery in android, so we know that settings do cross over.
Question is, is this affecting performance of Android at all? It looks like the settings are basically reducing power to the SD card, so is that slowing anything down since we are running from SD? Let's test...

Bakedbread said:
1. I installed BSB tweaks 1.6 and checked off "Power Management"
Click to expand...
Click to collapse
Did you mean turn OFF 'Power Saving' (first option)?

Just made the changes, now let's see if it's effective Thanks for the tips mate.

tgtoys said:
Did you mean turn OFF 'Power Saving' (first option)?
Click to expand...
Click to collapse
Sorry, i forgot what it was called
Yeah, its "Power Savings" in BSB tweaks, (1st option) and i turned it "ON"
i edited the 1st post so there's no confusion

tgtoys said:
Thanks for the tips, I'm gonna try this out now!
Little info, from what I know the reason you boot winmo in the first place is to initiate the drivers, which android is not doing yet. Pretty sure that means that they stay on once you boot android, but everything else in the wince kernel shuts down.
It makes sense that this should work. For example, every dev recommends turning off the 'auto backlight' setting in winmo and it has an effect on the battery in android, so we know that settings do cross over.
Question is, is this affecting performance of Android at all? It looks like the settings are basically reducing power to the SD card, so is that slowing anything down since we are running from SD? Let's test...
Click to expand...
Click to collapse
just an other example: sim lock! if you have unlocked your sim card in winmo, you didn't have to unlock it in android
i test it right now too and until now i can confirm that here is no affect on performance side - still smooth (shubCRAFT 1.2) and about 1230 points in quadrant...

Just ran Quadrant 2 times and got 1100 (below Droid X), and 1273 points. Seems that those settings slightly touch pure performance, but nothing noticeable concerning smoothness and general use.
Now waiting more time to see the improvement in battery.

Mangetsuginkei said:
Just ran Quadrant 2 times and got 1100 (below Droid X), and 1273 points. Seems that those settings slightly touch pure performance, but nothing noticeable concerning smoothness and general use.
Now waiting more time to see the improvement in battery.
Click to expand...
Click to collapse
nice
yeah, im scoring 1350 with a 8GB class 6 card and those registry tweaks, so its not a big issue for me
Android is running extremely smooth (since im using the Full RAM zImage as well) and battery life is great
we'll see how it is soon for everyone, since I think a lot of ppl have done the registry change but are just waiting to see how the battery life is.
I'm getting about 1% or less drain per hour on standby , so you can use that as a reference
now the only issue i have now is my battery only charging to 90-93% as "full"

Bakedbread said:
nice
now the only issue i have now is my battery only charging to 90-93% as "full"
Click to expand...
Click to collapse
Remove your battery from your device completely for 30-60 seconds and reinsert it again. Now your android should load it up to 100% again. It seems that the battery needs this kind of "reset" from time to time. Works fine for me.

This works! Using setcpu as well
Using:
CleanEx v6
Radio 2.10
Mattc 1.5
Sent from my HD2

Issues
Strange whenever i change the settings in WinMO, do reset and start Android a white screen appears and then nothing anymore....
I have reformatted my SD card tried it again without WinMO settings android installed and booted again luckilly. After reinstalling everything I thought I try it once more but same happens, white screen and eventually the screen goes off..... need to remove battery to restart, but cannot get into Android what can cause this and how to fix it without starting all over
Edit fixed the whitescreen issue by chaning startup.txt
#8 When u get stuck at white screen while rebooting change set cmdline to set cmdline "rel_path=Android lpj=638976" and reboot again..
When applying the powersave settings yet again with the changed set cmdnline option, the android will start again, finally!

thanks a lot, i'll have a try.
I agree with you, i think also that WM make a terrible batterie usage.

For these who want this tweak...:
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass\High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class\ High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class
DisablePowerManagement=0
Click to expand...
Click to collapse
...in easy way i cabbed it some time ago for polish PDAClub forum users. See atachment.

Bakedbread said:
Hi all,
I know there are a ton of other battery life threads, but i wanted to start one because I need people to confirm if this helps.
I've been using Android (Darkstone Froyo v1) for the last 2 weeks, and for the FIRST week of usage, my battery life was TERRIBLE.
I would unplug my phone at 10am (it would only charge to 93%), have the phone on STANDBY (not make ANY phone calls/SMS/browsing, literally screen-off sitting at my desk), and my battery would drain from to 25% in 5 hours.
I would go from 93% to 25% from 10am-3:30pm. This would happen with making ZERO phone calls, ZERO texts, and ZERO browsing.
I found myself charging my phone twice a day just to be able to have Android.
I even tried setCPU with the recommended profiles in the other thread, but still was experiencing the same battery drain
I came across this thread a while back (as i was a heavy tweaker for WinMo , constantly searching for new performance tweaks), and I decided to give it a try.
I had a theory (and this is where I need your help to confirm) - since Android boots from the SDcard and initially boots from WinMo, does it still use any of WinMo's power management features?
I put the theory to the test and so far its been working great for me.
1. I installed BSB tweaks 1.6 and turned ON "Power Savings"
2. Installed Resco Registry to edit WinMo registry, and performed the below changes: (credits go to tomksoft from the original post: http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=4967373&postcount=1)
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass\High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class\ High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class
DisablePowerManagement=0
(There are a couple of other tweaks from that thread, but these are the main ones i changed since they deal mostly with the SDcard)
After making the registry changes, i just rebooted my phone and loaded up Android.
Now I can get a FULL day use of my phone running Android.
Just yesterday I made about 10 phone calls, 10 texts, did a bunch of browsing and wallpaper downloads from Zedge, and still had 53% battery life by midnight.
So again, im not taking credits for the registry tweaks, i just remember noticing them a while back and decided to try it.
If anyone has battery life problems I suggest trying this out and reporting back.
Any feedback is welcome. hope this helps!
The only reason why i need confirmation is because I'm not sure how the whole Android/Linux bootup works. Ive read somewhere that booting to Linux/Android will "shutdown" all the other WinMo drivers/etc. That's why im not sure if any WinMo registry tweaks will even affect Android. But so far for me, after making these changes my battery life has significantly improved.
Fyi, my setup is:
ROM: Miri V17 6.5
Radio: 2.10.50.x
Android: Darkstone Froyo V1 ( july26th build - i like the barebone build without Sense)
zImage: zImage.FULLRAM (fixed the graphic issues with artifact fix)
I did a quadrant bench test and scored 1350. I'm using an A-DATA 8GB class 6 card btw
Click to expand...
Click to collapse
can you help me where to get this files you mention.. i want to get it a try... thnx in advance..
Resco Registry
BSB tweaks 1.6

BSB Tweaks: http://forum.xda-developers.com/showthread.php?t=589305
Resco Explorer you need to buy, but there's a 10 day trial you can download:
http://www.resco.net/downloads/pocketpc/explorer/en/rescoexploreren_aio.arm.cab
i'll add it to the 1st post
Has anyone had time to see if this helps at all?

awesome. will give feedback in a day of use

Related

SOLUTION: How to save battery life. Really works.

There are other threads already on the following app but some of you may not realise what it does if you were to read the subject line title.
There is an app which can underclock the cpu of the HD while it is on idle and suspend modes.
I have tested it on my HD and it works brilliantly.
Please visit this thread to read up on it more.
http://forum.xda-developers.com/showthread.php?t=507301
Install only version 1.0 if you have a HD and not the higher versions.
Have you had any problems with locking up or anything?
What happens if you set the backlight off to say 20mHz but have music playing, will it affect the performance?
Touch wood I have not had any lockups yet. Just tested playing music with backlight at 20mhz and no performance issues.
I'm trying this application...
And I'll tell you the result in few days.
Great.
For the record, I have got 2 days out of my phone so far with this app. Before using it my phone lasted about 12 hours.
Looks like good stuff...I'll check it out & report back.
the developer seemed to have disappeared... 1.2 is said to have problems with HD... there are random screen corruption reported too.. thats why i am hoping that 1.3 comes up first
leobox1, try the older version 1.0. I have and it works very well.
installed and will report later.
BTW, can you go as low as possible on the clock speeds for suspend and backlight off?
Thx for the link, i will test it!
This doesnt seem to work on my install of Miri 6.5 V10. I tried V1.0 first and the reported proc speed was always 528 on V1.0. I then uninstalled 1.0 and installed v1.2 just to see and the proggy always reported 528 @ 1.325v. Anyone else get it to work? I may have to go back to a 6.1 rom if not cuz I really would like to have this. Thanx for any info.
Daz
erm..strange question, but where does it install to?
I tried installing version 1.0 on my HD, it told me of no errors, but i cant seem to find it anywhere, not under programs, not with the file explorer..
It says its installed when I check installed software, but I dont know how to execute it..^^
I use Wm 6.5 miri's Rom V10.00. I installed the 1.0 version, but i can't see it on my start menu or anywhere else. i did restart , but nothing happens
Once installed you'll find it under settings, system, processors. You may need to restart.
will try that, thank you very much ;-)
trice1921 said:
Once installed you'll find it under settings, system, processors. You may need to restart.
Click to expand...
Click to collapse
Thx very much!
I leave less than 3% for a night (6hours)
It's amazing !
idunne said:
hi,what setting have you put on.....thanks
Click to expand...
Click to collapse
I've put on the same settings than the screenshot on the first page.
NB : 3 % for 6 hours on " suspend " then
8 % for surfing 20 minutes (on XDA-dev )
Could someone give the correct voltages to not damage the blackstone ?
(and Tha it can start nevertheless).
I tried version 1.0 and it made my battery life even worse. The other thing that is bad was the battery indicator would change by 5% increments. Last night i was 99% battery, 7 hours later on suspend it was still on 99%, so i'm thinking 'wow'. When i wake up and actually use the phone, not even heavy. 6 hours later it's on 60% with minor use.
I uninstalled it and now my battery is going down in 1% increments.
Bad program.
use the new version 1.3, it works now really flawless and I had over 8 hours suspend only 1% battery draining.

Battery Issue 1024LEO

I've been looking around for a long time but I haven't found a way to overcome the hell-like battery drain.
I tried to delete MMtaskmanager from windows/startup, I tried to flash different customized roms, but it doesn't seem that the problem is getting better.
Now I'm with RomeOS ROM 4.05, HSPL 2.08. Battery drain is horrible.
Someone said it might be a problem of HSPL2, but I don't think there is another version of HSPL for 1024LEO available.
May I have any ideas from someone here?
Thanks in advance.
The HSPL is just a bootloader, so I can't see that being the issue. Here is what I did:
- Go into \Windows\StartUp and delete "MMTaskManagerhook.lnk" - this is a big savings according to NRG (reboot)
- Turn off your auto "weather" and "stock market" refresh
- Go into Start > Tools > "Device Lock" (present in the NRG ROMs) and uncheck "enabled" and "lock if playing music"
- Turn down your screen's brightness and/or put on "automatically adjust backlight" (this is a huge savings as well)
Using the "tBattery" app located in Start > Tools > tBattery, my temperature is around 26' C and the draw is around -150 to -160. At idle (suspend), it is around -4 to -5.
It has also been said that the "Document Indexing" service and the .mp3 indexing service can cause quick battery drain if you have a lot of documents and/or if you have a corrupt .mp3.
You can turn those off as well, but an easier way would be to remove your MicroSD card and see if the battery drains slower. If that is the case, then you have an issue with or on your MicroSD card.
ruinertt said:
The HSPL is just a bootloader, so I can't see that being the issue. Here is what I did:
- Go into \Windows\StartUp and delete "MMTaskManagerhook.lnk" - this is a big savings according to NRG (reboot)
- Turn off your auto "weather" and "stock market" refresh
- Go into Start > Tools > "Device Lock" (present in the NRG ROMs) and uncheck "enabled" and "lock if playing music"
- Turn down your screen's brightness and/or put on "automatically adjust backlight" (this is a huge savings as well)
Using the "tBattery" app located in Start > Tools > tBattery, my temperature is around 26' C and the draw is around -150 to -160. At idle (suspend), it is around -4 to -5.
It has also been said that the "Document Indexing" service and the .mp3 indexing service can cause quick battery drain if you have a lot of documents and/or if you have a corrupt .mp3.
You can turn those off as well, but an easier way would be to remove your MicroSD card and see if the battery drains slower. If that is the case, then you have an issue with or on your MicroSD card.
Click to expand...
Click to collapse
Hi, I have his ROM, but I go to file explorer, windows/startup and I dont see that MMTaskManagerhook.lnk
Am I doing it wrong ??
I am using Energy.Leo.21895.Sense2.5_with_MaxManila.Mar.26
Thanks
ruinertt said:
The HSPL is just a bootloader, so I can't see that being the issue. Here is what I did:
- Go into \Windows\StartUp and delete "MMTaskManagerhook.lnk" - this is a big savings according to NRG (reboot)
- Turn off your auto "weather" and "stock market" refresh
- Go into Start > Tools > "Device Lock" (present in the NRG ROMs) and uncheck "enabled" and "lock if playing music"
- Turn down your screen's brightness and/or put on "automatically adjust backlight" (this is a huge savings as well)
Using the "tBattery" app located in Start > Tools > tBattery, my temperature is around 26' C and the draw is around -150 to -160. At idle (suspend), it is around -4 to -5.
It has also been said that the "Document Indexing" service and the .mp3 indexing service can cause quick battery drain if you have a lot of documents and/or if you have a corrupt .mp3.
You can turn those off as well, but an easier way would be to remove your MicroSD card and see if the battery drains slower. If that is the case, then you have an issue with or on your MicroSD card.
Click to expand...
Click to collapse
Thanks for your reply. I'll try to remove MicroSD card and see if the problem still exists. Will report here.
richsark said:
Hi, I have his ROM, but I go to file explorer, windows/startup and I dont see that MMTaskManagerhook.lnk
Am I doing it wrong ??
I am using Energy.Leo.21895.Sense2.5_with_MaxManila.Mar.26
Thanks
Click to expand...
Click to collapse
I dunno if it is in the MaxManila version, but it is present in the CookieMonster version.
Take a look in TaskManager and see if you have the MMTaskManagerhook.exe running.
Thanks for the tip. I'm giving this a go right now.
FYI, I'm experiencing battery drain on Energy. I've been reading that this is an issue with lots of roms.
ljwnow said:
I've been looking around for a long time but I haven't found a way to overcome the hell-like battery drain.
I tried to delete MMtaskmanager from windows/startup, I tried to flash different customized roms, but it doesn't seem that the problem is getting better.
Now I'm with RomeOS ROM 4.05, HSPL 2.08. Battery drain is horrible.
Someone said it might be a problem of HSPL2, but I don't think there is another version of HSPL for 1024LEO available.
May I have any ideas from someone here?
Thanks in advance.
Click to expand...
Click to collapse
Hello,
I am new to this phone, but not new to flashing and other things with HTC phones. One thing that I have always noticed with them is their battery life is horrible, and as the screens get bigger and more data intensive things are going on, the battery life is not going to be great.
How much time are you getting, a few hours, a day, half a day? Depending on usage and such, don't expect anything more than a day.
Also, if you can do the things that are noted, it will help significantly.
I have the stock rom and the battery life is horrible... worse than my n900 which sucks...
I read everywhere online how great the htc hd2 battery is.. 52hrs of up time? with mild use.. I get less than 10 with mild use.. and only 2-3 with heavy use..
I have had many phones this past year and so far this is by far the worse..
I have made my email update less.. turned off all auto updates as well..
I don't have many apps installed and have reset the device once already.
Screen brightness is set to auto..
Any ideas?
dmtaub said:
Hello,
I am new to this phone, but not new to flashing and other things with HTC phones. One thing that I have always noticed with them is their battery life is horrible, and as the screens get bigger and more data intensive things are going on, the battery life is not going to be great.
How much time are you getting, a few hours, a day, half a day? Depending on usage and such, don't expect anything more than a day.
Also, if you can do the things that are noted, it will help significantly.
Click to expand...
Click to collapse
Thanks for your reply. I just sold my HD. I remember my HD could go 1.5 days the same usage as my HD2. But HD2 could only make around 6hrs. I'm sure there is something wrong with the battery system oh HD2.
frankd14321 said:
I have the stock rom and the battery life is horrible... worse than my n900 which sucks...
I read everywhere online how great the htc hd2 battery is.. 52hrs of up time? with mild use.. I get less than 10 with mild use.. and only 2-3 with heavy use..
I have had many phones this past year and so far this is by far the worse..
I have made my email update less.. turned off all auto updates as well..
I don't have many apps installed and have reset the device once already.
Screen brightness is set to auto..
Any ideas?
Click to expand...
Click to collapse
Try to remove your SD card and test. Plz report here.
Tbattery
Hi, is any one here so nice to give a link to tbattery0.56? tbattery0.6 does not work on HD2, it will give out weird and huge numbers....I'm defeated by the battery, frustrating..
For me, the battery drain is all about the screen. The radios are actually pretty efficient. I've got weather/twitter/stock updating frequently (30/30/5 mins), and two push email services humming along (exchange/hotmail), and the phone barely sucks any battery if its just hanging out on my desk, pulling from data every few minutes. Talk time appears pretty good, too.
When my battery disappears absurdly fast is when I'm using the screen. Text messaging, web browsing, emailing....even light-moderate usage here sucks it down fast.
Other than turning down your brightness, I don't know what you can really do about that one. As screens get bigger, but batteries don't (in fact, my Palm Treo 755 had an 1800 mAh battery, Droid 1400, HD2 1230), battery life is going to suffer.
DeekoVB5 said:
For me, the battery drain is all about the screen. The radios are actually pretty efficient. I've got weather/twitter/stock updating frequently (30/30/5 mins), and two push email services humming along (exchange/hotmail), and the phone barely sucks any battery if its just hanging out on my desk, pulling from data every few minutes. Talk time appears pretty good, too.
When my battery disappears absurdly fast is when I'm using the screen. Text messaging, web browsing, emailing....even light-moderate usage here sucks it down fast.
Other than turning down your brightness, I don't know what you can really do about that one. As screens get bigger, but batteries don't (in fact, my Palm Treo 755 had an 1800 mAh battery, Droid 1400, HD2 1230), battery life is going to suffer.
Click to expand...
Click to collapse
this was, in fact, my biggest concern. Big screen means more power. All the reviews I've read indicated I should be getting better than I have been, which is bothersome. I'm tempted to revert to a stock rom and give it a go.
HotShotAzn said:
this was, in fact, my biggest concern. Big screen means more power. All the reviews I've read indicated I should be getting better than I have been, which is bothersome. I'm tempted to revert to a stock rom and give it a go.
Click to expand...
Click to collapse
Either turn your brightness down or turn on the auto brightness backlight adjustment.
ljwnow said:
Hi, is any one here so nice to give a link to tbattery0.56? tbattery0.6 does not work on HD2, it will give out weird and huge numbers....I'm defeated by the battery, frustrating..
Click to expand...
Click to collapse
Like what? It appears to be working fine for me (at least with the current power draw - which is all that I really care about).
ruinertt said:
Like what? It appears to be working fine for me (at least with the current power draw - which is all that I really care about).
Click to expand...
Click to collapse
OK. Here is my numbers from tbattery 0.6:
MS Percentage 52%
PA Percentage 52%
KADC 531%
RARC 528%
V_MBAT(V): 3.752
MAIN Battery ID(KOhm)31.5
pd_M 69
Temp 21.1
Current -222---------------------------See the current, the phone is idle now( not really, compass is running).
ARC 6464
FULL 12296----------------------------Weird, far away from the battery's capacity
1st dis_percentage 632%
1st dis_ARC(mAh) 7782
Cycle 0
Charger input Discharge
ljwnow said:
OK. Here is my numbers from tbattery 0.6:
MS Percentage 52%
PA Percentage 52%
KADC 531%
RARC 528%
V_MBAT(V): 3.752
MAIN Battery ID(KOhm)31.5
pd_M 69
Temp 21.1
Current -222---------------------------See the current, the phone is idle now.
ARC 6464
FULL 12296----------------------------Weird, far away from the battery's capacity
1st dis_percentage 632%
1st dis_ARC(mAh) 7782
Cycle 0
Charger input Discharge
Click to expand...
Click to collapse
The current seems about right in all honesty. Even though you *think* that it is idle, there is stuff going on behind the scenes (your screen, for example, takes up A LOT of power).
Go ahead and load up 0.5x or whatever and see if you get anything different.
ruinertt said:
The current seems about right in all honesty. Even though you *think* that it is idle, there is stuff going on behind the scenes (your screen, for example, takes up A LOT of power).
Go ahead and load up 0.5x or whatever and see if you get anything different.
Click to expand...
Click to collapse
Yes. You are right. I was just going to update, with microSD inserted and compass program running and tbattery running, the current is around -222. Now I stopped all the running programs in task manager, current seems to be -162.
I still couldnt find tbattery 0.56.
Miri's Elegant ROM TMO_US HD2
Using the ROM in the image below. Installed it with 64% at around 1pm today 03/29 and so far am still at 65% and thats with at least 30mins phone call, some web browsing and quiet a few text messages. tried the other ROMs for tmo_us and this MIRI ELEGANt is working out great for me. downloaded it at htcpedia.com

Bad battery life is typically not because of the hardware

Hi,
I'm posting this in return for all the information I found about the HD2 and poor battery performance. I read every thread I could find and every single post in them. I learned a lot and that allowed me to solve my problem.
I got no more than about 10 hours of use out of my battery with average use. Initially I thought this was the norm, reading a number of threads on this issue. I could however not believe that the performance was so poor, even taking the large screen into account.
I decided to try and determine exactly what it was that caused the battery to drain to quickly. I loaded BattLog and found it invaluable (see http://forum.xda-developers.com/showthread.php?t=444920).
I immediately noticed that my phone was drawing 85 mA even when it was in standby (or what I thought was standby). Based on what I was reading, the current draw should not be more than 5 mA while the phone is in standby.
I noticed in one of the threads that there were complaints about G-Profile causing battery drain. Since I had it on my phone I thought that might be a logical place to look. I uninstalled it a lo and behold... the current draw fell to below 5 mA when the phone was in standby!
In addition I loaded Bandswitch which switches off my 3G connection after it has not been used for 60 seconds.
Now I have about 48+ hours of battery life. When not using the phone a lot it extends to a lot more than 48 hours.
The long and short of it is that if you get poor battery performance, chances are it is because of some software that is installed on your phone.
Here are a couple of usefull things I have found in helping resolve my battery issues:
1) Use Batlog (http://forum.xda-developers.com/showthread.php?t=444920) to log the current your phone draws. If it draws more than 5 mA during standby you have a problem, most probably related to a piece of software on your phone
2) Your phone should not be drawing much more than about 150 mA when in 'active' mode with the screen at 40% brightness.
3) If you are running G-Profile, uninstall it and recheck your current draw. Chances are that it is the culprit.
4) Having an active data connection does draw power from the battery. In my case this is about an additional 130 mA. Load something like Bandswitch to disable the data connection when it is not needed.
I hope this information helps somebody. I realise that the situation is different for everybody out there because of all the variants such as age of the battery, sofware loaded and use. However, the reality is that the battery issues are most probably not because of a bad battery or the hardware but rather because of software on the phone.
BTW I am running:
OS Version: 5.2.21869
Manilla version: 2.5.19211619.0
ROM version: 1.48.421.2 (71294) WWE
Radio version: 2.05.51.05_2
Regards
gerhardvr said:
Hi,
I'm posting this in return for all the information I found about the HD2 and poor battery performance. I read every thread I could find and every single post in them. I learned a lot and that allowed me to solve my problem.
I got no more than about 10 hours of use out of my battery with average use. Initially I thought this was the norm, reading a number of threads on this issue. I could however not believe that the performance was so poor, even taking the large screen into account.
I decided to try and determine exactly what it was that caused the battery to drain to quickly. I loaded BattLog and found it invaluable.
I immediately noticed that my phone was drawing 85 mA even when it was in standby (or what I thought was standby). Based on what I was reading, the current draw should not be more than 5 mA while the phone is in standby.
I noticed in one of the threads that there were complaints about G-Profile causing battery drain. Since I had it on my phone I thought that might be a logical place to look. I uninstalled it a lo and behold... the current draw fell to below 5 mA when the phone was in standby!
In addition I loaded Bandswitch which switches off my 3G connection after it has not been used for 60 seconds.
Now I have about 48+ hours of battery life. When not using the phone a lot it extends to a lot more than 48 hours.
The long and short of it is that if you get poor battery performance, chances are it is because of some software that is installed on your phone.
Here are a couple of usefull things I have found in helping resolve my battery issues:
1) Use Batlog to log the current your phone draws. If it draws more than 5 mA during standby you have a problem, most probably related to a piece of software on your phone
2) Your phone should not be drawing much more than about 150 mA when in 'active' mode with the screen at 40% brightness.
3) If you are running G-Profile, uninstall it and recheck your current draw. Chances are that it is the culprit.
4) Having an active data connection does draw power from the battery. In my case this is about an additional 130 mA. Load something like Bandswitch to disable the data connection when it is not needed.
I hope this information helps somebody. I realise that the situation is different for everybody out there because of all the variants such as age of the battery, sofware loaded and use. However, the reality is that the battery issues are most probably not because of a bad battery or the hardware but rather because of software on the phone.
BTW I am running:
OS Version: 5.2.21869
Manilla version: 2.5.19211619.0
ROM version: 1.48.421.2 (71294) WWE
Radio version: 2.05.51.05_2
Regards
Click to expand...
Click to collapse
and imagine that your rom version is accused of massive batt draining!
an upgrade to 1.66 / 1.72 should make a difference..or a custom rom
batlog?
Hi Gerhardvr,
What is the batlog software you used?
I'm very interested about your post.
Thanks.
J6B.
Very useful findings, gerhardvr. Thanks!
found BattLog
ok, I found BattLog
It's just in showthread.php?t=444920
Have a nice day guys.
cu
J6B.
When I ran the Test, it said that I was using up 242mA in standby! I dont believe I have G-Profile installed, unless it was pre installed on the device. I have the latest versions of the ROM, Radio, Manila, and OS version, so I know the culprit cant be the ROM version... Any ideas? I bought this phone from T-Mobile US.... Sooo yeah
Folks, I've been trying to get to the bottom of this as well. I have a number of cab files which do seem to help a little. One of the bigest culprits I've found is the screen lockers. Disable them and see how you fair!
soopahsteve said:
When I ran the Test, it said that I was using up 242mA in standby! I dont believe I have G-Profile installed, unless it was pre installed on the device. I have the latest versions of the ROM, Radio, Manila, and OS version, so I know the culprit cant be the ROM version... Any ideas? I bought this phone from T-Mobile US.... Sooo yeah
Click to expand...
Click to collapse
Soopahsteve,
I suggest you use Battlog to log to file. This is very useful as it will log the time stamp, the current temp of the battery and the current draw at the point in time. In addition it logs arious events on the phone, in particular the startup and shut down of applications, data connectivity, when you make or receive a call, whether you are talking or receiving on the call, etc. This can be opened in Excel and then analysed and if you are very lucky, you will pick up some patterns allowing you to link some programs to the battery drain.
However, the situation is typically slightly more complex to resolve since the culprit software are usually software that is loaded as TSR application at reboot. The result of this is that Battlog will not show the startup of these applications in the log file since they are already running at the time you are starting Battlog.
You should look at programs that manage phone profiles, screen lockers, screen calls or SMS messages, etc. In other words, any program that does work behind the scenes.
The reason you are seeing 242 mA in "standby" is because your phone is not really in standby. Although the screen is blank, something is preventing your phone from going into true standby, the processor is still active. The trick is to find what this is.
Sometimes the only approach is to uninstall the applications you suspect one by one and see if it makes a difference until you either find the culprit or can prove that none of the them are an issue. Then reinstall the ones you think are "safe" one by one and check whether the probelm pops up again. unfortunately you have to do the double sided approach because there could be more than one application that cuases your issue.
Painful I know but worh it when you have two days worth of battery time with some to spare.
Regards
See no reason to upgrade to the latest ROM
chris2busy said:
and imagine that your rom version is accused of massive batt draining!
an upgrade to 1.66 / 1.72 should make a difference..or a custom rom
Click to expand...
Click to collapse
You know it. In reality I would love to upgrade to the latest and greatest but I've customised my phone to the Nth degree (did obviously not upgrade the ROM) by installing all the little apps I find useful, Cookies Home tab (best thing since sliced bread), etc. My phone is now just the way I like it.
It would take me quite some time to upgrade the ROM and to customise it again from scratch and I really don't see the benefit. I might be force to do it when I get to a stage where there are software that I would like to load that only works on the later ROMs but until such time I'm not gonna try to fix that that ain't broke.
Regards
is this the bandswitch u are using? if not, can i check where to get the program?
http://forum.xda-developers.com/showthread.php?t=286844
gerhardvr said:
It would take me quite some time to upgrade the ROM and to customise it again from scratch
Click to expand...
Click to collapse
I just upgraded my ROM and did a Level 1 restore with Sprite Backup ... everything comes back except (I think) for wifi passwords.
i am drawing 180mA on standby..
im using custom rom, energy rom so thats very strange, but i have to agree that my battery life is terrible.. so i got to find a way to cut down on the 180mA drain..
I've always had good battery life on stock 1.66 rom losing 3% overnight with wifi and bluetooth turned off. Had to do a hard reset and started losing 15% overnight with the same everything. Did further resets and got nowhere. Ended up giving up on 1.66 although it had been fine previously after numerous hard resets - makes no sense but this is what happened. Just flashed to 1.72 and back to losing 3% overnight what it should be. And that is out of the box, to be honest all the battery saving registry tweaks are not worth the time installing and I leave 3G on all the time with updates coming through.
So it's all a bit random and shame on HTC for not sorting it out. My advice is do a hard reset, switch the wifi and bluetooth off and see in the morning if you have a reasonable battery life (or use the batt consumption program to verify standby consumption is sensible). Do this first before installing everything, getting frustrated and starting over again like I did when you discover that you're still experiencing high battery drain. This ensures that your starting point is a good flash and the phone is getting good life before adding any apps that could be causing a problem.
i have found my hd2 really does not like being in a poor or no coverage area. other phones i've owned have normally coped pretty well with no or very little signal. but not the hd2.
also noticed more drain in areas where there is only poor 3g coverage and its switching between 'g' and 'h' coverage.
fi3ry_icy said:
i am drawing 180mA on standby..
im using custom rom, energy rom so thats very strange, but i have to agree that my battery life is terrible.. so i got to find a way to cut down on the 180mA drain..
Click to expand...
Click to collapse
Energy ROMs, just like the name goes, use a lot of Energy
They are baked in with a lot of performance tweaks so it's not unusual to get lower battery life per charge compared to other more down to earth vanilla ROMs.
Thanks for this thread, a lot of interesting information about the battery life of my HD2.
Just to mention: battconfig shows the power consumption directly in the task bar, a good way to find power guzzlers while they are active.
It's a pity we have no central place in this forum with a list of background applications that are known to drain the battery faster.
Or, also a needed information, a list of applications that are known not to do this (like PhoneAlarm, PocketShield).
I'm using the official rom only and have non fancy apps running or installed while I'm using the test bat program. As I speak the SD card is removed and celular radio is turned off.
Acording to program there is an indicator which is switching from -229ma to +78ma is that what its drawing of power?
Euroman28 said:
Acording to program there is an indicator which is switching from -229ma to +78ma is that what its drawing of power?
Click to expand...
Click to collapse
+78ma??? That must mean you are charging the battery. The best way to test current draw is when it is only on the battery.
I get about -5ma draw on standby and it tops out at around 180ma when I have the screen on, but usually hovers around 130 - 150ma. I have my screen brightness at the lowest setting possible.
@OP, I wanted to say this earlier... great topic, very insightful.
I have a few suggestions for everyone posting in this thread. Let's try and get some common data together that is more tangible in order to give us a more similar & common perspective for these discussions.
I suggest the following
1) Soft Reset. Once the device is on, do not run ANY applications. In fact don't do anything except for following the below instructions.
2) Turn your screen brightness all the way DOWN! (Turn off Auto Backlight and manually set it to the lowest setting)
3) Check your power settings and make sure that while your phone is on battery, that it is set to dim the backlight after 30 seconds and turn off after 1 minute
*** I have attached 2 REG files below for both Backlight and Power. Please use them instad of doing it manually.***
4) Turn off all the radios (Phone, Wi-Fi, Bluetooth). Let's make our first round of tests with the Radio's off. Radio ON complicates things a bit as there are several applications to keep track of that use the Data Connection. I'll come up with a more comphrehensive list later so we can do the Radio ON tests.
Screenshots
Use a program like Shave&Save and get the following screenshots
1) Use any Task manager and get a screenshot of all the processes running. Sometimes the number of processes displayed is longer than the screen size can accomodate. Take 2 screenshots in this case making sure that you capture all processes. Edit the image with MS Paint or some other Image Program and attach it here as one image. See the example in the post below this one.
2) Goto \Windows\Startup and get a screenshot of the folder contents
3) If you are using Sense, drag the slider all the way to the end (settings) and goto About Phone. Goto Software Information and get a screenshot of that.
Monitoring the Battery
1) Make sure your phone is not connected to the charger or to the computer.
2) Open BattLog (can be found here), set the refresh rate to 1 second and Start Logging.
3) After you start the logging process do not touch the screen / the phone again for exactly 2 minutes.
TIME THIS with a stop watch. As soon as the 2 minutes it complete, turn the phone back on and stop the logging.
Information to post here
1) All the screenshots from above.
2) The current draw (both on standby and while active). Also, please attach the file that logged all the information in this format: Forum ID - BattLog - dd-mmm-yy.txt
3) ROM - Whose ROM? Release Date? Does it have Cookie's Home Tab Installed or any other MAJOR Sense Modifications.
Click to expand...
Click to collapse
SAMPLE POST
HTC HD2 (T8585)
OS: WM 6.5
ROM: Energy * Build 21907 * Release 01.JULY.10 * CHT v1.8.5 - Dinik Edition
RADIO: 2.07.50.27_2
Current Draw (mA)
Idle: -3 to -7
Screen On (w/o Radios): -83 to -117
Those figures look normal to me. You should be getting about as good a battery life as a device like this can achieve.

Battery Solution the **FINAL POST**

UPDATE Dec 9:
ALL i did was use Autoboot (Exceller Multiple Build Loader) set at 3 seconds
Try this setup if all else fails
Rom: ChuckyRom Lite HERE
Radio: 2.15.50.14 HERE
Droid: HyperDroid 1.7 HERE
AutoBoot: Exceller Multiple Build Loader for Android/Ubuntu HERE (Comes preinstalled in ChuckyRom)
PLEASE KEEP LEAVING RESULTS AS I TRY THEM, AND CAN UPDATE THE FIRST POST
10/25:
I have been reading and in a recent post I read HAVE THE BUTTON LIGHTS ON WHEN U BOOT ANDROID and u will save battery and its true try this!
AGAIN, PRESS A BUTTON IN WM AND HAVE THE KEYPAD LIGHTS ON.
THEN AS QUICKLY AS POSSIBLE BOOT ANDROID.
I AM CURRENTLY GETTING 3MA WITH SETCPU
I had to try this twice before it worked but THE KEY IS TO BOOT ANDROID AS SOON AS THE KEYPAD LIGHYS TURN ON!
chrisizzle492 said:
I have been reading and in a recent post I read HAVE THE BUTTON LIGHTS ON WHEN U BOOT ANDROID and u will save battery and its true try this!
AGAIN, PRESS A BUTTON IN WM AND HAVE THE KEYPAD LIGHTS ON.
THEN AS QUICKLY AS POSSIBLE BOOT ANDROID.
I AM CURRENTLY GETTING 3MA WITH SETCPU
I had to try this twice before it worked but THE KEY IS TO BOOT ANDROID AS SOON AS THE KEYPAD LIGHYS TURN ON!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I just posted this in another battery thread but I think the real key is booting Android as quickly as possible and not really the lights so much as I have achieved similar results just using Exceller Multiple Build Loader app and not even touching the keys/lights. C/P from the other thread-->
Tried different techniques to get better battery and found that even on the same build with exact same setup would give varying results. Here's my setup that I would like others to try and post their results. SetCpu with screen off profile set to 245min/max 100 priority and whatever main profile you like; but use conservative preferably or interactive for best battery performance. Any task killer that auto kills all tasks with screen off (be sure to add SetCPU to ignore list). And here is the most important step, use an auto android booting app with minimum boot time setting. I have been doing some experiments with this and found that if you boot into Android as soon as possible, it seems to give better battery performance as opposed to playing around in WM then booting Android. Have tried this with several WM/Android combos. For the first time ever I'm able to get comparable battery performance out of Android as WM. I'm running a bare bones WM (but should work with and WM rom) and using Exceller Multiple Build Loader app set to 3 secs. Even running several sense builds I was able to achieve 3-7 mA draw during standby according to current widget. Took my phone off the charger at about 6:30 a.m. and it is now 11:15 and I still have 25% battery left after pretty heavy usage on standard battery. This is as good or better than what I usually get from WM! Hope this helps.
This was the one thing that was ruining my Android on HD2 experience. I finally got this step right after a few tries.
I've been using it for two days now, and getting consistent 5-8mA readings on standby. There's definitely something to either booting Android quickly and/or hitting the back button to turn on the LED backlight on the buttons.
I just checked my phone, and it's reading 5mA.
And I don't even have SetCPU on my phone. Should I try it out?
I think HTC winmo sense is the culprit. I disable the sense in winmo and get very low Android battery usage during standby. Sometimes around 3mA.
Sent from my HTC HD2 using XDA App
I also suggest to disable sense and put wmo in offline status.
Sent from my HTC HD2 using XDA App
leeyunfook said:
I think HTC winmo sense is the culprit. I disable the sense in winmo and get very low Android battery usage during standby. Sometimes around 3mA.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
why should turning off sense be good when it comes to battery usage under android? this would mean winmo and sense are running in the background of android...which is not the fact!
chrisizzle492 said:
I have been reading and in a recent post I read HAVE THE BUTTON LIGHTS ON WHEN U BOOT ANDROID and u will save battery and its true try this!
AGAIN, PRESS A BUTTON IN WM AND HAVE THE KEYPAD LIGHTS ON.
THEN AS QUICKLY AS POSSIBLE BOOT ANDROID.
I AM CURRENTLY GETTING 3MA WITH SETCPU
I had to try this twice before it worked but THE KEY IS TO BOOT ANDROID AS SOON AS THE KEYPAD LIGHYS TURN ON!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
You had to try this 2 times before it worked yet you claim this is the final solution for battery drain problems?
i agree with you guys but let me just throw this observation into the mix here. i've read somrthing here in these forums regarding the sd card that came with the phone had something wrong with it ( don't really remember the exact issue ) and if you swapped it out for another sd card, there would be less SODs and a better battery as well.
i've tested this as i have a 4gb sd card and have had no problems whatsoever. everything runs smooth as silk. and, once again, the battery life is great.
NOTE: i do use the keypads lights on trick as well.
anap40 said:
You had to try this 2 times before it worked yet you claim this is the final solution for battery drain problems?
Click to expand...
Click to collapse
Please re-read the post. i updated
Most of us don't need to do keypad gymnastics to get those same results.
Just use the exceller boot loader and set it for 3 or 6 seconds. Having stuff turned off till you need it is a great way to preserve the battery.
apallohadas said:
Most of us don't need to do keypad gymnastics to get those same results.
Just use the exceller boot loader and set it for 3 or 6 seconds. Having stuff turned off till you need it is a great way to preserve the battery.
Click to expand...
Click to collapse
Ya thanks for the comment, i was doin this in between class so i didnt have time to just try the Excellor Boot Loader!!!
Updated the First Post Thanks!!!!
well now we hav almost 48 hrs of battery life on android... and moreover i info radio 2.14.xxx is better than 2.15.xxx in battery life...
Not working for me
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
1. Are you using SetCPU with a 245 max screen off profile? 2. Are you disabling WiFi, data and GPS when not using it? 3. Are you using a auto task killer with only SetCPU and Current Widget in ignore list? Also, I don't have 3g in my area but if you do I guess it could account for increased battery drain. If you're in an area that is in/out of coverage, this will cause higher battery drain as well. I get spotty coverage where I work and the battery drain is terrible.
Try mdeejay sense rEVOlution 2.0 androind build with your vbn wom rom - works great !
Try this:
1. switch phone radio off in winmo
2. power off and charge until green light comes on
3. boot winwmo on vbn, then immediately click on EBL
4. boot into mdeejay sense rEVO 2.0
5. turn sense off and use LauncherPro
I get *very good* battery life now with avg 5-7mA draw as evidenced by currentwidget.
z
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
try my complete setup
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
a few things to try
1
boot into android as quick as possible, 3 or 6 seconds
disable gps location in android
activate the lights when haret is loading
disable wifi & 3g
disable hotspot
disable sync
running htc sense? try a build without it
and many more attempts
im finally at 3mA in airplane mode, 5mA on phone, 7mA with wifi, 20mA with wifi & 3g
chrisizzle492 said:
try my complete setup
Click to expand...
Click to collapse
I want to try that version of Android, but I don't want to mess with my good setup...
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
no need for keypad gymnastics or other weird and wonderful combinations - before booting into Android, just use KeypadLedControl to force the keypad lights to stay on, then fire up Android using your loader of choice (I use Android Loader, modified to automatically call KeypadLedControl to turn on keypad lights, instead of just letting it run on WinMo startup).
Been rebooting 5-6 times now with consistent low 5-10ma standby current.
Link to KeypadLedControl for lazy people: http://forum.xda-developers.com/showthread.php?t=605731
The Solution....kind of ;-)
Thx for u'r replys.
I considered all u'r tips and sry dudes it didn't work for me I think the problem was related to the Bangster Build, even though i have been lonesome with my issues.
I changed the LED lib, and tryed to let the LEDs on while booting, set CPU is in condervativ mode/screen off 245min/245max 100% interactiv. And yep, GPS and Wifi where off. I even searched for any SD-Card related Problems in regestry. But Chucky did some great work i think. (i switched again concernig to faster boot)
At some time i think each Leo is different to the other. I changed to Hyperdroid 1.7 with 2.14 Radio and the results are definitely mind blasting.
12 hours on the road, did some surfing, some calls, 2 h musik.
Strange though i used the same kernel and same Radio. Something must have gone wrong by flashing Bangster or something.

Possible soluition to fix 60mA: Enable GPS and wait for full sync

Hi friends.
I found the following coincedence.
When I install new build aparently CurrentWindget shows 60mA in stand by and no way to fix it to 5-7mA as it should be.
The solution which helps me to fix it is the following:
- enable GPS module in settings
- open Maps and wait for it to find where you are located
- go back to homescreen and put phone to stand by
It should be fixed now to 5-7mA current.
Hope it will help everyone.
I can even leave GPS module on all the time after that - standby current stays at 5-7mA level.
hlvl said:
I can even leave GPS module on all the time after that - standby current stays at 5-7mA level.
Click to expand...
Click to collapse
Very strange, but very cool if it works for you! I will give it a shot next time I see high battery drain. Thanks for sharing, it will help at least one other person if it helps you.
I've also found that switching Bluetooth off, then back on again, fixes this 60mA drain !
Common misconception: leaving GPS enabled in settings doesn't leave the GPS chip on the whole time. It just means that an app can enable it when it needs to (e.g. when you open Maps). As long as there's no GPS icon in your status bar, it doesn't drain *any* battery.
OT: that trick would be way faster than rebooting! Gonna try if it works for me too.
Really strange solution for this issue. I have the same problem but for this moment have drain about 5mA after quick boot with dualbootloader (wait time 3sec for Android load). For this moment 5mA in standby mode - with any enabled comm modules (WiFi,Bluetooth,GPS).
My experince of fixing the problem(temporary) is not using taskkiller too often, but it not always works
Curarpikt said:
My experince of fixing the problem(temporary) is not using taskkiller too often, but it not always works
Click to expand...
Click to collapse
Don't ever use your task killer again, it only causes problems.
Tried the above however no sucess..........please check out my post and tell me what you think
http://forum.xda-developers.com/showthread.php?t=857606&highlight=battery+wifi
I'm getting better battery life with wifi on
StephanV said:
Don't ever use your task killer again, it only causes problems.
Click to expand...
Click to collapse
Why? I use it a lot...
To solve 60mA problem, each time you want to boot android:
1) when you are in windows mobile, lock the phone and turn the screen off by press end call button
2) wait few seconds and press it again to turn on screen
3) you see lock screen, unlock your phone
4) after that boot your android quickly within 10 seconds! (you can do it by creat shortcut of android on your home sceen)
I test it and solve problem for me on both mccm and mdeejay builds!
Phantoml337 said:
Why? I use it a lot...
Click to expand...
Click to collapse
It was discussed hunderd of times. You dont need to free up mem in android 2.x
It has already a memory management built inside.
The only reason to use a task killer is to close an app that hangs or not properly close itself.
If you continue to kill your processes and backround apps just to free up ram, you will definitively drain more battery becaouse some of that apps will just load again automatically from SD or, when you open again one of them, it needs to load again from SD.
rafpigna said:
It was discussed hunderd of times. You dont need to free up mem in android 2.x
It has already a memory management built inside.
The only reason to use a task killer is to close an app that hangs or not properly close itself.
If you continue to kill your processes and backround apps just to free up ram, you will definitively drain more battery becaouse some of that apps will just load again automatically from SD or, when you open again one of them, it needs to load again from SD.
Click to expand...
Click to collapse
Exactly. And apps not closing properly is still not an excuse for using it. If the app is bad uninstall it or mail the dev to fixit, but don't go around screwing stuff up with a task killer.
Phantoml337 said:
Why? I use it a lot...
Click to expand...
Click to collapse
Me to....i use 2!
Autokiller on agressive,and a taskkiller....never troubles with drain etc
Or everyone check my signiture for my thread on battery drain solution
I think the OP is really onto something here. I tried this trick & my drain has gone from a steady 55-65mA down to around 5. I'm impressed!
Just one question, those of you that having issues with battery drain what WM do u use? I've recently had a problem on my HD2 (no USB) and i installed a stock ROM. Before i had the VBN Droid Reloaded 2 and with Mdeejay kernel current widget never showed me values above 300mA (witch i believe i only saw that value 1 time). Usually i'd get from 1-2mA to 250mA tops. Now i'll never go below 60mA and i've seen the record of 600mA. Today it drain me from 95% to 35% in about 2 hours. A bit too much for my taste...
I always find if you boot Android with Win Mo fully booted, it's over 60mA, but if I use Exceller Dual Boot to boot Android before Win Mo has finished loading, then it's 5-6mA.
Yea man task_killer - problem
Everything is working for me fine, i am using futureShocks MIUI build, the only thing is when i switch on bluetooth, my battery drain is about 60-80 mAh without bluetooth i have 3-6 mAh... no task killer, no setcpu, with other builds like mdeejays sense roms this problem is not !?
Everyone an idea how to solve the problem ?

Categories

Resources