Database Users

Battery Life Vogue Android

So, I recently got a vogue and immediately put android cupcake on it. (great work devs btw )
So here's the problem, I cant get through the day 7 am - 12 am with light to moderate use without needing to charge.
I would like to keep 3g/background data on during this time.
Has anyone had any success having their vogue-androids last this long?
Are there any advanced power managers that allow you to change the backlight quickly and easily or allow you to turn data off during certain times? (like data off for a 1/2 hour and then data on for 1/2 hour)
Thanks,
Kevin

sushichef said:
So, I recently got a vogue and immediately put android cupcake on it. (great work devs btw )
So here's the problem, I cant get through the day 7 am - 12 am with light to moderate use without needing to charge.
I would like to keep 3g/background data on during this time.
Has anyone had any success having their vogue-androids last this long?
Are there any advanced power managers that allow you to change the backlight quickly and easily or allow you to turn data off during certain times? (like data off for a 1/2 hour and then data on for 1/2 hour)
Thanks,
Kevin
Click to expand...
Click to collapse
There's an app called "Locale" which is apparently awesome, but I haven't tried it myself. It changes settings based on your GPS location, but I'm not too sure about time of day. You may want to check that out.
As for the battery lasting that long, I dunno... I don't think I'd fall into the "light usage" category. My battery typically lasts from about 7:30am till 9 or 10pm though... I'm not too sure, I usually plug it in when I get home from work around 6.

craig0r said:
There's an app called "Locale" which is apparently awesome, but I haven't tried it myself. It changes settings based on your GPS location, but I'm not too sure about time of day. You may want to check that out.
As for the battery lasting that long, I dunno... I don't think I'd fall into the "light usage" category. My battery typically lasts from about 7:30am till 9 or 10pm though... I'm not too sure, I usually plug it in when I get home from work around 6.
Click to expand...
Click to collapse
That would need more battery, since it would need GPS.
We don't have network-based GPS yet.

I have had the same problems with battery life on my vogue even with light usage. Also I don't believe CDMA has the same issues with 3g causing higher battery usage like gsm does. I have tried widgets to quickly toggle the backlight and gps function but only saw minimal improvement. Not sure if the increased battery usage is just a fact of android or if there remain porting/performance issues still to blame.

i've got my background data set to off and i keep gps and stuff off unless i need it and i've got my email set to update every hour and i found this actually gives me better battery life than when running windows so i just went and bought an extended battery off ebay and hopefully it'll get through a complete workday(10 hrs) where as right now i'm getting between 6 and 8 depending on how much I use it.

i've got my background data set to off and i keep gps and stuff off unless i need it and i've got my email set to update every hour and i found this actually gives me better battery life than when running windows so i just went and bought an extended battery off ebay and hopefully it'll get through a complete workday(10 hrs) where as right now i'm getting between 6 and 8 depending on how much I use it.
sorry double posted by accident and don't know how to delete

My battery used to drain pretty rapidly.. 7am - 2pm... but now it lasts from about 7am - 6pm. I think theres a certain amount that the battery can condition itself. I've tried discharging and charging and I do believe that its helped.
Do you guys notice that battery readings are not accurate though? Apparently it has something to do with the temp. sensor in the battery not being correctly configured. For example, if my battery is at 20% and I plug it in the charge, it'll jump to 40% in a matter of 10 mins.

psvillars said:
i've got my background data set to off and i keep gps and stuff off unless i need it and i've got my email set to update every hour and i found this actually gives me better battery life than when running windows so i just went and bought an extended battery off ebay and hopefully it'll get through a complete workday(10 hrs) where as right now i'm getting between 6 and 8 depending on how much I use it.
sorry double posted by accident and don't know how to delete
Click to expand...
Click to collapse
Oh, thats cool, how did you set up it to check every hour? is that an app? or?

sushichef said:
Oh, thats cool, how did you set up it to check every hour? is that an app? or?
Click to expand...
Click to collapse
well that's for my aol email gmail will not be affected i left auto-sync on and from what i could see it still auto-syncs without background data on you could uncheck that but then you'd have to manually update yourself

i too am having pretty bad battery life even when i don't use my phone. why would the battery drain so fast when its sleeping? would that togga app help at all with the latest cupcake build?

