Related
im new to rooting, and i apologize if this is the wrong forum, but i believed it to be best.
my issue is that ever since installing the latest cyanogen mod, my battery is terrible, after about an hour i am down to 65-70 percent battery with minimal usage (no calls or programs, perhaps a text or 5)
i tried using the trouble shooting on the wiki which states
Code:
Battery recalibration
If you're experiencing higher than normal battery drain, try the following:
1. Charge the phone to full battery; power off and let it keep charging until the light is green.
2. Boot to recovery mode and go to console (or adb shell) and type:
mount -a
rm /data/system/batterystats.bin
1. Reboot the phone and use it normally, but don't charge until it shuts off.
2. Recharge the phone completely and then use as you normally would.
but when i tried the mount -a command i get various errors pertaining to "not found" i still typed in the rm command but i got no notification that it worked.
any ideas? im loving the mod, and the root community as a whole and i would hate to go back to the original rom
also another oddity i noticed... my battery will drain down to 20 or so percent, and ill plug in the charger for 10min and then itll say 97 percent? (not exact just round abouts of percentage) whats going on?
also ill reboot my phone or start it back up after it shut down to low power and itll be at 50% or way higher then it said it was when it shut down/rebooted
I dont believe it's a problem with the rom itself, it might just be the battery. I had that problem, and solved it simply by replacing my battery.
Did you overcharge your battery? If so, that's probably why your battery is unable hold a charge, or is giving off false percentages. (one way of knowing if you did is if the battery is bulging out)
there does seem to be a miniscule bulge on the battery, as i often left it plugged in even when it was at a 100percent. even so i did not have the severity of the problems i am having before i switched over to cyanogen
Same problem
My G1 has been shutting off at 70% battery, too. I tried to do the charge, mount -a, rm /data/system/batterystats.bin bit, and while I could mount -a, when I put in the rm command, the console returns that there's no such file or directory. My battery also has the tiniest bulge; is the next step to just get a new battery? I was not having this problem before Cyanogen Mod, either.
gooberguy said:
im new to rooting, and i apologize if this is the wrong forum, but i believed it to be best.
my issue is that ever since installing the latest cyanogen mod, my battery is terrible, after about an hour i am down to 65-70 percent battery with minimal usage (no calls or programs, perhaps a text or 5)
i tried using the trouble shooting on the wiki which states
Code:
Battery recalibration
If you're experiencing higher than normal battery drain, try the following:
1. Charge the phone to full battery; power off and let it keep charging until the light is green.
2. Boot to recovery mode and go to console (or adb shell) and type:
mount -a
rm /data/system/batterystats.bin
1. Reboot the phone and use it normally, but don't charge until it shuts off.
2. Recharge the phone completely and then use as you normally would.
but when i tried the mount -a command i get various errors pertaining to "not found" i still typed in the rm command but i got no notification that it worked.
any ideas? im loving the mod, and the root community as a whole and i would hate to go back to the original rom
Click to expand...
Click to collapse
I rooted my phone for the first time and am using CM5.0.7. My battery is acting weird. Tried using the console and typing those commands above, but I get the error message as well. Does someone know the answer?
Thanks.
To all the posters that are having problems getting access to the file... You might want to try switching your recovery to Amon_RA's latest recovery. He has a menu option which removes the battery configuration file for you. I believe the option is under the wipe menu.
Additionally, make sure you follow the steps for recalibrating the battery outlined in the troubleshooting section of cyanogenmod's wiki because just deleting the batterystat file will not help with the battery drain unless you follow the steps.
in addition to all of this, the battery life issues on 5.0.7 is a known bug that cyanogen publicized on twitter through his own testing. it's currently being looked into. so far, wiping battery stats has had no measurable effect beyond what is percieved to be slightly longer life by the user.
my suggestion: stick it out until the fix comes, which will be prior to a "stable" CM5 release.
my suggestion: stick it out until the fix comes, which will be prior to a "stable" CM5 release.
Click to expand...
Click to collapse
Good advice also. That is what I will be doing. I wanted to stick with this ROM so I tried the recalibration technique but I do confirm that it is having little effect.
yeah, there are people claiming that it's having miraculous effect, and then in the next sentence saying "oh, but i'm also not running any apps, have wifi, bluetooth, data and the screen turned off and it's been plugged in for half the time". you cant rely on results like that. if cyanogen says himself that theres a battery problem, i'd tend to take that as gospel. the man kinda knows what hes talking about on a massive scale.
try this
this was an issue with an old cyanogenmod. 3.8.1
I posted a workaround in the 5.0.7 thread. this worked for me, but YMMV.
add this to your userinit.sh file now located int /sd-ext/
Code:
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
or run command in the terminal (not recovery's console)
check it with
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
before and after if you run it in terminal.
alternatively, set this value in setCPU. under advanced.
my values:
Code:
sampling rate : 2000000
up threshold: 60
ignore nice load: 0
power save bias: 200
this gives me about 10%-15% less battery life than the last build. which is better than I was getting friday.
AroundTheWorld said:
I dont believe it's a problem with the rom itself, it might just be the battery. I had that problem, and solved it simply by replacing my battery.
Did you overcharge your battery? If so, that's probably why your battery is unable hold a charge, or is giving off false percentages. (one way of knowing if you did is if the battery is bulging out)
Click to expand...
Click to collapse
I beg to differ, I'm having the same issues on the Evo 4G and have tried three different batteries. All batteries drain rather quickly and take FOOOOOREEEEEVVVVVEEEERRRRRRRRRRRRRRRRR to charge. Plugged in over night for over six hours only reaching 63% battery capacity?! Absurd! Does not happen with any of the Stock ROMs.
i have the same problem with a LG GT540f ... i installed cyanogenmod 7 and the battery life is extremly unestable... 1 hour and my cel gets OFF ....
no solutions yet?
Having seen so many posts on calibration of battery, i have decided to make this thread so to make it easier and useful for you guys. This thread can also be used to share your experiences with calibration and usage of milestone's battery.
Note: This is done using a the motorola milestone 1. So if you're using any other phone, pls ask abt them in this thread b4 you do anything!!!!
Intro:
The calibration of the battery is needed when you want to switch/install roms. This will make sure that the battery is really fully charged, thus preventing the battery life from dropping too drastically in a matter of hours.
I know there are some other methods to help calibrate your battery, but this is the only one I am sure of the steps. Please inform me of the other methods so to share with everybody.
Steps:
1. Before flashing a new rom, use root explorer (with read/write set) to delete the file "batterystats.bin" stored in /data/system/.
2. Charge your phone with it being turned off.
3. After it is fully charged(100%), take out its battery without plugging off the power supply.
4. Wait for a few moments, and a ? sign will appear.
5. Put your battery back in. You should see that the battery percentage increases quickly to 60%. If it increases to 100% with seconds, please skip to step 6.
6. If it stops increasing at 60%, let the phone continue to charge until 100%(takes quite a while)
7. Once it reaches 100%, let it charge for a further 15-20 minutes.
8. Once that's done, you can boot to OpenRecovery and flash your rom!!!
Alternative way of calibration(thanks a lot zeppelinrox!!!):
http://forum.xda-developers.com/showpost.php?p=11803458&postcount=10
This method allows you to calibrate the battery and use ur phone at the same time!!!
I hope this helps you people, because it really helped me!!!!
Note: i m not responsible for anything bad that happens to ur phone. Perform the calibration at ur own risk!!!(though it should be perfectly fine, unless u do something wrong or extra)
Btw, i am just writing things that i assume to be correct, so if anything needs to be edited/added, pls inform me through this thread or sending me a pm.
Credits to everyone (especially pcphobic for his post in http://forum.xda-developers.com/showpost.php?p=11604143&postcount=740) who have written all these in your posts that made it possible for me to gather and get all this info!!!!!!
You should give credits to whom you copied this from.
oh yea i almost forgot.Thx fellow citizen!!!!
And it's good to remove/wipe the battery status data with the charger plug-in as the last step.
thx bnwg, but i don't get you. Mind if you make yourself clearer? Thx!!!!
nickrule1896 said:
thx bnwg, but i don't get you. Mind if you make yourself clearer? Thx!!!!
Click to expand...
Click to collapse
He's referring to deleting the batterystats.bin file from the /data/system folder.
Yup, got it thx!!!!
mount -a
rm /data/system/batterystats.bin
For this set of instructions, can the console in the OR be used to perform it?
mods should make this thread a stickie.
Calibrating Without Downtime!
Edit: If this doesn't work on your device, try the Die-Hard Battery Calibrator Script to ensure a proper charge
This is proven to work with Motorola Milestone so I would imagine the Droid as well.
It works with the Milestone 2 but you may need to get the phone booted up manually (step 7) instead of the easy reboot in step 6.
If you have a different phone and this works, please let us know!
You probably won't believe that this will work but try it anyway.
The big benefit of doing it this way:
It's great if you don't plan on changing roms and just want to calibrate your battery without downtime so that you can just use your phone as you normally would.
Note: Be sure that the phone isn't running hot (feel the back)
1. While in Android, charge up to 100% and leave the phone plugged in.
2. Delete /data/system/batterystats.bin
3. Remove back cover
4. Press Power and choose to reboot normally.
5. When the screen goes black and the lights go out, pull out the battery before you get the M logo. It will probably still work after the M logo shows up but that's how I do it.
6. Surprise: The phone will boot up without the battery! - Mine does - every time
Note: Batterystats.bin is recreated when you see the M logo - even though the battery isn't in the phone.
Go to Step 8 if the phone booted up as described.
7. If it doesn't boot up and you see the battery with the ?
..........a) Put the battery back in (you will see 60%),
..........b) Power off the phone (press power until LED light goes out)
..........c) Power on the phone (press power until you see the M logo)
..........d) Remove battery... and watch bootanimation...
8. a) After the surprise of seeing the boot animation without a battery, you will then see the lock screen along with a "No SIM card error" and no signal.
...... Put the battery back in - the SIM card error will disappear, you will get a signal, it will show 60% full and the icon will show the battery charging.
...... Go to Step 9 if this works as planned. If it doesn't, reboot (again without the battery) and use step 8b instead of step 8a.
... b) Put the battery back in during the bootanimation, but after the haptic feedback/vibration (and the buttons along the bottom light up).
....... On a normal reboot, you can actually slide and unlock the phone when you get the vibration during the boot animation. You knew that, right?
9. Use your phone normally while you calibrate the battery
10. Let it fill it up to 100% + 15 minutes or so. When it is truly finished charging, the battery should be cool.
11. If the phone is running hot, weird things can happen. For example, you may get no signal when you put the battery back in or the battery doesn't begin charging (the status bar battery icon doesn't change). Just let the phone cool off and it should work next time.
100% full is approximately 4200mV
As you can see in the cap below, it's showing only 60% at 4241mV (This was after booting up without the battery and putting the battery in)
A few minutes later, still plugged in, it showed 100% at 4225mV and then it went up to 4230mV.
Finally, I then unplugged the phone and I got a reading of 4196mV
Notes:
Now, when I charge it up, it will go up to 4230mV everytime. I leave it plugged in an extra few minutes after that.
I highly recommend Battery Monitor Widget
Batterystats.bin gets recreated if you unplug your phone and plug it in again. So don't do that. Let it get recreated on the M logo (Step 6).
Thanks to pcphobic for a couple of important tips and to pcphobic and sileshn both for confirming that my phone isn't possessed!
Azhad (one of the two Androidiani OR developers) said another way to wipe battery
http://forum.xda-developers.com/showpost.php?p=11715432&postcount=967
now i don't know what's the right one? delete batterystats.bin or battd folder's contents? with full or empty battery?
nickrule1896 said:
Credits to everyone who have written all these in your posts that made it possible for me to gather and get all this info!!!!!!
Click to expand...
Click to collapse
It would have been nice if you mentioned my name or put a source link to my posting dated 24th February 2011 at
http://forum.xda-developers.com/showpost.php?p=11604143&postcount=740
etoy said:
Azhad (one of the two Androidiani OR developers) said another way to wipe battery
http://forum.xda-developers.com/showpost.php?p=11715432&postcount=967
now i don't know what's the right one? delete batterystats.bin or battd folder's contents? with full or empty battery?
Click to expand...
Click to collapse
Recently I follow Azhad's way to wipe the battery.
When I delete the file (ie. cc_data) under that folder and go back in it, the file will be regenerated. And the batterystats.bin is updated according to the timestamp of the newly generated cc-data file. I don't know if this is the same as the step 6 from zeppelinrox's method.
etoy said:
Azhad (one of the two Androidiani OR developers) said another way to wipe battery
http://forum.xda-developers.com/showpost.php?p=11715432&postcount=967
now i don't know what's the right one? delete batterystats.bin or battd folder's contents? with full or empty battery?
Click to expand...
Click to collapse
Maybe that's the method for CM7? I don't know because I'm a die hard CM6er lol
He also mentions a file (/data/system/batterystats.bis) that I've never seen mentioned before.
bnwg said:
Recently I follow Azhad's way to wipe the battery.
When I delete the file (ie. cc_data) under that folder and go back in it, the file will be regenerated. And the batterystats.bin is updated according to the timestamp of the newly generated cc-data file. I don't know if this is the same as the step 6 from zeppelinrox's method.
Click to expand...
Click to collapse
I have that cc_data file too but it's blank when I open it with a text editor.
im just linking my post here: http://forum.xda-developers.com/showpost.php?p=11603675&postcount=736
the myth about the batterysoftware needs some real facts. payce from german forum did some measuring with real astonishing results.
I have seen that article before.. thanks to you of course
I'll quote the conclusion of the first post:
That is, the stone over-estimated the voltage at the battery is full by ~ 60 mV and underestimated the power of up to 100 mV with an empty battery. The intent is well-battery protection (which is good too). It is pretended that 3.0 and 4.2 volts to discharge until it is loaded. In reality, there are more 3.1 volts and 4.15 volts (which by the way of battery manufacturers also better unanimous opinion!).
Click to expand...
Click to collapse
So the reading I get via Battery Monitor Widget aren't that far off and perhaps exactly where they're supposed to be.
After fully charging (showing 4230mV while plugged in) and then uplugging the phone, it will ideally show between 4150mV and 4200mV vs the 4.15 volts (ie. 4150mV) quoted above.
My phone will power itself off between 3150mV and 3200mV vs the 3.1 volts (3100mV) quoted above. Actually, I just checked BMW's log and today it powered itself off at 3162mV after 19.5 hrs.
I found it interesting that you use less power while downloading overclocked versus downloading at stock speed lol.
ABC: Android Battery Calibration - Video Guide
youtube.com/watch?v=fwrZu0DKp2c[/url]
@zeppelinrox: wouldnt ur steps be the same as doing the calibration my way, just that instead of booting to OR for flashing new rom, we just reboot normally?
@pcphobic: sry cos it would be hard for me to go around checking who posted this kind of info before. well, since u said it, i will definitely do it
nickrule1896 said:
@zeppelinrox: wouldnt ur steps be the same as doing the calibration my way, just that instead of booting to OR for flashing new rom, we just reboot normally?
Click to expand...
Click to collapse
Of course it would calibrate either way.
The difference is that I found a way to do it more conveniently.
You can do it anytime, use your phone normally and actually monitor the voltage as well.
Sent from my Milestone using Tapatalk
zeppelinrox said:
Of course it would calibrate either way.
The difference is that I found a way to do it more conveniently.
You can do it anytime, use your phone normally and actually monitor the voltage as well.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
I am using MS2 and there isn't an option of "reboot" when pressing the power button. Can this be done by using the "quick boot" app? thanks
https://market.android.com/details?id=com.siriusapplications.quickboot&feature=search_result
Ok this is silly .I ordered an andida 2000 mah battery and I can't edit sys/class/power_supply/battery/full_bat . I can't even access it in terminal with Su . I tried to Change the value from 1620 to 2000 and even tried editing subfolders to But it will not stick .I tried in es explorer changing permissions editing then changing them back so nobody can write but it still reverts back .
Is this kernal related ? If it is can kozmik make it avaible to change the value via aroma ?there is only these options 1620 stock .1800 .2000.or the extended at 3500 mah .
I fear this is kicking out and charging to full capacity and that's why most batterys suck in these phones .
Anyone have advice ?
Current setup .- unlocked HTC raider . Holics 1.3 . Kozmik beta 13 . S-off .Jupunbear hboot .TWRP recovery
raidrom said:
Ok this is silly .I ordered an andida 2000 mah battery and I can't edit sys/class/power_supply/battery/full_bat . I can't even access it in terminal with Su . I tried to Change the value from 1620 to 2000 and even tried editing subfolders to But it will not stick .I tried in es explorer changing permissions editing then changing them back so nobody can write but it still reverts back .
Is this kernal related ? If it is can kozmik make it avaible to change the value via aroma ?there is only these options 1620 stock .1800 .2000.or the extended at 3500 mah .
I fear this is kicking out and charging to full capacity and that's why most batterys suck in these phones .
Anyone have advice ?
Current setup .- unlocked HTC raider . Holics 1.3 . Kozmik beta 13 . S-off .Jupunbear hboot .TWRP recovery
Click to expand...
Click to collapse
I tried accessing the "battery" folder using Root explorer, and it caused Root Explorer to FC. (S-Off, pure velocity rom, bell raider)
I have the 2000mah andida battery also, and would like to ask: Is what you're trying to do necessary? What do you expect to happen if you can successfully edit and save the changes to that file?
Well it is part of the hardware files that controls LEDs and etc . What I believe is that it is sensing a full charge at 1620 mah and kicking off . With a green led indicating so. Just like you can leave you phone on the charger all night and it won't over charge it right . HTC has made it in the folders ad. Safety net . Where I'm sure other phones have N auto detect feature .just a thought
raidrom said:
Well it is part of the hardware files that controls LEDs and etc . What I believe is that it is sensing a full charge at 1620 mah and kicking off . With a green led indicating so. Just like you can leave you phone on the charger all night and it won't over charge it right . HTC has made it in the folders ad. Safety net . Where I'm sure other phones have N auto detect feature .just a thought
Click to expand...
Click to collapse
Neat. Interesting... I wish I could help figure this out more.
raidrom said:
Ok this is silly .I ordered an andida 2000 mah battery and I can't edit sys/class/power_supply/battery/full_bat . I can't even access it in terminal with Su . I tried to Change the value from 1620 to 2000 and even tried editing subfolders to But it will not stick .I tried in es explorer changing permissions editing then changing them back so nobody can write but it still reverts back .
Is this kernal related ? If it is can kozmik make it avaible to change the value via aroma ?there is only these options 1620 stock .1800 .2000.or the extended at 3500 mah .
I fear this is kicking out and charging to full capacity and that's why most batterys suck in these phones .
Anyone have advice ?
Current setup .- unlocked HTC raider . Holics 1.3 . Kozmik beta 13 . S-off .Jupunbear hboot .TWRP recovery
Click to expand...
Click to collapse
Not working here either...
EDIT: Let me play around and get back
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
Maqical said:
Not working here either...
EDIT: Let me play around and get back
Click to expand...
Click to collapse
Found It!..... Files permissions are set for READ only change permissions and it saves fine
im trying as well now ..do a little research on some adb commands lol .im surprised no developer has helped us out . would love to maybe just have a script to run
raidrom said:
im trying as well now ..do a little research on some adb commands lol .im surprised no developer has helped us out . would love to maybe just have a script to run
Click to expand...
Click to collapse
I don't think we know if what the OP is suggesting is even necessary for using the 2000maH battery. It would be nice to know that first. Keeping an eye on this one!
LaZiODROID said:
I don't think we know if what the OP is suggesting is even necessary for using the 2000maH battery. It would be nice to know that first. Keeping an eye on this one!
Click to expand...
Click to collapse
I am the OP lol . I emailed HTC dev. But they said we understand your need to get better battery life .but please take a hike basically
raidrom said:
I am the OP lol . I emailed HTC dev. But they said we understand your need to get better battery life .but please take a hike basically
Click to expand...
Click to collapse
LOL woops!! My bad.
http://developer.android.com/reference/android/os/BatteryManager.html
i need a script to be made from this ? its in the android.os .
i did someones suggestion to flash a new battery using the android kitchen and it seems to be better lol .just have to learn a bit of java i guess.and the command isnt in adb .
Hopefully someone will correct me if I am wrong here. But you are right, the /sys/ folder is very kernel related. They are not files that can be modified like normal. I will leave you something to do for homework! Browse the /sys/ folder and find your vibe in a terminal. Now this stuff links to your hardware, you cant open and edit the file. But you can "echo 1 > vibe" replacing vibe with the "file" of your vibe and of course no quotes. Now with your phone vibrating push a 0 to it with ........ echo 0 > vibe. Welcome to an excellent question that delves into linux hardware hacking!!!!! As for the mAH with these newer batteries, I am a lot less clear. Unless the battery has the info encoded to it, it should calculate that value from charge/discharge rate, change in battery voltage & change in time.
edit, should be able to use cat to get info btw ie "cat /sys/class/power_supply/battery/full_bat" will show its full value
Neat.
Running
Code:
cat /sys/class/power_supply/battery/full_bat
produced a value of 1620. I assume that is mAh? I currently have an Andida 2000mAh battery in my phone. Does this mean the phone isn't identifying my battery like a 2000 mAh battery? Or.. does it mean I could be missing out on extra life that this battery could offer?
Again, my normal disclaimer. I am not a pro at these things so my info may be off. The battery life SHOULD be dependant upon the actual capacity of the battery - drain rate. The phone should just monitor the voltage of the battery and shut it off when it reaches a minimum level (Lithium battery tend to not like to take a charge if drained too low). Charging is a different story as it will monitor charging rate, battery V and battery temp (Lithium batteries like to explode when too hot). Back to draining, as the batter drains its voltage drops. Now I have no clue if the OS does some sort of tom foolery and crazy calculation using batter V, capacity & discharge rate to get the percentage, or if it just reports back what percent it is between Vmax and Vmin. If its the former, you should notice its seems to last a long time when its nearly empty. if its the former it should stay slope a little bit the opposite way.
Lastly its a really long winded way to say who cares if it actually lasts longer? If it does not last any longer & reports as 1620 you probably got ripped off.
lamebmx said:
Lastly its a really long winded way to say who cares if it actually lasts longer? If it does not last any longer & reports as 1620 you probably got ripped off.
Click to expand...
Click to collapse
Yeah, it was a cheap eBay battery anyway. Haha... I wasn't expecting too much from it.
In ES Explorer if you go into settings you can change it to explore root (after granting SU permission) and then mount the system as writable. The system file defaults to read only otherwise.
raidrom said:
http://developer.android.com/reference/android/os/BatteryManager.html
i need a script to be made from this ? its in the android.os .
i did someones suggestion to flash a new battery using the android kitchen and it seems to be better lol .just have to learn a bit of java i guess.and the command isnt in adb .
Click to expand...
Click to collapse
Unfortunately, this class just represents values. You can't modify anything in it (no field setters, and the values are all declared "final", which means you can't modify them.) This class gets populated from somewhere else, and is only accessed to get values.
Like lamebmx says, I'm not so sure that value actually matters. Whether or not the 1620mAh value is hardcoded somewhere, batteries charge capacities change over time (ie worsen the older they get), and they are still able to fully charge because the charging and charging rate are based on electrical feedback from the battery charging circuit.
The charger will provide a certain number of volts at a certain regulated current, and time and test the response of the battery. Charging slows as the battery reaches it's max charge. It's logarithmic. Once the change in battery voltage growth slows to below a certain threshold, the charger will kick off. I very much doubt that the software controls the charge sensing. It might control the min and max charge current available (ie fast charge or slow charge) but I don't think it can control when the charge stops.
I might be way off here, but I've never seen a battery charger circuit anywhere for anything that has a max charge dictated by anything besides the actual voltage feedback from the physical battery.
I am making Progress with finding a solution on the Misaligned or wrong battery meter on the Zerolemon battery or any calibrated battery. I was able to change the System set 3220 mAH to show 10,000mAH on the Note 4. (See screenshots) I am working on seeing if it finally calibrates accurately now. If it does, this fix could possibly work across mostly ALL Android Devices with Root that use a Extended battery. The app I used is called Charging time. You can use this to check your Battery mAH and Voltages. https://play.google.com/store/apps/d...chargingstatus
The issue is that you don't edit the Framework-res power_profile.xml. Even when you edit that file, the system will still see it as a 3220mAH Battery. You have to edit sys/class/power_supply/battery.
The problem with this is that you can't use a XML or Text editor to edit it, nor will you be able to change permissions or edit the file via a File Root Explorer. You have to get Terminal Emulator and type in this command:
su
echo mA > /sys/class/power_supply/battery/charge_full_design
Replace mA with the mA of your Battery (10000 for 10,000 mAH battery)
So you should have this entered in emulator:
echo 10000 /sys/class/power_supply/battery/charge_full_design (All in the same line)
Once done, just reboot and use the App Charging time to confirm. I am running test to see if it is more accurate but it's a start. At least we will know where the fix could possibly be. I can say that the Battery level isn't dropping as fast like it use to be.
Does this actually work?
Doesn't work.
Doesn't work.
n910c
does this work on exynos variant?
didnt work (using the > ) also.
Verizon Note Edge DE
Possible to chmod it first?
The Battery life of my Galaxy S10 SM-G973U isn't really as good as I expected it to be. I bought it as a refurbished phone approximately 9 Months ago. When I fully charge the phone and then watch the battery voltage in for example Accubattery, it says 4.270V. However the charge voltage of the Battery is 4.35V. When I do the same on the Galaxy s7 the with the factory original battery, it says 4.35V. I once read that samsung does that in order to protect the battery when it gets older. But if that was the case, a battery replacement would be useless as the new battery would never get charged to 4.35V. Does everybody know if this is really the case and if there is a fix for this Limitation? Thanks in advance.
Fast_Lessy
I wouldn't worry about it. Monitor your SOT times. A heavily used (or abused) battery may need replaced every year. Just part of regular maintenance. When it gets to 80% of it original capacity replace it to prevent a failure.
Any swelling is a failure, replace immediately.
100% charges aren't desirable anyway...
Well my SOTs are around 3.5hours on a normal studying day and about 5h at the weekend with a lot of Youtube watching. They aren't bad but I see people with 5hours+ on normal usage and 8 hours with watching youtube. I just like to optimize and cant really reach the good SOTs.
Fast_Lessy said:
Well my SOTs are around 3.5hours on a normal studying day and about 5h at the weekend with a lot of Youtube watching. They aren't bad but I see people with 5hours+ on normal usage and 8 hours with watching youtube. I just like to optimize and cant really reach the good SOTs.
Click to expand...
Click to collapse
I'd expect better SOT if optimized. Constant high current drain is harder on the battery as well as inconvenient.
For starters ditch trash apps like all social media apps, none should be installed. They are security risks and battery hogs.
Use manual brightness control and stay under 50%.
It seems you are having the same problem I had when I replaced the battery on my Galaxy S10+. AccuBattery tells me I only have 75% battery left. So I bought a new battery, replaced it. And the capacity was exactly the same. The battery was only charged to 4.18V max.
This is my solution:
- Back up your device with Samsung's "Smart Switch" Windows app
- Root your phone with these tutorials:
- Install Ghost commander, enable root access in it
- Go to /efs/FactoryApp/ and copy the batt_discharge_level file to your storage
- Edit the file and put the number 100 there (that means 1 battery cycle, you can change it to a bigger number if you have older battery)
- Copy the file back to /efs/FactoryApp/ replacing original one
- Change the owner of this file back to "system" and the group "log"
- Dial code *#9900# and reset the battery information there
- Reboot the phone (it should now charge at 4.35V)
- Unroot device by flashing original AP file, relock bootloader, disable OEM unlock
- Restore data with Smart Switch
frogale said:
It seems you are having the same problem I had when I replaced the battery on my Galaxy S10+. AccuBattery tells me I only have 75% battery left. So I bought a new battery, replaced it. And the capacity was exactly the same. The battery was only charged to 4.18V max.
This is my solution:
- Back up your device with Samsung's "Smart Switch" Windows app
- Root your phone with these tutorials:
- Install Ghost commander, enable root access in it
- Go to /efs/FactoryApp/ and copy the batt_discharge_level file to your storage
- Edit the file and put the number 100 there (that means 1 battery cycle, you can change it to a bigger number if you have older battery)
- Copy the file back to /efs/FactoryApp/ replacing original one
- Change the owner of this file back to "system" and the group "log"
- Dial code *#9900# and reset the battery information there
- Reboot the phone (it should now charge at 4.35V)
- Unroot device by flashing original AP file, relock bootloader, disable OEM unlock
- Restore data with Smart Switch
Click to expand...
Click to collapse
Not worth all that trouble; under charging the battery will only increase its lifespan.
After replacement cycle 3 times from 100 to 20% to calibrate.
Never depend on SmartSwitch to backup critical data as it can fail you miserably. Always copy/paste critical files/folders instead.
Cycling from 100 to 20 will not help. Max charging voltage will be lower than 4.35V. Rooting is needed.
frogale said:
Cycling from 100 to 20 will not help. Max charging voltage will be lower than 4.35V. Rooting is needed.
Click to expand...
Click to collapse
I try a forced reboot, clear system cache and there may be other options in hidden settings ie abd edits.
Rooting is overkill unless you want to root it to begin with. Win-win if so...
Thanks for your answers. The Problem is I don't want to root my device or play around with the Firmware because it's my main device. I was hoping that there's a way to reset the cycles without the need to root or reset the device. If that's not the case, I won't change anything to be on the safe side.
But I apprechiate you guys for the help and answers.