yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] tobbbie:
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.
[Windows Mobile Development and Hacking General] mccune:
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!
[Windows Mobile Development and Hacking General] tobbbie:
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.
[Windows Mobile Development and Hacking General] mccune:
@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.
[Windows Mobile Development and Hacking General] tobbbie:
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?
[Windows Mobile Development and Hacking General] mccune:
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?
[Windows Mobile Development and Hacking General] tobbbie:
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 :-)

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.
[Windows Mobile Development and Hacking General] mccune:
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.)"
[Windows Mobile Development and Hacking General] mccune:
Updated the Rhodium section. This should be the data you were after, right?
[Windows Mobile Development and Hacking General] tobbbie:
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.
[Windows Mobile Development and Hacking General] mccune:
I use the regular Rhodium battery. Age is about 6 or 7 months now.
[Windows Mobile Development and Hacking General] mccune:
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.
[Windows Mobile Development and Hacking General] pgonza02:
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.
[Windows Mobile Development and Hacking General] tobbbie:
Hey - thats not bad, roughly ten hours is a good value! Mind that you have set your device to drain the battery by leaving the display full brightness on all the time. This is not happening for normal use.

Did you switch off all other current drains (device should be in Flight Mode, so no BT, Wifi or GSM/UMTS/CDMA active)?

Did you set the light to max brightness for battery use?

Can you tell what is the rated value of the battery (mAh)?

What is the current drain that the battery driver reports - there are some programs listed below that are able to tell you. From current drain and elapsed time it is very easy to see if the battery meets its specifications.

I did some more measurements myself and have enhanced the script quite a bit to log more data (also from Battclock). Will post the changes over the weekend and some explanations.

You can leave the link to the script in the autostart folder - it will continue to log your normal use over time.
[Windows Mobile Development and Hacking General] pgonza02:
I followed your instructions to the letter so all radios were off and the display was at max.

I am using the original battery which is 1100 mAh. Been meaning to get something a little bigger but don't want to have to change the back cover and haven't had much time to research it.

Which tool can I use to measure the current drain? Sorry but did not see any listings on the thread.

Thanks very much for the tool. I can help you test the new script on my device.
[Windows Mobile Development and Hacking General] mccune:
Did post info about it though :)

You can find it HERE.
[Windows Mobile Development and Hacking General] tobbbie:
I have added some tools at the bottom of the first post - easiest is the free acbpowermeter
[Windows Mobile Development and Hacking General] pgonza02:
My bad, missed it.

Will try that and post what I find.

Feels like this battery is much worse than my old Touch Cruise.
[Windows Mobile Development and Hacking General] tobbbie:
Devices are very different in how much current they draw from the battery. Mine vary from 65mA (Amadeus) to 120 mA (Vox). Same capacity battery will deliver only half "full light runtime" - but as said: this is not the normal use case!

Also mind that newer devices have more powerful CPU that drain more juice from the battery to supply all the eye-candy that you like.

This method will not delivery any data for real life use time of the device. It will simply tell what the battery delivers - nothing more.

It is up to you to decide later on what you will spend the juice (light, eye-candy, games, FM radio - other radio like BT, WLAN or 2G/3G - worst is usually GPS!). Nothing is for free and the more seductive the devices are the shorter the subjective perception of the runtime is.

If your battery driver delivers good data for current drain (my devices all do not do that sadly), just install the acbpowermeter and watch how the drain varies with all the different options - you will be shocked how fast the battery can be sucked away.
[Windows Mobile Development and Hacking General] tobbbie:
first post updated:

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.
[Windows Mobile Development and Hacking General] pgonza02:
I am going to play with acbpowermeter to try and get an idea of my power hug. I have a feeling that the auto-location services, like weather might have something to do with it. I have increased the auto-download time for weather to 3 hours.

Thanks for all the info.
[Windows Mobile Development and Hacking General] pgonza02:
I have been playing with different configurations and acbpowermeter but it never shows any variation in the power consumption.

Through manual trial and error I think I have narrowed down my problem to having Windows Live setup for push mail.
[Windows Mobile Development and Hacking General] tobbbie:
The battery driver does not report the real current drain - my experience is that the read outs are hardly ever relieable short term - so for my battery measurement it is just a good guess for the capacity calculation. I believe that the value is ok for a long duration constant power drain like I describe for the measurement.
[Windows Mobile Development and Hacking General] tobbbie:
Let me add some comments about the battery driver accuracy. In the meantime many Tornado devices have passed my desk (needless to say that I am a Tornado fan...) and all of their batteries and drivers have been measured. I noticed that the reported drain is mostly accurate (~75mA for this device and full lights on) but I have also seen devices report 95mA despite their real drain was 75mA only. These devices still behave normally what charge/discharge is concerned, so nothing to worry about.