fixxxer2008 said:
i too am having pretty bad battery life even when i don't use my phone. why would the battery drain so fast when its sleeping? would that togga app help at all with the latest cupcake build?
Click to expand...
Click to collapse
Togga has been replaced in Cupcake by Modem. They do the same thing, essentially. If you want to turn off your data connection, open Modem and click Disconnect.
Also, in your default.txt make sure the pm.sleep_mode setting is set to 0 for best power saving.
Lastly, update all your files to the latest. The newest rootfs.img is supposed to bring more power-saving functionality. I just installed it this morning, so I can't comment on it yet.

craig0r said:
Togga has been replaced in Cupcake by Modem. They do the same thing, essentially. If you want to turn off your data connection, open Modem and click Disconnect.
Also, in your default.txt make sure the pm.sleep_mode setting is set to 0 for best power saving.
Lastly, update all your files to the latest. The newest rootfs.img is supposed to bring more power-saving functionality. I just installed it this morning, so I can't comment on it yet.
Click to expand...
Click to collapse
yeah i just updated all of my files, ill check my text though.

i checked my text and it is set to 0 already! not a good thing when it only takes 5 hours to drain 50% of my battery life. i hope this can be fixed in future builds, i may have to go back to winmo for the time being because i need my phone for work.
i really love android though!

fixxxer2008 said:
i checked my text and it is set to 0 already! not a good thing when it only takes 5 hours to drain 50% of my battery life. i hope this can be fixed in future builds, i may have to go back to winmo for the time being because i need my phone for work.
i really love android though!
Click to expand...
Click to collapse
Do you have "Use Background Data" unchecked under Settings > Data synchronization? This makes a huge difference. If you have unchecked already, I don't know what to tell you.

with the previous rootfs (just before the new one today 2009-08-04) I've been getting 10 hours with moderate usage, backround data enabled, contacts and gmail auto syncing and locale set to turn my ringer off based on location (btw, I do beleive we have agps working now). Upgrading to the newest kernel and rootfs with more improvement to see if I can get a full day as I am awefully close now.
oh, and I also have a weather widget updating every hour, pretty good battery imo.
EDIT: Tip for battery life, I have my default screen brightness set pretty low, about 30%, as this is fine for most indoor conditions. I use an app called fastbright placed conveniently on my home screen to immediately turn my screen to 100% with the click of an icon when I am outdoors. I also use locale to turn the screen all the way down to 10% when the battery is less than 10%. Both are recommended apps.

I think I was getting much better battery life before introduction of rootfs, like on the order of 4-5 hours more (running hero themed ion). Anyone else have this experience, or is it just me?

tatnai said:
I think I was getting much better battery life before introduction of rootfs, like on the order of 4-5 hours more (running hero themed ion). Anyone else have this experience, or is it just me?
Click to expand...
Click to collapse
Actually yeah, I tried the latest initrd and rootfs today, but it seems like it's a bit lower than it usually is this time of day. I think the first implementation of rootfs was better than this latest over the non-rootfs versions, though. Maybe I just used it more. I kept all the same settings and usage for the day was typical.

Best option is to buy the Extended Battery from DealExtreme for $8.. search for HTC Touch S1 .. the back cover doesn't fit properly but you can always get a one that fits from ebay..
this battery lasts me thru out the day even with heavy usage.. and for $8 u can't go wrong

Today I didn't touch my phone for the first 4-5 hours of my day after charging overnight, and was down to sixty-something percent. I know that on older initrds I was doing much better than this, at least 80% at noon with no usage.
I'm wondering if optimizing memory with the new rootfs stuff has been a trade-off to poorer battery life. Since I'm using mssmison's hero themed ion which is screaming fast, I haven't noticed a difference with the root stuff and think I'm going to try switching back.
I'm switching back to the 7-30-09 initrd.gz, because that's the last one I know my battery was doing much better with and will post back after running it tomorrow.

My issue with battery life is that my phone doesn't seem to know how much battery it has left. It will be on 60 percent, I'll plug it in and 5 minutes later its fully charged.
Or after it comes off the charger overnight, it will go down to 60-50 almost immediately but stay there all day while at work with light usage. I also hate that it doesn't know when its full, I hate to overcharge the batter. So many opinions on if it damages it or not.

