yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] 3c:
Any spare battery I tried didn't deliver the expected capacity, ever! So it would seem that stock battery are following a different production path and all others are some kind of marketing fake?!

Got a 3500mAh extended battery (phone gets hugly), but it only delivers 2200mAh. The other 1800mAh spare battery only delivers 900mAh!!! Shop said it is broken and sending a new one, but I'm not sure it will help!

Those numbers provided by the app could easily be verified with both charging time and use time. Glad I only bought those for testing/building the app and paid something like 10 bucks each.

Did anyone try some branded battery, like Mungen?
[Android Apps and Games] 7_michel:
The one I bought on Ebay works fine .......

http://cgi.ebay.fr/ws/eBayISAPI.dll?ViewItem&item=360389328884
[Android Apps and Games] L_T_K:
Nice widget.. i will try it
[Android Apps and Games] shinesthru:
Evo 4g running decks 1.3d, tiamat 3.3.7. I have skimmed this thread and google but I have not found an answer. After running a few charge/discharge cycles the app has yet to measure the mAH. See screenshot below. Any ideas?
[Android Apps and Games] RedWave31:
Hi everyone!

I did bother to look for the first 3 pages and last 4 ones, and did look for the "GS2" tag, hope nobody else did ask or answer that!

I'm actually investigating battery drain with the help of BMW and BetterBS.

- BMW problem : reading seems incorrect, the battery ma fluctuates hard.

Option to retrieve is automatic, battery capacity is set to 1650, read from system file for 1% is on. I got, say, 3948ma for 60%, then 3972 for 60%, then 3964 for 60%, then it goes down, then up... 1% readings aren't even the top value authorized, since when going down one percent, it MAY go up that value...

- BBS problem : I'm getting awake readings without wakelock. MI:4 is on it's way and looks like i've found a ghost protocol lol

Currently swapping kernel (Siyah 2.2.3, going back to 2.1.1) to resolve the ghost awake pb, but i'm still looking for a way to have 2ma drain with all apps gone, a fresh ram wipe, and so on :-(

So i'll hope we'll have great readings from our GS2s, even if I know there's a new chip in there :p

TYVM!
[Android Apps and Games] negrobembon:
Man, i updated to the latest version of both BMW and system tuner and my battery started draining like crazy i dont know why, i had to freeze em

Im using an x10 with stock 2.3.3
[Android Apps and Games] 3c:
Update to the latest version from Android Market, this will resolve the issue.

I suppose you mean 3948mV @ 60% ?

Trying clearing both app settings (or check all refresh/logging rates), you probably changed some of the refresh rates.

Also check where you save battery history, switch to internal RAM, maybe your SD card has issues.
[Android Apps and Games] RedWave31:
Yep of course i was meaning mV (or whatev lol)

- Changing kernel made it all the way back, my guess i shouldn't try exp kernels (tough siyah is famous, so...)

WIll post in the appropriate section. For now, remember that strange drains may be kernel related.

Still don't have the explanation for that "awake" lock without kernel locks... :-(
[Android Apps and Games] 3c:
I'd suspect the awake times is experimental-kernel related too? Like the weird battery data you had, it's all provided by the kernel.
[Android Apps and Games] jpkbeddu:
Thanks for the support through Email.. I got working correctly now with HTC Thunderbolt monitoring method..with also mA corrections enabled.. I had last night standby drain rating @ 3mA constant.. Great work..

Finally a correct current monitoring app for HTC Incredible S...
[Android Apps and Games] DirkStorck:
Hi.

Do you have an Desire or an Nexus?

Do you get correct readings for mV and mA?

Does your battery go from 100% to 0%?

Thank you ?
[Android Apps and Games] 7_michel:
I have an HTC Desire. You can see a sample of data I got from BMW on different batteries : http://78michel.unblog.fr/htc-desire-battery-shutdown-analysis/

My old HTC battery has lost 15% of his initial capacity. I have not been able yet to calibrate it

The new HTC battery (P/N 35H00132-06M) gives me wrong readings.

