I was able to find a workaround for the battery percentage:
1. FIRST Get your battery capacity!!!
$ adb shell cat /sys/class/power_supply/battery/batt_capacity_max
800
2. Calculate your 100%
800 * 1.2 = 960
3a. Charge battery fully (UI will say 80%):
Use your new 100% value in place of my 960!!
adb shell
$ su
# echo 960 > /sys/class/power_supply/battery/batt_capacity_max
3b. To revert back (and see actual %):
put your old value in place of my 800 here
adb shell
$ su
# echo 800 > /sys/class/power_supply/battery/batt_capacity_max
Warning:
This is not persistent across reboots (but could be implemented as such)
This does not change the fact that your battery meter will say 80%
This confuses your phone into thinking the 80% limit is higher than it actually is
This could be harmful to your battery life, battery condition, and battery operation
The Control Chip on the battery itself should prevent any unnecessary charging from occurring
I'm just a guy on the internet, don't mess with your phone unless your are willing to pay for any mistakes.
How this works:
The Kernel reads the battery percentage from /sys/class/power_supply/battery/capacity
We make the maximum battery capacity increase by 20% /sys/class/power_supply/battery/batt_capacity_max (the commands above)
Kernel reads the battery percentage from /sys/class/power_supply/battery/capacity again and its now 20% lower because of capacity calculations (percentage = used capacity / batt_capacity_max)
Kernel lets the charging continue to 80% which is in actuality 100%
FAQ
Does this work?
Yes this works. The explanation is above. Succinctly, these commands trick your kernel into thinking the 80% limit is at 100% of the battery.
Shouldn't we be adding 25% to reach 100% of the battery?
While this is correct, I tested a few percentages and noted that 20% increase will reach 99% battery on my phone. This does not mean it will for everyone. PLEASE BE COGNIZANT OF OVERCHARGING
This isn't working for me, why do the values change?
You must be a superuser in the terminal for these commands to stick. They do not stick across reboots.
This still doesn't work, wah wah wah. I wan't 100%...
I am trying to help the community. If you don't want help you can keep the 80% charge. Multiple people have said it works. If you don't want to try it don't. Blindly saying it doesn't work is only poisoning the well.
Video Guide:
Setting Battery Maximum Past 80%
https://youtu.be/dEdmIDEKYtA
Setting Battery Maximum Back to Original
https://youtu.be/TDirEoSsSkk
But does it actually go to 100?
If you do step 3b after you charge to 80% it will change to say 100%.
Steps 1,2,3a will bring you to 100% charge physically; almost as if the battery meter was designed to go 0-80
Note: this charges to your battery maximum (regardless of what percentage it says)
nm1557 said:
If you do step 3b after you charge to 80% it will change to say 100%.
Steps 1,2,3a will bring you to 100% charge physically; almost as if the battery meter was designed to go 0-80
Note: this charges to your battery maximum (regardless of what percentage it says)
Click to expand...
Click to collapse
interesting, anyway to keep it persistent?
nm1557 said:
2. Calculate your 100%
800 * 1.2 = 960
Click to expand...
Click to collapse
That's 96%, multiply it by 25 to get 100%.
Hmm the original file says 948 though, strange.
peachpuff said:
That's 96%, multiply it by 25 to get 100%.
Hmm the original file says 948 though, strange.
Click to expand...
Click to collapse
Yours may be different. It's based off your battery stats. And it should only be 20% increase.
fever308 said:
interesting, anyway to keep it persistent?
Click to expand...
Click to collapse
Write a shell script that runs on start.
This is a verbose way to do this, I am looking into a better way to get around the kernel.
nm1557 said:
And it should only be 20% increase.
Click to expand...
Click to collapse
Yes but you're multiplying 20% of 80 which is incorrect, that only gives you 96% not 100%.
If you subtract 20% from 1000 you get 800, but when you add 20% to 800 its 960, get it?
peachpuff said:
Yes but you're multiplying 20% of 80 which is incorrect, that only gives you 96% not 100%.
If you subtract 20% from 1000 you get 800, but when you add 20% to 800 its 960, get it?
Click to expand...
Click to collapse
That's the thing, The 800 value has nothing to do with percentage. It's variable across devices and its coincidence thats its 800.
So is it really 100 or just the image of it
Rally517 said:
So is it really 100 or just the image of it
Click to expand...
Click to collapse
It really is 100%.
Hmmm. Have you battery life changed in any way? Just got me excited
i bit the bullet on this and went for it. everything seems to be fine so far. my max_batt_capacity value was 885, so 100% would be 1062, however, i backed it off to 1000, just to be safe. will update after tomorrow.
If A is the number we want the phone to charge the battery to, and the phone stops charging at 80% of A, the number we need to set A to is A * 1.25 , not A * 1.2
So, if the original number is 800, we need to set it to 1000, since the phone will calculate 80% of 1000 to allow it to be charged until 800.
Does that make sense?
So you are effectively increasing the battery capacity of an s8 by 600 mah and s8+ by 700 mah? Am I understanding this thread correctly? If so this seems like a huge problem waiting to happen.
tommyg562000 said:
So you are effectively increasing the battery capacity of an s8 by 600 mah and s8+ by 700 mah? Am I understanding this thread correctly? If so this seems like a huge problem waiting to happen.
Click to expand...
Click to collapse
no, this is a work around after using the SAMpwned root method, which caps the battery life at 80% of max.
Lol I have a feeling we are gonna see some batteries exploding again, lol
Sent from my SM-G955U using Tapatalk
I'm still on the stock rom and unrooted and the stock valve in the batt_capacity_max file is 990
great find! i figured it had something to do with that file but wasnt sure how it was calculated as mine says 1000 but others was different lol..
but our idea was if this was in fact the case that you create an init.d script that runs on each boot that will automagically correct it each time you reboot the phone
---------- Post added at 07:35 AM ---------- Previous post was at 07:34 AM ----------
to add, this is also why we releaeed it as is, we figured someone in the community would figure it out!
thanks again!
---------- Post added at 08:26 AM ---------- Previous post was at 07:35 AM ----------
actually, changing that file instantly changes back to its original setting for me
One thing that I didn't get.
Okay, the phone will think the maximum is 1000 and will try to charge the battery up to 800, which is the real target. Great.
The screenshot, though, shows the indicator on the notification bar close to 100%, in the rooted phone.
So, the routine that checks the phone charge and limits it to 80% is independent from the check embedded on the indicator charge, right? Otherwise the indicator would never reach 100% even on the rooted phone, and even though the battery was actually 100% charged.
Related
I used this method to get a reading
-> download from Market 2 widgets, if you haven't already, they are CurrentWidget and Brightness Level by CurveFish http://curvefish.com/widgets/brightness-level.htm
..Both are well popular and free widgets...
->Put them on the same desktop.
-> Wait for the CPU to "settle down processing", about half a minute + have your phone resting on a steady surface.
-> Choose 0% brightness, wait 15 seconds and tap "update now" on CurrentWidget -> tap it once or twice more to make sure it registers the ~same value.
-> Repeat this for brightness of 25%, 50%, 75% and 100%.
After posting it please just name your Model number and what ROM, Kernel you are using. If u are feeling lazy, just do the 0 - 50 and 100% brightness measurements...
These are mine stats:
0% display brightness - 96mA
25 % display brightness - 110 mA
50% - 148mA
75% - 184mA
100% - 230mA
Phone is S510e, stock rom and stock kernel.
_______________________________________
The reason I am posting this is mainly because my "Battery status and level" reports stats like this: 15 hours of battery time since charge, 10 of which on standby, and 5 hours with me doing something with the phone on 30% screen brightness...Display consumption for this is 82% ..
And ofc, in my opinion, a very bad battery life due to this overall.
The more people do this the better, we will see what really is going on... If you have any other battery related stats or experiences, pls post here too..Thx!
P.S. CurrentWidget logs 11 to 14 mA in locked mode...
I'd also suggest that you also download and use BATTERY MONITOR WIDGET application as well as current widget, the two widgets do the same thing but I believe that BMW clocks very different (and in my opinion correct figures) which are slightly lower 5-8mA screen off compared to 10-12mA.
Can you tell me your stats Ben?
Bombastc said:
Can you tell me your stats Ben?
Click to expand...
Click to collapse
I believe that my system is configured for efficient for battery usage.
Auto Sync = OFF
Wi-Fi = ON
Mobile Data = OFF
These are my results using Battery Monitor Widget
I ignored the first reading after the brightness widget was operated and the level was changed so that the system had an opportunity to stabilize and then picked the next two readings, with a sample rate of 30secs apart.
% - mA
0% - 47/46 mA
25% - 62/61 mA
50% - 89/92 mA
75% - 97/98 mA
100% - 108/107 mA
Thanks
ben_pyett said:
I believe that my system is configured for efficient for battery usage.
Auto Sync = OFF
Wi-Fi = ON
Mobile Data = OFF
These are my results using Battery Monitor Widget
I ignored the first reading after the brightness widget was operated and the level was changed so that the system had an opportunity to stabilize and then picked the next two readings, with a sample rate of 30secs apart.
% - mA
0% - 47/46 mA
25% - 62/61 mA
50% - 89/92 mA
75% - 97/98 mA
100% - 108/107 mA
Thanks
Click to expand...
Click to collapse
Thx Ben! Spread is pretty much equal from 0% to 100%. 100% wastes times 2.3 more amperage then 0% brghtnss..Crazy thing is that currentWidget shows douple the amperage in comparison to your widget . But I have read your threads on this subject and it seems that it is more correct...
Btw..I have also offed mobile and syncing and left wifi on during measuring.
CurrentWidget does seem to report twice the amps of Battery Monitor. I am not sure of the exact reason for that.
If you prefer current widget there is a setting that allows for a "Custom Operation" to be performed on the current value. I adjusted this setting so "operation type" is "divide" and "operation value" is "2", which gives me to get the same current numbers as the Battery Monitor Widget.
ben_pyett said:
I believe that my system is configured for efficient for battery usage.
Auto Sync = OFF
Wi-Fi = ON
Mobile Data = OFF
These are my results using Battery Monitor Widget
I ignored the first reading after the brightness widget was operated and the level was changed so that the system had an opportunity to stabilize and then picked the next two readings, with a sample rate of 30secs apart.
% - mA
0% - 47/46 mA
25% - 62/61 mA
50% - 89/92 mA
75% - 97/98 mA
100% - 108/107 mA
Thanks
Click to expand...
Click to collapse
Those values are WAY too high! At 0% brightness mine sits at a comfortable 18-20mA (dependant on WiFi operation).
At 100% brightness, mine sits at 87mA (again, fluctuates 1 or 2 mA dependant on WiFi operation).
LaKraven said:
Those values are WAY too high! At 0% brightness mine sits at a comfortable 18-20mA (dependant on WiFi operation).
At 100% brightness, mine sits at 87mA (again, fluctuates 1 or 2 mA dependant on WiFi operation).
Click to expand...
Click to collapse
I take it you run cm7? And that those results were obtained with BMW?
So that's the different a sense ROM makes..
Swyped from HTC Desire S using XDA Premium
ben_pyett said:
I take it you run cm7? And that those results were obtained with BMW?
So that's the different a sense ROM makes..
Swyped from HTC Desire S using XDA Premium
Click to expand...
Click to collapse
Yes and yes!
You guys aren't doing anything stupid like running a Live Wallpaper when testing, are you? I'm fairly sure you aren't, but I have to ask!
100+mA for 100% brightness on the display is frankly abysmal! I mean, my Motorola Xoom manages less than that (actually the Xoom eats far less power than any other Android device I've come across, by a HUGE margin... hence why I need only charge it once a week at most, even though it's powered on with WiFi running 24/7)
Yes, Sense is a battery hog! It's why my guide on maximum battery runtime explicity recommends ridding yourself of it entirely!
As bad as Sense 2 is on the stock ROM, Sense 3 is at least 25% worse (from my experience with several Sense 3 ROMs, anyway)!
Why don't mobile manufacturer's focus on what really matters: longevity of uninterrupted, AC-free (I.E. battery) runtime?
Phones have already reached the necessary performance mark! We don't need hex-core 9001GHz CPUs in phones... we need a phone that'll run for more than a day between recharges!
Hell, I'd happily accept the Desire S being TWICE the thickness, if it meant double the battery runtime!
If you're reading this HTC (which I severely doubt).... why not make a "Fatboy" range of your current mobile offerings? I'd buy a "HTC Desire F" or a "HTC Sensation F" if you could guarantee more than a day of runtime under typical bench conditions! I bet many others would too!
LaKraven said:
Yes and yes,
If you're reading this HTC (which I severely doubt).... why not make a "Fatboy" range of your current mobile offerings? I'd buy a "HTC Desire F" or a "HTC Sensation F" if you could guarantee more than a day of runtime under typical bench conditions! I bet many others would too!
Click to expand...
Click to collapse
LOL, HTC fatboy....
no live wallpaper here, and every battery consuming option off...
As time progresses and the non Sense ROMs improve and become stable I do become more and more tempted to make the switch......
I tried this with CurrentWidget (divide by 2 option enabled). wifi on, data off, sync off. 30s apart readings like ben_pyett.
0 - 42/45
25 - 56/54
50 - 69/72
75 - 87/89
100 - 109/106
I have CM7.1 & Tiamat 1.1.2. I have also gone through LaKraven's battery minimisation how-to (except for any Tasker steps). I don't get numbers like him though. Maybe my stock radio is a contributing factor.
Should point out that my readings are taken in a GSM "notspot" (no mobile reception of any kind) and I'm running a modification to drastically increase the polling interval when the signal is unavailable.
This means that I get spikes on the GSM (which I ignore when taking measurements as I meter the GSM drain separately).
Even so, even with GSM on, I still think that 100+ mA for screen at 100% is higher than it's supposed to be! As I say, my Motorola Xoom doesn't even use 100mA for its 10.1" display at max bright (in fact, the Xoom's biggest battery drain is its CPU, followed closely by the WiFi radio)
EDIT: To match my measurement method, use Airplane Mode to cut out all the radios (leaving only the screen and CPU consumption to meter).
Right now, screen at 100% (button backlight off)... 87mA
Button backlight on... 106mA (there's the ambiguity!)
LaKraven said:
EDIT: To match my measurement method, use Airplane Mode to cut out all the radios (leaving only the screen and CPU consumption
Right now, screen at 100% (button backlight off)... 87mA
Button backlight on... 106mA (there's the ambiguity!)
Click to expand...
Click to collapse
this method isn't possible as There is an issue on most roms certainly all sense ROMs where by air plane mode uses over five times the battery consumption than just leaving phone on, which is madness, but true
Swyped from HTC Desire S using XDA Premium
ben_pyett said:
this method isn't possible as There is an issue on most roms certainly all sense ROMs where by air plane mode uses over five times the battery consumption than just leaving phone on, which is madness, but true
Swyped from HTC Desire S using XDA Premium
Click to expand...
Click to collapse
Let me put it this way...
Display switched off... GSM chip (no signal area) switched on = 47mA drain
Display switched off... Airplane mode = 2mA drain
Not sure why others are reporting that airplane mode is drawing more power... you using a custom Radio by any chance?
LaKraven said:
Let me put it this way...
Display switched off... GSM chip (no signal area) switched on = 47mA drain
Display switched off... Airplane mode = 2mA drain
Not sure why others are reporting that airplane mode is drawing more power... you using a custom Radio by any chance?
Click to expand...
Click to collapse
We'll I might be at the moment, but, that's certainly not the problem, as I've tried all of the RADIOs that we have available to us and the problem is always there, the air plane battery drain issue has been previously been noted in several threads and the conclusion drawn so far is that its either a STOCK kernel or a STOCK ROM issue....which is the reason why you don't get it I imagine!
Evidence like that certainly sway the balance of the scales in CM's favour!
EDIT: Just realized I've used a couple of custom kernels (MDJ & UNITY V2) and the problem still existed.
Any idea if your Kernel would function on my sense ROM? I don't think it would unfortunately.....just to test the theory....
ben_pyett said:
We'll I might be at the moment, but, that's certainly not the problem, as I've tried all of the RADIOs that we have available to us and the problem is always there, the air plane battery drain issue has been previously been noted in several threads and the conclusion drawn so far is that its either a STOCK kernel or a STOCK ROM issue....which is the reason why you don't get it I imagine!
Evidence like that certainly sway the balance of the scales in CM's favour!
EDIT: Just realized I've used a couple of custom kernels (MDJ & UNITY V2) and the problem still existed.
Any idea if your Kernel would function on my sense ROM? I don't think it would unfortunately.....just to test the theory....
Click to expand...
Click to collapse
I'm running the Tiamat Kernel (http://tiamat-dev.com/tiamat_saga/)! It has enabled me to get my phones batteries to last.... a gobsmackingly long time!
LaKraven said:
I'm running the Tiamat Kernel (http://tiamat-dev.com/tiamat_saga/)! It has enabled me to get my phones batteries to last.... a gobsmackingly long time!
Click to expand...
Click to collapse
I tried your kernel (which I know isn't built for Sense based ROMS) unfortunately it had some intermittent issues with wifi (in that wi-fi worked fine to start with then I just couldn't get any joy from it) I didn't do a full test but the phone signal seemed fine.
With your kernel (Tiamat_Saga-v1.1.2) rather than the HTC stock (build 1.48.707.1) Airplane Mode = 18mA which I appreciate isn't exactly great, but, it's less than half of what it normally consumes (38mA) on a Sense ROM.
I'm not quite sure what that proves, but it's progress at least!
I faced some problems with ICS. Heavy Battery draining......
So I found a solution to that problem...
http://forum.xda-developers.com/showthread.php?t=1861229
The device needs to be at rest (turned off) for at least an hour when its empty and then when it charged back. This will let chip to make 2 open circuit voltage measurements.
How to make sure that device is discharged enough for calibration to take the place? If capacity is off big time then gauge may report SOC 30% but in the fact battery is in 70%, so chip will not execute calibration procedure.
The most sure way to check this is in terminal, execute this command:
cat /sys/class/power_supply/battery/voltage_now
or through adb:
adb shell cat /sys/class/power_supply/battery/voltage_now
your good discharged start point should be anything below 3700 (3.7V). If your device is telling that you have 0% capacity but voltage is more then 3700 then keep rebooting the device (this will refresh counter for a moment) or just boot in CWM and let device run/sit there for some time.
Then charge it with power adapter to 100%, you can check voltage at this point - should be around 4100, usually you should be good.
Then shutdown the device for another hour or two.
That's it. You should be good now unless you are still using certain custom kernels.
Simple method...::
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down the device and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours, full charge (90+%)...
4. disconnect the charger and let it sit for 1 hour in idle (shutdown state or in cwm). (this is needed for the second measurement)
5. boot up the device and test it, if your battery is still not calibrated you can flash back your backup and repeat calibration procedure.
But for me Compared to GB in ICS Battery drain is less, i am on Leaked ICS with Ardatdat's kernel and Pankaj's Deodexed ROM ...
Sorry for being a noob, but could you kindly explain what is terminal and how to use it?
boulder96 said:
Sorry for being a noob, but could you kindly explain what is terminal and how to use it?
Click to expand...
Click to collapse
Here, terminal in linux/android is just like command prompt in windows... Search for terminal emulator in play store... And google for further information...
Sent from my GT-I9103 using xda app-developers app
mj.vikram said:
But for me Compared to GB in ICS Battery drain is less, i am on Leaked ICS with Ardatdat's kernel and Pankaj's Deodexed ROM ...
Click to expand...
Click to collapse
You are lucky... My battery drained in 6 hours with no use... But.. When I callibrated by above method... I got more than a day... At the end of the day... I had 30% still left....:beer::thumbup:
Sent from my GT-I9103 using xda app-developers app
Even if anyone does feel that.. He is getting good backup...
He should at least check the full charge voltage and zero charge voltage of battery to get confirmed that the battery is properly callibrated in your device...
You can check the voltage by following simple adb/emulator command as shown above....
Sent from my GT-I9103 using xda app-developers app
bhargav143 said:
I faced some problems with ICS. Heavy Battery draining......
So I found a solution to that problem...
http://forum.xda-developers.com/showthread.php?t=1861229
The device needs to be at rest (turned off) for at least an hour when its empty and then when it charged back. This will let chip to make 2 open circuit voltage measurements.
How to make sure that device is discharged enough for calibration to take the place? If capacity is off big time then gauge may report SOC 30% but in the fact battery is in 70%, so chip will not execute calibration procedure.
The most sure way to check this is in terminal, execute this command:
cat /sys/class/power_supply/battery/voltage_now
or through adb:
adb shell cat /sys/class/power_supply/battery/voltage_now
your good discharged start point should be anything below 3700 (3.7V). If your device is telling that you have 0% capacity but voltage is more then 3700 then keep rebooting the device (this will refresh counter for a moment) or just boot in CWM and let device run/sit there for some time.
Then charge it with power adapter to 100%, you can check voltage at this point - should be around 4100, usually you should be good.
Then shutdown the device for another hour or two.
That's it. You should be good now unless you are still using certain custom kernels.
Simple method...::
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down the device and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up the device and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
Click to expand...
Click to collapse
Than you!! I'll try it ASAP. My battery doesn't resist 1 day of normal use.
Enviado desde mi GT-I9103 usando Tapatalk 2
My battery dies just after 6h of light-moderate usage. 3h music, 3h internet
Going to calibrated it tmmrw
boulder96 said:
My battery dies just after 6h of light-moderate usage. 3h music, 3h internet
Going to calibrated it tmmrw
Click to expand...
Click to collapse
I think this method should help your device....
Sent from my GT-I9103 using xda app-developers app
I dont get it, should I drain the battery as much as i can and then start it in cwm? How can I check the voltage in cwm?
solhasse said:
I dont get it, should I drain the battery as much as i can and then start it in cwm? How can I check the voltage in cwm?
Click to expand...
Click to collapse
Yup...
1.Drain it as low as possible....
2.Keep it off for an hour....
3.Charge it full...
4.Keep it off for another hour...
Measure the voltages while in CWM via your computer connected in usb mode with the galaxy r...
Use adb and put the command....
adb shell cat /sys/class/power_supply/battery/voltage_now
It will give you the current voltage...
With full charge the voltage should be around 4100mv..(milli volt)...
And with empty charge it should be at least less than 3700mv...
Sent from my GT-I9103 using xda app-developers app
I accidentally drained my battery to 3250mv. But then I charged it to 100% which was around 4180mv. Still testing battery life
I discharge my phone till 1% and it's voltage says 3380 mV .... is it normal ?? do I need to follow procedure suggested ??
PS: I know it is given it should be less than 3700mV but wondering if 3380mV is too low / any problem ??
ashvyas said:
I discharge my phone till 1% and it's voltage says 3380 mV .... is it normal ?? do I need to follow procedure suggested ??
PS: I know it is given it should be less than 3700mV but wondering if 3380mV is too low / any problem ??
Click to expand...
Click to collapse
At 0% its supposed to be around 3400mv. So I would say it's fine.
Sidenote: I accidentally thanked you when I wanted to press reply
boulder96 said:
At 0% its supposed to be around 3400mv. So I would say it's fine.
Click to expand...
Click to collapse
thanks
Sidenote: I accidentally thanked you when I wanted to press reply
Click to expand...
Click to collapse
that's cool , you are welcome for such mistakes
boulder96 said:
I accidentally drained my battery to 3250mv. But then I charged it to 100% which was around 4180mv. Still testing battery life
Click to expand...
Click to collapse
Its ok... But...dont repeat it again and again...otherwise the battery life cycles will reduce....
for e.g. If ours has 1000 charge cycles... It may get reduced to 800 or so....
Dont drain the battery excessively, otherwise you might have to buy a new one sooner........
ashvyas said:
I discharge my phone till 1% and it's voltage says 3380 mV .... is it normal ?? do I need to follow procedure suggested ??
PS: I know it is given it should be less than 3700mV but wondering if 3380mV is too low / any problem ??
Click to expand...
Click to collapse
answered above....
boulder96 said:
At 0% its supposed to be around 3400mv. So I would say it's fine.
Sidenote: I accidentally thanked you when I wanted to press reply
Click to expand...
Click to collapse
Ya accidentally thanks is good... But.. Dont u think my reply deserved a thanks.... Lol....
Sent from my GT-I9103 using xda app-developers app
bhargav143 said:
Its ok... But...dont repeat it again and again...otherwise the battery life cycles will reduce....
for e.g. If ours has 1000 charge cycles... It may get reduced to 800 or so....
Dont drain the battery excessively, otherwise you might have to buy a new one sooner........
Click to expand...
Click to collapse
sorry for a bit off topic ... wondering which way battery will last longer :
1) charge till 100% --> use it till lowest level almost less then 5% ( no change in-between) --> then charge till almost full ( no discharge before full change) --> less charging cycles I guess
2) charge whenever get a chance so battery level will remain in middle ( neither fully discharge nor fully discharge ) ---> will not it consume charging cycle fast
---------------------------------------------------------------------------------------------
Sent from my Samsung Galaxy R GT-I9103
Hit THANKS If I have Helped you
ashvyas said:
sorry for a bit off topic ... wondering which way battery will last longer :
1) charge till 100% --> use it till lowest level almost less then 5% ( no change in-between) --> then charge till almost full ( no discharge before full change) --> less charging cycles I guess
2) charge whenever get a chance so battery level will remain in middle ( neither fully discharge nor fully discharge ) ---> will not it consume charging cycle fast
---------------------------------------------------------------------------------------------
Sent from my Samsung Galaxy R GT-I9103
Hit THANKS If I have Helped you
Click to expand...
Click to collapse
First of all... The method is for one time calibration only... Dont repeat it more than twice... It will cause unnecessary strain on your battery.
The first method u mentioned will give u more battery cycles...
But, instead of discharging it to 5%... Get the charger as soon as you have below 15%.....
Sent from my GT-I9103 using xda app-developers app
@bhargav123: Ok I just gave you a thank! Thanks for sharing this useful method!
bhargav143 said:
First of all... The method is for one time calibration only... Dont repeat it more than twice... It will cause unnecessary strain on your battery.
The first method u mentioned will give u more battery cycles...
But, instead of discharging it to 5%... Get the charger as soon as you have below 15%.....
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
thanks buddy for useful information
I have a problem with my mi4c.
Everytime my phone touches the 30 % mark it shuts down.
After it is off I restart it and I can see ~25% and use it until shuts down at 0%.
Does anyone know how to solve the problem?
I'm running Resurrection Rom 5.7.4 with 2.00 OC kernel.
Also I'm using magisk.
I flashed the Rom etc. Around 3 days ago
first of all, flash some other rom to see if it persists
but frankly, most probably the battery is worn out, ie. if there's some stress and huge amount of power is being drawn, a dead battery won't be able to give proper voltage, the voltage drops and the system reads it as if battery level dropped to 0% level (the percentage is calculated from actual voltage, ie. ~4,35v = full, somewhere about 3,5v means 'empty') <-sorry for non-scientific description
btw. my battery shows similar symptoms - ie. it quickly drops from 100% to 85% and it happens that the phone shuts down if I try to run something demanding when batt level <20%. waiting for replacement to be delivered
I have the same issue
I just saw similar complaints in polish mi4c forums - I believe the batteries are either bad quality ones or rather they're designed to give too much output concerning their real size/capacity. How is that? just let electronics charge it waay over 4,2v - you "gain" some capacity and then you let it discharge to much less than 3,6v - you "gain" another couple of mAh. You can boast your slim battery has 3000mAh, but only for first 50-100 cycles (enogh for web tests to get good opinions and sell many phones) and then its capacity falls rapidly - because you're left with "real" battery capacity (I mean for voltages between 4,2 and 3,6v).
So, I personally believe the replacement battery will behave more or less the same because of the phone electronics it will be killed within similar period of time
adamuadamu said:
I just saw similar complaints in polish mi4c forums - I believe the batteries are either bad quality ones or rather they're designed to give too much output concerning their real size/capacity. How is that? just let electronics charge it waay over 4,2v - you "gain" some capacity and then you let it discharge to much less than 3,6v - you "gain" another couple of mAh. You can boast your slim battery has 3000mAh, but only for first 50-100 cycles (enogh for web tests to get good opinions and sell many phones) and then its capacity falls rapidly - because you're left with "real" battery capacity (I mean for voltages between 4,2 and 3,6v).
So, I personally believe the replacement battery will behave more or less the same because of the phone electronics it will be killed within similar period of time
Click to expand...
Click to collapse
Could be.
But why does it shut off at 30 %?
If I restart it I can use the 25%.
Is the voltage drop at 30 % so high that it shuts off?
I don't know if it happens on Miui.
I only experienced it on cm13 /rr 5.7.4
I was curious to find how's the battery condition, installed that app: https://play.google.com/store/apps/details?id=kr.hwangti.batterylog
it allows to see battery percentage, temp and current voltage when the percentage changes
so, my battery is already junk - there are numerous serious voltage drops like:
Code:
98% - 4270mV
96% - [COLOR="Red"]4075mV[/COLOR]
95% - 4199mV
or from previous charge cycle:
Code:
34% - 3715mV
33% - [COLOR="red"]3498mV[/COLOR]
31% - 3764mV
my new battery is on its way to destination country, curious to see how it'd look after replacement
right now, no wonder why it's shutting itself randomly
could you guys check your voltages and post here, too?
adamuadamu said:
I was curious to find how's the battery condition, installed that app: https://play.google.com/store/apps/details?id=kr.hwangti.batterylog
it allows to see battery percentage, temp and current voltage when the percentage changes
so, my battery is already junk - there are numerous serious voltage drops like:
Code:
98% - 4270mV
96% - [COLOR="Red"]4075mV[/COLOR]
95% - 4199mV
or from previous charge cycle:
Code:
34% - 3715mV
33% - [COLOR="red"]3498mV[/COLOR]
31% - 3764mV
my new battery is on its way to destination country, curious to see how it'd look after replacement
right now, no wonder why it's shutting itself randomly
could you guys check your voltages and post here, too?
Click to expand...
Click to collapse
According to the log, i also find random drops (max ~200mV). However I dont think my battery has problem. Battery life is excellent too. Maybe thats normal for LiPO batteries.
Ydraulikos said:
According to the log, i also find random drops (max ~200mV). However I dont think my battery has problem. Battery life is excellent too. Maybe thats normal for LiPO batteries.
Click to expand...
Click to collapse
can you share what ROM you're using? I wondered if this can be somehow linked to rom and its internal readings and or interpretation
adamuadamu said:
can you share what ROM you're using? I wondered if this can be somehow linked to rom and its internal readings and or interpretation
Click to expand...
Click to collapse
CM13 with kuma sources latest (20161006) build from emfox
thanks for the reply
will try to change the ROM to see if it persists
I've tried with xiaomi.eu stable ROM. I have the same values. I think that it is regular, since even in the play store's images you can see the same.
adamuadamu said:
could you guys check your voltages and post here, too?
Click to expand...
Click to collapse
Here, have my log (in attachment) from charged at 100% to completely discharged. There are a few drops here and there but it recovers quickly. I get around 5h 30m screen-on-time on TeamSuperluminal's CM13.
This is happening to me too (and to others on our italan facebook group).
I was posting this:"Guys i'm not able to solve this problem: i have a xioami mi4c (1 year old), and recently (every time) when i arrive under 20% of battery it suddenly shuts down. I already tried to turn it off multiple times and to charge it back to 100% without unplugging it but it doesn't work.
I don't know what to do; and when it should be without power (like you cannot turn it on) it shows something like 43% when connected to the charger."
When i saw this thread .
I always had miui but till last week i flashed cm13.1 TS.. i went to cm trying to solve heating issues and now the phone is really a lot less hot but i'm keeping with me those battery issues.. they're really annoying :/
Sent from my Mi-4c using Tapatalk
---------- Post added at 11:34 AM ---------- Previous post was at 10:41 AM ----------
Phlogistol said:
Here, have my log (in attachment) from charged at 100% to completely discharged. There are a few drops here and there but it recovers quickly. I get around 5h 30m screen-on-time on TeamSuperluminal's CM13.
Click to expand...
Click to collapse
How can you reach so many hours?i play sometimes to pokemon go or clash royale and i usually reach 3h!
Sent from my Mi-4c using Tapatalk
Bazzu said:
How can you reach so many hours?i play sometimes to pokemon go or clash royale and i usually reach 3h!
Click to expand...
Click to collapse
It's not the topic for that, but I rarely play games on the phone and mostly use it for text messaging. I also keep the screen brightness low (around 45 to 50%).
There seems to be quite a lot of variation between individual Mi4c's, so I guess some have better batteries or screens that spend less power; I've read up a lot on it and nobody's decided on an answer as of yet.
Aren't we in a troubleshooting thread ? this thing about variations between same model makes me really sad and angry..why the [email protected]%$ should be possible! I'm enjoying a lot my xiaomi but how can i trust again in the brand?
Sent from my Mi-4c using Tapatalk
Bazzu said:
Aren't we in a troubleshooting thread ? this thing about variations between same model makes me really sad and angry..why the [email protected]%$ should be possible! I'm enjoying a lot my xiaomi but how can i trust again in the brand?
Click to expand...
Click to collapse
It's well known that manufacturers mix and match components to assemble even a single phone model. The most familiar case is Apple with the iPhone 6 and the A8 SoC, which had two flavors: TSMC and Samsung. But, what I've said is speculation and not fact.
I'm sure there are two variants of the Mi4c that use either a Sharp or an AUO screen, and it might be that the battery life is impacted by this or that there are two or more battery variants that are put into the Mi4c. No one ever collected enough data to be sure this is the definite cause of weaker battery life, though.
Same as everyone, I'd suggest buying the phone that gives you the most bang for your buck, be that Xiaomi or some other manufacturer. That's why I bought the Mi4c and I have only minor complaints, though the great community definitely helped
Phlogistol said:
It's well known that manufacturers mix and match components to assemble even a single phone model. The most familiar case is Apple with the iPhone 6 and the A8 SoC, which had two flavors: TSMC and Samsung. But, what I've said is speculation and not fact.
I'm sure there are two variants of the Mi4c that use either a Sharp or an AUO screen, and it might be that the battery life is impacted by this or that there are two or more battery variants that are put into the Mi4c. No one ever collected enough data to be sure this is the definite cause of weaker battery life, though.
Same as everyone, I'd suggest buying the phone that gives you the most bang for your buck, be that Xiaomi or some other manufacturer. That's why I bought the Mi4c and I have only minor complaints, though the great community definitely helped
Click to expand...
Click to collapse
Yeah you're absolutely right :good:
I bought the mi4c for the same reason...but after all, i have to complain about its battery and touch (yeah i don't like it so much).
Anyway a new battery is coming; up to now it's working good but i don't trust so much of the hardware, so before the "shutting down threshold" grows, i'd like to be "safe".
(little ot: inside our italian forum someone suggested that redmi 3 pro is far better then mi4c ; what do you think ? ; if you prefer you can private message me)
redmi 3pro would be far better except for the camera depends on your needs - also, if you want to run custom roms, check if there are any stably ones beforehand
my battery arrived yesterday, changed yesterda, charged overnight and observing - still running battery log and so far the voltage drops are negligible compared to the original one like 0,02v instead of 0,2v. I'll give full report after full discharge cycle
adamuadamu said:
redmi 3pro would be far better except for the camera depends on your needs - also, if you want to run custom roms, check if there are any stably ones beforehand
my battery arrived yesterday, changed yesterda, charged overnight and observing - still running battery log and so far the voltage drops are negligible compared to the original one like 0,02v instead of 0,2v. I'll give full report after full discharge cycle
Click to expand...
Click to collapse
Was the change easy to do?
I don't care so much about camera..i absolutely prefer battery and a smooth system, for casual gaming and browsing
Sent from my Mi-4c using Tapatalk
Use only MIUI 8 from Xiaomi.eu
Any other rom has various problems.
So without further ado, I bring you a manual way to charge past 80% and with the new root s9 this should work for you guys to. Let me know and we can or will adjust accordingly.
First off, The good stuff.
I Nor anyone else is responsible for what you do to your devices.This is all done at your own risk.This "manual" charge is basically one small hack allowing us to charge so far up to 98% I have yet to be able to charge fully to 100%
So for starters,Obviously We need a U.S. Snapdragon rooted S8 There are several guides in either the General sections and or the Development sections, Quite easy to find with Xda's wonderful search bar at the top of each page.
Now that where all on the same page first of let me explain what is going on and what we are going to be doing about this.
We all rooted users know that Samsung implemented a safety feature starting back with the note 7. They limited charging to 80% While using any Boot-loader other than pure stock User Release.
What we are going to be doing is basically once we charge our devices to 80% We are then going to fake the battery gauge out into thinking the device is dead.
The file we have to modify is,First off undone by every Reboot as it lies in /SYS/Class/Power_Supply_Battery Which is a non persistent partition...So any modifications will be undone with this file on Reboot.
More Disclaimers
Will be installing a Xposed module called Critical battery shutdown disabler. You need the version I will list Further down below, and this one exactly!!!!The one in Xposed and other sources are of a different make and are not what is needed...
So with this modded Module,If your battery does ever reach 0% it will not shutdown it will not reboot...So you can truly flat-line your battery if you do not pay attn...... Which is double bad for us Samsung users, As we also face a known bug called Deep discharge. Which in means if your battery flat-lines. There is a chance which it will not power on and will not charge... This sometimes can be remedied by placing device on wireless charger and USB at the same time.
I will post ScreenShots down below, Hopefully in order as well So you can follow a bit better.
So first off Download this version of Critical Battery Shutdown Disabler here... CriticalBatteryShutdownDisable
Now that that's installed Activate and reboot. Charge your device as normal to 80%. As shown below in the First SS
So once we hit 80% We need to navigate in a Root file explorer to this directory /SYS/CLASS/POWER_SUPPLY_BATTERY_battery_capacity_max. Open as a text file and is will show some value 1000 being the highest. Well with this module installed and This file open You can now change this value which mine is 1000 To 0 And save.... As in second third and fourth screen shots
I have had to click save several times on occasion. This should take up to 10 to 15 seconds and you battery gauge will drop to 0 and low power mode may come on... But if you now notice, Since we are charged to 80% and now it claims 0 The device now begins to charge... As you can see in the 5th screenshot below
So now your device is charging At first impressions it just sits at 0% while charging But I have learned even though this is true Several tests revealed once I get to a actual 94 to 95 % the gauge begins to climb rapidly back up...
So I am assuming there is another safety net in place, As I figured this would possibly lead to over charges if left unattended for long periods......But no matter how many times i try about 95% it always reverts the file and Max capacity back to 1000 Almost making this a Foolproof design.... So far....
You can see in other screen shots i reverted the file back and forth to show it charging and such
I just know Those of us that say are on @partcyborgs Rom We get awesome battery life with several of us hitting well over 8 or 9 hours of SOT....
Now just imagine what we can achieve with a extra 15% plus more since in the end the device will not reboot at low battery.....
I want to see 11 hours of SOT And I think I can hit it.:good::good::good:
Hey remember the Thanks button goes a long way And Make sure to go out and thank all of our local heros That keep our S8s alive.
Credits
@firefds For modifying CbSd for our device to make this all possible.
@partcyborg For finding a root method and for a wonderful Rom
@jrkruse For getting us a root method on Bit 5 bootloaders and several nice roms
@elliwigyFor the countless hours he has put in, and suffering of dealing with me
On a side note this should work for any samsung note 7 or higher on a US eng or combo bootloader.
I hit 97% this morning and felt confident enough i fell asleep not watching it. And just as several times before. It trickled of to the point of not charging any more. A t 97%.
Today has been the best day ever for battery. Om at 59% since about 530 am. Youtube most of the day for music while doing yard work. Screen on since 8 am its a little after 2 now. Im aiming for 11 hours SOT?????
TheMadScientist said:
So this is a wip right now. I have been testing last few nights guys for root on s8. But this would work on s8 and up rooted.
I will tonight or tomorrow start posting screen shots and method once i work out one last major hitch in my hack.
But long story short. I have managed to once charged to 80% to charge now to 92 94 and 97% manually. Which i will disclose shortly.
This method will not be for the faint off heart. Can be dangerous. And probably is. But again once i limmit down one last issue. I think we will be able to hit a full 100% charge.
I need help from the community. And its weird i know. Bit to hit a 100% charge i need to find a app or xposed model. Like critical battery shutdown disabler. As it seems to only work to 4.3 or so.
So if any one has any suggestions on this please let me know.
Click to expand...
Click to collapse
I forked the original xposed model on Github and I'll try to enable it for Android 9
firefds said:
I forked the original xposed model on Github and I'll try to enable it for Android 9
Click to expand...
Click to collapse
Im still on nougat. All us snap users rooted are nougat. Thank you for the response good sir love your app???
firefds said:
I forked the original xposed model on Github and I'll try to enable it for Android 9
Click to expand...
Click to collapse
So what i got going on is we cant charge above 80%. But i can pretty much fake the battery gauge but only to 0% but once i do fake it it starts charging again. But randomly shuts down due to "low power". So if i can get it to not randomly reboot due to low power i can get 100%
I showed a few fellars. This morning. I hit 96 and 94 % last night. And i can do it any time i want. Again this is dangerous as the device sees 0%. Even though its really at 80% +. So you have to kinda keep an eye on the graph like i did i followed the curve + time and estimated. But i cant pass 94 to 96 % without a low power shutdown
@TheMadScientist please try the attached APK
firefds said:
@TheMadScientist please try the attached APK
Click to expand...
Click to collapse
Tells me i need a newer framework. 90+ thus can't be activated
TheMadScientist said:
Tells me i need a newer framework. 90+ thus can't be activated
Click to expand...
Click to collapse
What's your xposed version?
firefds said:
What's your xposed version?
Click to expand...
Click to collapse
89 framework
I see something now about a90 betta
TheMadScientist said:
89 framework
Click to expand...
Click to collapse
This should work
firefds said:
This should work
Click to expand...
Click to collapse
Yes sir
So i will teat this and see if i can hit my goal. Ive actually got the best battery life today. Than ive had in a very long time. So. Time to charge up boys and see if i can hit closer to 100%
So every one know the question isn't if I get passed 80% it's if I can make to 100. I have proven we can get passed the 80 barrier. I'm charging up to 80 as we speak. Then I'm going to apply this hack job of a idea and run it.
So wish me luck into not having the exploding s8????
firefds said:
This should work
Click to expand...
Click to collapse
As soon as i hit it and knock the gauge to 0% it shuts down straight away pretty much.
TheMadScientist said:
As soon as i hit it and knock the gauge to 0% it shuts down straight away pretty much.
Click to expand...
Click to collapse
The module performs a shutdown once its on 0 percent.
I can make it do disable the auto shutdown completely.
solution-official modded pie img by jrksure. (ability of safestrap only, no root, no xposed for pie). even though there is no root/xposed. i am still glad i made the decision to upgrade.
---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------
https://forum.xda-developers.com/ga...wip-n950u-bootloader-unlocking-build-t3854549
thread looks abandoned but i hope he finds a way for us.....
firefds said:
The module performs a shutdown once its on 0 percent.
I can make it do disable the auto shutdown completely.
Click to expand...
Click to collapse
That's what i need. That would be perfect. And yes i know the risks. I assume ask risks. ??? Thermo nuclear war. Dead cars lost puppies. All the usual. ??? I technicly don't have a dead battery so i should be ok. So what I'm doing is once i got 80% i fake the gauge. Only way to fake it is back to 0. No in between. But it starts charging again. But if coarse being at 0 shuts down randomly. I removed the module and was able to get 95 last night. But i started dozing off so i stopped and rebooted as this gets undone upon reboots.
Either way you are a life saver i never thought we would be able to pull this off. This will be wonderful for any one who is technicly available in the head. And had a few minutes.
From my gathering. From 80 to 100% takes about 25 to 30 minutes as again no way to tell since gauge reads 0. The battery hd app has a nice real time graph. As i follow the curves. I guesstimate and sofar have been within 2 or 3 % of actuality %s. So i theorize that even if i was to mess up and over charge to say say 103% i don't think much harm will come
My battery in 1.5 years. Still reads 0 cycles. As i charge. Everyday from 35% to 80%. Prime pristine condition
Another APK for testing
firefds said:
Another APK for testing
Click to expand...
Click to collapse
Nope still rebooted.
[Guide]: How to check your battery cycle count on your phone :
1. Dial *#*#6485#*#* on phone dialer
2. Then see what number is written after MF_02
3. That is the number of battery cycle counts for your device. ?
Enjoy.
FAQ: Please read the FAQ before asking questions.
P.S: This guide doesn't work on custom roms and also doesn't work on Samsung Devices and if you have done any modifications to your kernel or if you have rooted your device and if you have done any stuff like that.
Q1. What is meant by this battery cycle count ?
ANS - A charge cycle happens when you use all of the battery's power—but that doesn't necessarily mean a single charge. For example, you could use half of your notebook's charge in one day, and then recharge it fully. If you did the same thing the next day, it would count as one charge cycle, not two.
Q2. How does in effect battery life ?
ANS - Typically, a modern phone battery's (lithium-ion) lifespan is 2 – 3 years, which is about 300 – 500 charge cycles as rated by manufacturers. After that, the battery capacity will drop by roughly 20%.
Q3. Why is the MF_02 could hidden or showing the count "0" ?
ANS - It is because your device manufacturer has hidden it for your device.
Q4. Is there any way to check the battery cycle count on rooted phones and on custom roms ?
ANS - Yes, there is a way but you need to be rooted.
Find battery capacity using termux app:
su
cat /sys/class/power_supply/bms/charge_full
Guide by @Aadilgillani
Mine shows "MF_02: (Chinese text) 0".
Mine also shows 0 after MF_02.
Mine Shows "MF_02: (Chinese Text) 6"
Note That, I Have Been Using My Mobile Device Last Two Years.
322 i have it for 21months
what is the MF_3 refers to?
Aadil Gillani said:
Guide : How to check your battery cycle count on your Phone
1. Dial *#*#6485#*#* of phone dialer
2. Then see what number is written after MF_02
3. That is the Number of Battery Cycle counts for your device.
Please share your battery cycle count screenshot below.
Enjoy.
In general, number of cycles for a rechargeable battery indicates how many times it can undergo the process of complete charging and discharging until failure or it starting to lose capacity.
Typically, a modern phone battery's (lithium-ion) lifespan is 2 – 3 years, which is about 300 – 500 charge cycles as rated by manufacturers. After that, the battery capacity will drop by roughly 20%.
Click to expand...
Click to collapse
So if I understand correctly, "0" indicates exhausted cycles?
It says 6, i am using it since january of last year
I have a OnePlus 7 and the number just disappears
Azukegi said:
I have a OnePlus 7 and the number just disappears
Click to expand...
Click to collapse
yup same on my 8 pro. OnePlus doesn't want us to access it. unfortunately :/