Im using stock ke7 that is rooted. When im using currentwidget to show the battery drain it says no data. Battery % and voltage is shown correctly but not the actual drain.
Is it only me or is this problem for all sgs2?
current widget doesnt support Samsung devices because the way the hardware reads the temperature or something is not accessible...not sure the exact reason tho but there is another app called "battery monitor widget" which displays some "ma" but it will just be an estimate so it won't be 100% accurate..
the max10742 fuel gauge chip in the galaxy s2 does not output current readings, only voltage, temperature, and a few others. the original galaxy s used the max10741 and it also did not output current readings.
most other phones, like HTCs use the ds2784 in the nexus one for example, and they DO output current readings.
i think there is a way to re-write the battery driver to maybe change this, but thats a project for another time.
battery monitor pro only guesstimates mA readings when it cannot find actual current files from the kernel.
Related
I have extracted framework-res.apk from a Galaxy player 5.0(2.2) and put 1% battery mod in it
The file is not tested as i don't have the player at this moment, so TAKE YOUR OWN RISK!
Feedback is appreciated.
View attachment 835896
Let us know if this works, I may root if it does!
I am testing the file with a player bought in hong kong
It seems that for some reasons, the battery level step up or down every 5%
but good news is it should do no harm to your player too
l_ung said:
I am testing the file with a player bought in hong kong
It seems that for some reasons, the battery level step up or down every 5%
but good news is it should do no harm to your player too
Click to expand...
Click to collapse
I suspect that changing the framework-res.apk is not sufficient. My player is also modded to include battery icons for 1% increment but I still see an increment of 5%.
I've looked up some similar mods for other android devices, it seems that modification to the services.jar is needed. e.g. http://forum.xda-developers.com/showthread.php?t=1278136
We may want to look at how it is done on other devices.
The 5% increment appears to go all the way down into the kernel. I've never seen it report anything but 5% increments.
The fuel gauge architecture seems completely different from GalaxyS phones despite the hardware similarities.
BMW shows it going down in 5% increments, but the mV readings are much more accurate. Is there a way to use the mV values for displaying %?
tcat007 said:
BMW shows it going down in 5% increments, but the mV readings are much more accurate. Is there a way to use the mV values for displaying %?
Click to expand...
Click to collapse
Technically yes - if you knew how Maxim's ModelGauge algorithm works. But this is a major trade secret for them, so it's unknown how they manage to get reasonable battery SoC estimations from voltage only.
The problem is that battery voltage depends not just on state of charge, but on load. The moment you connect a charger - BOOM the voltage goes up significantly. Increase load significantly - voltage drops. (And actually, even Maxim's algorithm used in the MAX17040 and 17042 fuel gauges fails here - a heavy load right after a FG reset confuses the chip, making it report low. This is why Galaxy S II devices will experience significant SoC estimate drops when they are rebooted at low battery due to the battery load that happens on boot.)
Does anyone know if Current Widget or Battery Monitor Widget is compatible with this phone? I am getting readings of -100mA ~ -400mA on standby. Charging readings seem to be accurate though. I get high amperes at lower percentages then as it reaches 100% it lowers to about 5mA, but it never hits 0mA.
I'm just wondering if it might have the same issue as the Sensation when it first came out. Is anyone else using Current Widget or Battery Monitor Widget with this phone? What readings are you getting?
Edit: Oh I forgot to add that I have calibrated the battery
idaggerpwn said:
Does anyone know if Current Widget or Battery Monitor Widget is compatible with this phone? I am getting readings of -150mA ~ -400mA on standby. Charging readings seem to be accurate though. I get high amperes at lower percentages then as it reaches 100% it lowers to about 5mA, but it never hits 0mA.
I'm just wondering if it might have the same issue as the Sensation when it first came out. Is anyone else using Current Widget or Battery Monitor Widget with this phone? What readings are you getting?
Edit: Oh I forgot to add that I have calibrated the battery
Click to expand...
Click to collapse
get a different program
I am on the same boat. I have current widget on my amaze and i have never seen it go to 0ma.
I don't know why because my nexus 1 will always show 0ma when fully charged. Am guessing the amaze battery is never fully charged and is always drawing power from the charger..
What are your current readings like? Is it in the -100mA ~ -500mA?
Charging -- btw 750ma and 900ma
Fully charged-- btw 10ma and 200ma... It depends on what am doing with the phone... When at idle it is usually around 10ma and 40ma
For some reason the lowest I can get while it's idle is around -120mA... Any idea why? I have syncing off, data off when screen off, wifi off, bluetooth off. Pretty much everything is off but the cell radio...
Even with the cell radio off, the lowest it gets is about -100mA. That is why I started the thread in the first place. I assumed the readings were incorrect. I attached a copy of my log for anyone who may be interested.
just because I didn't want to create a new thread
keywords: Battery Monitor Widget, Battery Current Monitoring mAh mA, latest version as of 8/5/2012 (can't find a way to get the version number)
For Battery Monitor Widget, I went to settings -> Monitoring -> mA Retrieal Method -> HTC Sensation
I DID NOT check the "mA Corrections"
Idle current usage says -48 mA (~ 2%/hour, which is somewhat ideal) ... turning the screen on makes it go to -150 mA
Will test the other options(that listed other devices later)... i've Tried "Some HTC devices" option before, didn't help, still reported -100 at idle..
could use some help from other people testing the various options: EDIT: testing a couple of the other options, seems like the Sensation option is the best one
Bootloader unlocked + rooted, S-Off, SuperCID'd, SIM unlocked,
RUU: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
ROM: Project Butter Speed Rom 8/5/12
Kernel: KozmiK Ruby v0.5a - badass governor, powersave option, undervolted by -12.5
1 gmail account, data on, auto-sync
Ankor 1900 mAh battery
Moved to Q&A, where it belongs.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice
Sent from my HTC One X, using XDA Premium
http://forum.xda-developers.com/announcement.php?a=81
So take apps like Ampere for example, they show some battery-related stats, one of which is battery health. I've yet to see any other value than "Healthy". So wondering how does the app / system determine the battery to be in good shape or not? Does it calculate the current maximum charge the battery can hold and compare to maximum, something like 2970mAh / 3000mAh can be considered healthy? Does it use the voltage value? Does it just use the temperature?
To provide context, my Note 5 is feeling like the battery has gone bad, I'm getting very limited screen on time even with light usage. Ampere and similar apps still show my battery as "Healthy", so I don't know if it's just a bogus stat or something scientific and can be trusted (which means my problem lies in something software-related).
Thanks for any input!
I've noticed a lot of posts on the subreddit recently complaining about lag when under a claimed particular battery percentage. This will explain the functional reason and allow some insight into perhaps modification using root.
I got my A7 new only a few months ago so my battery hasn't degraded enough to have the issue yet. I did notice the lagging symptom before I ran my battery flat recently. I've got an interest in battery life after modding around on my last device a Sony Z3C and since then the A7 too.
From experience I know /sys/class/power_supply/bms/device/v_cutoff_uv 3200000 is the voltage threshold at which my Z3C shuts down. Battery configuration varies a lot by models, the A7 lacks this writable file.
On the A7 I found these related writable files in /sys/class/power_supply/bcl/device/
high_threshold_ua 4200000
low_threshold_ua 3400000
vph_high_thresh_uv 35000000
vph_low_thresh_uv 3300000
Google search provides this generic related documentation. The initial description paragraphs translated in lay terms describes a CPU throttling function based on battery voltage and current load limits. https://android.googlesource.com/ke...mentation/devicetree/bindings/arm/msm/bcl.txt
Of direct interest is "vph-low-threshold-uv: The battery voltage threshold below which the BCL driver starts monitoring the battery current thresholds and mitigates the CPU on the event of high load."
Also "vph-high-threshold-uv: The battery voltage threshold above which the BCL driver clears the previously applied mitigation, disables the battery current monitoring, and starts monitoring for low battery voltage."
The "-threshold-uamp" descriptions don't match the A7's provided values of seemingly voltage rather than micro amps. Assuming they're voltages of 4.2 and 3.4 but I can't guess how they take effect.
What this means for those with slowed devices under a particular percentage, check your battery voltage to see if this is the cause using a battery app or something like DevCheck. BMS State of Charge fuel gauge percentage is a varying arbitrary number influenced by numerous functions and algorithms, in other words it's a meaningless number to troubleshoot. If your battery voltage is under 3.3V at something like 50%, your battery is severely degraded and the fuel gauge is completely off, you could perhaps try setting /sys/module/qpnp_fg/parameters/restart 1 (it will restart fuel gauge calibration and the setting will automatically go back to 0). Alternatively we could try to disable the Battery Current Limit but I suspect the purpose of it is to prevent Nexus 6P style sudden early shutdowns which require an external charger to jump start them again. In any case at least this info will help those diagnose why and how degraded their battery is.
Infy_AsiX said:
I've noticed a lot of posts on the subreddit recently complaining about lag when under a claimed particular battery percentage. This will explain the functional reason and allow some insight into perhaps modification using root.
I got my A7 new only a few months ago so my battery hasn't degraded enough to have the issue yet. I did notice the lagging symptom before I ran my battery flat recently. I've got an interest in battery life after modding around on my last device a Sony Z3C and since then the A7 too.
From experience I know /sys/class/power_supply/bms/device/v_cutoff_uv 3200000 is the voltage threshold at which my Z3C shuts down. Battery configuration varies a lot by models, the A7 lacks this writable file.
On the A7 I found these related writable files in /sys/class/power_supply/bcl/device/
high_threshold_ua 4200000
low_threshold_ua 3400000
vph_high_thresh_uv 35000000
vph_low_thresh_uv 3300000
Google search provides this generic related documentation. The initial description paragraphs translated in lay terms describes a CPU throttling function based on battery voltage and current limits. https://android.googlesource.com/ke...mentation/devicetree/bindings/arm/msm/bcl.txt
Of direct interest is "vph-low-threshold-uv: The battery voltage threshold below which the BCL driver starts monitoring the battery current thresholds and mitigates the CPU on the event of high load."
Also "vph-high-threshold-uv: The battery voltage threshold above which the BCL driver clears the previously applied mitigation, disables the battery current monitoring, and starts monitoring for low battery voltage."
The "-threshold-uamp" descriptions don't match the A7's provided values of seemingly voltage rather than micro amps. Assuming they're voltages of 4.2 and 3.4 but I can't guess how they take effect.
What this means for those with slowed devices under a particular percentage, check your battery voltage to see if this is the cause using a battery app or something like DevCheck. BMS State of Charge fuel gauge percentage is a varying arbitrary number influenced by numerous functions and algorithms, in other words it's a meaningless number to troubleshoot. If your battery voltage is under 3.3V at something like 50%, your battery is severely degraded and the fuel gauge is completely off, you could perhaps try setting /sys/module/qpnp_fg/parameters/restart 1 (it will restart fuel gauge calibration and the setting will automatically go back to 0). Alternatively we could try to disable the Battery Current Limit but I suspect the purpose of it is to prevent Nexus 6P style sudden early shutdowns which require an external charger to jump start them again. In any case at least this info will help those diagnose why and how degraded their battery is.
Click to expand...
Click to collapse
Just curious since you pointed this out and me finding this delightful information, I'm at 92% right now with a voltage of 4064 MV, is that a bad sign of battery degradation?
troy5890 said:
Just curious since you pointed this out and me finding this delightful information, I'm at 92% right now with a voltage of 4064 MV, is that a bad sign of battery degradation?
Click to expand...
Click to collapse
Can't really know by that. Easier to notice at the low end, if you get the CPU lag under a particular percentage, check if voltage is below 3.3V.
Sent from my ZTE Axon 7 using XDA Labs
Infy_AsiX said:
Can't really know by that. Easier to notice at the low end, if you get the CPU lag under a particular percentage, check if voltage is below 3.3V.
Click to expand...
Click to collapse
I did it get a little lag when I was playing an emulation at 15%. I checked and it had a voltage of 3504 MV.
troy5890 said:
I did it get a little lag when I was playing an emulation at 15%. I checked and it had a voltage of 3504 MV.
Click to expand...
Click to collapse
Hm checking after when there's less current load won't show the real time voltage drop. To examine the BCL effect, probably need to watch voltage in real time, IIRC watching CPU freqs also shows the throttling. DevCheck pro can overlay cpu freqs, or Trepn profiler can for free IIRC. For a voltage and current overlay, can use CoolTool which is free for it's custom labels. Kind of technical yeah but has to be to figure this out. If anyone wants the CoolTool overlay custom settings, let me know.
If you straight up just want to test BCL off try setting the vph thresholds to 3000 3100 respectively, below shutdown cut off as to not take effect. Maybe it won't allow values less than cut off though, testing with monitoring the only sure way.
Sent from my ZTE Axon 7 using XDA Labs
Mine lags at any percentage, I can't browse Chrome as fast as I was able to in the past. Whenever I launch it, it lags, when switching tabs it lags, tapping the search bar takes the keyboard up to 5 seconds to appear... And it's not just Chrome, the whole phone got slow but mostly Chrome. I used to be able to smoothly manage up to 200 tabs, but now it even lags with only 20. I might try a factory reset soon, I hope it helps. Clearing recent apps didn't help at all, clearing the cache partition helped for a few hours, then it was lagging again.
i executed this /sys/module/qpnp_fg/parameters/restart 1 and my battery % dropped from 8% to 2%.I put it on the charger and its charging normal,also normal speed.
Why i have the feeling this is our bsm reset?
My battery has about 51% of its life left estimated below 20% it chugs hard. When thrown on a charger 0-30% takes about 10 seconds. I don't have root but can look at some point. I've upgraded to a mi Max 3 but my A7 is now my car multimedia system.
Infy_AsiX said:
I've noticed a lot of posts on the subreddit recently complaining about lag when under a claimed particular battery percentage. This will explain the functional reason and allow some insight into perhaps modification using root.
I got my A7 new only a few months ago so my battery hasn't degraded enough to have the issue yet. I did notice the lagging symptom before I ran my battery flat recently. I've got an interest in battery life after modding around on my last device a Sony Z3C and since then the A7 too.
From experience I know /sys/class/power_supply/bms/device/v_cutoff_uv 3200000 is the voltage threshold at which my Z3C shuts down. Battery configuration varies a lot by models, the A7 lacks this writable file.
On the A7 I found these related writable files in /sys/class/power_supply/bcl/device/
high_threshold_ua 4200000
low_threshold_ua 3400000
vph_high_thresh_uv 35000000
vph_low_thresh_uv 3300000
Google search provides this generic related documentation. The initial description paragraphs translated in lay terms describes a CPU throttling function based on battery voltage and current load limits. https://android.googlesource.com/ke...mentation/devicetree/bindings/arm/msm/bcl.txt
Of direct interest is "vph-low-threshold-uv: The battery voltage threshold below which the BCL driver starts monitoring the battery current thresholds and mitigates the CPU on the event of high load."
Also "vph-high-threshold-uv: The battery voltage threshold above which the BCL driver clears the previously applied mitigation, disables the battery current monitoring, and starts monitoring for low battery voltage."
The "-threshold-uamp" descriptions don't match the A7's provided values of seemingly voltage rather than micro amps. Assuming they're voltages of 4.2 and 3.4 but I can't guess how they take effect.
What this means for those with slowed devices under a particular percentage, check your battery voltage to see if this is the cause using a battery app or something like DevCheck. BMS State of Charge fuel gauge percentage is a varying arbitrary number influenced by numerous functions and algorithms, in other words it's a meaningless number to troubleshoot. If your battery voltage is under 3.3V at something like 50%, your battery is severely degraded and the fuel gauge is completely off, you could perhaps try setting /sys/module/qpnp_fg/parameters/restart 1 (it will restart fuel gauge calibration and the setting will automatically go back to 0). Alternatively we could try to disable the Battery Current Limit but I suspect the purpose of it is to prevent Nexus 6P style sudden early shutdowns which require an external charger to jump start them again. In any case at least this info will help those diagnose why and how degraded their battery is.
Click to expand...
Click to collapse
should we execute this line /sys/module/qpnp_fg/parameters/restart 1 (it will restart fuel gauge calibration and the setting will automatically go back to 0),when battery sits on 100%? then charge to 100% again,wipe batterystats,and reboot system? Can this be a proper way to calibrate the battery? When i charge my battery sometimes it says 5V at lockscreen
Hi,
in past it was possible to check real current battery capacity in mAh. I mean in service menu when you type:
*#*#7378423#*#*
Now there is no info on battery capacity.
Any idea how to check it?
Maybe different code?
I have my doubts Android reports it even close to accurately. Maybe Sony does it better but run time is generally the best indicator of actual capacity. Accubattery Pro's mAh gauge gives a good -relative- vs actual measurement. Again Accubattery's discharge history ie run time is the best method I've found.