Related
I have noticed one thing yesterday.
From the moment i had my Rhodium (2weeks ago) i installed advanced Config 3.3 on my Rhodium.
From the start i had the "SDcard power management" enabled.
Since then i had a terrible battery life, 20% loss in 3 hours so at the end of the day my battery was empty.
And did not blame the powermanagement of this.
Trying to locate the power loss i used acbPowermeter.
After two weeks i came till the conclusion that there was nothing which drains my battery.
True out the day i use my phone for just a couple off calls and sms messages.
3G is disabled because the poor reception.
Also auto weahter updates every 2 hours and my mail is also checked every 1 hour.
Bluetooth is always discoverble which does not effect battery drain more then bleutooth off.
Activesync is killed and Opera does realy close and used the nopushInternet tweak.
So after testing al these and more.
Even how much those apps uses de proc.
I had to try one more thing, disable the SDcard power management in Advanced Config 3.3.
And today that config change made me verry happy.
Normaly i start working at 5am and work till 3pm in that time the battery has lost 60% power.
And today i was supprised my Pro II had 91% power left.
So i just want to let you know that in my case the SDcard Power management f*****k up my batterylife.
Specs
HTC Touch Pro II
ROM-Vers: 1.19.404.1 (51489) NLD
ROM-Date: 06/22/09
Radio-Vers: 3.44.25.27
Engergy Info Tab says at 90% battery life:
Last fully charged
23:24 Thu 18aug 2009
Standby time:
18 hours and 40 minutes
Speak time:
1 hour and 4 minutes
Device Use:
5 hours and 4 minutes
I believe these specs aren't that bad because before i disabled the power management my battery would be emty in 16 hours.
So i hope that my findings will help you all.
Bluetooth is always discoverble which does not effect battery drain more then bleutooth off.
Click to expand...
Click to collapse
Are you sure about that?
in most devices bt in descovery mode drains the hell out of the battery!
I always have my BT ON only, because thats all you need once you devices have been paired.
faria said:
Are you sure about that?
in most devices bt in descovery mode drains the hell out of the battery!
I always have my BT ON only, because thats all you need once you devices have been paired.
Click to expand...
Click to collapse
Hey Faria,
First off all i still love your rom on my old wiza200.
Back ontopic:
As i found on the internet and my findings with the discoverble mode that it is not on all the time.
It only opens the BT pairing when a device want to pair.
After that it closes and acts as BT on mode.
BT does not sends it signal all the time.
But correct my if i am wrong
edit
If i may believe AcbPowerMeter the power drain with BT on and BT discoverble is nill and BT off against BT on is that it isn't a power drainer
Hey Faria,
First off all i still love your rom on my old wiza200.
Back ontopic:
Click to expand...
Click to collapse
Wow!
As i found on the internet and my findings with the discoverble mode that it is not on all the time.
It only opens the BT pairing when a device want to pair.
After that it closes and acts as BT on mode.
BT does not sends it signal all the time.
But correct my if i am wrong
edit
If i may believe AcbPowerMeter the power drain with BT on and BT discoverble is nill and BT off against BT on is that it isn't a power drainer
Click to expand...
Click to collapse
ha.. you mean you have it in a timed descovery mode. if that is the case then it is correct.
if i m not mistaking bt on only, drains less than 1% in 24 hours of the battery.
I get 7 hours of battery life and I'm a heavy user. I already have that option disabled. I need to improve this battery!!!
incredible!! your results are great!! any other detailed report, to clarify things a bit?? it would be interesting to have some data to elaborate some statistics and see what we come up with
in your fisrt post, you mean that you achieved the written results at the cost of only 10% battery life, or have I misunderstood it all??? if it's correct, wow!! °_° you have a nuclear battery! from 100% (and powermanagement enabled) I usually achieve 24 to 26 standby hours, 30min calls, 5 hours device usage (most of them connected on 3g). no bt nor auto connections of any kind.
thinking about it, it sounds a bit strange though: the OS is basically the same since quite a long time, and so the management of sd power (I think). so why would it do good (if enabled) on many devices, and not on TP2, having on the contrary such a bad impact on battery life?? I hope my question is clear enough!
since I'm no expert or programmer, I'd really like to have a little explanation by someone who really knows how these things work!
thanks a lot for the contribution, everything that may improve battery life even just a minute is super appreciated! best regards!
faria said:
Wow!
ha.. you mean you have it in a timed descovery mode. if that is the case then it is correct.
if i m not mistaking bt on only, drains less than 1% in 24 hours of the battery.
Click to expand...
Click to collapse
Nope my is discoverble the whole time.
About the 1% drain i am not sure, but after i am done with testing we will see how much it drains our battery.
HeavyComponent said:
I get 7 hours of battery life and I'm a heavy user. I already have that option disabled. I need to improve this battery!!!
Click to expand...
Click to collapse
I am still testing how to improve our battery and be able to do something with it.
cyberpunk627 said:
incredible!! your results are great!! any other detailed report, to clarify things a bit?? it would be interesting to have some data to elaborate some statistics and see what we come up with
in your fisrt post, you mean that you achieved the written results at the cost of only 10% battery life, or have I misunderstood it all??? if it's correct, wow!! °_° you have a nuclear battery! from 100% (and powermanagement enabled) I usually achieve 24 to 26 standby hours, 30min calls, 5 hours device usage (most of them connected on 3g). no bt nor auto connections of any kind.
thinking about it, it sounds a bit strange though: the OS is basically the same since quite a long time, and so the management of sd power (I think). so why would it do good (if enabled) on many devices, and not on TP2, having on the contrary such a bad impact on battery life?? I hope my question is clear enough!
since I'm no expert or programmer, I'd really like to have a little explanation by someone who really knows how these things work!
thanks a lot for the contribution, everything that may improve battery life even just a minute is super appreciated! best regards!
Click to expand...
Click to collapse
I expect that my testing will be done with in two or three weeks.
Because i want to exclude every possible power drain and drain the battery till its empty to besure how long it takes.
Althought my battery isn't empty jet i will post some screens of the actual battery state.
And later this weekend when the battery is empty i will also post data of my findings.
With my tests i hope to save power and still be able to use the Pro II as its ment to be.
Or else it will be useless expansive plastic brick after 7hours of use time.
At this moment my battery has 43% power left.
And the last full charge was at 4am on 20-08-2009.
So its standby for a little over 54 hours. (current time 11:30am)
In my attached screen it say standby time 49 hours.
I do not know if this standby indication is the actual standby or what is left.
I mean that my Pro still has 49 hours to go.
Think there is a bug in de energy tab, but can not find anything on the NET.
This is what i have done the last 54 hours.
Why is tell you this? althought i am not an heavy user like many people here.
It maybe can help to compare my use with all you people.
- 4am 20-08-09: woke up and disconected my phone from the charger.
- 5am got to work, at work no provider connection so phone is searching for connection for little over 8 hours.
- 3pm got home, so now and then check the weather, play arround with new appz, had to put is some new appointments and contacts.
- Tryed some new reg tweaks, and took some pictures and make a short movie (1.39min) off the awefull weather over here.
- 10pm got to bed with 73% power left in my battery.
- Same story: 4am woke up and got to work to arrive at home at 3 pm.
- Did some checking on the weahter app, added a new contact, tryed some g-sensor games.
- And made two phone call about 10 minutes (not much for the last two days)
- Also send about 12 sms and 2 emails.
- Got to bed at 11pm and woke up at 10am with 43% power left in my battery.
- My mail is checked every two hours, no pushmail by the way
- I used the alarm function as my wake up call
I will let the battery drain completly and try some other possible power savers later this week.
And will post my findings over here including some findings i made with acbpowermeter and what effects background services or programms have on the battery.
At this moment i think i have charge my battery tomorrow morning if it does not shut it self off because of an empty battery over night.
If 4 days standby time is possible with little use then i'm not happy with the power drain.
Why: my wifes Omnia i900 is not used for over 3days (Backup phone at the moment) and has a been standby for 4,5 days and has 50% power left.
Okay i know i can not compare these two devices.
Because there different and we do not use the devices the same.
Later this weekend i will post what i have done and post some data and statistics.
And i will post which changes i made for my new tests week.
What i have done so far,
Energy settings:
-screenlight in battery power is full
-screen goes off after 1 minute
-device goes off after 2 minutes
Phone settings:
-band settings are set both to auto
Bluetooth:
-is set to discoverble
WiFi:
-Did not use it this test
Commanager
-Do not know whoe made it.
but is use the new commanger to quickly switch between 3G on or off.
Because in my area there is a poor reception of 3G
So currently 3G it is switched off
Advanced Config:
-sdcard powermanagment is disabled
-also the others mmc, nand, sim, async, pptp,l2pt
-Data connetions (gprs auto attach) disabled
-miscellaneous (auto daylight savings) disabled
Appz & tweaks
-manilla nopushinternet
-Opera wil close instead of minimize
-Activesync is killed by faking a server
-No2chem 1% battery bar
-Zuinigerijder TouchLockPro
-XDA-Developers GPRS 1 minute auto detechment
Rhodium settings tool:
-Auto rotation is off
-Power special tweak is switched off (next week testing it switched on)
So next week more data and background info
waiting to see the final results!!
btw, what is "power special trick"?? never heard of that.. sounds useful
the more minute of battery life we can obtain, the better!
how do you disable the sd card power management? i want to give this a try. also this is my first post and id like to say this site has alot of useful information!
any updates
I tried disabling and...well maybe there is some little improvement here, but I don't know if it's really because of this or if it's because of different patterns of usage during the days.. mine varies a lot.
as a raw comparison, it went from almost 60hrs standby and 5 of usage to almost 75 and 6 /6.5. both test with phone always on on 3g network, no data connections, no wifi, bt and such. just simple usage (documents reading, editing, tweaking, mostly PIM related tasks.
again, I'm not really sure it's power management related.. maybe V6Maniac did a more rigid comparison, mine's not worth it
waiting for updates
cheers
Palringo
Guys,
I am not a techie so dont flame me if what I say proves to be wrong.
When I installed cleanRAM and when went to the Customized Process List, I saw Palringo as one of the running processes. I remembered using Palringo on the day I installed it, but never after that, which is at least 10 days before. And it stayed there even after a day. Hence I decided to remove the installation and the process is gone now.
Now my batter is really good!!! I had a full charge by 6 pm yesterday and now it is holding at 84%. I did connect to Internet through WiFi for about 20 to 30 mins for skype call, updated weather and stock. Yet it is holding at 84%.
Let me observe it for few more days and let me come back to you if I find anything interesting.
it is known that certain programs are really nasty battery drainer. there's a recent thread somewhere reporting that a (maybe older( version of ESET mobile antivirus did the same. so we have another entry for the black list of abnormal battery drainer
thanks a lot!
I've scanned through, but can't find an answer to this.
Is there an app that will let me see what has been using the battery on my HD2?
I mean, if I leave it overnight, a program that I can open in the morning, and see what has caused the battery to lose %? rather than something that tells me what the current usage is at a particular timne.
I'm interested in this too... I'm getting about 13% battery loss overnight, with NOTHING updating, 'my location' off, no programs running in task manager etc. As soon as I actually start using the phone, this drops a lot faster. I struggle to get 24 hours out of it, with light usage
...I forgot to say, that is with WMLongLife and Touch X Power Management on, too.
It's a problem with the battery meter.
For me it's like with average daily use :
100% -> 50% in 12 hours
50% ->5% in more than 24 hours.
No doubt, there are issues with the battery meter, but my device struggles to last 24 hours with light use, so that suggests the battery itself has a problem. My average usage in 24 hours would be:
SMS sent/received: 30ish
Call time: about 30 minutes
Email: manual update, about 3 or 4 times
Internet browsing: none
Auto-update of any features: none
MP3 listening: 30 - 60 mins
I have WM LongLife on (so no idle connections), I close all programs in the task manager (and then the task manager itself), the screen is set to 30% brightness, and vibration is off.
This is in stark contrast to reports I have seen on here, and other websites, of users with much heavier usage than me getting 2 days out of their phone. My battery has been through 9 full charge cycles.
Just search for Battlog (free programm) here in the forum or via google. Theres a thread where some users already posted some results. I could figure out the problem which caused my battery to drain with this proggi.
elburna said:
Just search for Battlog (free programm) here in the forum or via google. Theres a thread where some users already posted some results. I could figure out the problem which caused my battery to drain with this proggi.
Click to expand...
Click to collapse
Thanks. I'll give that a try.
Hi friends
i find out that my HD2 use 3% battery in 1Hr in standby mode (not using phone) (in GSM mode)
PLZ test ur battery usage (example leave ur phone for 2Hr and see the usage) and say result in this topic.
---------------------------------------------------------------------------------
i found somethings !! see Post 23.
link: http://forum.xda-developers.com/showpost.php?p=5171100&postcount=23
Hmm, Why?
Hi Wizard,
What are you hoping to achieve here?
Battery usage is a complicated scenario. Even in sleep mode your device is doing things in the background e.g listening for SMS & Emails, attentive to Exchange Server requests, dealing with items in the notification queue, etc etc.
Your initial conditioning of your battery also has a part to play in its performance as has the age of it. Also data connections also play into this scenario. In addition if you are in a low signal area your phone will spend more energy hunting for e.g. data connections than if you were, say, slap bang next to a transmitter.
People telling you that in 1 hour they saw x% drain or Y% drain tells you nothing unless you know why that is.
Do you want to rethink this and come back with a more focused thread.
Hope this helps.
WB
PS: You can kill off data connectivity by using a utility called Modaco No Data. Might help you if you think your battery problems are bad (do a search).
PPs: There's a stack of threads already on here about battery usage. You might want to link into those rather than kickoff yet another thread on this?
wacky.banana said:
Hi Wizard,
What are you hoping to achieve here?
Battery usage is a complicated scenario. Even in sleep mode your device is doing things in the background e.g listening for SMS & Emails, attentive to Exchange Server requests, dealing with items in the notification queue, etc etc.
Your initial conditioning of your battery also has a part to play in its performance as has the age of it. Also data connections also play into this scenario. In addition if you are in a low signal area your phone will spend more energy hunting for e.g. data connections than if you were, say, slap bang next to a transmitter.
People telling you that in 1 hour they saw x% drain or Y% drain tells you nothing unless you know why that is.
Do you want to rethink this and come back with a more focused thread.
Hope this helps.
WB
PS: You can kill off data connectivity by using a utility called Modaco No Data. Might help you if you think your battery problems are bad (do a search).
PPs: There's a stack of threads already on here about battery usage. You might want to link into those rather than kickoff yet another thread on this?
Click to expand...
Click to collapse
what an angry !
sorry man
Btw its vice versa here. My battery drops about 1% in 3h (or 4% in 12h exactly). If u have bad coverage than its annoying but normal that it drops that fast in standby.
Remember that the battery meter is not designed and is not accurate enouch to measure 1 and 2% of battery use.
If they where, then ALL batteries need to have the exact same discharge cycle. This is not possible.
So 3% one hour, and 1% next hour could just as well be a result from the battery meter calibration.
The battery meter have only two references. Full and empty. All values in between are guestimates
wizard6601 said:
what an angry !
sorry man
Click to expand...
Click to collapse
Don't take this too hard buddy
He's right about there being other threads focused on these issues and it's always best to first take a look and see if one exists before starting one. I say this coz I see this is one your first posts and you're probably not familiar with the rules.
As for battery life, yes as WB said there can be too many reasons why your battery drains this much. The most important of which are background data connections, updates, etc. So try using the "No Data" program and see if you get any improvement
zeroSIXzero said:
Remember that the battery meter is not designed and is not accurate enouch to measure 1 and 2% of battery use.
If they where, then ALL batteries need to have the exact same discharge cycle. This is not possible.
So 3% one hour, and 1% next hour could just as well be a result from the battery meter calibration.
The battery meter have only two references. Full and empty. All values in between are guestimates
Click to expand...
Click to collapse
i test it in 6Hr (19% usage at 6 Hr)
i test it 3 times.
19/6=~3%
mightymn said:
Don't take this too hard buddy
He's right about there being other threads focused on these issues and it's always best to first take a look and see if one exists before starting one. I say this coz I see this is one your first posts and you're probably not familiar with the rules.
As for battery life, yes as WB said there can be too many reasons why your battery drains this much. The most important of which are background data connections, updates, etc. So try using the "No Data" program and see if you get any improvement
Click to expand...
Click to collapse
all u say, was off (no update, no conection and ...)
when i use the phone battery usage is reasonable and acceptable. but in standby mode, this usage that i have, is much
Wizard,
I guess English is not your first language otherwise you would have recognised I was not putting you down. I was doing my best to be helpful.
I still think your starting point should be to install the application Modaco No Data, run it before you go to bed and see what happens.
There are just so many variable in battery usage, which is what I was trying to tell you.
WB
wacky.banana said:
Wizard,
I guess English is not your first language otherwise you would have recognised I was not putting you down. I was doing my best to be helpful.
I still think your starting point should be to install the application Modaco No Data, run it before you go to bed and see what happens.
There are just so many variable in battery usage, which is what I was trying to tell you.
WB
Click to expand...
Click to collapse
Tnx
yes, english is not my first language (it is my 3rd language)
i'll test it
11% on 3g with data connection on durring 9 hours
4% on edge with data connection off durring same 9 hours
Even though this is at some point so irelevant because battery usage is determined by so many other factors, wacky has a strong point here
snowblindd said:
11% on 3g with data connection on durring 9 hours
4% on edge with data connection off durring same 9 hours
Even though this is at some point so irelevant because battery usage is determined by so many other factors, wacky has a strong point here
Click to expand...
Click to collapse
i do a hard reset, i dont instal any thing, on EDGE, no gprs conection, and ... >> i have 18-19% usage in 6Hr. it's sooooooo much!!
i had same problem with HTC Diamond.
I also, when having no data connections on, regardless of GSM/3G, have a usage of 3% during ~8h (when I sleep).
i install "battery log" and monitor battery usage.
when phone is in use, show 160~200 ma. and when phone is standby, 6~12 ma.
i think its natural and good and acceptable. but why in practice, use so much battery ? ur usage is 3% in 8Hr but my usage is 3% in 1Hr !!!!!!
my phone use battery in other place except windows ?! lol my phone has seepage !
Wizard,
If you are absolutely sure you have all data connections switched off via the Modaco utility AND all Wifi, Bluetooth and Beam connections killed off ( for good measure you could also switch your radio off, ie the telephone, not the FM radio) and you still think battery usage is on the high side then there are a number of things you should consider:
1) You have a battery that was not conditioned properly and therefore is not discharging correctly
2) You have a dodgy battery which you need to change
3) You have a faulty device
4) You have both a faulty device and a dodgy battery.
For no's 3 & 4 I would suggest you send the device back under warranty or ask for an exchange. You know what to do with 1 & 2.
WB
wacky.banana said:
Wizard,
If you are absolutely sure you have all data connections switched off via the Modaco utility AND all Wifi, Bluetooth and Beam connections killed off ( for good measure you could also switch your radio off, ie the telephone, not the FM radio) and you still think battery usage is on the high side then there are a number of things you should consider:
1) You have a battery that was not conditioned properly and therefore is not discharging correctly
2) You have a dodgy battery which you need to change
3) You have a faulty device
4) You have both a faulty device and a dodgy battery.
For no's 3 & 4 I would suggest you send the device back under warranty or ask for an exchange. You know what to do with 1 & 2.
WB
Click to expand...
Click to collapse
TnX my friend
now i have changed simcard and insert another simcard from another operator . (10 min ago)
maybe
you have the rare case of phone sleep walking
(sorry for my bad english)
I also have this problem. In plane mode (gsm off), with all data connection off, my battery have a usage of 11% during ~8h (when I sleep).
It's french SFR rom.
Mine's set to UMTS (3g) without having data connections/wifi/bluetooth turned on - it loses 2-3% each 4-5 hours (standby only).
snowblindd said:
11% on 3g with data connection on durring 9 hours
4% on edge with data connection off durring same 9 hours
Even though this is at some point so irelevant because battery usage is determined by so many other factors, wacky has a strong point here
Click to expand...
Click to collapse
umiss said:
I also, when having no data connections on, regardless of GSM/3G, have a usage of 3% during ~8h (when I sleep).
Click to expand...
Click to collapse
Fatherboard said:
Mine's set to UMTS (3g) without having data connections/wifi/bluetooth turned on - it loses 2-3% each 4-5 hours (standby only).
Click to expand...
Click to collapse
which rom U use ?? (my rom is 1.43) (and i'm waiting for 1.61 official rom ) (without goldcard!)
Hi all,
...since I could not find a program to achieve this, I had to write one myself. Well, it is not a program, but just a MortScript to do the job of data collection while the battery is discharged.
As MortScript runs on all WM platforms from WM2k3 onwards and on both: Smartphone (standard) and PocketPC (professional), you can use this concept for all devices that MortScript runs on.
You have to take care yourself that the battery is full before you start and that the discharge is constant over time. Both is easy however
The job to discharge your battery while measured is done by the display lit to the maximum brightness and all other big current drains should be off to get comparable data. The script runs in the background and whenever the Battery% goes down is writes to a file remembering the timestamp for this.
For my devices the time to drain the batteries from full to zero was 1-16 hours, depending on how much the fully lit display draws off the battery and capacity and health of the battery.
Evaluation is done off-line with a spreadsheet program.
Usage:
install MortScript
unzip the attached file to your PC
put the battery-rundown.mscr file to the folder \My Documents\Battery or \Storage\My Documents\Battery for WM2K3 on your device
put the battery-rundown.lnk (*-wm2k3.* for WM2k3) file on your device to the \windows\startup folder. This makes sure that the script starts as soon as your device starts. It will not do any harm there and can even stay there for a longer time if you want to learn about your battery charge cycles. You can also copy it to any other place you like in the startmenu for easy access.
make sure all radio access is off (GSM/UMTS, BT, WLAN)
adjust the display and backlight on battery to stay on forever as well as backlight brightness for battery use to maximum
switch off the device
charge it until the battery is full (green light). Optionally leave it like this for another 1-3 hours to get the trickle charge squeeze the last electrons to the battery. Impact of this should not be more than 10% capacity - skip it if you are impatient.
switch on, the script starts automatically and measurement has created a file where the mortscript resides. It will continue to write to this file until the battery goes to 0% and device switches off.
disconnect from the charger (but you did this already, or?)
You can check from time to time the content of the log-file to see the progress if you like.
leave the device alone until is is off - this will take several hours, best is to do this over night. Put it at a place where the battery warning is not disturbing you at night.
after the device is off due to the empty battery, reconnect the charger and switch on after a few seconds of recovery
now you can look at the log-file and examine or post-process it in a spreadsheet program - the timestamp should tell you which file it was.
The resulting file "bd_<date-time-started>.csv can be loaded to a spreadsheet and evaluated, so you can compare your own batteries to see which is the best.
Even better, for the same device type the standardized method of measurement, where the current drain by the fully lit display should be reasonably identical for all devices, makes it possible to share battery quality data for 3rd party suppliers. A reasonable point of comparison for one device type is the time it takes until the battery is drained down to 10% - despite the discharge is not at all linear (usually).
I did all this and supply you all my data as an example to depict what you can do yourself now.
I hope you find the script useful.
For device specific discussions, please open a thread in the relevant device forum - pointing to this thread for the method - and not here. This thread is only to discuss the scripts or the method of measurement.
Note:
Please also read post 2 (device specific links) and post 3 (general hints on batteries) of this thread. I will update them from time to time when new info is available.
20100225 added:
If you want to find out how much drain happens to your battery in the test-setup, you can ask the battery driver, e.g. by using HomeScreen++ or BattClock. Mind that this data is not immediately reliable, especially when you change conditions (e.g. dim the light) the change is often reflected only minutes later. The true value can only be found by measuring the drain with an Ampere-meter. This is harder than you may think as the impedance of the meter must be very low to get the device started up properly.
20100313 added:
More programs to read the power drain:
free: acbpowermeter
cost: acbtaskman (can also export data) same provider as above.
Update to the script and few more data inserted to the spreadsheet:
The script now logs several items from the registry, including the Data for CurrentDrain and BatteryTemperature that BattClock writes if it is configured to show them in display.
Started to measure standby drain on all my spare devices - mileage varies. This is also not a real life measurement as the devices have everything shut off (light, radio etc..) and the only process that keeps them busy is the script waking up each 5 minutes. If you like you can change the value for MaxSleepTime in the script to much higher values to decrease the impact of drain to the measurement. I am not sure how this will behave on WM Professional with its complicated power model (standby mode) but on smartphone it runs very well. First data are available in the spreadsheet. It would be best of course to be notified by the system if the battery percentage changes instead of polling for it, but MortScript does not supply a method to achieve this.
20101123 added:
The script reads from data that the BattClock program writes to the registry if you configure it to do so. Further changes are:
Also BatteryVoltage is read from BattClock Data
Added log of status even if % has not changed if MaxLogWait has passed and if Battery % is below a given limit of LogForcePercent. This is needed as the last % (e.g. from 1 to 0) may take a long time (seen as 1h on an Asus P565) and the 0% will not be written because the device just switches off when 0% is reached. There is no chance for the script to write the last data to file in such case.
added a delta-% column to easily detect non linear decrements
The full change history is included in the script:
Code:
# Date ID comments
# 20101123 tobbbie changed script to match to a TAB alignment of 8 characters
# 20101123 tobbbie altered the logic for LogForcePercent and set default to 0 to not log anything by default.
# 20101010 tobbbie Added log of status even if % has not changed if MaxLogWait has passed and if Battery % is
# below a given limit of LogForcePercent. This is needed as the last % (e.g. from 1 to 0) may
# take a long time (seen as 1h on an Asus P565) and the 0% will not be written because the
# device just switches off when 0% is reached. There is no chance for the script to write the
# last data to file in such case.
# added a delta-% column to easily detect non linear decrements
# 20100425 tobbbie added Registry Read for BattClock BatteryVoltage, rearranged sequence of items
# 20100313 tobbbie added evaluation of \HKLM\System\State\Battery "main" to logging
# 20100313 tobbbie added identification of device via HKLM\Ident and IMEI in headerline
# 20100312 tobbbie made dword registry data to be logged as "0" if no data retrieved
# 20100302 tobbbie added registry read for data created by BattClock
# 20100205 tobbbie added self-adjusting sleeptime (InitSleepTime to MaxSleepTime in ms)
# 20100201 tobbbie initial version
# 20100128 tobbbie draft versions, proof of concept
Device Specific threads are available for:
Vox (tobbbie)
Tornado (tobbbie)
Hurricane (tobbbie)
Typhoon/Amadeus (tobbbie)
LG KS20 (tobbbie)
Rhodium/Touch Pro 2 (mccune)
...I will add more here if someone else starts other device specific threads, please PM me for this.
A lot of background information can be found at the "Battery University": http://www.batteryuniversity.com/index.htm
A specially interesting part is the one about charging: http://www.batteryuniversity.com/partone-12.htm
I have seen a strange charge curves on my Hurricane device - it goes to 68% and jumps to 100% suddenly. This device has a very bad discharge curve (% accuracy) anyway - so the charge fits to that as well. I am using the T-Mobile Germany SDA 2 standard firmware of the device - and since it is in my "museum" I will not put more effort in getting it tracked down.
At least I can confirm that the discharge for the same battery in the same device is nearly identical (I did this for the worst performing battery). I will upload some new result Excel soon.
To be on the safe side that your battery is properly charged, leave the battery charging for at least 4 hours. This should make sure that "step 2" of the charge (where the charge current goes down until charge cut-off) is sufficiently executed. In how much the "green LED" signal is linked to charge-cut-off is device dependent - it may even be different if you charge via the bootloader (device is completely "off") or with the battery driver controling the job.
This is really an amazing tool. Thanks
Ooops, this thread was lifted to the front-page news (I checked there to see the new design), so I hope to see some new device threads starting up and some more comparable data on "my" devices.
The echo was quite low (as of now: null) on these threads, so I suspect that people are happy with their batteries and have no need to know (or report) the truth.
Will post this in the Rhodium section as well. Great idea!
Don't give up on projects like these. It looks like XDA has a lot of members compared to a few years back, but the group of tech geeks (this is actually meant positive) remain about the same.
Thanks. Works on HD with Topix rom.
Please get back to this thread or PM me if you have reports of the test running on other devices. I'd prefer if you can deliver data along with your reports - of course.
Mind that the script can easily be enhanced to collect more information, e.g voltage or battery drain if these can be accessed via MortScript. A good place to observe is the HKLM\System\State\Battery\ where different drivers are updating useful information. Unfortunately not for mine, so I have not included it here.
I've posted this in the Rhodium section as promised.
You can find it right HERE. I did copy your post to keep things more general.
concerning the images you've posted they seem to lack some quality and are a bit hard to read.
EDIT: It seems that the graphics in the attachment from the first post are just fine.
Currently I'm charging my TouchPro2 to perform the test!
thanks, mccune!
I have added your post to the list in post 2 of this thread. I really hope that all the speculation on usage time and performance which is derived by comparing "average use" over time will fade away using this simple method.
If you like to adapt the script by adding related registry values from your device, feel free to do so. Many newer battery drivers are supplying data to the HKLM\System\State\Battery hierarchy of the registry.
If doing this, please do it conditionally on existence of the value so that the script can stay generic and still run on devices where the driver does not supply the data.
I would like to follow two real physical values when the battery runs down: battery voltage and current drain from the battery. This could put the comparison of batteries even out of the "device specific" cage - still assuming that the supplied values are sufficiently accurate though. However, since charging LiIon batteries is much depending on accurate voltage, this assumption should be valid.
Regarding the pictures: The board limits the picture size to 640x480 and resizes accordingly. As you found out the ZIP has the original pictures inside.
@tobbie
I've finished the testing but I did not get the values quite correct in the Excel sheet it seems.
Can you have a look at it? You can just send me the pics and I'll post them in the Rhodium section for you.
I performed two tests.
First: just charging the battery till the LED turns green (100%) and followed the instructions from the first post to perform the test.
Second: After the first test I've removed the battery for about 30 seconds and inserted the battery but left the device turned off. After it was fully charged I removed the battery again for 30 seconds. I put back the battery and performed the test again. I've read that this is the way to calibrate your battery after flashing.
The data looks fine - you can take the sheets directly to generate an individual graph in Excel. Just mark the first 2 columns, select the "Graph" button and then the "Points(XY)" graph type.
You also have to take care that the right % values are taking the time data. It sometimes happens that the % rundown is not getting all values, so certain % values are simply never seen (like 99,98 or 24 in your data).
If you want to use one of my sheets as a sample, then you need to create a % scale first for your device (it seems it can take all % values - while for the Tornado the < 20% are stepping in larger increments).
Then the copy/paste has to use the "transpose" option of the "paste information" menu to convert the column to line data.
I have done a quick graph on your data, see attach. You can further beautify this. I am surprised to see that the device has 10 hours of rundown time with the large display. Are you sure you have set the light to the maximum value on battery?
What were the current drain readings you got from the driver?
Thanks for this I can really work with this. I realized that I could just replace your data with mine but you've already done it.
Concerning the brightness. I did set it to maximum. The ROM used however is my own custom Rhodium ROM. Maybe I'll repeat the test with a WM6.5 ROM to see if you can actually notice any difference. At the moment I'm testing a Nokia E72 so my Rhodium can be used for testing a little longer
I normally use Homescreen++ to view the current drain. Another option would be to use BattClock 1.9 which seem to support this feature as well.
What method do you use to read out the current drain?
mccune said:
The ROM used however is my own custom Rhodium ROM. Maybe I'll repeat the test with a WM6.5 ROM to see if you can actually notice any difference. At the moment I'm testing a Nokia E72 so my Rhodium can be used for testing a little longer
Click to expand...
Click to collapse
Good that you can spend some time on it. I doubt that the ROM is making a difference as the OEM drivers and settings (battery, display) are usually not changed when cooking.
You have seen in the charts that the "calibration" is actually not doing anything worth noting down. Put in a different battery (other vendor) and you will see a difference. Nice to see that the percentage rundown is nearly linear on the device
mccune said:
I normally use Homescreen++ to view the current drain. Another option would be to use BattClock 1.9 which seem to support this feature as well.
What method do you use to read out the current drain?
Click to expand...
Click to collapse
Both programs ask the same driver so they should deliver the same values.
Can you actually TELL what the value of your drain was on the Rhodium?
My "method" is to connect an Ampere-meter (an old analog one to get a clue on the average current) - a little tricky though but it works once you have managed to get the "adapter" assembled.
My current drain on the Rhodium is:
- full lit display: 134 mA
- dim display: 35 mA
- Backlight can't be turned off so can't tell what the current drain for the third measurement is.
Modified the post in the Rhodium section.
Also added this line to the post:
"(If you want to use software try HomeScreen++ or BattClock to get the readings about the current drain.)"
Updated the Rhodium section. This should be the data you were after, right?
Yes it is - actually for calculating the capacity it is now simple: roughly 10 hours with 135 mA gives 1350 mAh capacity for the battery in the Rhodium. What is the rated capacity of the battery inside?
Was it the regular battery or a spare one from a different vendor?
If you use my sheets as a template you find fields for any of the interesting data that can be listed - also battery manufacturer and serial to tell apart different batteries.
I will add the two programs to the first post so that people do not have to read the full thread. Thanks for the information.
tobbbie said:
Yes it is - actually for calculating the capacity it is now simple: roughly 10 hours with 135 mA gives 1350 mAh capacity for the battery in the Rhodium. What is the rated capacity of the battery inside?
Was it the regular battery or a spare one from a different vendor?........
Click to expand...
Click to collapse
I use the regular Rhodium battery. Age is about 6 or 7 months now.
Today I've finished the test with a WM6.5 ROM. As you've predicted it's pretty much the same so I decided not to add it.
What might be useful to know is that you only get 10% increments when using the default battery driver from HTC. On my 6.1 ROM I was using a 1% driver so the data is measured much more frequent.
Data for PURE
Hi,
I have recorded data for my PURE.
It seems to suck battery very fast. Doesn't normally last a workday.
I am running TESS LEO IV ROM.
Would love to compare with someone with a similar device but did not see a thread for the PURE/D2/Topaz
Thanks.
With the HD2's pretty short battery life compared to my previous HTC phones, and also as I was a bit bored , I decided to have a look at how much the different systems drain in the HD2, and did some tests.
So for anyone interested, here are the results:
Base consumptions: (pick the one that suits your situation)
Standby, phone on, WIFI+BT off, no connections active: 5mA
Processor running idle, screen off, connections as above: 55mA
100% CPU usage (Coreplayer benchmark), connections as above: 315mA
USB connected, connections as above: 125mA
Additions: (add this to the base one depending on what you have on)
Connections:
BT on, idle: +1mA
Wifi on, idle: +5mA BUT!! If you enable wifi during standby (with BsB Tweaks or the WifiNoStandby CAB), the processor does NOT go to standby
anymore, so the base needs to be the 55mA above!
Connected to EDGE, idle: not measureable
Connected to 3G, idle: +4mA
Beware those 2 will occasionally and unpredictably send data every now and then, so this doesn't necessarily mean much.
BT transfer (file copy through ActiveSync, 120kB/s, CPU usage ~2%): +80mA
Wifi transfer (file copy with Wifi Remote access, 1MB/s, CPU usage ~3%): +200mA
EDGE/3G transfer: Pretty impossible to measure due to so many variables, but can be extreme (total current consumptions of 850-1150mA, so very approximative 500-800mA draw from the data connection during page loads are common!), and leads to most of the energy draw when using the net a lot. EDGE uses more power than 3G, consumption is higher when network coverage is lower, bad network throughput or congestion also mean lots of retries/overhead and less effective data transfer, using power for a longer time until the data is finally there.
Memory access (large file transfer):
Internal read/write through ActiveSync (speeds 2.5 / 2.1 MB/s respectively): +20mA / +130mA
Card read/write through ActiveSync (speeds 3.2 / 2.7MB/s respectively): +25mA / +40mA
Card read/write in USB disk mode (speeds 7.5 / 5MB/s respectively): +40mA / +45mA
Backlight:
10%: +65mA
20%: +78mA
30%: +90mA
40%: +105mA
50%: +121mA
60%: +136mA
70%: +154mA
80%: +170mA
90%: +190mA
100%:+210mA
GPS:
+95mA
Flashlight (with HTC Flashlight):
Level 1: +32mA
Level 2 (same as camera flash on): +107mA
Level 3 (same as camera "bright flash during shot"): +530mA
And remember the battery capacity: 1230mAh
So with this you can calculate your battery life for various activities. For example:
- Playing a video with full backlight: Let's say the video is well encoded (30% CPU use, for example 720x400 1Mbps DivX), that's about 150mA base, + 210mA backlight = 360mA, resulting in about 3h20 battery life.
- Same at night with only 40% backlight: Life goes up to about 5h!
- Wifi during standby for an 8h night, or a program that somehow prevents the phone from entering standby: 60mA or 55mA respectively, draining about 40% of the battery during that time.
- GPS program, with 70% backlight: Let's assume 150mA for the processor as it has some work to do, 90mA for the GPS, 154mA for the backlight = 394mA, or 3 hours.
- Music through wired headphones, screen off: the 55mA base plus a little 5mA as MP3 decoding is nothing for the CPU = 60mA or 20h.
- Same with a BT headset, with about half the BT bandwidth: 60+40 = 100mA or 12h
etc.
Charging
[EDIT 14.04.10]
This is now a dedicated section as I did some more thorough charging tests.
So, as some of you might know, the HD2 has 2 charging "modes".
- One is USB, that is used if the phone is connected to a PC, or an unknown device. In this mode, the current the HD2 will draw from the port/charger is limited to approx. 470mA, to stay within the maximum of 500mA a USB port can supply.
- The other is "dedicated charger", which is recognised on the original HTC charger (and some others, it's becoming a standard for a "dedicated charging USB port") by shorting of the 2 data pins of the USB connector in the charger.
USB charge
Important to know, during USB charge, the phone will NOT go to sleep, as it's supposed to be connected to a PC, and be running either ActiveSync, Disk drive mode, or modem, and in all 3 cases would be expected not to shutdown. So not only the current supplied to the HD2 is low, but the phone draws some of it for itself, leaving very little for actual charge - so expect loooong charge times.
USB charge with screen on (backlight dimmed, 10%): 285mA
USB charge with screen off (standby): 345mA (which shows the processor still runs and draws the "base USB" current)
Dedicated charger
When used with a charger that has the 2 USB data pins shorted, such as the original charger, the HD2 will draw a current that is proportional to the voltage on the USB power lines. To measure this I have used the original supplied USB cable, a variable regulated power supply, USB socket (with data pins shorted), and 2 meters for voltage/current. Voltages are measured at the "PC" end of the USB cable, so not taking account of losses in the USB cable. Will talk more about this later on.
Current vs Voltage diagrams are attached. Charge current is proportional to voltage, linearly until it reaches the max charge current, approx 830mA. This was measured so that the only draw is charge. If the phone is turned on while at max charge current, it will draw extra, until it reaches about 980mA, and will then stop to respect the 1A rating of the stock charger.
Now, to the influence of USB cables. I initially had some trouble with inconsistant numbers, phone only drawing 670mA from the stock charger, i.e matching neither the ~350mA from USB, or ~830mA from stock charger in "normal" condition. Turns out that to make it more convenient on my workplace I was using an USB extension between charger and HD2 cable. It was a $2 extension I bought on Dealextreme. Removing it solved the problem... and after making those measurements I poked with it again. Turns out that at 1A current, the voltage drop in the extension (which by the way isn't longer than the HD2's USB cable) was 1.8V! Yep, nearly 2 Ohms for a 1.5m extension! Couldn't believe it.
I have a cheap Chinese microUSB cable that wasn't as bad,but still significantly more resistive than the stock one, hence me noting I used the stock cable for my tests. So, quality of the cables, extensions, adapters IS important! Note the phone correctly reaches full charge current a little bit under the 5V USB spec, so everything is well tuned.
Now, important to know, Most 3rd party chargers will not have the 2 USB data pins shorted, and will thus result in the same behavior as mentioned under USB charge, the processor will also be running continuously drawing the "base USB" current.
It is often possible to modify 3rd party chargers by opening them and shorting the pins, speeding up charge. The voltage/current curve behavior is actually helping there, because thanks to it if the charger is overloaded its voltage will most likely fall a bit, and the HD2 will thus draw less and find a nice balance point. This DOES NOT mean there's no possiblilty of damaging the charger, but all 3 I modified did well. One that was really weak resulted in not much more current being drawn after the mod than before (i.e voltage fell very low, approx. 4.4V), however the gain from not having the processor running like in USB mode still sped up charge a little.
Thank you, that is one useful chunk of comprehensive information
Could you please explain the exact measuring method for these tests?
40% backlight at night is a tough example tho, Lumos on my device is set to 10% for 0 sensor value, and only because I can't set it to lower than 10%... nice to know battery drain goes up twice from 10% to 60%!
Also, 100% is usually really necessary under direct sunlight, in a normal lit room probably 40% backlight is more than enough to watch a video... all in all, with your superinteresting info, the battery doesn't look like lasting "too short" now, but more or less "the right amount considering the battery capacity".
My iPaq 210 has a 2200mAh battery, just to make a comparison... that's why I could go for 8 hrs during some bus trips while watching tv series, and I just needed to swap battery and used a little of the second one.
What's your estimate of the drain caused by activating push email? I've recently been doing some rather crude experiments myself, and one provisional conclusion is that push email on a hotmail account uses a lot more battery than push email on an Exchange server.
Excellent stuff, you are to be congratulated.
I have a long held theory and I wonder if you are in a position to to test it?
I believe that battery consumption is greatly increased when an app is run from mem card and would be intrigued to see a comparison between an install to this as opposed to phone mem.
Any chance?
Battery levels
I found that power consumption of the battery got even worse after I went to Rom 1.66.707.1. However, after a few days, I let it run all the way out, switched back on, it ran out after a few minutes. Then after an overnight charge I found the battery (on standby) only went down by about 10 -12 % in 24hrs. I'm hoping this performance will continue.
What did you use for the testing?
pa49 said:
Excellent stuff, you are to be congratulated.
I have a long held theory and I wonder if you are in a position to to test it?
I believe that battery consumption is greatly increased when an app is run from mem card and would be intrigued to see a comparison between an install to this as opposed to phone mem.
Any chance?
Click to expand...
Click to collapse
That would be reasonable as reading from an external media will need energy to access its contents... still, once the app files have been loaded into the device's RAM, it shouldn't matter much
You could also test by comparing:
1) copy say 30mb from one location to another of the internal mem
2) copy from microsd to microsd
3) copy from mem to microsd
4) copy from microsd to mem
ephestione said:
Could you please explain the exact measuring method for these tests?
Click to expand...
Click to collapse
Simply using the built-in current sensor, getting the reads from AEBPlus battery information screen, and methodically turning things on/off once the others are evaluated and can be subtracted from the total reading.
ephestione said:
40% backlight at night is a tough example tho, Lumos on my device is set to 10% for 0 sensor value, and only because I can't set it to lower than 10%...
Click to expand...
Click to collapse
Really? You should force the backlight off then
I love bright images myself, so even in my bed in total darkness if I watch a video or photos I'll force 100% backlight I have Lumos set to force 100% for Coreplayer, Resco Photo manager and HTC album
Of course not for browsing or just messing around, in that case it's 20% for me
Shasarak said:
What's your estimate of the drain caused by activating push email? I've recently been doing some rather crude experiments myself, and one provisional conclusion is that push email on a hotmail account uses a lot more battery than push email on an Exchange server.
Click to expand...
Click to collapse
That's one thing I'd have no idea about... I've never used push email at all. And that's "standby usage", so hard to evaluate, as you never know when it kicks in.
Measuring that would need to be done on a long time. I'd say to leave your phone one night with push email off, one night with Exchange only, and one night with hotmail only, and then check the difference, preferably with a battery at about 80% charge at the start (mine seems to fall from 100% to 90% in a few minutes before becoming more regular, so I'd say the top of the scale isn't that reliable).
And I should really try push email once, that would be nice, but I *think* I have no provider that can do it for me... well I have a gmail account I never use, I should try to see if I can have it check my usual 3 mail accounts, aggregate and push... never really looked into that stuff.
pa49 said:
Excellent stuff, you are to be congratulated.
I have a long held theory and I wonder if you are in a position to to test it?
I believe that battery consumption is greatly increased when an app is run from mem card and would be intrigued to see a comparison between an install to this as opposed to phone mem.
Any chance?
Click to expand...
Click to collapse
Thanks
Well I'd tend to refute that theory, because when I tested the BT and Wifi in use I tried read from internal memory, write to internal, read from card and write to card, and all 4 were identical. I should have mentioned it indeed, but I was mostly interested to seeing if reads (wifi/BT "sending") and writes (wifi/BT "receiving") would have an influence on consumption, which wasn't the case, as well as whether the throughput was different, which wasn't the case either.
But I've done a few more tests, see the updated first post
One intersting thing is firstly that when the HD2 is connected to USB, the current draw grows significantly, so I've made a new "base consumption".
Next, the card is actually faster than the internal memory both in reads and in writes, tested both through activesync for consistency. Writing to the internal memory eats a LOT more than writing to the card. Reading from the card eats a little more than reading from internal memory, probably evens out as the reads are shorter due to faster transfer rate.
I've added some charging tests as well. Apparently, even if the phone "disconnects" from USB when turned off, the processor still runs and uses about the "USB connected" base current.
kilrah said:
Simply using the built-in current sensor, getting the reads from AEBPlus battery information screen, and methodically turning things on/off once the others are evaluated and can be subtracted from the total reading.
Click to expand...
Click to collapse
d'oh aebplus has a battery information screen, checking it right away In that case you'd have to take into consideration aebplus' current absorption anyway... which is not measurable as you cannot check the current intake of aebplus without aebplus being running
I have the cab on the sd already, but didn't install if after noticing that didn't work for button assignments with later versions of the rom... does it work for you on that side? I used the program all the time on my previous ipaq because it was oh so useful but never got around to notice it had a battery info subsection.
Really? You should force the backlight off then
Click to expand...
Click to collapse
Wouldn't have much sense doing it in the dark would it (admitting it's possible altogether on the HD2!)
But I actually used my oooold casio cassiopeia, about 7 years ago, with backlight turned off, while reading ebooks with speed reader plus during train trips, as the neon lights created a reflection good enough on the display so that I didn't need backlight...
in the end, the backlight died altogether and until I bought a new device, I managed to use it with light turned off
A flashing LED (incoming SMS warning, e.g.) seems to add consumption of 1-3mA.
Running FlexMail in background with a push service (IMAP IDLE) adds up to 30mA.
ephestione said:
does it work for you on that side?
Click to expand...
Click to collapse
AEBPlus works fine for me yes... but I don't have a "latest version" ROM AFAIK. I don't like WM6.5.x new softkey arrangement, so I'm staying with 6.5.
Anyway more about Push, I configured that through gmail yesterday, and it works just fine. I left it on during the night, and this morning I had lost 8% battery. So it's pretty much negligible. I received 2 e-mails during the night and was on 3G network.
this is a nice topic! i am interested in how much extra it uses when you are playing a MP3 with the build in HTC app?
maybe it would be a nice idea to make a program that outputs results like you pasted fast and easy (something like a benchmark app) so we can test different rom's fast? too bad i cant write anything otherwise i would try..
OK, seems MP3 uses 120mA screen off, both with Sense player and Coreplayer, so:
Processor running idle, screen off base + 65mA
But it seems to make some pretty big "jumps" once in a while. Maybe they both decode ior fetch from memory by "batches"...
my test,
HD2 rom 1.66
with BT on and BT off (configured but no connection to headset) difference in consumption is 60mA .!
BT is draining my HD2 .!
kilrah said:
OK, seems MP3 uses 120mA screen off, both with Sense player and Coreplayer, so:
Processor running idle, screen off base + 65mA
But it seems to make some pretty big "jumps" once in a while. Maybe they both decode ior fetch from memory by "batches"...
Click to expand...
Click to collapse
OK, I can't confirm the BT issue. Did you observe over a long period of time? The "quiet" current for MP3 I seem to get is 185mA with screen on and backlight at 10%, but sometimes it will climb to 280-320mA for a moment and go down again, both with BT on and off. With screen off for a while it seems to stabilise at the "quiet" level.
BTW, it seems that Advanced task manager isn't reporting CPU usage levels properly. Does someone know of a CPU monitor that works correclty on the HD2?
Yup. review over multiple 6 mins. all baseline(3g/brightness) setting the same. resetting each time for off on BT.
kilrah said:
OK, I can't confirm the BT issue. Did you observe over a long period of time? The "quiet" current for MP3 I seem to get is 185mA with screen on and backlight at 10%, but sometimes it will climb to 280-320mA for a moment and go down again, both with BT on and off. With screen off for a while it seems to stabilise at the "quiet" level.
BTW, it seems that Advanced task manager isn't reporting CPU usage levels properly. Does someone know of a CPU monitor that works correclty on the HD2?
Click to expand...
Click to collapse
Another consideration:
Data connection sucks power when used actively. Badly. As mentioned in the OP I haven't made comprehensive tests due to low monthly allowance, but I've had a look during normal use.
I'm pretty regularly doing 1hr train rides, during which I will be listnening to music , and browse the net at the same time. It's usually bright, so backlight will probably be at 70%. Signal is relatively low most of the time, on EDGE, inbetween small towns. When I'm on a "static" page (reading an already loaded page), current drain varies between 250 and 350mA.
But while loading a page, it will easily soar to 800mA+. Considering it takes 30-60 seconds to read a page, 20 to load a new one, and repeat... you can quickly see that this kind of usage leads to serious drain... in less than 2 hours the battery would be dead.
So be aware of how much power data connection will use. It's directly proportional to the amount of transferred data, and the worse the reception the more power it uses.
I should try using opera mini again, like I was always doing on my Kaiser. I never noticed excessive drain with it, but opera mini easily divides traffic by a factor of 10...
Just wanted to report that the new version of the superuseful BattClock has now a builtin battery current output, even if it's not really update once per second... seems more like one every 10 seconds.
I get ~240mA playing fullscreen stretched Frasier in lowest backlight (but that's with the keypad leds turned on all the time, I don't know why they don't go off, and I don't have keypadledcontrol installed... so that's a problem), and I get a total 630mA with HTC flashlight at maximum.
Good news! Bye bye Batti
Normal about the refresh time, the sensor only updates every 20 secs or so.
Some new considerations I posted somewhere else but should have put here.
After some time the HD2 seems to have better battery life, but usually it's not your battery lasting longer, it's just you not spending your day playing with the thing anymore.
It's always the same thing, the more a device can do, the more you do with it. On my first 1h train journeys after getting my HD2, I was able to kill 50% battery in 1hr. My first thought was "wow, with my Kaiser I would only use like 15%!!"
But then I took a second thought. I used 50%, but I was browsing the web, in bad reception areas, while listening to music the whole time. With my Kaiser, I'd put music on, check 3 webpages, then put it on the tray with just MSN connected and just pick it up to read/type a message once in a while.
On a next trip, I "forced myself" to do the same with the HD2. Just checked the news for 5 mins, then only listened to music and picked up msn once in a while, plus an unexpected 10min phone call. Guess what? I've only used 20% battery during the trip this time
The "problem" is that browsing with the Kaiser was just painful, so I'd just check the news and put it away. On the HD2 it's so comfortable I forget it and just spend my whole trip browsing heavy pages, which obviously kills battery in no time...
exactly my thoughts and findings