I also noticed that without any exception the bundled original batteries (Samsung, CelExpert, Sanyo) deliver the best performance, especially counting the age they have reached now.

Not a single 3.rd party China label matched equal performance. They reach 900 - 300 mAh only. The higher the labeled capacity, the lower the performance. So don't fall for the false promises on capacity!

You have the power to measure it yourself - don't believe in rumors!
[Windows Mobile Development and Hacking General] tobbbie:
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

See first post
[Windows Mobile Development and Hacking General] Joe Bleau:
How to Create Graph w/ csv?

@ tobbbie: Thank you for the script tool. I installed BattClock & logged data to csv as well as ran your script as by instructions in post #1 for two different batteries.

I attached the 3 files to this message but don't know how to create a graph with Excel comparing these 2 batteries on htc Tilt 2 (Touch Pro2) running this ROM: Energy.RHODIUM.28244.Sense2.5.Cookie.2.0.Feb.19.

Can you help me? :confused:
[Windows Mobile Development and Hacking General] tobbbie:
You can re-use any of the supplied charts for your purpose. Basically some advanced copy/paste actions. It requires some Excel know how to get useful charts and align the scales so it works. As the tilt2 seems to have a full scale of %, use the KS20 as your template if you want. I have quickly put something together - yet not as fancy as the supplied charts.
[Windows Mobile Development and Hacking General] Joe Bleau:
Re: How to Create Graph w/ csv?

Thanks for the quick reply, I'm surprised you still follow this thread.

I'm a total noob when it comes to Excel. From the data I posted above, which battery is better or has the most mAh capacity? Run 1 or 2 as I don't see time in the xls graph you attached.
[Windows Mobile Development and Hacking General] tobbbie:
It is easy - the big numbers are the seconds passed since rundown started. So re-calculate that to hours dividing by 3600. Both batteries are rather equal in total capacity. One give a better impression over time as it takes longer until a percentage is run down, but they both roughly end the same time.

On that graph things are reversed, the percentage should be reverse (100 -> 0) and on the other axis. But Excel takes it that way and you need to supply the data differently to see the graph differently (like in my example charts).

The current drain is looking not very constant - have you really switched off all other power suckers, especially all Radio parts (GSM/UMTS, Wifi and BT)? What about scheduled activities on the device?
[Windows Mobile Development and Hacking General] Joe Bleau:
"On that graph things are reversed, the percentage should be reverse (100 -> 0) and on the other axis" - So only the x & y labels should be corrected & the data remains the same in the file you posted above?

I'm running the stock NRG ROM above w/o SIM, WiFi or BT but had Tbattery running w/ logging. Backlight set as instructed in post #1. I'm testing a third battery bought on Fleabay advertized as OEM @ the present so will post the background processes tomorrow as I want to have the same conditions as the previous 2 tests.