The only one which is working fine and gives correct readings mV, mA, T°C is an unbrabded chinese one......
[Android Apps and Games] jpkbeddu:
When I create a new profile in Calibration for my battery, its asking for root permission.. So is the app clearing the battery stats bin like the Battery Calibration app do..? And what's the meaning of Update reference means..?
[Android Apps and Games] 3c:
Yes, the app will clear the battery stats when creating a new battery profile, and switch the stats file when changing battery. The app stores each battery stats separately so that calibration is retained.

Update reference, will update the mV range reference. Useful only if your battery seems to be aging (smaller mV range can be achieved) and you want to reset it. Once I had a mV range from 3100-4300, though the 3100 was achieved once only, so had to update the reference range to reset it and get a 0% aging back.
[Android Apps and Games] jpkbeddu:
Wow.. awesome app for battery calibration.. Great work..

Even though I am running stock battery of Inc S 1450mAHr... I am seeing Measured value around 1700mAHr with +/- 51%..

Does this mean, the app needs more battery cycle monitor to get correct Measured value..? And what does +/- value represents..?
[Android Apps and Games] 3c:
The +/- is the error margin. To increase accuracy, you have to run a larger % charge cycle. The 51% is the result of an average 50% charge cycle. Running a near 100% charge cycle should produce a much more accurate reading.

EDIT: The current version calculates mAh based on all history loaded, so it can take much time before it improves. The next update will use last data first and keep only the most accurate (wider % range) so it will be more precise. Update due today or tomorrow.
[Android Apps and Games] coolfire:
As usual, awesome stuff from you! :)
[Android Apps and Games] hollander1985:
the problem of charging at my htc desire HD is that when the battery is almost empty (around 5% orso) and i'm gonna charge it.

then when he is around the 30% he says that the batter is 100% full

But actualy he needs to charge for 70%

Has anybody here the same problem and knows a solution?
[Android Apps and Games] zeppelinrox:
Calbrate the battery
[Android Apps and Games] AmonLeusi:
i have 2 batteries - sometimes the BMW recognize the original battery as the 3rd party battery, but only sometimes; also the measure is wrong, f.e.: 1500mAh battery is now a 2500mAh battery. only fix: battery out, wait minute, battery in - fixed. ;)
[Android Apps and Games] 3c:
There's no way BMW can "recognize" a battery as from an Android perspective batteries don't have identification! So I'm not sure what you mean by that.

Also, the measured value might be wrong, though you don't have to "use" it. An option in the monitoring settings is available to set it manually to the actual value. Android again doesn't read battery capacity, it's instead hard-coded in the kernel. So whether you put battery X or Y, Android kernel will continue to report the same battery capacity!

Now, you can reference all your batteries in BMW and store their capacity/historical performance, etc... But it's all done manually: You shutdown Android, swap battery and on boot you go back to BMW and tell it you have changed battery, selecting the new one manually.

The next update should improve the calculations and the data reference per battery. Should be released in the next hour. Running final tests :)

EDIT: The app has been updated on Market (v2.0), that should greatly improve your multi-battery experience! ;)
[Android Apps and Games] AmonLeusi:
thanks, now i'm understanding the working mode/function.
[Android Apps and Games] 3c:
No problem, i'm actually sorry for the lack of documentations/guides. As the app is getting more stable, I'll try to focus on that.

Hopefully I can add a help menu in all screens pointing to web pages detailed how everything works, but again that will take time and I'm still working on System Tuner, where there's a lot to do.

Just hope you can get the most out of the app ;)
[Android Apps and Games] hollander1985:
i have calibrated it many times, but it didn't help.
[Android Apps and Games] shinesthru:
So if I am getting a measured mah that is all over the place (ranging from about 300-1000) on my 1900 mah battery, do I need to wipe stats? I am having the same problem on my stock 1500 mah battery and I have run about 5 full charge cycles on each battery.
[Android Apps and Games] Braneless:
Are you talking about discharge mA? That increases or decreases depending on cpu load.
[Android Apps and Games] shinesthru:
No, under the calibration tab there are "In Use" & "Measured" mAh values. Ever since the last few updates the "Measured" values have not seemed accurate. I don't think it is the battery because it does the same on at least 3 batteries. What's odd is that sometimes the value will actually drop after a full charge cycle.

Maybe I should note I am on an evo4g, running deck 1.3d with tiamat 3.3.7 sbc. I also get great battery life with moderate phone use (a few calls, a little gaming, plenty of texts, and lots of web) use lasting 12-20 hours depending on which battery I am using.

