friends I give some tips to those who complain of the Ram & The wear of the battery:
1) Use The Gemini App Manager (free on google play) and from blocking the autorun all unnecessary applications
2) Get in the recovery mode and delete the statistics of the battery, then charge your phone off to 100%,
3) then without disconnecting it, Light it. and use this application (Battery Calibration) (google free play) and calibrate your device, then disconnect the charger.
4) use until it is 100% downloaded, and when you give your next load before loading open this application (battery dr. repair) (payment is playstore) loading until the application tells them completely.
5) from now on, use it to have 20% of battery, and then off without interrupting Please charge to 100%, to meet the proper charge cycles the battery, and thanks to gemini app manager. their applications will consume no ram, no wake up the phone when in locked screen, and save a lot of battery.
Other Tips:
1) If your phone temperature rises, let it rest and then continue using it. (Measure the temperature with this app: Battery Doctor Save (Free on google play) If over 38 º, leave to cool, use it consistently below that temperature.
2) Try not to overclock & use roms that have good performance and are well optimized for the use of the battery.
3) Make undervolting helps in some cases to save battery, but is problematic to start the device and in some applications like (Link2SD) because the CPU does not have the necessary energy to work properly and load the application at startup.
4) Try not to leave the device near appliances or products with magnets or magnetic waves, as these discharge the battery faster too.
5) try manter your device away from humid places, or away from the sun (or intense heat) as this can also damage the hardware, plus the battery life
6) if possible .. try not to forcibly remove the battery when the device is turned on .. (if phone is lag, wait for answer) only in extreme cases that do not respond. if you remove the battery there .. and wait at least 1 minute before replacing it.
7) not to use task managers to remove applications, since some applications required (for more than the closures, it will return to open, eg playstore) instead, cerralas manually. or use any task manager that let choose which applications fail to remove (eg, the administrator who brings go launcher prime) (and blacklist those that are necessary and you know it will return to open), pressing the button "clean" .. (Thanks to @korrectmethod)
8) where possible, keep off (Wifi-GPS-Data Synchronization-3G-trafficking funds - Google location services) when not needed. and maintain screen brightness (medium or low) (thanks to @korrectmethod)
Thanks for the Tips. I will take note
Thanks for the tips.
thanks for the tips :good:
thanks for the tips :good: by the way could u explain the 4th step again,did u mean to use the battery till its completly dead and fully charge it again and using this carnglo application
Good list for people newer to android.
AFAIK wiping battery stats isn't necessary as its auto wiped every time you fully charge your phone.
Also, the lipo battery in phones don't really have "memory" like say a ni-cad battery would have.
Be careful with some tasks managers because the way android handles ram, it might hurt your battery by having a service always running and scanning tasks.
The overall best thing you can do is keep brightness down, turn off data/wifi/sync/GPS when you aren't using it, and turn off Google location services when not needed.
Sent from my R800i using xda app-developers app
mmm .. can someone re-explain the 4th tip please
Hey Guys, Recently i Wanted to Use the Stock Xperia Play Battery which has a Capacity of 1500mah, I was shocked at Such Terrible Battery Life and Did Lots of Research and Found How to Prolong my Battery Life by about 2 Hours! ~ Be Warned, U May have Already Seen These Tips!
Guide:
1.) Use a Fairly Debloated Rom
- I Suggest Stock Debloated for Best Performance/Battery Balance!
2.) Set Screen Time Out to 30/15 Seconds
- Settings>Display>Screen Timeout>30/15 Seconds
3.) Turn Down Brightness
- Settings>Display>Brightness>15% (IMO)
4.) Turn off any unused connections
5.) Download and Setup Du Battery Saver
6.) Change the Wifi Sleep Policy to Sleep When Screen Off
- Settings>Wireless & Networks>Wi-Fi Settings>(Press Menu Button)Advanced>Wi-Fi Sleep Policy>When Screen Turns Off
7.) Turn Off Ur Screen After use, dont wait until it turns off itself!
8.) If On ICS or JB Use the Media Kill Script on Boot
9.) Adjust Mobile Network Scan to Manual
- Settings>Wireless & Networks>Mobile Networks>Network Operators>Search Mode>Select Manually
10.) Modify Build.prop, Wifi Scan Interval to 180
- Download & Install Root Browser> Browse to /system/build.prop> Locate "wifi.supplicant_scan_interval=XXX"> Modify to "wifi.supplicant_scan_interval=180"
Thats It!,
Enjoy Your Prolonged Battery Life!
Some say battery calibration is a myth, I'm quite sure it works!
You can give that a try after flashing a new rom to improve your battery life! :victory:
(the guide is tested but still i'm not responsible for any demage to your phone)
1. you need a recovery to access a specific file
twrp works
2. you need the xposed app: disable low battery warning (or a likely name)
(for that you can fully dischage your phone)
3. you need a battery discharger app this one: Fast discharge
(for that you can faster discharge)
4. you activate the xposed app and discharge your battery with the app (set the app to discharge to 0%)
(i wouldn't activate the light or the vibration since i don't know if they can overheat for discharging the battery)
5. set the governor to performance to have a faster discharge
6. your phone will kind of be fully discharged and just turn off at maybe 5% battery or later
7. charge your phone just plug it in until it's 100%
(i couldn't boot like that to the system so i had to reconnect after 100% charging which isn't the right way to calibrate battery)
(so if you can then boot whilst charging or plug back in after booting on 100% quickly)
8. enter the recovery and search for this file:
> /data/system/ batterystats.bin
then reboot
thats all!
More info about the myth here. I only calibrate my bat when I feel it needs to be calibrated, even being a myth:laugh:
P.S: or you can download a battery calibration app from Playstore.
The myth of "calibrating the battery makes it last longer" was dispelled by Google's own engineers. All calibrating the battery does is wipe the battery statistics file that keeps the usage history you see in settings. This is something that happens when the device nears 100% charge anyway so its pretty much useless to do it.
As for "the right" way to calibrate the battery, the OP clearly has no idea what he's talking about... its the battery usage history file, there are 2 ways to delete it - manually or just charge the battery to 100%, neither of those does any harm to the device and neither is better than the other seeing as this whole thing of calibrating the battery is utter nonsense.
To which end I don't really see a reason or need for this thread.
Hello Guys,,This is my first thread for Moto G Forum
This thread will guide you to calibrate your phones battery for best performance
Note: I am not responsible for whatever you do to your phone.
Follow Instructions Carefully...
This method is tested by me and it works fine if followed carefully...
Here You Go -->>
-> Charge phone to 100%
-> Restart phone
-> Wait 15-20 min after you are sure it is 100% (charger should stay plugged in)
-> Now Download Battery Calibrator App from Here
-> Open the app and tap on "Calibrate" (It will need root access).
-> Now restart the Device, and Get ready to unplug the phone and then power off instantly and the phones screen goes off(Note: You have to remove AC Adaptor after the phone's screen goes off and before it starts again)
-> Then press thew power key for 5 seconds to be sure to remove the small amount of current is left in the device, Wait 30 seconds and replace battery
-> Allow phone to boot
-> Run through ENTIRE CHARGE (COMPLETELY DISCHARGE) the battery (whether normal usage or looped media files whatever you have time for)
-> Restart phone to be sure it is totally dead
-> Charge fully one more time
You should be good to go! :fingers-crossed:
Use this to quickly discharge your battery, Click Me
""When I talk of charging it is highly highly recommended you use the AC adaptor and charge with phone off for absolute best results.""
If any queries, You can ask them below...
Hit Thanks Button...
Credits
Even though Google's Engineers have stated many times that battery calibration apps are a waste of time, my jury is still out on it. What I do know is, your method has a serious flaw and that's quickly removing the battery. That's not going to happen in the Moto G and leaves me wondering how you tested it.
Yeah. Not necessary.
Sent from my Moto G 2014 using XDA Free mobile app
Agree, not necessary
....just like the 12hour first charge the salesmen recommend....
Instructions weren't clear enough, pulled out my battery with a crowbar and my phone just went kaboom and now won't boot - HALP!
Edit: fixed by turning it off and on again
While I've had many Android phones, this is the first phone that I decided to use a battery charging controller to regulate how my battery is charged. I just wanted to share my journey with others and encourage others to try this out if you are not already.
Although there are several different battery charging controllers out there (and more than one named "ACC" which makes it even more confusing) I decided to use the Advanced Charging Controller module developed by VR25. I choose this module because I felt it provided the most customization.
Step 1 - Installation
Installing the module is easy. It is listed in the Magisk repository. Simply browse the available modules and find the one titled, "Advanced Charging Controller (acc) created by VR25 @ XDA-developers". There are several ACC modules, so make sure you install the one by VR25 to follow this thread.
Magisk will flash the module and start it automatically. You don't even need to reboot, although it is the only way to clear the Magisk notification that the module will be started at the next reboot.
Step 2 - Changing the Charging Switch Setting
I found that the default charging switch setting (auto) does not work reliably with our phones. Therefore I would suggest changing it using the commands below. Personally I have choose option 2 (battery/charge_disable 0 1) but I listed all the options with the quirks that I have found with each one.
Step 2.1 - open your preferred command line app - I use Terminal Emulator.
Step 2.2 - type "su" and hit enter to gain root
Step 2.3 - type "acc -s s" and hit enter - this is the command that allows us to select another charging switch
Step 2.4 - type what number of the charging switch you want to use.
Here are the available charging switches and the issues I have found with them:
1) Automatic - this switch tries to cycle through the available switches until if find one that "works".
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: No - I found that the phone would charge anytime it was plugged in and below the Pause threshold. It did not seem to wait until the battery level was below the Resume threshold.
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:
2) battery/charge_disable 0 1 :
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:3) battery/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): No - phone begins discharging from battery when Pause threshold is reached but the phone is still plugged in
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: No - may show charging icon when phone is really discharging, especially during cooldownratio times and the chime doesn't always ring when charging resumes.
- Suffers from wakelock issues when phone is plugged in but not charging: No
- Other issues: The phone seems to follow the cooldown charge/discharge times even before reaching the cooldown threshold. I find the phone pausing for 10 seconds (my cool down ratio) when the batter level might be a 50% - long before the 60% cooldown threshold I have set in the config file.4) dc/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:5) battery/charge_control_limit 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:
Step 3 - Configuration
You can configure the ACC controller using a couple of different methods. You can do everything using command lines, you can use the beta ACC app (see note below), or you can edit a config file that ACC creates when it is installed. Personally I found that editing the config file was the quickest and easiest method to make general changes.
The ACC config file is found at /storage/emulated/0/acc The file is named "config.txt" You can open the file with a text editor. I personally use the app Root Explorer. I long click on the file name, and then press the three dot button in the upper right hand corner. Choose "Open in Text Editor" and the config file will open and allow changes to be made. Saving the file will automatically push the changes to ACC, you do not need to reboot or restart the ACC daemon for changes to take effect.
I won't go into a lot of detail about all of the different configuration options here as the developer's xda thread is the best place to get that type of information. But I will talk about the most basic setting - the "capacity" setting. It is the second setting listed in the config file and it should look something like "capacity=0, 60, 70-80". Here is a break down of what those numbers mean:
- The First Number (0): is battery level were the phone will shut off. The default setting of 0 means the phone will turn off when the battery level hits 0. Personally I don't want my battery completely draining, so I have it set at 5.
- The Second Number (60): is the battery level where the module starts it's "cool down" functionality. Cool down (listed as coolDownRatio in the config file) is where the phone will stop charging briefly and then restart charging. The default "cool down" setting is coolDownRatio=50/10 which means the phone will charge for 50 seconds, and then stop charging for 10 seconds before charging again for 50 seconds, etc, etc, etc. This is designed to keep the battery temps low. A battery with a charge level less than this number (60 in this example) will charge without pausing, but when the battery level gets to this number or above, the phone will charge and pause based on the coolDownRatio.
- The Third Number (70): is the "resume" value. If the phone's battery level is below this resume value, the phone will charge. If the battery level is at or above this resume value, the phone will not charge even while plugged in.
- The Fourth Number (80): is the "pause" value. This is the battery level where the phone will stop charging and should not charge above this value.
The default settings are set this way because research has shown that a phone's battery will last the longest with the least amount of battery capacity loss if it is charged to a max of 80% of the battery's capacity, and allowed to discharge just a small amount (10%) before being charged again. I realize this goes against the old "wives tale" that our phone's batteries have a very limited number of charges and it is best to limit the number of charges by only charging the phone when it gets to a low level. This is not true in actual battery performance however and if you charge like this, you are actually decreasing your battery's life expectancy and performance.
Obviously the default settings may not be the best setting for you. The default settings are probably only practical for a device that is plugged in 100% of the time. Personally I have changed my capacity setting to capacity=5, 60, 70-90. This means my phone will turn off when the battery level reaches 5% (something it has never dropped to yet), it is charged to a max of 90% and will discharge to 70% before charging again, and the cooldown charging cycling starts when the battery is 60% or higher. Obviously I'm not on my charger all the time, so it is very common for my battery to drop below 70%. However, if the battery is below 70% and I have a charger at my disposal, I am going to charge the phone back to 90% rather than let it the battery levels continue to fall.
Final Notes and Misc Thoughts
There are lots of other options and commands you can use in ACC. Feel free to share any changes you like to make, or post if you are having problems getting the module to work as expected on the 3a. I hope this helps some people feel give the module a try.
There is an ACC app that is available now that allows you to control some of the settings from a nice GUI. I personally did not like using it as I found it would overwrite settings in the config file that I was not intending to be changed.
There is an ACC telegram group if you want to join and have direct communication with the developer and others.
Thanks to @jellopuddingstick for educating me on what the battery idle mode does and why it is beneficial to have it working!
if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.
pbanj said:
if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.
Click to expand...
Click to collapse
This is why I always use a low current charger unless I absolutely need a quick charge. I have used the Dash charger that came with my OnePlus 5 only about 10 times in 2 years.
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
sic0048 said:
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
Click to expand...
Click to collapse
I was having issues with ACC not working before installing the apk. I'll report back if I have any issues.
Nice guide BTW.
I've continued to edit my original post to provide as much information about the different charging switches and the issues I see with each one. Hopefully it is easy to understand.
I still find myself defaulting to the 3rd charging switch option and while it can act a little erratic sometimes, it does work normally most of the time.
I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.
sic0048 said:
I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.
Click to expand...
Click to collapse
I've been using the apk auto switch, no issues.
Is this working for anyone:
usb/current_max:500000
I have is set in the app as an On plugged option and It is not working for me.
gargleblarg said:
I've been using the apk auto switch, no issues.
Click to expand...
Click to collapse
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.
sic0048 said:
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.
Click to expand...
Click to collapse
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
@creeve4, I can't get the On Plugged options to work either. I tried "./usb/current_max:500000" and "usb/current_max:500000", I tried unplugging/plugging in the charger, resetting the daemon, still no luck. The settings were saved to the config file correctly. No idea.
gargleblarg said:
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
Click to expand...
Click to collapse
Interesting. That's unfortunately not what I experience.
I just tried the auto setting and plugged my phone in and it immediately went into what I am calling a "maintenance charge". It was only charging the phone by about 200 mA. I set the charging switch back to #3, unplugged and replugged in the phone and it is charging at about 1200mA which a pretty normal charging current for me.
It's this same roughly 200mA charge that I have seen previously with the auto setting after the phone reaches the set pause threshold - so the phone charges at normal current levels and then drops to the 200mA current after reaching the pause threshold. Admittedly, I did not allow the phone to reach the pause threshold this time (which would take forever at 200mA), but seeing that charging level at all leads me to believe that the auto charging switch is still not working for me (it should either be fully charging or full discharging). I suspect because the phone was above the resume threshold it defaulted to this maintenance charge (thinking the phone shouldn't be fully charged until it dropped below the resume threshold).
sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
What was the battery level when you plugged it in?
sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
That is interesting, have you tried updating yet?
I should also mention that I have only changed the percentage to 3% for the phone to shut off, the rest of the options are default.
Is anyone else getting the following message in the acc app after updating to the latest version?
creeve4 said:
Is anyone else getting the following message in the acc app after updating to the latest version?
Click to expand...
Click to collapse
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.
sic0048 said:
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.
Click to expand...
Click to collapse
I just needed to update to the latest app version. The module was updated before the app.
Did anyone else lose their config settings when updating the ACC module recently? I updated a day or two ago and woke up to my phone at 100% charge. I started troubleshooting and found that the config file was set to all the default settings. This means the charging switch was set to "auto" which has never worked for me and it explains why the module didn't pause the charging at the default pause setting (80%).
The release notes talked about a lot of changes in the config file, but it never mentioned that users would lose their settings and be reset to default. I was just curious if anyone else experienced the same thing or not.
There's a bit of misinformation / misunderstanding going on here, I think. The best control file for our devices is battery/charge_disable. The "maintenance charge" (ACC refers to it as "idle mode") you're referring to is a good thing! This is explained both in the ACC readme [1] and by the developer of Battery Charge Limit [2][3]. The ping-ponging between the upper and lower thresholds is a fallback, it's not the desired mechanism. Hope this clears things up!
[1] "Charging switches that support battery idle mode take precedence", https://github.com/VR-25/acc/blob/master/README.md
[2] https://forum.xda-developers.com/showpost.php?p=76523599&postcount=1834
[3] https://android.stackexchange.com/a/200037
umm, i would be happy if someone give an advice to me the best configuration for the best battery charging cycle, anyone can help me?