Related
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.
I ask for an opinion to experts.
I installed the app Battery Life Repair
https://play.google.com/store/apps/details?id=com.BoshBashStudios.batterydoctorrepair
I can't understand if this app is really effective or if it is a fake. In both cases, if you want to give your opinion can you justify it with technical considerations?
It's strange to see so many high ratings, but it is also strange that there are no tests or in-depth reviews.
Sorry for bringing a thread from the dead but I am also very curious as to how this app works (or if it does at all).
Such apps don't work.. They're usually fake and earn money through ads. Battery life is purely hardware and can't be increased by a software other than changing kernel features...
Sent from my Moto G
MasterAwesome said:
Such apps don't work.. They're usually fake and earn money through ads. Battery life is purely hardware and can't be increased by a software other than changing kernel features...
Sent from my Moto G
Click to expand...
Click to collapse
what a load of crap.
You can increase the length of your battery time betweeen charges by lessening the load on the cpu(which causes ups in voltage usage).
we reduce cpu load by reducing ram usage too.
also, turning the display brightness down and turning off unneeded features like bluetooth or wifi.
the kernel can be made more efficient like you said. so i agree there.
Lgrootnoob said:
what a load of crap.
You can increase the length of your battery time betweeen charges by lessening the load on the cpu(which causes ups in voltage usage).
we reduce cpu load by reducing ram usage too.
also, turning the display brightness down and turning off unneeded features like bluetooth or wifi.
the kernel can be made more efficient like you said. so i agree there.
Click to expand...
Click to collapse
Trying to do that the battery app takes more battery by being in the background always. sometimes it also steals data.. There's no point you're better of without it.
Regards
MasterAwesome
Sent from my Moto G
MasterAwesome said:
Trying to do that the battery app takes more battery by being in the background always. sometimes it also steals data.. There's no point you're better of without it.
Regards
MasterAwesome
Sent from my Moto G
Click to expand...
Click to collapse
Of course the battery does nothing.
thats what the settings > battery
function is for anyways. to see the resource hog of the system.
so it works in identifiying the problem.
but your right, the battery app is unnecessary since we already have a stock implementation.
but that wasn't my point. my point is that you can modify the userspace for more battery between charges.
Lgrootnoob said:
Of course the battery does nothing.
thats what the settings > battery
function is for anyways. to see the resource hog of the system.
so it works in identifiying the problem.
but your right, the battery app is unnecessary since we already have a stock implementation.
but that wasn't my point. my point is that you can modify the userspace for more battery between charges.
Click to expand...
Click to collapse
At the end of day we agree that battery apps are not required... Android is pretty optimized by itself.
Decrease screen brightness and timeout it takes the highest amount of battery.
Sent from my Moto G
MasterAwesome said:
At the end of day we agree that battery apps are not required... Android is pretty optimized by itself.
Decrease screen brightness and timeout it takes the highest amount of battery.
Sent from my Moto G
Click to expand...
Click to collapse
"At the end of day we agree that battery apps are not required.." obviously.
"Android is pretty optimized by itself. " its not about android(I didnt mention android being optimized, I figured that it was pretty obvious and didnt need discussion), it was about android having the tools to find the problem. see the following:
"Decrease screen brightness and timeout it takes the highest amount of battery. "and this brings me to MY POINT.
We are talking about app hogs which ARE a problem.
I would expect the OP has enough of a brain to reduce the brightness.
You have app services that use tons of ram and cpu. Why can't you accept that?
The theory behind a battery app is legitimate, but the OP just has to use the builtin android application.
Lgrootnoob said:
"At the end of day we agree that battery apps are not required.." obviously.
"Android is pretty optimized by itself. " its not about android(I didnt mention android being optimized, I figured that it was pretty obvious and didnt need discussion), it was about android having the tools to find the problem. see the following:
"Decrease screen brightness and timeout it takes the highest amount of battery. "and this brings me to MY POINT.
We are talking about app hogs which ARE a problem.
I would expect the OP has enough of a brain to reduce the brightness.
You have app services that use tons of ram and cpu. Why can't you accept that?
The theory behind a battery app is legitimate, but the OP just has to use the builtin android application.
Click to expand...
Click to collapse
Confrontation Much
The original posting he said was that software does not have impact on hardware in that it can not fix physical damage on the battery such as dead cells.
Such apps are just fake.
I purchased a new phone and same day I installed repair battery life. It showed 8 low cells and one inactive. It claimed it will increase my battery life by 18% (WOW, LOL)
After that I tried again and it showed me all green cells.
I cleared the app's cache, cleared data and uninstalled the app.
Later on, I calibrated the battery with another app called "battery fix" which needs root and deletes batterystats.bin file
I once installed "repair battery life" and guess what? It showed again 8 low cells and one inactive.
It's just another fake crAPP
Number of cells shown suggests fake.
I tried Battery Life Repair by "Extended Apps " and I remain very sceptical. Nowhere it is explained what the app actually does.
A normal Phone has one or two cells. This app shows 100 cells and claims that some are broken or damaged and the software can repair it through some extraordinary (supernatural?) process. It Claims it repaired these problematic cells (like 5 out of 100), although it physically makes no sense considering a phone has one or two cells, which are usually either working or broken. Then it also requests access to media, identity and accounts, which is suspicious given what the app claims to do.
Comments in the app-store just prove to me that placebos work. On the other hand, some people figured that if the "battery repair" is done, the app data is deleted and the app run again, it again shows the same amount of "problematic cells".
aj1789 said:
I tried Battery Life Repair by "Extended Apps " and I remain very sceptical. Nowhere it is explained what the app actually does.
A normal Phone has one or two cells. This app shows 100 cells and claims that some are broken or damaged and the software can repair it through some extraordinary (supernatural?) process. It Claims it repaired these problematic cells (like 5 out of 100), although it physically makes no sense considering a phone has one or two cells, which are usually either working or broken. Then it also requests access to media, identity and accounts, which is suspicious given what the app claims to do.
Comments in the app-store just prove to me that placebos work. On the other hand, some people figured that if the "battery repair" is done, the app data is deleted and the app run again, it again shows the same amount of "problematic cells".
Click to expand...
Click to collapse
I strongly suspected myself this app is complete bull twaddle, but I was also curious so installed it just to see what it makes of the battery "analysis".
It magically 'fixed' the problem cells, but unlike you on a subsequent retest the previously 'faulty cells' had still be 'fixed'.
I wonder how this app is polling the 'cells'? Or is it just making up some fancy graphics and not actually doing anything at all under the hood?
I also wonder what would happen if I switched batteries or took the existing one out and in again? Maybe I'll try at some point.
This is my experience.
I thought this is impossible but i installed it just to try..
In that time i first tryed it i had Galaxy 3 Apollo. Battery was so bad that percentage was going low when you were looking on it and after some short period of time phone just shutdown by itself.. I decided to try it so maybe i save money for new battery. With few shutdowns i finally did it and something happen. Battery didn't go low that way and phone stoped turning off by itself!! It could stop while i was washing dishes but it was "fixed" after i used that app, so i dont know. I don't personally think that some app can fix hardware issue but i think it works as some "refresh" or something like that. I don't know really but in my case was money saver what ever that is. Oh and i'm talking about "Extended Apps" app.. :/
I'm also skeptical about these things but unlike others in here, I tried before drawing conclusion with my awesome rational brain. And yes it works marvelous. My Galaxy Note 3 battery is working as brand new, giving 3 to 4 days without charging and it was 1 to 2 days before the app. I don't think that is placebo effect and I have absolutely no idea what the app does, and too bad the dev doesn't have a website, but the app is good. Also using the other app from the same dev, called Advanced Battery Calibrator and letting the phone charge till 100% while off did wonderful things.
I still wonder how it can fix hardware of it simply erase data from the battery increasing risk to catch on fire, but it does work.
As far as I know, the software keeps data of the battery in other to avoid charges over 100%. With time that will effectively make the battery charge till 99% then 98% and goes on, till u have a battery on 70% for example but the software say its 100%, because it wont charge more than that to avoid the risk of fire. Perhaps this app erase that data and increase the risk of mal function. But I have no idea.
douglasrac said:
I'm also skeptical about these things but unlike others in here, I tried before drawing conclusion with my awesome rational brain. And yes it works marvelous. My Galaxy Note 3 battery is working as brand new, giving 3 to 4 days without charging and it was 1 to 2 days before the app. I don't think that is placebo effect and I have absolutely no idea what the app does, and too bad the dev doesn't have a website, but the app is good. Also using the other app from the same dev, called Advanced Battery Calibrator and letting the phone charge till 100% while off did wonderful things.
I still wonder how it can fix hardware of it simply erase data from the battery increasing risk to catch on fire, but it does work.
As far as I know, the software keeps data of the battery in other to avoid charges over 100%. With time that will effectively make the battery charge till 99% then 98% and goes on, till u have a battery on 70% for example but the software say its 100%, because it wont charge more than that to avoid the risk of fire. Perhaps this app erase that data and increase the risk of mal function. But I have no idea.
Click to expand...
Click to collapse
If your battery has dead cells im sorry but no app will fix it, unless its magic! It must replace the cells somehow magically! Omg do some basic research these apps are fake garbage! Maybe it can fix my dead s3 battery hahaha NOT!
hilla_killa said:
If your battery has dead cells im sorry but no app will fix it, unless its magic! It must replace the cells somehow magically! Omg do some basic research these apps are fake garbage! Maybe it can fix my dead s3 battery hahaha NOT!
Click to expand...
Click to collapse
ofc is not gona revive a battery,but even that it can be made,in some cases,i saw that of ppl proving that live,they took a dead battery and test it to show that it is dead and just used another same model battery that it was working and hold them connected like 5 min toghether,after that it just put the dead battery at charged and what u know?it did revived it,no idea how the battery actually work,but it seems that they can actually get stuck somehow and they can get a "forced" revive,like a CPR for humans,but like i said,not working with all,same as like on humans,not all can be revived with CPR,but i guess that this app has to do something coz like some in here i did used it and ... the magic worked,not on a dead battery,so scheptical as it sounds,on some batteries it works even tho maybe is not something hardware but maybe just something software,why i say that,i had a tablet and a few times when i was restarting the tablet,after a min was turning off coz of battery 0%,and that after i got the recharger plug off,so it was 100% for sure,after a few times restarting the tablet it was showing again 100 % as it should be,so i guess that not even android is always reading the data correctly
Of course is a full fake. Uninstall them, becouse they can do bitcoin mining or whatever gain trough pupup and promotions., as well as getting your data.
1) Ion litium or polymer batteries cannot be repaired.
2) cells are 1 or max 4 not 256 as those apps shows
3) clearing the cache brings different fault cells
4) reinastalling shows other broken cells
5) strangely the application after "repair" stays open in background. So at least the word "repair" is a joke fooling people.
6) dynamic ram and ddr are always powered and refresh cycles are required in all the address space generally, so saying that freeing ram allow more battery duration is a fake.
7) whatever the app does to have battery least more is just sw and tricky. I would not rely on that and remove the app.
Wow...
MasterAwesome did u disable Lgrootnoob's account because it says its disabled was it because he challenged ur opinion? lol childish much? Who cares if it works it either works or it doesnt I dont see it hurting me
---------- Post added at 07:50 AM ---------- Previous post was at 07:47 AM ----------
Crazydan360 said:
MasterAwesome did u disable Lgrootnoob's account because it says its disabled was it because he challenged ur opinion? lol childish much? Who cares if it works it either works or it doesnt I dont see it hurting me
Click to expand...
Click to collapse
Didnt notice this was my brothers account he uses my phone
Hello, there's a way to calibrate your battery without root.
to calibrate your battery, i found by my self a way to(when i did it, the battery time left was increased):
1)charge your phone to 100% battery.
2)turn on- wifi, auto rotation, bluetooth...(everything that is consuming battery not including apps)
3)leave your phone with screen off.
4)discharge much as you can.
5)when you finished, charge your phone and don't use the phone.
optional:
if you want a proof that this is worked- open settings and see how much time left for your battery(you will see that it had been increased).
FYI I just finished testing Battery Life Repair 2018 by running it on a new Android tablet with a huge 8000+mAh battery. It reported about 14 weak or bad cells out of a total of 120 cells. When told to fix those cells, it requests you to download another of their apps to help support them. Just say YES, then kick back out without downloading and the fix finishes. I had hardware "USB Safety Tester" connected during this test (it displays various info including the charging voltage and amperage). With about 12% of the cells reported bad, after the fix the Tester recorded zero increase in Volts or Amps. So it maintained a steady watt draw from the charger even after 14 more cells were now drawing watts to charge. Next I cleared storage on the app, ran it again, and got 12 different cells reported to have problems. Fixed those cells, and again, no change in charge draw.
I also found it strange that it would use WIFI and Cell Data and run in the background. Why?
The Battery Life Repair app reports that my Galaxy S5 also has 120 cells in its battery. Seeing as almost 99% of phones and tables have a SINGLE cell in their battery (one or two phones have 2 cells), the display of a 120 cell grid seems rather fishy. Having a 120 cell battery requires cell balancing hardware and software that that would add to the cost of the phone, plus make the battery physically larger. My electric bike has about 80-90 cells in it and it weighs about 15lbs and is 30,000 mAh and 47 volts. Hard to do in one or two cells. That is a good example of why a multi cell (3.6 v each?) battery is needed. But not a cell phone or tablet.
I know my test is not the most scientific, but at least I did check for a change in wattage draw before and after fixing cells, and not just ecstatically claim my battery has improved.
So I call Battery Repair Life 2018 to be a steaming pile of BS that is probably robbing you of your contacts and other personal information while running in the background sucking up your data plan. But, hey, that's just me.
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
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.
Hello everyone what is the actual battery size in your brand new phone?
One way to check is to see the value of the charge counter in aida64 when the phone is at 100%.
My unit has 4785 mAh. Which is 95.7% of the advertised 5000 mAh value.
At which point does it become false advertising?
Should Samsung say this is really a 4800 mAh cell (if it is one, or my unit has a smaller capacity)?
Go to Settings>About Phone>Battery Information. You will find that Samsung rates it at 4855 mAh.
JoraForever said:
At which point does it become false advertising?
Click to expand...
Click to collapse
What makes you trust 3rd party apps so much, and so easily?
High storage temperatures and voltages can degrade Li's. I wouldn't worry about it, but replace it when it drops below about 4000 mAh capacity.
TheMystic said:
What makes you trust 3rd party apps so much, and so easily?
Click to expand...
Click to collapse
The number aida64 gives is not created by it.
That number is created by the android system.
You can use other apps to view the same system variable.
I believe it is accurate because the system can measure battery drain very accurately.
Battery capacity is the integral of the battery drain measurements, which the system does automatically.
JoraForever said:
The number aida64 gives is not created by it.
That number is created by the android system.
You can use other apps to view the same system variable.
I believe it is accurate because the system can measure battery drain very accurately.
Battery capacity is the integral of the battery drain measurements, which the system does automatically.
Click to expand...
Click to collapse
This assumes the sensors and algorithms used are accurate... they may not be.
blackhawk said:
This assumes the sensors and algorithms used are accurate... they may not be.
Click to expand...
Click to collapse
Why wouldn't those be? Measuring current/voltage is one of the things electronics do best.
Innacurate algorithms? What is this 2007?
blackhawk said:
High storage temperatures and voltages can degrade Li's. I wouldn't worry about it, but replace it when it drops below about 4000 mAh capacity.
Click to expand...
Click to collapse
This is just a question of the difference between 'Typical capacity' and 'Rated capacity'. This being a brand new device, with battery health expected at 100%, it is too early for the battery to see any sort of degradation just yet.
JoraForever said:
The number aida64 gives is not created by it.
That number is created by the android system.
You can use other apps to view the same system variable.
I believe it is accurate because the system can measure battery drain very accurately.
Battery capacity is the integral of the battery drain measurements, which the system does automatically.
Click to expand...
Click to collapse
3rd party apps often do not have access to all data to give you 100% accurate information. They often use some calculations using available information.
As an example, you can try other 3rd party apps and I won't be surprised if they all report slightly different numbers. I always see this happen to storage analyser apps. Each one reports a different value for a particular type/ category of files.
The point is this:
Every unit in the manufacturing process is slightly different from each other, and no two units are absolutely identical.
Rated capacity is the minimum expected capacity of the battery, which Samsung itself says is about 4,855 mAh.
Typical capacity is the average seen among all units in the manufacturing process, and that is about 5,000 mAh.
Depending on the number of charge cycles, the ambient temperature, the battery temperature, etc. this value will keep changing every time you actually measure it, although the differences would be marginal.
A Fun Fact
I stopped using 3rd party apps that reported stats to me after a highly popular app reported high temperature when the phone was cold to touch, and reported low temperature when the phone was actually warm to touch. I trusted my instincts based on how it felt to the touch than what an app reported. Needless to say, I uninstalled it.
My experience with my phone improved significantly once I stopped bothering with too many stats.
JoraForever said:
Why wouldn't those be? Measuring current/voltage is one of the things electronics do best.
Innacurate algorithms? What is this 2007?
Click to expand...
Click to collapse
It could be a defective component. Samsung is always in a big bad hurry and makes mistakes as does Gookill Android. Return it if it bothers you. Otherwise what I said to begin with.
TheMystic said:
This is just a question of the difference between 'Typical capacity' and 'Rated capacity'. This being a brand new device, with battery health expected at 100%, it is too early for the battery to see any sort of degradation just yet.
Click to expand...
Click to collapse
Li's start to degrade the moment they're assembled, born to die. How they are stored makes a big difference in how much they degrade; one over temperature event at high cell voltage can noticeably degrade them.
Regardless time itself kills them.
blackhawk said:
It could be a defective component. Samsung is always in a big bad hurry and makes mistakes as does Gookill Android. Return it if it bothers you. Otherwise what I said to begin with.
Click to expand...
Click to collapse
This is exactly why i'm asking this question, I wonder what is the real battery capacity of other users.
blackhawk said:
Li's start to degrade the moment they're assembled, born to die. How they are stored makes a big difference in how much they degrade; one over temperature event at high cell voltage can noticeably degrade them.
Regardless time itself kills them.
Click to expand...
Click to collapse
That's true. But the S23 series wouldn't have lost about 4% battery health so soon (this isn't a display unit). OP is placing over reliance on the values reported by a 3rd party app, which itself is questionable to begin with. He just assumes it to be true, which it need not be.
TheMystic said:
This is just a question of the difference between 'Typical capacity' and 'Rated capacity'. This being a brand new device, with battery health expected at 100%, it is too early for the battery to see any sort of degradation just yet.
3rd party apps often do not have access to all data to give you 100% accurate information. They often use some calculations using available information.
As an example, you can try other 3rd party apps and I won't be surprised if they all report slightly different numbers. I always see this happen to storage analyser apps. Each one reports a different value for a particular type/ category of files.
The point is this:
Every unit in the manufacturing process is slightly different from each other, and no two units are absolutely identical.
Rated capacity is the minimum expected capacity of the battery, which Samsung itself says is about 4,855 mAh.
Typical capacity is the average seen among all units in the manufacturing process, and that is about 5,000 mAh.
Depending on the number of charge cycles, the ambient temperature, the battery temperature, etc. this value will keep changing every time you actually measure it, although the differences would be marginal.
A Fun Fact
I stopped using 3rd party apps that reported stats to me after a highly popular app reported high temperature when the phone was cold to touch, and reported low temperature when the phone was actually warm to touch. I trusted my instincts based on how it felt to the touch than what an app reported. Needless to say, I uninstalled it.
My experience with my phone improved significantly once I stopped bothering with too many stats.
Click to expand...
Click to collapse
Measuring Device Power | Android Open Source Project
source.android.com
This is literally the data the os provides with an API.
I'm not worried about my phone, i'm just asking what are the capacities that other users really see.
If what samsung says it's true, then there should be as many 5200 mAh brand new phones as 4800 mAh phones, i'm just wondering if there are actually people with more or close to 5000 mAh.
TheMystic said:
That's true. But the S23 series wouldn't have lost about 4% battery health so soon (this isn't a display unit). OP is placing over reliance on the values reported by a 3rd party app, which itself is questionable to begin with. He just assumes it to be true, which it need not be.
Click to expand...
Click to collapse
I wouldn't worry about it. Otherwise it opens a big can of worms.
Returning it is the only other sane option. At this price point I wouldn't hesitate to do so. I'm not pleased with this model to begin with. Lol, I'd go for a cash refund...
JoraForever said:
I'm not worried about my phone, i'm just asking what are the capacities that other users really see.
Click to expand...
Click to collapse
JoraForever said:
At which point does it become false advertising?
Click to expand...
Click to collapse
The numbers reported for each device would be slightly different. This isn't false advertising.
blackhawk said:
Returning it is the only other sane option.
Click to expand...
Click to collapse
There is absolutely no need for it.
blackhawk said:
I'm not pleased with this model to begin with. Lol, I'd go for a cash refund...
Click to expand...
Click to collapse
You have other reasons...and I don't agree with those...
JoraForever said:
This is exactly why i'm asking this question, I wonder what is the real battery capacity of other users.
Click to expand...
Click to collapse
Mine is between 5000-5100. I use accubattery. Do not unplug for around 30 min after your phone reaches %100, because it keeps charging even if it hits %100.
Kfatih said:
Mine is between 5000-5100. I use accubattery. Do not unplug for around 30 min after your phone reaches %100, because it keeps charging even if it hits %100.
Click to expand...
Click to collapse
What's your top voltage?
blackhawk said:
What's your top voltage?
Click to expand...
Click to collapse
4.45
Been using for2 months
JoraForever said:
Measuring Device Power | Android Open Source Project
source.android.com
This is literally the data the os provides with an API.
I'm not worried about my phone, i'm just asking what are the capacities that other users really see.
If what samsung says it's true, then there should be as many 5200 mAh brand new phones as 4800 mAh phones, i'm just wondering if there are actually people with more or close to 5000 mAh.
Click to expand...
Click to collapse
Testing now. I'll report back in about an hour once the phone is fully charged. Battery Guru is reporting 5015mAh as an estimate based on my charging history but I don't usually let it trickle to full after it shows 100% so that's likely on the lower side.
It's amusing to me that people believe that AIDA64 would be reporting incorrect info when it's one of the most respected desktop applications for system info. I opened up the battery screen and plugged it in and everything it's reporting there is the same as the phone itself reports, right down to the remaining time before it's fully charged and the battery temperature matches Battery Guru too.