edit: Oh, and my discharge mA looks pretty healthy. I usually idle at around -20 to -30, and it jumps to -200 to -300 while in use.
[Android Apps and Games] 3c:
The measured mAh is calculated based on mA measures. Since v1.9.9 it's only based on charge cycles, because discharge mA can be very inaccurate on some phones.

What your charge time? It usually correlate with the charger capacity (1Amp) and the total capacity of the battery. A 1000mA charger will take around 2h30m to charge a 1500mAh.

You can also check your history file, and the % range while charging. If it's missing some history, the value will be reduced. So I'm working on calculating the missing history if any for better calculations.

Though I'm surprised you get a measured mAh ranging from 300 to 1000! 300 is like the app found only a couple of charge measures! Or maybe you're charging your phone completely off, hence without complete history?
[Android Apps and Games] 3c:
What phone are you using? Do you get real or estimated mA? Estimated mA are based on used capacity. Hence if you update the 'used mAh' with unrealistic value, you will get messed up mA, hence messed-up measured mA.
[Android Apps and Games] 7_michel:
The measured mAh is calculated based on mA measures. Since v1.9.9 it's only based on charge cycles, because discharge mA can be very inaccurate on some phones.

I just made a full charge and discharge cycle on my HTC Desire. Then I take the data from BMW and put them in an Excel sheet to calculate the actual battery capacity from both the charge and discharge cycle. I notice that results are very close.

This means that Li-ion Battery are able to deliver back almost the same curent charge they received during charging..... if the charging is stopped as soon as the 100% charge is reached.

I did not imagine, up to now, that the Li-ion batteries could reach such a very high efficiency

As a consequence this is a very good idea to calculate the battery capacity at the charging cycle as the current level is always high and the accuracy much better than with low discharge current
[Android Apps and Games] shinesthru:
Evo 4g. I use automatic mA reading.
[Android Apps and Games] shinesthru:
My charge time on the 1900mAh is around 3 hours.

I don't have actual gaps in the history file, but the % does tend to jump like from 74, 79, 85, 91, 95, to 100% in 20 minutes.

Also, I haven't been charging the battery while the phone is off.
[Android Apps and Games] 3c:
Can you send your history file. That way I can load it in the app and check the app logs for the result variations. You can use the app's mA support request in the settings, adding a special note at the beginning of the new email so I can spot it amongst the many I receive!

Note I'm still working on fine-tuning the measured mAh, though on your phone it's usually very precise!
[Android Apps and Games] shinesthru:
Can do, thanks for the help.
[Android Apps and Games] [] AL []:
Hi there and fist off, thanks to the devs of this apk; it's great.

Now, I admit, I haven't followed or read this whole thread yet and I'm sorry if this has been covered before.

But I have to ask this: why do I (and as MANY other CM7-Jordan users (Moto Defy) have reported and inquired about) get those recurrent current spikes and battery power drops both on charging and discharging? [see pics]

It's seems to happen in 2-3 different cases: 1) in the middle of the battery charges - from ~57% down to 49% and 2) when the charging instensity switches: when getting close to 90% or very low/early within the charge state - around 10% to 20%.

Is that hardware, firmware, software (BMW apk and/or my rom) related or even a mix of all those? Anyone has a definite answer on this, or even better, a fix??

Because it's seems like I'm always losing/wasting 20-30% of each battery charge because of this...

Thanks in advance and thumbsup again.
[Android Apps and Games] [] AL []:
Excellent initiative!

That would have been my next request: estimations.

Because I really have a hard time getting anything close to be realistic from the estimations. I've tried all the possible combinations with reset batt history, reset estimate history and the many widget estimation settings.

Rebooting and/or charging (not only when powered off but also when connected to PC with SD card access ;)) quickly render estimations useless. I sometimes wish that there was a simple entry box to fill in- something like input 3.5 days max battery and that the estimations would be done based on that...

I sometime see 31 days estimations and sometimes only just over a day on a fresh full charge (and no usage); so yeah, estimations can be all over the place.

But again, i have more reading to do here but I sure did try to sort this out for a long time with not much success.

Cheers.
[Android Apps and Games] 3c:
Well, you're talking about different things here.

