Related
i guess a picture is worth a 1000 words... have a look...
more pix for ur eyes ^_^
If your rooted, try battery calibration. Plenty of threads about, and varying methods.
If not, another battery, and if new, ensure charge fully, phone off, overnight, before first boot.
Sent from my GT-I9100 using xda premium
forgot to mention i'm running [Rom]Wanam v3.2 at that time, currently on v3.4, the dark extended areas is me at work where i turn airplane mode on due to serious bad reception at work... sync is on rest of the time for gmail/whatsapp/kakao other than that manual updates on twit and some news apps...
u can see the first jump in the first pic, that was due to me exchanging with 1st spare battery( got 4 + original batt= total of 5)
i dont know if its the phone and exchanging batteries thats causing such high battery losses at the end of the battery life...
plus yesterday and the day before battery goes crazy when it reaches 30-20% and when i go for a restart to freshen things up... the phone wont switch on thinking the battery is totally dead... i put in the new battery and its @ 100% ... switch back to the old battery to see where the 30-20% went... it wont start...
now im thinking... keeping 1 battery in the phone with a charge from 0-100% actually takes the phone all the way to 0% but exchanging the battery wont...
how am i supposed to use the full potential of the batteries...
UpInTheAir said:
If your rooted, try battery calibration. Plenty of threads about, and varying methods.
If not, another battery, and if new, ensure charge fully, phone off, overnight, before first boot.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
been using this app since my old sgs, it sure works and have been using it ever since...
tho in the [Rom]Wanam ... install procedure says that its backing up the battery stats and this lead me to think that a batt calibration is not needed... or am i wrong to think so?
If you change batteries, all previous data will be irrelevant, and you need to calibrate each time. You can do things manually by installing battery monitor widget, charge to 100% AND until the mA reaches zero (Voltage spills be approx 4200mV). At this point, quickly delete battery stats (menu / stats /) and immediately unplug.
https://market.android.com/details?id=ccc71.bmw
Top help with monitoring, You can config the update rate and widget content so it shows mA, %, mV. Also have alarm when stops charging (if configured).
There is also an option for calibration, but I only use this method when done above first. Never discharge to zero, 1% min.
Sent from my GT-I9100 using xda premium
UpInTheAir said:
If you change batteries, all previous data will be irrelevant, and you need to calibrate each time. You can do things manually by installing battery monitor widget, charge to 100% AND until the mA reaches zero (Voltage spills be approx 4200mV). At this point, quickly delete battery stats (menu / stats /) and immediately unplug.
https://market.android.com/details?id=ccc71.bmw
Top help with monitoring, You can config the update rate and widget content so it shows mA, %, mV. Also have alarm when stops charging (if configured).
There is also an option for calibration, but I only use this method when done above first. Never discharge to zero, 1% min.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thing is, what's the use of having spare batteries if this will happen on each battery swap and having to go thru calibration means having a charger nearby...
and by 0% i didnt actually mean 0 but till that 1% turned the phone off
if what u said is true, then i guess i need some kind of script to help and keep the batt data even after swapping.. based on 1 good calibrated file swapping batteries should start from a certain point even if the batteries do lose some of their charge but continue to moniter things as they were... i dunno if what i said makes sense... correct me if i'm wrong
Not really 100% sure, but sure I have not always calibrated after a battery swap in the dhd..The previous battery was calibrated and performing well, and the replacement would have been very close to 100% charge. I didn't notice any irregularities in the battery data, or battery drain.
So I suppose a good bat stats file should help the phone showing relatively "accurate" data after a battery swap, if they're both "conditioned" (gone through a number of charging cycles, not straight out of thre box)
Maybe I could be wrong, but based on past experience.
Sent from my GT-I9100 using xda premium
UpInTheAir said:
Not really 100% sure, but sure I have not always calibrated after a battery swap in the dhd..The previous battery was calibrated and performing well, and the replacement would have been very close to 100% charge. I didn't notice any irregularities in the battery data, or battery drain.
So I suppose a good bat stats file should help the phone showing relatively "accurate" data after a battery swap, if they're both "conditioned" (gone through a number of charging cycles, not straight out of thre box)
Maybe I could be wrong, but based on past experience.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
thanks a lot for ur replies ^_^ much appreciated
anybody else wanna shed some light on this ?
This is a good app for more info on battery drainage.
http://forum.xda-developers.com/showthread.php?t=1179809
Have you tried different radios/modems for better reception? if your phone is struggling to get decent reception its going to use your battery.
You could try changing to 2G only in wireless settings. used to help me alot.
mynamesteve said:
This is a good app for more info on battery drainage.
http://forum.xda-developers.com/showthread.php?t=1179809
Have you tried different radios/modems for better reception? if your phone is struggling to get decent reception its going to use your battery.
You could try changing to 2G only in wireless settings. used to help me alot.
Click to expand...
Click to collapse
i'm already using it steve, thanx for the helpful info ^_^ , tho it has nothing to do with my strange problem... before going to work i switch to 2g coz i mainly use it for calls so after work is done, i wanna have fun with the phone so its back to 3g... i hardly have reception as i mentioned before is due to really thick walls and working underground in some rooms... its just common sense... plus im on latest modem and its actually performing better than other phones (nokia,BB,moto,iphones....) at where i work, 5 guys got convinced and got a sgs2 coz of mine lol
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.)
LGP500
Yaa why? The phone has three terminal the battery has 4. Has any one noticed that, can we do some tricks to speedup charging? Like short the extra terminal...
4silvertooth said:
LGP500
Yaa why? The phone has three terminal the battery has 4. Has any one noticed that, can we do some tricks to speedup charging? Like short the extra terminal...
Click to expand...
Click to collapse
Faster Charging = more harm to the battery than good
The battery terminals are generally labelled:
+ ; - ; T ; and D or Do.
T is conneted to an internal temperature sensitive component ( thermistor) . This is to prevent overheating of the battery so it is very important on safety point of view
D or Do is a newly introduced contact. It is a data line which allows smartphone and battery to exchange information about current, voltage, temperture, residual battery capacity etc.... It has been introduced to improve % remaining battery capacity readings.
No way to speed up the charge on that side........
4silvertooth said:
LGP500
Yaa why? The phone has three terminal the battery has 4. Has any one noticed that, can we do some tricks to speedup charging? Like short the extra terminal...
Click to expand...
Click to collapse
Nice findings...lets see where this thread goes...
Neway, feels good to see u back...
Ive looked thru this forum and can't seem to find info on a battery temp that becomes hazardous. I've just started running an app called trapster, but the battery gets very hot. I think it read 110 yesterday. My battery charge indicator app has an alert function. One of the alert functions choices is ""temperature rises to""______. I don't know what temp (F) is considered "OK" and at what point is it no longer OK. Any body have good info about this?????♦
simagic said:
Ive looked thru this forum and can't seem to find info on a battery temp that becomes hazardous. I've just started running an app called trapster, but the battery gets very hot. I think it read 110 yesterday. My battery charge indicator app has an alert function. One of the alert functions choices is ""temperature rises to""______. I don't know what temp (F) is considered "OK" and at what point is it no longer OK. Any body have good info about this?????♦
Click to expand...
Click to collapse
I wouldnt worry about it too much, having overheated the phone a few times playing angry birds
The phone just shuts itself off when it gets too hot.
Agreed ....
I believe the bulk of the heat is coming from the CPU .....followed by the battery ....and as mentioned above, the device will handle itself.
I know this doesn't answer your question, but I've never seen any published data on battery temperature specs ....g
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