Degraded battery BCL device lag - ZTE Axon 7 Guides, News, & Discussion
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
Related
up to 1% accuracy battery Mod
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.)
Lets try to narrow down the Overheat issue.
Edit: From what I have gathered from those that have provided info. Around 120*F is normal for heavy use, around 105-110* for medium use, 100-105* for light use. This is with cell data enabled, wifi lowers temps 5-10*, also temps are for extended use scenarios. (over 10-15 min) Heavy use= 3D game or graphically intensive 2D game, streaming videos especially HD Medium use= basic games web surfing sites with lots of images or some flash content Light use= sending SMS, basic fooling with settings or other basic functions, streaming music with the screen off I think we need to get a bit more scientific about testing this overheating issue out. I need help from a large group of people. I need those who think they have overheat issues and those who do not for the info to be useful. First off... I believe these temps are just the battery, not the CPU. I think the CPU is running relatively cool as the rest of the phone does not heat up, or it seems what heat is felt is coming from the battery only. This would explain why people claim that the extended battery does not have this issue. As batteries with higher mAh ratings are able to handle the higher power demands with less heat. We need to do comparison tests using the same apps across tests and the same use times as well. Also no over or under-clocking and using the same CPU governor. (and between everyone participating where possible) I have Minecraft and Sleepy Jack, they both produce similar temps after 15 minutes of play time. (around 117-120*F) I do not know if it gets any hotter with longer use because I rarely play longer than that at a time. I am at about the same temp after only 10 minutes so maybe that is the highest it gets. I know for certain that enabling WiFi has a big impact on the temps. My fiance's phone would only get about 95*F, (according to the SetCPU widget) but when LTE is enabled it would get to 115*F. Mine hits 105* on WiFi. I want to do at least two tests. Lets use the following steps to test: -For all testing the test time will be 15 minutes of play time. -Lets all use Minecraft since there is a free version and I know the app causes the phone to work hard. -No over or under-clocking -On Demand governor Test 1) Airplane mode enabled Test 2) 3G enabled (not everyone lives in a LTE area, if you do, data from LTE enabled would be useful as well) Now some optional tests. I did some rudimentary testing and there seemed to be an impact on temps. Optional 3) Using interactive governor or Lag free governor Optional 4) Use a different kernel... If you are on stock switch to ziggy's and vice versa. (this may be the most promising test as since switching to ziggy's I have had a few lockups where the old Android logo pops up on the screen and I need to do a battery pull to fix it. This happens to the fiance's device as well) If you do these tests, please post the results, and what ROM and kernel you are using. I will keep track of the results and update as appropriate. Lets see if we can find some consistent data and narrow this heat issue down. Edit: Running Ziggy's kernel I hit 108*F kept playing and shortly after the phone did the odd crash I mentioned.
Nice, had the same idea to do one of these over the weekend - you just beat me to it I've done alot of research/ testing heat wise, and the pseudo-scientific conclusion that i've come to is that in a room temperature environment something like 75-85F idle & 110-115F netflix is normal for this gen of phones (Rezound, Galaxy Nexus, Galaxy S II, etc) - Give or take another 5F if you're using 4G. Seems like some devices are luckier than others & stay slightly cooler, but i'd gauge that they aren't the typical use case. IMO, (along side battery) data is a huge reason we've seen some of the face melting temperatures people have been reporting. One thing I think would really help this thread is to set an easy to follow format for posting results. For example, here's a few tests I've done: ### Phone Info ### ROM - Stock Kernal - Stock CPU Speed - Default (1.5) Battery Type - Standard Case - Generic TPU ## Test 1 ## Charging - No Data - 4G (4 bars) App - Field Runners Test Duration - 15 min Start battery temp - 85 F End battery temp - 112 F Total Battery Drain - 20% ## Test 2 ## Charging - No Data - 4G (4 bars) App - YouTube Test Duration - 20 min Start battery temp - 85 F End battery temp - 104 F Total Battery Drain - 16% ## Test 3 ## Charging - No Data - 4G (4 bars) App - Onlive Test Duration - 30 min Start battery temp - 85 F End battery temp - 125 F Total Battery Drain - 40% Hope this helps, i'd really like to see people participate - this information will be helpful for pretty much everyone in the Android community with a current gen phone.
Stock rom Extended battery Charging - yes App - shine runner Duration - 20 min Start temp - 96F End temp - 115F 3g, 3bars This extended battery will get just as hot as the stock, just takes a little longer. Edit-not quite as hot as the stock, but pretty toasty.
if it's the battery, then isn't the only parameter we need to test is current draw from the battery? no matter what radios/apps are enabled/disabled. It's bottom line is, the more we're drawing off the battery the hotter it's getting? I'd have to bring a pro in here on how Li-ion works in this form factor and why it gets hot, or what corners the battery manufacturer cut to make it possible!
The only time my battery gets hot is when I am in a weak signal area and the phone is searching for the 3G-4G signal. During daily use in a good signal area it never heats up.
My phone (and wife's also) heats up most notably during charging, especially when the battery is around 99% and going 100%. Usually the temp goes to ~ 45C (115F). In some rare cases, it was too hot to touch (dunno the exact temp). But some other times it would stay cool at all time. Wife's first phone went into bootloop and her current phone is a new replacement. I kind of believe the overheating was the main cause of the bootloop problem.
thatsricci said: if it's the battery, then isn't the only parameter we need to test is current draw from the battery? no matter what radios/apps are enabled/disabled. It's bottom line is, the more we're drawing off the battery the hotter it's getting? I'd have to bring a pro in here on how Li-ion works in this form factor and why it gets hot, or what corners the battery manufacturer cut to make it possible! Click to expand... Click to collapse It's more than just the battery. Also: feel free to post a test - the more data we get from everyone, the better.
One important variable missing: ambient temp.
I was just playing words with friends for ten minutes: Ambient temp: 67, Screen brightness: 50%, 4g: ON wifi: OFF my temp went to 105F, it's NEVER gone to 105F when playing before... and I play it every evening. It was hooked to the USB charger at the time, and when I felt it getting so hot, I looked at battery monitor and my net charge was negative, so it was using more than it was charging off the usb... maybe something in some of those apps triggers something that causes the temp to rise? a loop? something?
thatsricci said: I was just playing words with friends for ten minutes: Ambient temp: 67, Screen brightness: 50%, 4g: ON wifi: OFF my temp went to 105F, it's NEVER gone to 105F when playing before... and I play it every evening. It was hooked to the USB charger at the time, and when I felt it getting so hot, I looked at battery monitor and my net charge was negative, so it was using more than it was charging off the usb... maybe something in some of those apps triggers something that causes the temp to rise? a loop? something? Click to expand... Click to collapse I noticed any time I charge with USB and use my phone it gets hot Sent from my HTC Rezound
dustintheweb;21090574 One thing I think would really help this thread is to set an easy to follow format for posting results. For example said: Good layout... and I think you are right about 115-120 degrees is normal for heavy use with apps that really stress the CPU or radio. thatsricci said: if it's the battery, then isn't the only parameter we need to test is current draw from the battery? no matter what radios/apps are enabled/disabled. It's bottom line is, the more we're drawing off the battery the hotter it's getting? I'd have to bring a pro in here on how Li-ion works in this form factor and why it gets hot, or what corners the battery manufacturer cut to make it possible! Click to expand... Click to collapse A pro huh... good thing I'm here. Ok I'm not a "pro" as it were, but i know a thing or too. Its not going to be simply the battery, but I think it is a big culprit, and most of these devices only provide battery temps, not CPU or internal temps, this limits our overall knowledge of what is going on internally. The battery getting hot causes the device to heat up as well so a bad battery that overheats can cause the device to overheat. All batteries will convert some energy draw into heat. This is caused by the internal resistance of the battery. Li Ion batteries have fairly low internal resistance compared to other types, but battery design an affect power output handling. Pulling more power than the battery can handle or near its limit and you get more heat than normal. The heat to output ratio stops being proportional and becomes exponential. So that means the real kicker is the actual amp draw on the battery. How much power the battery can handle is related to both the capacity of the battery and the manufacturing process/ design of the battery construction. I bet the new devices are straining the battery more than the current design can handle. There are better battery manufacture processes for better power handling, but that increases the cost of the battery. (BTW battery is a misnomer for these, they are cells, specifically one 3.7/8V Li Ion cell. The difference is that batteries are made up of 2 or more cells. This goes for AAA, AA, C and D cells as well. Car batteries for example are made of six 2V cells, 6V lantern batteries are made of four 1.5V cells and 9V batteries are six 1.5V cells) This is one reason I want to do a test with airplane mode on. This helps lower the power draw and allows us to get a better overall device temp, this helps us know if there is an issue with the CPU getting excessively hot vs just the battery being stressed to hard. Kane5581 said: One important variable missing: ambient temp. Click to expand... Click to collapse I assumed most testing would be done at room temps of 68-72 degrees. If anyone tests in temps that are much higher or lower, then that would throw off the measurements. I switched back to stock kernel, going to check for lockups and issues like I had before. Click to expand... Click to collapse
nev310 said: I noticed any time I charge with USB and use my phone it gets hot Sent from my HTC Rezound Click to expand... Click to collapse Charging always causes heat. You are forcing power into a small space. Charging via USB should only get the battery a little warm to the touch. 95* or so at most. Charging with AC should get it a few degrees higher. I would think over 100* is odd. as you reach 100% is when the heat should spike to the max temps I mentioned, before that it should just be warmish. I will check mine to see how it behaves, but all my R/C batteries behave that way.
Replacing the kernel with stock lowered my temps quite a bit. I was around 110-115 degrees after 30 minutes or so. This was with LTE enabled.
Nobody else have anything?
noticed most of my heating issues when 4g was on (even when idling on 4g). Leaving in wifi and 3g keep the stock battery cool...on the extended I never really notice the heat, even on 4g.
I realize that you're trying to keep things as similar as possible, but I had an issue today listening to the broncos game in the NFL app while charging. It got so hot it boot looped. After getting it back up and running I started monitoring battery temps and even with the screen off and just listening to the game, it would get extremely hot. Btw, I have 4G 4 bars. A couple of times I ran to the freezer and put the phone in it for a couple minutes to cool it down as the temps got above 117°F. From here, I thought it might be the CPU, so I set the maximum setting to 384 in antutu and then let the phone sit there with the screen off just as before listening to the game and still charging. Same thing, phone got extremely hot, 115°F. Although, what I find strange, is I can watch Netflix while charging and even tho it gets warm, it never gets above 115°F and never goes into the boot loop issue. Same exact location, charger, ambient temps, signal, the works. So I'm wondering if an app is just poorly written and causes some sort of excessive use of the radio. On another note, I had a rezound battery in my thunderbolt and never had any issues what so ever with heat. Sent from my ADR6425LVW using Tapatalk
What temperatures are you people expecting to see just out of curiousity? I mean if we run 3d intensive apps, videos, extreme web browsing we're going to see high temps since we are stressing the devices. We do have to remember these are compact devices and they are limited to what type of heatsinks/cooling they can add. From the multiple posts form this thread and others like it, we can see the majority of our devices run at same temps while under load. If it hasn't already been done maybe we should contact HTC and see what they say? Just a thought.
zetsumeikuro said: What temperatures are you people expecting to see just out of curiousity? I mean if we run 3d intensive apps, videos, extreme web browsing we're going to see high temps since we are stressing the devices. We do have to remember these are compact devices and they are limited to what type of heatsinks/cooling they can add. From the multiple posts form this thread and others like it, we can see the majority of our devices run at same temps while under load. If it hasn't already been done maybe we should contact HTC and see what they say? Just a thought. Click to expand... Click to collapse I am trying to find the norms and what is too hot. I am thinking 115 is normal for heavy use. But we need to be sure, if someone says they only hit 100 under similar conditions as someone that hits 120. it may be that 120 is a problem temp and that 100 is normal. It may also be that the person only hitting 100 is just lucky. tbot said: I realize that you're trying to keep things as similar as possible, but I had an issue today listening to the broncos game in the NFL app while charging. It got so hot it boot looped. After getting it back up and running I started monitoring battery temps and even with the screen off and just listening to the game, it would get extremely hot. Btw, I have 4G 4 bars. A couple of times I ran to the freezer and put the phone in it for a couple minutes to cool it down as the temps got above 117°F. From here, I thought it might be the CPU, so I set the maximum setting to 384 in antutu and then let the phone sit there with the screen off just as before listening to the game and still charging. Same thing, phone got extremely hot, 115°F. Although, what I find strange, is I can watch Netflix while charging and even tho it gets warm, it never gets above 115°F and never goes into the boot loop issue. Same exact location, charger, ambient temps, signal, the works. So I'm wondering if an app is just poorly written and causes some sort of excessive use of the radio. On another note, I had a rezound battery in my thunderbolt and never had any issues what so ever with heat. Sent from my ADR6425LVW using Tapatalk Click to expand... Click to collapse Go play an app that is heavy in 3D, lets see what temps you get. If you go much over 120 it may be an issue.
Running Gun Bros for about 20 minutes gets me up to about 105°F. Right now after the phone had been sitting for 5ish hours doing nothing its at 98°F. Sent from my ADR6425LVW using Tapatalk
I think it is Ziggy's kernel I have never got 125f when tethering for 30min or playing GTA for 30 min. I am going to try another kernel.
How does android / smartphone OS determine "battery health"?
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!
Phone slows down dramatically when less than 20% of battery
I've been experiencing this for a wile now. In the beginning, when the battery hit 10%, my Le Max 2 would get really slow, basically unusable. Now it's staring around 15%. I've tried multiple ROMs and it persists through all of them. Does anyone share this problem, or know if there's a fix to it?
joaoVi said: I've been experiencing this for a wile now. In the beginning, when the battery hit 10%, my Le Max 2 would get really slow, basically unusable. Now it's staring around 15%. I've tried multiple ROMs and it persists through all of them. Does anyone share this problem, or know if there's a fix to it? Click to expand... Click to collapse What rom do you use?
Rodcoco said: What rom do you use? Click to expand... Click to collapse I'm using Lineage OS 17.1 august 28
Heyyo @joaoVi, this is the expected behaviour as Qualcomm intended it to be. It is NOT recommended to let your battery drain below 10%. Qualcomm has a safety put in place in the kernel that disables the big cores, so that only the little cores are running. This is to try and prevent further battery wear. The safest ranges for a battery is 40% to 80%. Anything higher or lower will cause extra wear to the battery charge cycles which is why I also never recommend charging a device with a poly-lithium battery overnight, as charging it to 100% and then letting it sit at 100% causes a lot of battery wear. Linus Tech Tips has a good video on this subject too
It's winter and the 4 year old battery cannot supply enough voltage to the CPU so the big cores turn off. You can verify this behavior by CPU monitoring quick settings tile built in most ROMs It gets more difficult for a battery to supply higher energy at lower tempreatures (winter!)
Question Is my Pixel 6 Voltage figure someting to worry about?
I have a pixel 6 and noticed that my voltage figure on AccuBattery is high. Its reading as 4.3mv ?? I have no idea what ths means or if its something i should be concerned about?
I would like to know this also. I'm only observing it when I use my Motorola quick charger. It's the quickest, just powerful charger I have at the moment.
Those apps only measure battery voltage, not charger voltage.
With that said, is the number we are seeing for battery voltage something to be worried about?
chrisnewton said: I have a pixel 6 and noticed that my voltage figure on AccuBattery is high. Its reading as 4.3mv ?? I have no idea what ths means or if its something i should be concerned about? Click to expand... Click to collapse That does NOT say 4.3mv (which would indicate a bug in the program, since the phone would not power on at that low of a voltage) That says 4,318 mV, as in four thousand three hundred eighteen milli-volts, or about 4.3 V. That's a reasonable value for this kind of battery. Nothing to worry about, move along.
4.318V (which is what it is) is indeed high if you read about the max voltage Lithium Ion cells should be charged to, to maintain reasonable service life. However I have found my previous Pixels do a similar thing and Lithium chemistries can vary quite a bit so I wouldn't be too concerned. Having said that, have a look at the 'battery' thread here if you want to get maximum service life from the battery. In that case you should probably keep the charge levels in the 40-65% range in an ideal world. But at the end of the day, many folk don't care or obsess about this stuff, especially if they're replacing their phone every couple of years and/or are happy to get a battery replacement when capacity drops too far.
Different chemistry tweaks can affect the the voltage of a cell. My battery also goes that high, so I assume this is normal performance for the particular cell Google chose.