I have a clue on the battery problem

Ok... I was big into kernels, processes, everything on my N1 so I am quite familiar with tracking battery life by different means. I can provide the following information:
At 11:20pm, my phone was at 100% and had moderate signal and was connected to WiFi - full strength.
At 5:50am, my phone was at 83% battery with NO USAGE, not even the screen turned on once.
My Battery Use had the Android System at the top of the usage with ~30% usage. The CPU Usage was over 1h 30m!
The above is extremely odd since I didn't touch the phone. My N1 would've been <2 min.
In the Battery History CPU Usage section, SUSPEND was the only item with red and it was roughly 15% full.
The SUSPEND function, I believe, is the controller that suspends the functions of the phone so it can go to sleep. It should never use this much battery.
There are tons of packages in the Battery Use screen, which is weird. Some of the ones are: Settings Storage, RilFactoryApp, com.sec.android.app.lcdtest, AllShare, Error, Checkin Service, BluetoothTest, Perso, BrcmBluetoothServices, Com.samsung.InputEventApp, Sync Feeds, Settings, Factory Test, Network Location, VPN Services, Android System, WlanTest
A lot of these items (and more) show up in Advanced Task Manager, and they never existed on my N1.
I believe that destroying these services via ATM greatly improves battery life (even though generally it isn't needed in Android). After killing them all and keeping an eye on it, only 2 or 3 have respawned and my CPU usage is <1m which proportionally is much lower than the former experience.
Anyone have any ideas or input?

I've been trying to figure this out also...each battery had its on date on it..my first battery was june 21...my current one is june 28...my 6/28 battery also had a little qr barcode on it....
The 6/21 battery was pretty awful...today I'll be using my 6/28 battery for the first time...it was charged at 39% and 10 hours later overnight...it only lost 10% and is at 29% now...i must say that's pretty good because I was certain it would be dead in the morning. I'm gonna test it the next couple of days and see how it holds up....our issues may be as simple as getting the right production of batteries...wouldn't that be a relief? Lol
Or....i could just be crazy
Sent from my Samsung Vibrant using XDA App

My only battery weirdness is that I turned off autobrightness and cranked the brightness and my battery life dramatically improved. Would get home form work and have 30%, now I have something like 50%...
No clue why unless using the light sensor or making the adjustments uses more juice than it should.

popypopy said:
My only battery weirdness is that I turned off autobrightness and cranked the brightness and my battery life dramatically improved. Would get home form work and have 30%, now I have something like 50%...
No clue why unless using the light sensor or making the adjustments uses more juice than it should.
Click to expand...
Click to collapse
This isn't relevant to these problems though as I'm talking about standby time.

Oh and my android system is only at 3%
Sent from my Samsung Vibrant using XDA App

Anyone else have any ideas?

good idea
I think it is a good idea to track running tasks.
Let us create a list of tasks for stock apps and the most often used off the market ones. Then everybody could decide for herself what apps to run. Being able to compare function and price (here battery drainage) is a great thing. The list might contain:
name of the app | the name as appeared in task managers | function | typical power drainage (high, moderate, low, or how many hours will battery last if only the app were running)
I think, the top post could be moderated as needed appropriately.

I don't know, but my battery life is pretty bad. Today I had the phone connected to my laptop via USB, and my laptop connected to the wall. I was using the phone and my battery percentage was STILL going down, even though it was plugged in!
Sent from my Samsung Vibrant using XDA App

ArcticWolf91 said:
I don't know, but my battery life is pretty bad. Today I had the phone connected to my laptop via USB, and my laptop connected to the wall. I was using the phone and my battery percentage was STILL going down, even though it was plugged in!
Sent from my Samsung Vibrant using XDA App
Click to expand...
Click to collapse
Well USB will always charge slow...

hah2110 said:
Well USB will always charge slow...
Click to expand...
Click to collapse
Always plug the phone into the wall if you can. The USB from the laptop doesn't charge at the same rate.
I kill all my running apps that I don't need with ATM, then rid all unnecessary widgets, turn the brightness off of auto and on the lowest setting you prefer, turn off GSP, turn off Wifi, turn off Bluetooth and noticed a huge improvement.

iunlock said:
Always plug the phone into the wall if you can. The USB from the laptop doesn't charge at the same rate.
I kill all my running apps that I don't need with ATM, then rid all unnecessary widgets, turn the brightness off of auto and on the lowest setting you prefer, turn off GSP, turn off Wifi, turn off Bluetooth and noticed a huge improvement.
Click to expand...
Click to collapse
Now you just need to reduce screen size by 80%, get rid of the touch interface and you have a Nokia 6110. I guaranty 7 days until the battery drains.
Some other ways to deal with battery life are:
a. Get a second battery.
b. Charge the damn thing once in a while.
That way, you can actually enjoy the smartphone and think less about killing processes and *****ing how bad the battery life is on forums.

I just rooted my Vibrant the other day and installed setCPU. I set the max to 800 and the min to 200 using the conservative setting and i noticed much better battery life the very next day. Having a 1ghz processor is awesome but it seems that default settings for this phone probably has it running at the rate possibly when the screen is off also.

al74 said:
Now you just need to reduce screen size by 80%, get rid of the touch interface and you have a Nokia 6110. I guaranty 7 days until the battery drains.
Some other ways to deal with battery life are:
a. Get a second battery.
b. Charge the damn thing once in a while.
That way, you can actually enjoy the smartphone and think less about killing processes and *****ing how bad the battery life is on forums.
Click to expand...
Click to collapse
I'd have to go with this. Just some common sense will go along way. If you dont absolutely need the GPS, bluetooth, or WiFi turn them off (the phone even gives you a widget for it...). Even with the brightness at 0% its still darn bright.
Sure it requires a bit more input from the user but its still a darn good device.

popypopy said:
My only battery weirdness is that I turned off autobrightness and cranked the brightness and my battery life dramatically improved. Would get home form work and have 30%, now I have something like 50%...
No clue why unless using the light sensor or making the adjustments uses more juice than it should.
Click to expand...
Click to collapse
Thats what i did and my battery life improved alot.

[Q] Very High Power Consumption Android On HD2

Hi,
Ive recently installed Android 2.2 Froyo on an SD card on my HD2 and the battery is going down so quick... it wasnt great in Windows mobile but now I'm struggling to get it to last all day...
I'm saying to myself this cant be normal, I'm also trying a Samsung Galaxy S and the battery is so much better!!
Is there anyway I can improve the battery power on my HD2, I know in a HD2 the battery is a 1350mah and the Galaxy S is a 1500mah battery.
Should that make such a difference?
I'm considering going back to Win Mobile but dont really want to but havent got any other choice if the battery carrys on like this....
I also notice the screen and back get really quite warm... I suppose Android is making the system work harder?!?!?!

Its safe to say that you havent read any of the threads about battery life.
Before you say I did a search and didnt find anything Ive already typed in battery in search and found a bunch of threads.
Now what you need to do is find out why its running so warm.
It could be the kernal version you are using.
Ways to improve battery life are using setcpu and underclocking. A lot of members use current widget as a method to see when High drain is occuring.
In sleep mode you should be seeing less than 10ma. If you dont see less then this there is a problem.
Set current widget to 1 min intervals.
Dont use task killers they dont help anything no matter what anyone says.
Dont compare the captivate to the hd2. 2 different phones.

I am using mccm 1.5 customize, and CurrentWidget shows 5mA on standby which I think is good enough. Sometimes, it shows 60mA on standby in a while and my battery drains very fast, even I use Advanced Task Killer but it does not help. I have to reboot the phone to get it back to 5mA on standby.
Anyone has any idea of what may cause my standby power that high (60mA)?
Thanks.

hazard99 said:
Its safe to say that you havent read any of the threads about battery life.
Before you say I did a search and didnt find anything Ive already typed in battery in search and found a bunch of threads.
Now what you need to do is find out why its running so warm.
It could be the kernal version you are using.
Ways to improve battery life are using setcpu and underclocking. A lot of members use current widget as a method to see when High drain is occuring.
In sleep mode you should be seeing less than 10ma. If you dont see less then this there is a problem.
Set current widget to 1 min intervals.
Dont use task killers they dont help anything no matter what anyone says.
Dont compare the captivate to the hd2. 2 different phones.
Click to expand...
Click to collapse
Thanks for your tips for better battery life. I was curious about a few things and hope you could clarify a few things for me and some instruction or threads on how to do so. And yes I have searched, that's the first thing I always do before I do anything web based as far as positng.
1. How do you setcpu and underclocking?
2. How do you find the amount of battery that standby takes? i.e. 60mA? How do you get to that setting in android?
Thanks for your help in advance.

Setcpu is an app used to control your cpu speed.
link included
http://forum.xda-developers.com/attachment.php?attachmentid=394848&d=1283568967
the setcpu dev's site with complete info on how to use it.
http://www.pokedev.com/setcpu/
To check ma's use (current widget)
http://forum.xda-developers.com/showthread.php?t=776085
long press on the desktop and apply current widget. It will ask you if you want to create a log. Create a log for 1 min intervals. Put the phone to sleep and leave it for a good 5 mins.
You can then open the log file usint astro file manager and check your drainage while sleep.
One thing I found is that If i am having high drain i turn my gps on and restart then it usually settles down and I can turn the gps off.
If you have apps that are syncing you will a higher than normal drain during those times the apps sync. if you set your apps to sync at longer intervals the amount of batter drain will be unnoticable.
I have major battery ocd. I constantly check my battery and have to force myself not to look but still use my phone as any normal person would.
I can pull more than 12 hours easy!

Thanks hazard99!
The first time I ran android I don't think I've had any battery issues and now that I'm looking at the percent on my homescreen Im beginning to feel battery OCD too. It's like I lose 1% atleast every 15 minutes when I look at my screen. But I did take and apply all the tips you told me and I do see that it only uses 5ma when screen is off. I truely don't understand. :/

Stop looking at your screen. Stop worrying. The more you look the more juice you use while the screen is on. There will be more points where the phone is off.

traithudo said:
I am using mccm 1.5 customize, and CurrentWidget shows 5mA on standby which I think is good enough. Sometimes, it shows 60mA on standby in a while and my battery drains very fast, even I use Advanced Task Killer but it does not help. I have to reboot the phone to get it back to 5mA on standby.
Anyone has any idea of what may cause my standby power that high (60mA)?
Thanks.
Click to expand...
Click to collapse
Ive also been trying to investigate this, my standby drain is usually 60+ mA, and during use it jumps to the 200's, strange stuff indeed....For you to have 5mA, lol i wish that was for me too =/

otakubakaa said:
Ive also been trying to investigate this, my standby drain is usually 60+ mA, and during use it jumps to the 200's, strange stuff indeed....For you to have 5mA, lol i wish that was for me too =/
Click to expand...
Click to collapse
What radio and wm are you using? Do you use SetCPU?

I had high battery consumption, too. But now I found something interesting...
Due I'm not allowed to post links, yet, search for the post with topic:
[SOLUTION] Possible solution for heavy battery drainage.
With this fix: over night I only lost 20% instead of 59% of battery.

uninstall SetCPU

10507 said:
What radio and wm are you using? Do you use SetCPU?
Click to expand...
Click to collapse
im using the same radio as you (2.10), energycookie rom 21916, and my setcpu is at interactive 245/729, and for sleep its at 245/384, hastarin kernal.

Use a Battdrv.dll from older HD2 ROM 1.48 Etc. I'm not sure if you recmod the module and replace the current one in Windows if you will get the same benefit as if you cooked the driver in.

i just updated my kernal to the latest zimage in mattc's froyosense's evo tree, and my standby is around 6-11 ma now, guess that solved some issues lol, anyone know whats the normal operating ma power consumption for texting?
EDIT: Now when i try to enable wifi i simply get "error", did i mess up on something? =/
EDIT: Solved above problem. WOOT!

Simple Trick To Get 4-11ma In Standby

First, sorry for the new post on this, but I have not seen this mentioned. Didn't want it buried before it could help anyone.
I have used pretty much every android ROM out now, and for some strange reason they each have one constant.
ROMS which give 54-67ma on standby on first boot can be reset a couple of times until they reach the 4-11ma in standby point. Usually takes 1-3 resets.
Now, I'm not sure why this is all I know is it works. And yes, there is a huge amount of difference between 5+ and 50+ma.

I can surely confirm this
Hatefly said:
First, sorry for the new post on this, but I have not seen this mentioned. Didn't want it buried before it could help anyone.
I have used pretty much every android ROM out now, and for some strange reason they each have one constant.
ROMS which give 54-67ma on standby on first boot can be reset a couple of times until they reach the 4-11ma in standby point. Usually takes 1-3 resets.
Now, I'm not sure why this is all I know is it works. And yes, there is a huge amount of difference between 5+ and 50+ma.
Click to expand...
Click to collapse
This is most definitely true, might sound illogical or fake but I personally took battery logs when my drain was 58mA but could not find anything, I changed Kernels just to observe the same and I finally gave up but I accidentally had to reset my phone a few times as I forgot to put it on charge/freeze then after a few days I happened to see terrific battery improvement 5-8mA, I didn't know why but then I understood it was because of the resets..

Good to see I'm not going crazy. Like I said, I tried this with a bunch of different ROMS. All the same.
So if you are having bat problems. Try a few resets and see how that works for you before giving up on the ROM.
Oh, I might also mention I am not running any sort of set cpu app.

Check again
Hatefly said:
Good to see I'm not going crazy. Like I said, I tried this with a bunch of different ROMS. All the same.
So if you are having bat problems. Try a few resets and see how that works for you before giving up on the ROM.
Oh, I might also mention I am not running any sort of set cpu app.
Click to expand...
Click to collapse
Funny that just the both of us are populating this thread.. But yes I too do not use any Set CPU or Task Killers..
Currently on
Mattc Leo 1.8 with hastarins r7.6 with 5-7mA battery drain on Stand by (Wifi, GPS,Bluetooth off, data on(but disconnects sometimes))....

I can confirm this too.

Im a little new to Android on the HD2, running Mdeejay eVo Sense v. 2.3 rEVOlution 7.7 Hasteran at the moment.
Im finding the battery life on v2.3 less then on v.2.2 so I'll try a few resets & see if it improves, thanks.
Oh, is it really necessary to run SetCPU or a task killer?
Im forever closing tasks with task killer & the though of a task being auto closed when I turn the screen off is comforting, but is it best to just leave things to the kernal?

The most consistent way I have found to get 4-5ma on standby was to use exceller's android loader set autoboot android and 3 secs.

I can confirm this too.
I am trying dual boot (http://forum.xda-developers.com/showthread.php?t=723200) to boot into Android right away to see if that leads to more consistent standby battery drain. (this was mentioned on another thread.)
I have abandoned TaskKiller and AutoKiller, made no diff in battery drain for me.
I so still use SetCPU to slow the CPU when battery gets low.

Juno-First said:
Im a little new to Android on the HD2, running Mdeejay eVo Sense v. 2.3 rEVOlution 7.7 Hasteran at the moment.
Im finding the battery life on v2.3 less then on v.2.2 so I'll try a few resets & see if it improves, thanks.
Oh, is it really necessary to run SetCPU or a task killer?
Im forever closing tasks with task killer & the though of a task being auto closed when I turn the screen off is comforting, but is it best to just leave things to the kernal?
Click to expand...
Click to collapse
For better battery life, setCPU is a MUST! Creating different profiles to change the cpu clock is huge in conserving battery; especially, the the screen off profile.
Ditch ATK and download Watchdog instead.

even hastarin himself is using android without setcpu. with kernels 7.6, 7.7 I get same batt juice as with setcpu, BUT less stuttering in general, i.e. android runs more smoothly.

Honestly I have found that every ROM I have used set cpu was a detriment to battery life.
I'm still not 100% that even task killer is helpful in some cases. I think that on the other hand has to do more with how you use your phone and what apps than anything. Some people can prob get away with it.

SetCPU is pretty much pointless now with the latest kernels, only thing it's useful for is overclocking, but even without it I've not found anything that can't run. Even graphically intensive games like Reckless Racing run perfectly fine at stock CPU speeds.
I've just updated last night to ShubCraft 2.0 DropMode and I get 6ma in standby, my battery dropped 9 percent in 8 hours of standby while I slept, and after a full day of using my phone from about 9am to 6pm tonight (texting, calls, wifi use, 3G use, picture taking, playing a few games and listening to over an hour of music) my battery only just hit 50% at 6pm. This is without SetCPU.

What i've done is just swap out the micro sd card for another one. I had the stock 16gb and replaced it with an 8gb micro sd card and i'm getting fantastic results.
Without any type of task killers or Set Cpu, i'm constantly getting 3ma - 9ma stand by readings from Current Widget.
I also downloaded Juice Plotter from the Market ( what a fantastic app IMO ) and it tells you how much time you have left on your battery as well as a graph detailing the percentage of power battery has used.
I can go a day to a day and a half with out charging my phone. I am in complete Android Heaven.
NOTE: Keep in mind that when booting into Android, when you hit the Haret, make sure that the hard key light are on.
I also have the auto sync off to save battery as well.

To get the 4-11 mA, just make sure the keypad lights on the phone are on when booting haret.(pretty much, boot asap)
Sent from my HTC HD2 using XDA App

alantak said:
I can confirm this too.
I am trying dual boot (http://forum.xda-developers.com/showthread.php?t=723200) to boot into Android right away to see if that leads to more consistent standby battery drain. (this was mentioned on another thread.)
Click to expand...
Click to collapse
After several reboots this is holding true.
Before when I making sure the keypad lights were on before booting Android I would still occasionally get bad standby drain, so I think that is myth.

Exceller's auto boot app = no battery drain!!!
szfjcr said:
The most consistent way I have found to get 4-5ma on standby was to use exceller's android loader set autoboot android and 3 secs.
Click to expand...
Click to collapse
GOLD!!!! PURE GOLD!!! Been trying to preach this for days now! The battery drain is eliminated by booting Android before WM/Sense fully boots. Has nothing to do with keypad lights being on or off. Hence, use Exceller's auto boot app set to boot 3 secs and restart your phone and let it auto boot. Battery drain ELIMINATED!!!!!
secano said:
To get the 4-11 mA, just make sure the keypad lights on the phone are on when booting haret.(pretty much, boot asap)
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
See above comment.

anush.isaac said:
This is most definitely true, might sound illogical or fake but I personally took battery logs when my drain was 58mA but could not find anything, I changed Kernels just to observe the same and I finally gave up but I accidentally had to reset my phone a few times as I forgot to put it on charge/freeze then after a few days I happened to see terrific battery improvement 5-8mA, I didn't know why but then I understood it was because of the resets..
Click to expand...
Click to collapse
When you guys say do a few resets do you mean pull the battery or just use the off menu?

danielefeldt said:
When you guys say do a few resets do you mean pull the battery or just use the off menu?
Click to expand...
Click to collapse
Just do a hot reset if your android buid has that option, even better power off and and reboot from windows

I'm using bangster v1.5 with hasterin 7.7. I only get 2-3 ma standby.
Sent from my HTC HD2 using XDA App

For me the problem was the SD card. I formatted it with 4098 (or similar)block size, copied the Android build back over the top and bang from 115-170mA to 4-9mA on standby!!! WOW.

[Q] Battery Issues;BSOD/SOD;EBL?

So, I'm at a loss of what to do here. No matter what settings I seem to use I can't get good/decent battery life.
In fact, I get terrible battery life. With light to moderate usage I have to charge my phone at least two times a day, mostly three. Current widget reads that at standby I'm anywhere between 55mA-70mA and when in use 200mA-500mA. When charging it reaches 400mA-600mA
I see everyone talking about being able to get 5-10mA and I'm amazed at this. I've searched and read most "Battery saver" threads and none of it seems to work.
I was originally using Chucky rom lite and when I noticed the drain was abnormal I switched to the set up that chiasoft uses in his ReadMe for the ROM (stock 2.10ROM/2.08 radio).
Although since switching to the stock WinMo ROM I had repeated BSOD and SOD issues. To the point that it became unusable. I switched over to latest Energy ROM.I installed EBL and on both Stock and this Energy ROM. I am still having BSOD/SOD problems. Could it be the EBL? I plan on upgrading the radio to 2.12 in a few after I test out this EBL theory.
My setup as of this post is this:
WinMo ROM: Energy.BLACKSTONE.21916.Sense2.5.Nov.08 (Switched back to Stock 2.10)
Radio: 2.08.50.08_2 (Switched to 2.12)
Android: MooMoo Froyostone Sense 3.2 w/hastrain kernel
SetCPU:
998max/245min Ondemand on boot
Profiles: Screen off; Priority 100; 384max/245min ondemand
Battery <25% 576max/245min Priority 0 ondemand
Sampling 20000; Up Threshold 40
Advanced Task Killer:
Kill Level Agressive
I really don't want my LI-ON battery to die before I've even had the phone for the year. So if anyone can think of anything to help I'd be ever so grateful.
And of course, thanks to all the people who make all this possible.
(Sorry for the tl;dr post. I wanted to give as much info as possible.)

when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.

mofoahh said:
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
Click to expand...
Click to collapse
idk what it is fully charged. I'll be sure to check it later though. How do you calibrate the battery?
Also, I realized that I made an oversight on my part. When I switched to the stock WinMo rom I hadn't realized fully that it changed my Radio to 2.08 even though I posted it.
The rom chef recommends 2.10ROM/2.12 Radio, so that's what I switched to to check out that combination.

btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.

mofoahh said:
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
Click to expand...
Click to collapse
I don't have interactive in my options.

what version are you running?

mofoahh said:
what version are you running?
Click to expand...
Click to collapse
2.03 I got it through here.
Just installed 2.04 and there still isn't an interactive.

thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4

mofoahh said:
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
Click to expand...
Click to collapse
Yeah. No interactive settings. Also, that guide recommends 1190 max, but mine only goes up to 998.
Also, I finally got it to down to 7mA in standby. When I changed the radio to 2.12 and using a 2.10 stock WinMo rom.

no issues here getting 48 hours of light use, or a full 24 of moderate use...

I've yet to "condition" my battery. I'm worried it'll do more harm than good. Especially since I just got it finally to a decent mA draw. Although I'm worried my phone won't charge up to 100%. Always stop at 95.
Is conditioning really necessary/important?

easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..

t1h5ta3 said:
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
Click to expand...
Click to collapse
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.

mofoahh said:
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
Click to expand...
Click to collapse
Yeah, 48 hours seems improbable. I finally got it down to 7-10mA on standby, and I think it charges up to 4.2 but I'll find out for sure tonight.

same
I had the same problem, make sure you use EBL android launcher and set to autoboot at 3 seconds. Make sure you restart your phone anytime youw ant to load android. I assure you this will work.

My HD2, like all others can be flattened in 2-3 hours with windows/android if used hard, the difference seems to be on very light usage/standby win mobile could last 4 days... with everything turned off and basically not used Android would struggle to last 2 days !
Same phone same network/signal levels etc, can only be poor power management within Android, and I think that means voltages for all the processor and comms modules, not just a simple case of turning down speeds.
What do others think ?

Update: Upon switching to WinMo:2.10 and Radio:2.12+ MooMoo's MMS fixed froystone3.2 I was achieving 6-10mA in standby. The phone would last all day with a two-three hour charging period with moderate usage. Low battery use, rare DC's. Perfect. Best build I've used so far.
I'm noticing a new problem however, and I wonder if it's happened to Chiasoft who recommended this build. I'm getting serious touch screen freezes since last night. Anytime before that the set up was working AMAZINGLY.
Now? It's almost unusable sometimes. This morning it was happening in Android so I switched to WinMo and surprisingly enough it happened in there too. So I read touch freezes are Radio problems mostly. Is this true? Should I switch to a new radio? I'm confused as to why it would just randomly start happening though and worried it would mess up my battery troubles I just solved.
Any advice?

Hmm. I noticed that it almost always freezes when I hold down the end home button to turn off the phone or data or to silence it. I can't actually use the touch screen again until I hit the button again to put it to sleep.
I wonder if it's hardware related because it was happening in WinMo that way as well.

Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.

pretzdothack said:
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
Click to expand...
Click to collapse
I give you only a very short suggestion
You have just to DELETE SETCPU
and delete ANY TASK KILLER (you can keep it just to close any apps that could hang, but not to "free up ram")
Android is not Windows, you dont need to free up ram, and you dont need to overclock/undervolt to gain some minutes of battlife despite stability.
Talk to any Dev and they will confirm this.
Good Luck