Thanks again for the explanations tobbbie. :cool:
[Windows Mobile Development and Hacking General] tobbbie:
Everything is "right" in the sheet as it is. It can only not so easy be interpreted. Usually if time is part of a chart, then it is used on the x-axis (so running from left to right, here it is on the y-axis. Changing the labels of the axis will not help, you must re-organize the source data, row to column.

Representation can be done differently, just look at the example excels. There the data are organized differently (row + column) and the chart looks different (as I think it is "intuitive" to understand). If you want nice charts, use the "KS20" worksheet and copy/paste (transpose) the column data to row data in that sheet. Converting Column to Row is done by marking the original column data (following the 100->0), "copy" to clipboard, then go to the new sheet where 100% starts in the heading and replace the data there by "paste content", select "transpose".
[Windows Mobile Development and Hacking General] toan1101:
thanks much
[Windows Mobile Development and Hacking General] Joe Bleau:
Re: How to Create Graph w/ csv?

If I select my data, 1 run at the time & try to paste to your LG KS20 worksheet

exactly

as you described (paste special > values > transpose) I get: can't do it because format is not the same, do it one by one. :( I tried other pasting options to no avail. :confused:

I attached the data for my 3 runs using the worksheet you attached above. What is the real capacity (mAh) for all 3 batteries? Could you edit the graph so it's easier to interpret? Is the surface below the curves representative of the battery capacity?

Maybe you could create a

simple template with graph directly applicable

to your file output and add to your post #1 for us Excel-challenged noobs? ;)

Edit: The script saves files as .csv, they need to be renamed .txt to be opened w/ Excel as txt to get the Text Import Wizard and select in Step 2: semicolon and coma.

I attached the 3 original xls files with all the data provided by BattClock and tobbbie's script.

*****

Then click on the Thanks button! :cool:
[Windows Mobile Development and Hacking General] gdsdj:
Thank you, I am from China, Chinese: 谢谢您，非常不错，准备测试我的电池！
[Windows Mobile Development and Hacking General] tobbbie:
Somehow I missed the replies here, sorry :-(

This is easy to calculate: If you know the current drain (and you trust it), then the capacity is simply: capacity[mAh] = <average current-drain>[mA] * <elapsed time at shutdown>[sec.] / 3600 [sec./h].

The example excels do all this automatically - strange that copy/paste did not work for you.

As I am no Excel Wizard, I cannot supply anything else than what I did already.
[Windows Mobile Development and Hacking General] akashroy1987:
Help Needed

Ok, heres my result in csv format. But since i dont have access to a pc at this moment, can some kind soul pls do the technical stuff and let me know whats the state of my HTC VOX's battery. Its on the verge of dying already. I'm unable to use the phone without the charger pin inserted. :(

Just wanted to cross check, since the battery shows no wear at all from the outside, it didnt even swell.
[Windows Mobile Development and Hacking General] tobbbie:
This battery has only ~15% capacity left even if fully charged. Another effect of this lost capacity is that the inner resistance of the battery has grown and so any higher current drain (like for activating radio or wifi) will drop the voltage below the shut-off level. A good battery should last with the testing conditions given about 8 hours (3600*8 seconds) on the Vox.

It may be hard to get a good replacement as even new (unused) Li-Ion batteries die after a few years after production date - simply because Li-Ion chemistry is not stable in that regard.
[Hero, G2 Touch Android Development] naivemonarch:
Hey, new to the forums, recently purchased a GSM Hero.

I have done some development for free software (think freedom, not price) projects, and have become accustomed to git repositories and structured development.

Upon entering the world of custom Android ROMs (at least Hero ROMs) I have been sorely disappointed with the development practices going on, releases on file sharing sites and the like.

On top of this, none of the ROMs available suit my needs.

This is all fine, as I'm not developing those ROMs.

I have decided that I need to start working on my own custom ROM, however guides and documentation regarding this process are in short supply.

It would be much appreciated if someone could link me to some guides to starting my own custom ROM.

I intend it to be a light vanilla ROM, with none of the bloat that seems to perpetuate other ROMs, I'm aware other such ROMs do exist, however none of them support all features, and even those that claim to do so, often require me to FC :(
[Hero, G2 Touch Android Development] pvillasuso:
Have you tried this one ? >[2.1] aychteesees-vanilla-cupcake< NOT the [3.0.1]verison ..this is still @dev

http://android.modaco.com/content/h...96/3-0-1-aychteesees-vanilla-cupcake-rom-gsm/

Give it a try [2.1] ! :cool: and tell us how it went ... :D
[Hero, G2 Touch Android Development] naivemonarch:
Yeah I tried that one, it claims to have full functionality, however I frequently had to FC various applications.

I'm downloading 3.0.1 as we speak, however I'd still like some resources on making my own ROM.
[Hero, G2 Touch Android Development] mauro269:
I'm interested on this documentation too....thanks
[Hero, G2 Touch Android Development] pvillasuso:
That's weird , I have used almost everything ( apps ) with that ROM [2.1] ... and never get FC's

Did you flashed from Zero .. I mean with all he possible wiping . inlcuding SD ext partition wipe

???

That is a MUST ..!
[Hero, G2 Touch Android Development] FunkTrooper:
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.

This leads me to another question: all these custom ROMs that we see available for download -- are they free/open source? Like, do they have source code available? I certainly don't think they do, but if they don't, then aren't they violating the terms of the GPL by not providing source code?
[Hero, G2 Touch Android Development] adwinp:
There's Paul's (modaco) online kitchen, but if you want to compile by yourself, there's a plethora of gits on github (cyanogen, lokx, kiall to mention just a few).
[Hero, G2 Touch Android Development] dsixda:
Good question. Yeah it would be nice if there was a 'Cooking Class' thread on this forum like in some of the other forums. There is a decent tutorial however at HTCpedia.com under the HTC Hero ROM Development section, it's in the stickies there. However, I still have questions and that forum is not visited as much as xda.

Link to cooking thread:

http://htcpedia.com/forum/showthread.php?t=1404