Note there is 4 different type of estimates, all explained here.

Then there are phones with 'estimated' mA based on battery capacity, and phones with real mA. For the first category it is important to have the proper capacity set in the monitoring settings, at least for the 'real-time' estimate.

The estimate calculation do not use history at all, so if all you want is estimates, you can disable the history logging (will disable the graphics too) and save cpu time too.

The best estimate (imo) is the global estimates at the top of the estimates screen. It's the mix of past pattern usage and current usage since unplugged.

The estimates rarely go all over the place, but the real-time estimates when going out of standby will show the remaining time on standby! When the mA gets updated it will then show remaining time with the new mA value, that is if the drain is constant until battery is fully drained. This one is useful when having a single activity (game, internet) to show you how much time left doing the same thing.

Back to the calibration screen and measured mAh, this turns out to be much more complex than expected! If you run full charge from let's say 5% to 100% each time, the value will be very accurate. But it turns out some users do half charge from 5% to 40% or from 60% to 100% and those 2 examples gives very different results! because charging mA is not linear!

Charging from 5% to 40% is when the battery is charged as fast as possible, taking in around 1000mA... But starting around 50/60%, the charging rate is decreasing.

So the app needs to extrapolate the total capacity out of very different measures! For now the app does not make the difference between those 2 examples, only considering the % range, which can give poor results (when charging 60% to 100%).

Now considering many small charges, from 5% to 45%, then stops for 5 minutes, then again from 45% to 78%, then stops 2 minutes, then again from 78% to 100%! The calculation can become very complicated!

Now consider a user charging is phone from 40-60% upto 100%, never going lower than 40%!?

So the app needs to consider the % range and the starting % to extrapolate the whole capacity! And everybody expects the result to be precise at +/-10mAh! :D and do not even consider the +/- <error> % margin value!

Well, I think I'll put back a mandatory range from 10% upto 60% for the app to provide a measured mAh! Extrapolating is impossible because every charger/phone does charge the battery differently! Some are more linear than others!

Sorry for the long explanation, hope it makes more sense.
[Android Apps and Games] [] AL []:
"Sorry for the long explanation, hope it makes more sense."

Yes, all good; I'm fine with long answers ;)

So if I understand well, the 'battery drops' are somehow related to how the user and/or the charge is performed and do not mean that there is a real "drop" ?

To get more accurate estimations, I should turn off battery history logging? I don't think that logging every few minutes is taking so much battery.. and it would be kind of strange (or a pitty) if we couldn't get good estimations and still see how our battery has been discharging.

I always make sure that the max battery capacity (mAh) is entered properly and I also enter the max and min mV values in the calibration tabs. But anyway, I understand that battery estimation is never 100% accurate and that it could be a science field of its own :D - too many hw/sw and user variables.

Thanks again anyway.
[Android Apps and Games] 3c:
Yes you're correct all the way, no much battery saving disabling history logging, depending on how charge is done the measured mAh can vary (a lot sometimes!), a field of its own indeed! Didn't know that when I put my feet into it!

Just one thing to clear-up: there is the estimates screen (displaying remaining time) which do not need history, and there is the calibration screen which requires the history file!

Working on a next update that will try to be more precise and use the most accurate charge cycles to provide a better measured mAh.
[Android Apps and Games] tamshiwen:
sorry, wrong thread
[Android Apps and Games] ephestione:
Just wanted to follow up in here what I tried off the main website's forum, that is having the log file saved to internal memory instead of sdcard.

I have a galaxy note and I was seeing about 8-10% of the battery draining overnight, so where everything else failed, I finally disabled BMW. What do you know, back to 2-3% drain overnight :D

So I moved the history txt from sd (actually internal sd, non external) to /data/data/blahblah, and with BMW history enabled, 3% overnight.

I take this opportunity to ask if it's feasible a feature to "disable history logging while in deep sleep", to have BMW only log when phone is already woken up for anything else (be it even the scheduled 3am maintenance backup), thus estimating, as soon as the phone wakes up because of something else, the average mA drain in that lapse of time, be it 1 hour or 8 hours.
[Android Apps and Games] Cap'flamme:
Hello!

I've an HTC HD2 running hyperdroid cm7 rom. What kind of mA retrieval method should I use? Is automatic fine or I should go for "some HTC devices", "HTC sensation" or "HTC Evo / Evo 3D" ?

