[MOD][TOOL] MaxLife v1.0.9c - Battery Lifetime Extender - Moto G Original Android Development

If your are using LP or MM and having issues, please check out the detailed guide from @the_poolee, right below the downloads
This is a native program for Android that addresses the wear done on Lithium-ion batteries by prolonged elevated voltage, high-resistance, and high heat charging. With lithium-ion batteries it is recommended to not quite charge to full capacity or keep the battery on the charger at an elevated voltage for lengths of time because making this a regular practice will rapidly degrade the battery.
Using apps that alert you that charging has completed or is 90% complete may be helpful but aren't always practical or convenient, such as over night charging, or as in my case a phone case with built in battery that charges itself and the phone at the same time, but it charges much more slowly and keeps the phones battery voltage elevated even after the phone has reached 100%.
I created MaxLife to make the handling of said situation convenient and entirely automatic. MaxLife runs as a background system service that interacts with the power_supply subsystem. Using a value chosen by you for the target battery percentage (or 90% default if not provided) monitors how far along your charge is until either you've disconnected the power source or your battery has charged to the target level you set. Upon reaching the target it stops the charging of the battery (even though the charger IS still connected) and suspends charging for a minimum of 15 minutes. After 15 minutes have passed however it still will not restart charging until the battery has fallen below your desired charge level.
This is perfect for trading a small amount of the battery's capacity for a longer and more reliable life of operation. Aside from keeping your battery's charge capped at the desired level it also beats the shortcomings of having to leave your phone unplugged overnight by assuring that it will be charged to the chosen percentage when you're ready to use it not leaving you with a potentially discharged battery due to overnight idle drain (whatever the cause may be e.g. wakelocks).
Prerequisites:
• init.d support
• custom recovery
• Qualcomm device
• A fairly complete busybox install. Toolbox and toybox won't cut it.
INSTALLATION:
Setting it up is simple. At the bottom of this post will be a recovery flashable zip. It installs two files onto your system partition: the MaxLife binary and an init.d script. To choose your target battery percentage first install the package, and use the settings editor described below (title of that section is in bold) (default is 85 in init script and tool is hard coded to 90 if no value or an invalid one is supplied).
New Feature:
Built in settings editor
Optional settings file
Live settings changes (no reboots)
Auto-BattStat Reset
Charge Rate Control
MaxLife now accepts a second argument to set the rate of charge (by changing the input current that is accepted). Valid values are slow, normal, and turbo. If no second argument is supplied in the init.d script or on the command line MaxLife defaults to "normal" (which means no change, system default). The default value in the installer zip is "slow".
slow- Will take somewhat longer to charge, but the battery will remain much cooler during charging and it places less stress on it, prolonging its operational life.
normal- Nothing is adjusted. Equivalent to leaving the option blank.
turbo- Fast charging for those scenarios where time is valuable and you need to get as much into your battery as fast as you can. Hotter charging temperature and more stress/risk to battery and charging components. Recommended to be used sparingly.
This parameter can be set in the init.d script just like the percentage setting.
NEW BUILT-IN SETTINGS EDITOR
There is also now a very straightforward and self-explanatory GUI with MaxLife for settings management now.
To change the settings override/live settings file from MaxLife itself from the command line, just use a terminal app and (as root/superuser) run:
Code:
maxlife set 70 slow
or
Code:
maxlife set slow 70
The options after set can be in either order and equally valid. If your settings are invalid you will get an error message saying so, otherwise it'll display an output of the newly applied settings. REMEMBER: It only takes options in lower case.
IMPORTANT:
If you do edit 91bms, please be sure your text editor is saving the file using UNIX text format. Other formats break the installation. I use the built in editor in ES File Explorer as my editor of choice because it let's you see what format you are saving text files in.
Uninstall:
Delete /system/etc/init.d/91bms and /system/bin/maxlife
This tool is very safe in its interactions with your device, but I am not liable for anything that happens to your device.
It is tested and confirmed working on the Moto G and ZTE Speed both running 4.4.4; however it was designed with the goal of Lollipop/Marshmallow compatibility as well as compatibility with any Qualcomm chip set, so if anyone wants to help test and confirm all and any aspects of compatibility feel free to lend a hand.
LICENSE:
By downloading and/or using MaxLife, you are showing that you accept the terms of this license.
This project is my own proud work, so please be respectful and do not redistribute, sell, modify, or reverse engineer the MaxLife binary and the data contained therein in any form or manner without first acquiring my permission and also giving due credit upon redistribution after receipt of my permission.
This software is being provided free of charge with no guaranteed nor implied warranty. I also hold no responsibility or liability for any damages direct or indirect that come to your person, property, or device from the use of MaxLife.
I also retain the right to modify the terms of this license at any time without having to give any notice of modification.
ENJOY!!!
MaxLife v1.0.9c Unified:
(UNINSTALL older GUI like normal app first)
https://drive.google.com/file/d/0B_hgNZE_j5sVVkJPM2hnWFVId1E/view?usp=drivesdk
If your are using LP or MM and having issues, please click below to open a detailed guide from @the_poolee
From the_poolee:
Well as our beloved @elrod16 seems rather hesitant to upgrade to later android versions, he asked me to do a post regarding proper setting for Maxlife in LP/MM. I should clarify beforehand that I'm no dev nor do I have any coding knowledge. I just happened to find a solution for a persistent issue that most of us on LP/MM faced. And if it matters, I'm currently on CM13 (Android 6.0.1 Marshmallow), with Maxlife v1.0.7. I don't have Xposed or other addons, except for Greenify, working in Root mode. So here it goes....
The first and foremost thing to remember is that Maxlife doesn't have any front end UI with quick toggles @elrod16 seems to be working on it). But it doesn't mean that the actual stuff that works behind screens is completely hidden from root level apps like Greenify and native Doze in MM. And therein lies the core problem.
Since CM13 got some issues with init.d(as per my understanding, it doesn't have it), I used the terminal commands. The charging rate setting and even charge level setting, all worked. My sole issue, then, was that under an unattended night-charge session, the charging went beyond the set values. Since everything was okay in the short-run trial, I assumed something was messing up in the extended session. I couldn't think of anything other than Greenify and Doze at that moment.
In Greenify for MM, there are Shallow Hibernation and Aggressive Doze options. And of course, Automatic Hibernation is also there. Like any other battery - life - caring - guy out there, I had all of these options turned ON. Talking about Doze, it is another factor that may mess with proper Maxlife working. But as per my understanding, doze mode doesn't kick in when connected to a charger. The extra Doze setting in Greenify is just an extension of the normal Android back-end doze,wherein Aggressive Doze puts the device into doze faster than usual, but again, not when charging. Besides, @elrod16 had done some tweaks to ensure that Maxlife is not suspended unnecessarily in Doze(via wakelock). So doze cannot be the culprit. Even then, I tried turning each one off, and voila, guess what, as soon as I turned off Automatic Hibernation in Greenify, Maxlife settings persisted - charging never went beyond the set limits - even through full night charge sessions. I just solved the issue then and there. But I should add that for guys using Greenify in Xposed mode, the behaviour may be different.
In a nutshell, my observation is that apps like Greenify may interfere with Maxlife and hence, make sure that all of them are disabled, or at least, their automatic modes are disabled. Doze may not have been the problem child in my case, but even then, try turning off such Aggressive doze options or instant doze modifiers, if nothing else works.
NOTE: auto charge resume may not work with portable chargers because they often power down after the connection is dropped.
Also any relevant feature suggestions, bug reports, or other design suggestions are always welcome.
Changelog:
v1.0.9c- Split the engine and GUI into separate downloads until this issue with flashable updates and the GUI is resolved. The engine has also been tweaked so that resource hungry apps running in the forground are less likely to make MaxLife miss its target because it was forced to wait for its turn to run. It adjusts its niceness and I/O priority to accomplish this.
v1.0.9a- Now every 10 boots MaxLife forcea the battery guage to synchronize with the battery's internal reading to prevent drift in readings from not allowing full charge cycles.
v1.0.8a- Graphic user interface added with bug in mode setting in test version of UI fixed.
v1.0.7- Rolled the charge delay back to 15 minutes. Improved the wakelock code so that during the charge delay time if you disconnect your device from the charger it'll release the wakelock but continue counting the delay. Old versions the wakelock stayed on during the charge delay whether the device was connected or not.
v1.0.6- Lowered the charge waiting delay to 3 min. MaxLife now keeps the device from suspending while connected to a power source. This is experimental and aimed at fixing the issues with deep sleep. MaxLife has its own settings editor now for the live settings feature. Eliminates any possibility of the file being saved in DOS format.
V1.0.5a- Fixed a bug in a block of code shared between MaxLife and MaxOpt where data wasn't being thoroughly validated before being used.
v1.0.5- Now whenever the settings are changed using the new "on the fly" way, an update of the new settings is written out to logcat, just useful for individual debugging or troubleshooting. This message is at the Verbose priority/level/filter in logcat.
v1.0.4b- When launched from a terminal app (such as for testing) MaxLife now prints out the settings it initially detected and will use. There is also a new way of configuring the settings that also allows "live" changes, changes that will take effect without a reboot or restarting the tool.
v1.0.3- MaxLife now automatically resets your system battery usage stats when it hits the charging cutoff set point. The settings app battery page should no longer endlessly fill up.
v1.0.2- Added a kernel level suspend block (rather than app runtime PowerManagerService.Wakelocks) to fix issue of the tool missing the charge cutoff from deep sleep. Suspend block is released as soon as charging is stopped or charge cutoff is met. Changed default percentage in init.d script to 85.
v1.0.1b- Fixed a small mistake in the installer zip layout.
v1.0.1- Introduced charge speed setting. Details above in post in "New Feature" section.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

I always leave my phone to charge overnight. Flashing it now on Exodus 5.1.1.

For me it didn't worked , charging didn't stoped at 90%
---------- Post added at 01:48 AM ---------- Previous post was at 01:47 AM ----------
Resurrection remix custom rom lp 5.1.
Xt1033 Dual Sim.

BhavikRB said:
For me it didn't worked , charging didn't stoped at 90%
---------- Post added at 01:48 AM ---------- Previous post was at 01:47 AM ----------
Resurrection remix custom rom lp 5.1.
Xt1033 Dual Sim.
Click to expand...
Click to collapse
Was the phone booted? Also some devices the charging icon may stay on but the device is in fact not accepting charge and the percentage wont rise.
Running "ps | grep maxlife" in Terminal app should show if it is running. If it isnt running try running "maxlife 90“ or such in the terminal and see if it does launch or returns an error.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

If anyone is having any issues with this tool please inform me of the issue, your ROM, kernel, and any other charging/power management apps you have installed. Troubleshooting/debugging is an interactive process, no program is perfect, but providing me with your bug reports and helping me test new updates and fixes gets us one step closer and helps me provide the functionality you were looking for.
On the other hand if this program did help you, please hit the thanks button and help keep motivation to continue development strong thanks everyone
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

Hi, suscribed to your topic for following ...will surely try your tool soon and keeping you informed...
Thanks for your work and keep your motivation strong

After flashing the 91bms is not in the int.d file

Ohhdayumm said:
After flashing the 91bms is not in the int.d file
Click to expand...
Click to collapse
It looks like i made a goof when packaging the installer zip. The link in the OP has already been updated, see if that one flashes correctly for ya.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

elrod16 said:
It looks like i made a goof when packaging the installer zip. The link in the OP has already been updated, see if that one flashes correctly for ya.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Click to expand...
Click to collapse
no problem Ill try it when I have time today and I'll tell you if it works thanks for the work!

Hi thanks for the script! It does work the charging stopped at 89%

This only works on moto g?

Ohhdayumm said:
This only works on moto g?
Click to expand...
Click to collapse
No, in theory it should work on a variety of Qualcomm based devices. I can confirm that the ZTE Speed is definitely supported.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

Which value do you recommend for better battery life?

abeloman said:
Which value do you recommend for better battery life?
Click to expand...
Click to collapse
For the best battery longevity I'd probably use "70 slow" but for a good balance of longevity and capacity I'd probably use either "85 slow" or the default settings.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

Its really working

@elrod16 :
And if you want to remove it totally ? Enough to let it in place and change value to 100, for example ? (just an idea, i'm testing it for moment, don't want to remove it yet )
One more : Nice, that selection of charging modes...just a little bit difficult for those who don't know how to edit a file. GUI, maybe, or best solution, integration in a kernel and settings avaible in Kernel Adiutor (or any other apk) ???

satanas17 said:
@elrod16 :
And if you want to remove it totally ? Enough to let it in place and change value to 100, for example ? (just an idea, i'm testing it for moment, don't want to remove it yet )
One more : Nice, that selection of charging modes...just a little bit difficult for those who don't know how to edit a file. GUI, maybe, or best solution, integration in a kernel and settings avaible in Kernel Adiutor (or any other apk) ???
Click to expand...
Click to collapse
Hey thanks for testing! To effectively disable it without removing any files you could change the settings to "100 normal" and to actually uninstall it, delete /system/etc/init.d/91bms and /system/bin/maxlife. Those two files are the whole mod.
I would like to make GUI's for my different mods I've posted :/ but alas, my phone is my development environment, so if it can't be made with GCC I can't do it. However....I think Tasker App Factory could be able to cook something up that could handle a simple task like editing those settings, so when time allows, I will probably go that route. Thanks for the input and suggestions
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

Working perfectly on Resurrection Remix LP Final Build. Thank You.
Moto G XT1033

elrod16 said:
Hey thanks for testing! To effectively disable it without removing any files you could change the settings to "100 normal" and to actually uninstall it, delete /system/etc/init.d/91bms and /system/bin/maxlife. Those two files are the whole mod.
I would like to make GUI's for my different mods I've posted :/ but alas, my phone is my development environment, so if it can't be made with GCC I can't do it. However....I think Tasker App Factory could be able to cook something up that could handle a simple task like editing those settings, so when time allows, I will probably go that route. Thanks for the input and suggestions
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Click to expand...
Click to collapse
You"re welcome
One more suggestion :
Put the tips for uninstall in OP...

elrod16 said:
This is a native program for Android that addresses the wear done on Lithium-ion batteries by prolonged elevated voltage, high-resistance, and high heat charging. With lithium-ion batteries it is recommended to not quite charge to full capacity or keep the battery on the charger at an elevated voltage for lengths of time because making this a regular practice will rapidly degrade the battery.
Using apps that alert you that charging has completed or is 90% complete may be helpful but aren't always practical or convenient, such as over night charging, or as in my case a phone case with built in battery that charges itself and the phone at the same time, but it charges much more slowly and keeps the phones battery voltage elevated even after the phone has reached 100%.
I created MaxLife to make the handling of said situation convenient and entirely automatic. MaxLife runs as a background system service that interacts with the power_supply subsystem. Using a value chosen by you for the target battery percentage (or 90% default if not provided) monitors how far along your charge is every 30 seconds until either you've disconnected the power source or your battery has charged to the target level you set. Upon reaching the target it stops the charging of the battery (even though the charger IS still connected) and suspends charging for a minimum of 15 minutes. After 15 minutes have passed however it still will not restart charging until the battery has fallen below your desired charge level.
This is perfect for trading a small amount of the battery's capacity for a longer and more reliable life of operation. Aside from keeping your battery's charge capped at the desired level it also beats the shortcomings of having to leave your phone unplugged overnight by assuring that it will be charged to the chosen percentage when you're ready to use it not leaving you with a potentially discharged battery due to overnight idle drain (whatever the cause may be e.g. wakelocks).
Prerequisites:
• init.d support
• custom recovery
• Qualcomm device
INSTALLATION:
Setting it up is simple. At the bottom of this post will be a recovery flashable zip. It installs two files onto your system partition: the MaxLife binary and an init.d script. To choose your target battery percentage first install the package, remount system as RW by whatever means you want, using a file explorer navigate to /system/etc/init.d, open the file 91bms, and change the number within to whatever you choose (default is 90 in init script and tool is hard coded to 90 if no value or an invalid one is supplied).
New Feature:
Charge Rate Control
MaxLife now accepts a second argument to set the rate of charge (by changing the input current that is accepted). Valid values are slow, normal, and turbo. If no second argument is supplied in the init.d script or on the command line MaxLife defaults to "normal" (which means no change, system default). The default value in the installer zip is "slow".
slow- Will take somewhat longer to charge, but the battery will remain much cooler during charging and it places less stress on it, prolonging its operational life.
normal- Nothing is adjusted. Equivalent to leaving the option blank.
turbo- Fast charging for those scenarios where time is valuable and you need to get as much into your battery as fast as you can. Hotter charging temperature and more stress/risk to battery and charging components. Recommended to be used sparingly.
This parameter can be set in the init.d script just like the percentage setting.
This tool is very safe in its interactions with your device, but I am not liable for anything that happens to your device.
It is tested and confirmed working on the Moto G and ZTE Speed both running 4.4.4; however it was designed with the goal of Lollipop/Marshmallow compatibility as well as compatibility with any Qualcomm chip set, so if anyone wants to help test and confirm all and any aspects of compatibility feel free to lend a hand.
This project is my own proud work, so please be respectful and do not redistribute MaxLife in any form or manner without first acquiring my permission and also giving due credit.
ENJOY!!!
MaxLife v1.0.1b
https://drive.google.com/file/d/0B_hgNZE_j5sVaURLeXpDNUYyTkk/view?usp=docslist_api
NOTE: auto charge resume may not work with portable chargers because they often power down after the connection is dropped.
Also any relevant feature suggestions, bug reports, or other design suggestions are always welcome.
Changelog:
v1.0.1b- Fixed a small mistake in the installer zip layout.
v1.0.1- Introduced charge speed setting. Details above in post in "New Feature" section.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Click to expand...
Click to collapse
How to roll back changes? My phone is lagging after flashing this zip in my moto g1(falcon) in marshmallow.

Related

Diamond battery voltage

In need to know the voltage across the diamond standard battery (900mAh) when the battery is fully charged and when the battery is fully discharged (the phone automatically switched off)
Could someone give me this information?
When my battery is low I read 3.2V
When my battery i high I read 4.1V
Is this correct?
That's about right, +-.1
Thanks, I've a lot of problems with the charging and discharging cicles, this information could help me to understand
While which is the charge current when the battery is fully discharged?
For my Diamond it can be very high, up to 800mA (I know it from BatteryStatus), it is a normal value?
wasm said:
While which is the charge current when the battery is fully discharged?
For my Diamond it can be very high, up to 800mA (I know it from BatteryStatus), it is a normal value?
Click to expand...
Click to collapse
Try a program, "PowerGuard", it's a very nice (and free) program developed by Muyz that will give you current and temp info, including graphs with a lot of flexibility in settings. You can get a good feel of where the current draws are. I think charge current is in the area of 700-800mA on initial charge.
Or another called Battlog. It,s better because it logs the measurements - on Powerguard it's difficult to see the actual (current, not in electrical, but in time sense ) measurement.
Thanks I'm going to try them
For now I'm testing Batlog...
This evening I'm going to make a full charging log, so I could post it tomorrow
Could you do the same? This could give me the possibility to compare them
I'm experimenting some problems with the charging circuit
mjaxa said:
Or another called Battlog. It,s better because it logs the measurements - on Powerguard it's difficult to see the actual (current, not in electrical, but in time sense ) measurement.
Click to expand...
Click to collapse
I agree with mjaxa, since your post I've found and installed Battlog. Works great on my Diamond. Very robust program and easy to read the log file or import into excel for analysis.
I have no idea why I didn't find this software when searching for a good battery monitor for my Diamond except I must have not used "log" in my searchs.
Thanx mjaxa.......
JRMX said:
Works great on my Diamond. Very robust program and easy to read the log file or import into excel for analysis.
Thanx mjaxa.......
Click to expand...
Click to collapse
I should, of course, also thank Palladium TD now that I've found the source for this fine program.
I'll also add that while the data logging is very good, I found that some of the functions do not work on my Diamond (US ROM 1.93). I know it's a beta program or maybe I just haven't figured it out yet. Using 0.2.3.130 beta I have noted:
No response on the help and other icon on the left side, battery temp read is off by a factor of 10 (noted on the Battlog thread) and cum use (mAh) does not display.
I'll post the comments on the correct thread.
In the following I reported the log of my battery charging cycle in txt and graphic format
If you can post comments or other logs, I'll appreciate
P.s. another bug in Battlog (I'think) is related to the sampling interval, as you can note observing the X axis on my plots: it is not constant in time
No one want help me with a charge/discharge log?
With the holidays I haven't had too much time to work with battlog and the phone use is not typical. I did run about 16 hrs of data and it does give some insight.
Charging overnight looked normal with current draw cycles at 2hr intervals for mail checks.
I was going to upload the excel file, but the format isn't permitted. The txt file is too large. I'll mess with it some more, but I didn't see anything that was unlike your data. 800ma on initial charges, -200ma on using various applications and phone calls, as much as -800ma on internet use and -9 to -20ma on locked standby. I did not see what I'm looking for which is an unexplainable deep discharge, overnight or during the day, I'll keep monitoring.

Analyzing the Standby drain from Android OS

Let me keep this short and to the point. As numerous other users, I am also extremely bothered by the huge Android OS drain while on standby. On average, standby drain is 3% - 4% per hour,which is unacceptable. Let me describe my condition and my findings.
My setup
Stock OpenBeta 10 - 12, stock kernel, with Magisk and greenify. Dual sim (Airtel + Jio). 4G mobile data always active on Jio. Drain remains same if I disable both/ one of the sims, turn off data, or switch to flight mode.
What I tried
Used this command from a PC to check if any rogue app is using too much CPU. It once showed me Google drive was constantly using 6% CPU, but it was an one time bug, rebooting fixed it and never showed up again. Clearly, active usage was not problem, only the standby.
Code:
adb shell top -m 20 -s cpu
Then I checked BetterBatteryStats and I always see such alarming "Wake (Screen Off)" times. As you can see in screenshot in attachment. It is almost 50% of total standby. It might seem if the wakelocks are due to Google Play Services or GoogleQuickSearchBox, but no! Google's app take wakelock only if the phone is already awake, the primary reason of waking up has to be checked by this tool called Battery Historian by Google
To use it,
Download the repository as Zip file from https://github.com/google/battery-historian
Install python 2.7 and add python to your path.
Unzip Battery Historian after downloading as ZIP and go to scripts folder.
Run these two commands in cmd with phone connected in USB Debugging mode
Code:
adb shell dumpsys batterystats > batterystats.txt
python historian.py batterystats.txt > batterystats.html
If you cant get python running, skip the second command and upload the txt file here.
Now you will have a HTML file, possibly around 4-5MB. Opening it takes a bit of time to fully load in browser, like 1-2mins. Be patient.
In this graph, compare your screen, wake_lock* and wake_reason rows. In my case, the wake reason is almost always QCOM SMD-MODEM or QCOM SMD-MPM. And loads of wakelock from RILJ_ACK. Both of these point to possible screw ups from OnePlus at proper optimization of the radio interface.
I am not exactly sure what this means as I don't have much expertise on the kernel level, instead I am an app developer. I highly suspect it is a bug at the firmware/radio level.
I urge everyone to post their own findings and also help in fixing the problem with proper explanation if anyone possesses the kernel level expertise. I have also included my own battery stats in the attachments, if anyone is interested in further investigation
RESERVED

Tips to get better battery life. With or without root.

General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
beache said:
General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
Click to expand...
Click to collapse
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Craz Basics said:
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Click to expand...
Click to collapse
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Tips for better battery life.
And a lot of common sense.
tuncan said:
Tips for better battery life.
And a lot of common sense.
Click to expand...
Click to collapse
very helpful thanks
chewingum16 said:
very helpful thanks
Click to expand...
Click to collapse
Tnx. :good:
Zombie said:
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Click to expand...
Click to collapse
yes it will on many cases, but I can't tell with the OP5. Is the circuit will cut-off the battery from the phone to avoid drain? If yes, in that case, it won't hurt significantly the battery.
In general , what can hurt li based batteries : time, heat and numbers of time of electrons changing direction.
Having the phone plugged in, every X time the % will drop, and the charging circuit will trigger the battery.
As I said, can't tell how op5 is working, and it probably be minimal anyway. But technically it will reduce the capacity : http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
Heat : 20W charger, even if its a vooc, at one point the battery will get a high current load = heat, and chemical li-po arrangement changes.
Time : cant do nothing here, chemical arrangement will degrade, its a normal process for most battery, specially li based one.
But at the end, not much people would see any difference, since nowadays people changing their phone every 1-2 years, fck ridiculous...
Back to topic :
Pixel off apps , many of them on the play strore, can't tell which one is good or not.
Basically, it will turn off pixels on the screen.
https://play.google.com/store/apps/details?id=com.anrapps.pixelbatterysaver&hl=fr
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
dkryder said:
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
Click to expand...
Click to collapse
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
shangxor said:
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
Click to expand...
Click to collapse
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
dkryder said:
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
Click to expand...
Click to collapse
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
[/COLOR]
shangxor said:
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
Click to expand...
Click to collapse
yes, i offered the link as a punchline to your comment about joking. however i do have a question about your comment,
"He had based part of his study on incorrect data also"
why didn't you include the part of the study and the incorrect data? because, when statement like this is made it is left to the reader to determine the part of the study and the incorrect data which may lead to misunderstandings.

Limit Battey Charge % Android 11

Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge.
Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.
I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.
jljtgr said:
I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.
Click to expand...
Click to collapse
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
This the settings you have?
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
hawkswind1 said:
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
Click to expand...
Click to collapse
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1
jljtgr said:
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1
Click to expand...
Click to collapse
I think that's the custom setting probably restored from your Google backup. Same one I was using. I'm gonna try it again though, thanks
hawkswind1 said:
Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge. Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.
Click to expand...
Click to collapse
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).
v12xke said:
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).
Click to expand...
Click to collapse
Accubattery is fine and all for reporting and giving an idea of where you want to stop charging... but it has no ability to limit charging. The only thing it can do is nag you to take the phone off the charger. This thread is about root applications actually blocking the phone from charging past a certain level without making the user do anything or even notifying the user about what's being done.
I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.
rcbjr2 said:
I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.
Click to expand...
Click to collapse
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.
jljtgr said:
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.
Click to expand...
Click to collapse
Thanks for the reply. The problem is that I use the notification to trigger Tasker profiles, so I was hoping to figure out a way to get it to stop flipping back and forth while also retaining the notification. I think it's just the standard control file since it's a OnePlus phone, but I'm not sure I can figure out otherwise. When I first start using BCL, I found the control file and was able to manipulate it with a SQL editor and Shell commands in Tasker, but I haven't poked around the OnePlus 8T that much yet.
Just as a PSA, I think Adaptive Charging from the January update can conflict with this. On days where I set a morning alarm, I found that my battery was more full than it should be. I suspect that Adaptive Charging does something that Battery Charge Limit cannot block. I won't know for a few days if turning this off in settings fixes things 100% or the January update just really screws with this.
Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com
Well, as a root method it does seem to work. Depending on your taste, it might be cleaner than an app toggling a different variable. Of course you need an app to set the file back to 100 when you want it. Some Tasker widgets work for my purposes... could probably make it a QuickSettings toggle in the shade, actually.
Bottom of that thread, I was wondering specifically if there might be way to force an unrooted device to think it met one of these conditions, so it only charges to 80%.
Specific post link:
Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com
i.e.
... your phone automatically limits charging to about 80% under certain conditions:
Continuous charging under high battery drain conditions, like game play.
Continuous charging for four days or more.
I've done very little research on this, but I expect the ways to fool the phone into thinking those things are happening is even more complicated than using that root file control. Meaning also requiring root but manipulating other control files.
I suppose you could have a case and a ribbon USBC connector that fools the charging logic into thinking it is constantly connected to a hardware charger even though it's still at a net negative power. After 4 days of having the case on, it might work. I don't know why anyone would have already built something like that, however.
I would root my phone but, as my daily driver, I need things like banking apps to work. They (at least some) detect rooted phones and refuse to load as a security measure (which is probably a good thing) :-(
Banking apps are usually just a frontend to their website used API. They have no problem with you using a browser on a rooted phone or Linux PC, etc. Any app that stores sensitive data on your phone and relies 100% on the filesystem being locked down was created wrong and lazily. The only thing about banking apps that might be legitimate is when things like unique CC info is stored for NFC and using a TPM can't be assured. Most banking apps, however, do not store anything sensitive on your phone aside from a login token which all websites also do. (it's called a cookie)
My personal preference is that no app is better for me than being able to root my phone. I don't play mobile games that want to keep you from cheating and I don't even care about Google Pay, which I'm not sure has legitimate need to block root either... they just do it to keep banks happy, which as I suggested, I think they're full of BS.
The only thing more BS than this no-root nonsense from app companies is when carriers do it by locking bootloaders. I try to re-use my phones for as long as possible and without the ability to limit battery charge, the batteries swell and die quickly, every time. It's good news that Google added code where phones plugged in constantly will limit charge automatically... but I doubt there is a way to trick it from the outside. (without root)
Hmmm. Maybe lazy programming, but I'm not ready to change my Bank so I can root my phone
Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.
jljtgr said:
Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.
Click to expand...
Click to collapse
I would like to definitely solve this problem I have been struggling with for years. What did you do, can you please help me? It seems extremely similar to what you wrote here.
I have been using battery charge limit on my Xiaomi Mi Mix (1st model) since android 7.1 (lineageos) (and I might have messed with a couple files, not sure, can't remember). When updating to android 9 (lineageos) couple years ago I started having the problem you described. Also I notice sometimes I plug the phone at safe levels such as 35% or 60% and it doesn't charge same thing. Also it only charges with certain chargers and not others.
Earlier today it was 11% battery, could not boot android, didn't charge. I got the idea for the first time to try booting in TWRP (on+volume up buttons) and it immediately started charging at full speed. So there's obviously nothing wrong in the hardware, it's software or just config.
I would like to definitely solve this problem, but I don't understand exactly what you did on your side to fix it. Please reply or message me if you have any suggestion Thank you!

Question Please help me about battery oneplus 10 pro ver 2213

I just bought this phone, one thing i dont know why because battery's using time is short, only 5 hours. I want to know that everyone the same as me?
You either have a n app eating thru your battery or a faulty battery.
Check in Settings/Battery. If nothing special pops out there, you might want to try a factory reset and see if that still happens.
In the past I also used GSam to get more info on battery usage.
maddler said:
You either have a n app eating thru your battery or a faulty battery.
Check in Settings/Battery. If nothing special pops out there, you might want to try a factory reset and see if that still happens.
In the past I also used GSam to get more info on battery usage.
Click to expand...
Click to collapse
Thanks buddy, what rom are using in phone and the time on screen'battery
Having the same issue with the same model.
Follow the 2nd post.
(SOT) Leaderboard - post your longest SOT's here 👍🏻
Looking at the OnePlus 10 pro on paper, it has everything you would possibly need to achieve incredible screen on times. The idea behind this besides some healthy competition is to whittle out the bugs and battery draining apps and habits.... in...
forum.xda-developers.com
Keep all social apps insta FB and WhatsApp with restrictions of background and foreground activity and keep auto launch off . That's make your battery long lasting. Keep optimization on in battery settings.
U can check other apps which are battery hungry and keep activity restricted.
Do not use always on display function.
dladz said:
Follow the 2nd post.
(SOT) Leaderboard - post your longest SOT's here 👍🏻
Looking at the OnePlus 10 pro on paper, it has everything you would possibly need to achieve incredible screen on times. The idea behind this besides some healthy competition is to whittle out the bugs and battery draining apps and habits.... in...
forum.xda-developers.com
Click to expand...
Click to collapse
As far as I know I am the current leader of the SOT thread with 12.5 hours SOT and 23% battery left, unfortunately I literally didn't even try to get it at first and was in 120hz 1440p (no auto switch) with no battery saver at all lol. If you want a lot of SOT you can cheese it by streaming and doing nothing else thanks to the Snapdragon 8's efficiency with video
jld2k6 said:
As far as I know I am the current leader of the SOT thread with 12.5 hours SOT and 23% battery left, unfortunately I literally didn't even try to get it at first and was in 120hz 1440p (no auto switch) with no battery saver at all lol. If you want a lot of SOT you can cheese it by streaming and doing nothing else thanks to the Snapdragon 8's efficiency with video
Click to expand...
Click to collapse
That would be great. Do you have the screenshots you would need to register your sot?
As per the requirements?
If so I'll be happy to add your time
If you're experiencing rapid battery drainage with your OnePlus 10 Pro, there are a few steps that you can take to solve this issue.
First and foremost, it is important for you to understand why the battery drains quickly. There are several factors that may contribute to this problem, such as the presence of background apps running in the background without your knowledge and an inefficient power management system.
To address the first factor, reducing or disabling any applications running in the background can help improve battery performance significantly. To do so: go into Settings > App Manager > Running Apps, where you can see which apps are currently active on your device. You should close or uninstall any unnecessary apps as they consume energy even when not actively used by you.
For further improvement of your device’s power efficiency, it also helps to recalibrate its internal Power Management System (PMS). This process involves resetting how much power is allocated for different tasks on your OnePlus 10 Pro allowing it to run more efficiently and effectively utilize whatever charge remains in its unit’s battery pack while still providing optimal performance. It is recommended that this procedure be done at least once per month or after factory resets – but no more than three times per month – as excessive PMS calibrations will only lead to shorter lifespan of both software and hardware components over time instead of better performance gains and improved efficiency levels.
Finally if these two solutions fail then eventually replacing/repairing parts inside phone such as motherboard may prove beneficial for fixing Oneplus 10 pro Battery Drain Fast issue permanently however seeking professional help from authorized service centers would be necessary before attempting similar DIY repairs within home due safety related issues involved with components which are sensitive enough handle with proper care & expertise .
Some tips I've shared over the years.
Change 5G to 4G
Remove tiktok it is 100% dodgy Chinese spyware.
Remove Facebook use web based
Remove Facebook messenger use web based
Remove Twitter use web based
Remove any ad based apps pay for the pro version
Turn off gestures like lift to wake
Change from QHD to FHD (No difference)
Allow auto brightness
Turn off WiFi overnight
Turn all updates to manual not auto (play store)
Remove any so you don't use
Change back up to once a month (WhatsApp)
Turn off location history (Google)
Use titanium to remove any system apps you don't need
Don't allow anonymous usage statistics for any app ever.
Don't allow tracking cookies on any website
Use adaway (root needed)
Don't open web pages in Google app (I use Samsung browser)
Don't use xposed.
If you game you will not get high SOT scores, period.
Don't bother with battery saving apps or monitoring apps.
Streamline your apps, if you don't use it, remove it.
Don't allow WiFi scanning (as in letting other apps use it when it's not on)
Never allow personalised ads.
Never allow notifications from websites
Always decline cookies unless your absolutely have to allow some tracking (common sense prevails here)
Optimise as many apps as possible unless it affects performance.
Don't allow apps to remain open in the notification area.
Change your launcher, my preferred launcher is lawn chair and this did actually burn up some battery when compared to the OnePlus launcher.
Don't use live widgets (yes they look cool, but they annihilate your battery)
Live wallpaper, again very cool, but battery burners.
Again! Don't charge overnight, make a note of your percentage then see what it is in the morning, you shouldn't be losing more than 5% really, if you've done well then it'll be reflected here, the good SOT results will follow.
Turn off live read outs of network speed, RAM usage in the status bar.
Turn off NFC unless in use.
Leave location on in quick settings.
Don't overcharge your phone, IE: overnight
Don't allow your phone to fully deplete the battery.
Whatever anyone says, this does 100% damage batteries, there is no argument here and I won't entertain anyone who says otherwise, Ive seen through real life tests what this results in, bloated, inefficient, possibly dangerous lithium batteries.
Keep your phone out the sun.
Keep it out of extreme cold.
Keep your device clean dust free.
Snapchat, Viber, house party, apps like that tends to use more battery as they don't have great dormancy periods.
Apps like speed test by Ookla tend to have location tracking, similarly they tend to turn themselves on and off when they feel like it, my advice, install test and uninstall.
Allow a couple of battery cycles between tweaking sets, to give you an idea of how much of a difference you've made.
Use BBS to see what is being used, once you've removed problems, remove BBS.
I've just written this from the top of my head so o probably missed some things, the general idea is to keep your device clean and fresh, remove files you don't need any more.
Keep an eye on apps that misbehave or aren't wanted, index your folders so they aren't a mess.
The more good things you do means the more potentially bad apps you can have on your phone, eg if you really need Facebook, you could keep it so long as you clean up other areas of your phone.
Good luck.
When it comes to battery optimization for the OnePlus 10 Pro, version 2213, I have a few suggestions that might help you maximize your device's battery life.
Firstly, it's important to note that OnePlus devices generally come with a variety of built-in battery optimization features. To begin, make sure you have enabled the battery optimization settings on your device. You can usually find these settings in the device's "Battery" or "Power" section within the settings menu.
Additionally, I recommend keeping your device's operating system up to date. Manufacturers often release software updates that include battery optimizations and improvements. So, regularly check for updates and install them as they become available.
Another effective approach to conserving battery life is by managing your apps and their power consumption. Identify any apps that are known to drain battery excessively and either limit their usage or consider uninstalling them if they are not essential. You can find battery usage statistics in the device settings, usually under "Battery" or "Power."
Furthermore, adjusting the screen brightness and timeout settings to a level that suits your needs can significantly impact battery life. Lowering the brightness and reducing the screen timeout duration can help conserve power.
Lastly, keeping unnecessary features and connections turned off when not in use can make a difference. Features like Wi-Fi, Bluetooth, and GPS can consume additional power if left enabled unnecessarily.
Maria1991 said:
When it comes to battery optimization for the OnePlus 10 Pro, version 2213, I have a few suggestions that might help you maximize your device's battery life.
Firstly, it's important to note that OnePlus devices generally come with a variety of built-in battery optimization features. To begin, make sure you have enabled the battery optimization settings on your device. You can usually find these settings in the device's "Battery" or "Power" section within the settings menu.
Additionally, I recommend keeping your device's operating system up to date. Manufacturers often release software updates that include battery optimizations and improvements. So, regularly check for updates and install them as they become available.
Another effective approach to conserving battery life is by managing your apps and their power consumption. Identify any apps that are known to drain battery excessively and either limit their usage or consider uninstalling them if they are not essential. You can find battery usage statistics in the device settings, usually under "Battery" or "Power."
Furthermore, adjusting the screen brightness and timeout settings to a level that suits your needs can significantly impact battery life. Lowering the brightness and reducing the screen timeout duration can help conserve power.
Lastly, keeping unnecessary features and connections turned off when not in use can make a difference. Features like Wi-Fi, Bluetooth, and GPS can consume additional power if left enabled unnecessarily.
Click to expand...
Click to collapse
Good post
Would you say the Oneplus 10 Pro is still a good phone for this year even? Very new?

Categories

Resources