Thanx for this great app. I used the free version for a few months and was happy with it, so I just decided to buy the full version today.
[Android Apps and Games] ephestione:
Don't set it, the HD2 has a decent chip which reports real mA values, no need for estimates.
[Android Apps and Games] 3c:
Interesting findings. I tested that too, didn't see a difference! I suspect it highly depends on hardware and SD card performance.

Anyway, this would be indeed possible. The Android scheduler has an option to set alarms that wakes up the device or not, sending the alarm the next time the phone wakes up.

Last time I tested it, I found out the logging was still taking place! But with a few holes here and there. Not sure the actual savings will be higher than the required calculation when phone awaken again. Though worth a try! I'll check if I can make it a user option without having to add too much calculations.

Thanks! On HD2, the 'Some HTC devices' is usually the right choice, though it can vary with custom ROMs. You should see very quickly if that settings is ok.
[Android Apps and Games] Cap'flamme:
mmmh...there is some discrepency here...:D

For the moment I'm on automatic, I guess. Measurements seem coherent from what I can tell but BMW is just reporting a measured battery capacity of 935mAh for an original capacity of 1230mAh where it was reporting 1230mAh with my previous ROM (DHD based). That's why I'm wondering if my readings are correct now.

If I set the measument method to something else, how would I know which setting is appropriate? Should I have completely out of range reading if I don't use the correct parameter?
[Android Apps and Games] ephestione:
This is exactly my point, as long as you don't need much coding to implement that optional function, then it should make sense to implement it ;)

well, between me and the software developer, there is no doubt whom to trust :D

I can only report my own experience, on a CM7 port for the HD2, and I remember I didn't even touch the mA estimation method.

IMO the best way, on the HD2, to check if the readings are ok, is if, under history, you see a constant 4mA drain for when the phone is idle in GSM only (and you should also see 4mA in the widget everytime you wake up the device after a few minutes it's been in standby).

On my Note instead, the real drain in standby with GSM should be around 8mA, but BWM, estimating the current value because of stupid Samsung not including a decent chip with amperometer functions in their devices, the drain will slowly decrease on each history entry even during standby and deep sleep, until, during overnight stands, it will reach a constant value of a few mA's.
[Android Apps and Games] Cap'flamme:
When mA retrieval mode is set to "some HTC devices", I have a 3 mA consumption in deep sleep on GSM only with data inactivated. It seems correct to me, no?
[Android Apps and Games] ephestione:
Well that's good, considering I very rarely got less that 4mA, and only on WM6.5, never on Android ;)
[Android Apps and Games] RussianBear:
guys, anyone having a 0 ma reading with the screen on? once the screen is off, the readings go back to normal. the phone is htc sensation. tried uninstalling and reinstalling - no effect.
[Android Apps and Games] zx34:
No, minimum on main is 100ma with the screen on!

Sent from HTC Sensation, Elegancia ROM Series....
[Android Apps and Games] OCedHrt:
Yep. HD2 is awesome :) I'm not on a Nexus S and the "estimated" mode drives me a little crazy! But with more charge cycles it seems to be more accurate now.
[Android Apps and Games] RussianBear:
put into "sensation" monitoring, seems to be working right now.
[Android Apps and Games] jastop:
Thanks for the help (and very minor ui issue)

How much battery time do you get on your phone? I do have a Galaxy Nexus (don’t think the operator matters here) and I get 24 hours with heavy use (lots of WIFI download + app testing + playing 3D game) and the app running along with System Tuner recording activity. I use mostly the default settings.

...

Can you check you run the latest version of the app from Market (2.0.2)? and try again?

Thanks for the help. The changing the interval, and the newest version, made the behavior I was seeing a non-issue.

I noticed that the "&gt" is not being translated to the appropriate character on my Galaxy Nexus or Tab. See the attached screen capture.

I have been through two full discharge charge cycles since downloading the latest app and clearing the battery stats, hopefully the estimates will start to show longer battery life and more battery capacity after a couple more cycles.:)
[Android Apps and Games] 3c:
Sorry this is a bug in the app, some of the text resources got messed up at some point. Will be fixed in next update. Sorry for the inconvenience.