Related
I am trying to compile a large list of tips and tricks that we users can use to extend the life of our small batteries.
List is here:
http://android-simplicity.blogspot.com/2009/08/bag-of-tricks-1-increase-battery-life.html
On-Going Power saving List
1. Under-clock your cpu(for root users only). Download->over clocking widget->set cpu speed to lowest value
2. Turn off GPS
3. Reduce the number of start up apps
4. Restart phone
5. Lower screen brightness
6. Turn off Wi-fi when you are not around any wifi networks
7. Turn off 3G Mobile Data Network - Settings--->Wireless Controls--->Mobile Networks and check the box that says "Use Only 2G Networks.
8. Disable auto Data Sync
9. Download and install "Power Manager"
10. Disable back ground apps - [~JDBDogg]
11. Turn off keyboard backlight (for Dream/G1 only for obvious reasons) with Backlight Off app. Only works on rooted phones. [~Chahk]
12. Turn off any unnecessary noises or vibrations, such as for on-screen keyboard and games. [~AdamPI]
13. Make sure your firmware and apps are up to date, efficiency may be improved. [~AdamPI]
14. Use headphones. [~AdamPI]
15. Turn off Bluetooth. [~AdamPI]
16. [~Yours goes here]
If you have any tricks that you use to get the most time juice out of your phone, please share them to the rest of us. Thanks.
Disable background apps
Turn off keyboard backlight (for Dream/G1 only for obvious reasons) with Backlight Off app. Only works on rooted phones.
Chahk said:
Turn off keyboard backlight (for Dream/G1 only for obvious reasons) with Backlight Off app. Only works on rooted phones.
Click to expand...
Click to collapse
nice, one ! didnt think of that~
Lower the time it takes for the screen to time out.
Id also say take off any widgets you may have but i guess that falls underneath the "disable background apps" category
Bluetooth isn't mentioned.
Turn off any unnecessary noises or vibrations, such as for on-screen keyboard and games.
Make sure your firmware and apps are up to date, efficiency may be improved.
I'd guess using headphones is better than the speaker, plus no-one on the bus wants to hear your "music".
Has anyone tested decoding efficiency of video and audio codecs? AAC saves space, but does it use more battery than mp3?
up to 15
AdamPI said:
Bluetooth isn't mentioned.
Turn off any unnecessary noises or vibrations, such as for on-screen keyboard and games.
Make sure your firmware and apps are up to date, efficiency may be improved.
I'd guess using headphones is better than the speaker, plus no-one on the bus wants to hear your "music".
Has anyone tested decoding efficiency of video and audio codecs? AAC saves space, but does it use more battery than mp3?
Click to expand...
Click to collapse
Now thats thinking out of the box. Thanks AdamPI
We have now 15 on the list. Lets see how long this can go~
Someone should do a test using all of these tricks and do a comparison, although it will be a very boring phone at this point with everything off.
Don't use a ROM that requires a linux-swap Partition
This causes the phone to die faster because the sd card is constantly being acessed
jf4888 said:
Don't use a ROM that requires a linux-swap Partition
This causes the phone to die faster because the sd card is constantly being acessed
Click to expand...
Click to collapse
SD Cards are so cheap these days that you shoudn't worry about damaging them. In a weird way though, this advice does make sense. Swap = more apps are being kept in memory, thus more work being performed by the phone, which translates to higher power consumption.
But then again, following this logic a similar advice would be to not run any apps at all. Or better yet, just shut your phone off! Maybe then it will last a full day on a single charge
Seriously though, if you're worried about damaging your phone, read up on Lithium-Ion/Polymer batteries and how to prolong their lifespan. The main points are:
Don't let them get too hot. Heat damages battery cells and cause them to lose their capacity.
Deep discharge cycles (letting the battery drain before fully charging them) kill these batteries fast. LiIon/LiPolymer batteries like to be "topped off" once the level gets to 60-70% mark.
Discharge cycles can improve state-of-charge estimation, so only perform those when the battery meter goes out of whack and doesn't tell the charge level properly. This doesn't happen often.
They don't suffer from the "memory" and overcharge issues that used to plague batteries using older technologies (NiCad/NiMH), so it's safe to keep the phone plugged in whenever you can.
The "first-time cycle" is a myth left over from Nickel-based batteries. This means you don't need to charge the batter for 8 hours the first time you use it.
Do not use "fast chargers" since their usage can decrease the lifespan of the battery.
Get an app that turns off your data network completely (like WiSyncPlus). Not just "use 2G only" but COMPLETELY. I can go a whole weekend, with normal use, without charging my phone if I need to. (From one Fri 6am to Sun 6pm give or take was my best)
The one I use (WiSyncPlus, there are others I guess) turns off the network automatically when I unplug the charger from my phone. Txt msgs piggy back the cellular network so no issue there, otherwise, if I want to jump on the internet or check the weather, I hit the toggle switch on my Home screen...in ~3secs I'm all set again. Toggle back off when finished.
Best $3 by far I've spent on an app for my G1.
i use APNdroid for that
No one mentioned using a ROM that allows changes to the CPU scaling.
I'm on Cyanogen 4.1.2.1 and I have it scaled from 245 to 527 with the CPU only jumping up to the next clock speed when it needs it.
So, most of the time, my phone is on 245 and it clocks to 383 and then 527 as needed. I had overclock widget set so it showed me the current clock speed. Once I was comfortable with the frequency and load under which it changed speeds, I removed the widget from the desktop.
I use my phone a lot and it lasts a full day easily.
if youre using a hero rom there is an option to completely turn off mobile networks so there is no data connecion at all.
i have to go with
turn the phone off
get a car charger
spare battery or extended one
What can you expect from these tips?
*Increase battery life by 3 times compared to a situation without any tip implemented!
My target is to unplug my phone at 6am in the morning and have it around 10% at 11pm. The below tips enabled me to reach this target whereas, without them, I would run out of battery at noon (same usage, of course)!
Disclaimer: I consider that manually "swith off location" or "switch off wifi" as well as having Juice Defender on "extreme" are not acceptable. Why? Because we all need tips that enable battery savings without decreasing the user's experience! If you need to operate manually each time you want to connect and/or have 3G... this is not a solution. If Juice Defender just cut-off every communication and don't let e-mails flow, etc... this is not a solution!
However, for those who want those kind of tips, I created a special section in post 2!
Red % signification: Well, those % in red are gut feeling of "tip contribution" to the total battery saving.
My settings which enable best battery savings without reducing user's experience!
1. Use a NAND ROM
2% of battery improvement
Yes, compared to an SD ROM, a NAND ROM is less battery demanding. But as you can see, 2% is not a big part of the total improvement.
2. Use "SetCPU" with appropriate settings
5-10% of battery improvement
My Main is:
Max: 1190400 / Min: 245000 / Scaling: ondemand - yes! I want light speed HD2!
Click to expand...
Click to collapse
My profiles are (in order - this is important):
Screen Off
Max: 384000 / Min: 245000 / Scaling: ondemand
Battery <5%
Max: 614000 / Min: 245000 / Scaling: powersave
Battery <15%
Max: 614000 / Min: 245000 / Scaling: ondemand
Battery <30%
Max: 806000 / Min: 245000 / Scaling: ondemand
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3. Lower VDD values as low as you can (till device becomes unstable)
5-10% of battery improvement
I am using Tyween settings from his ROM Typhoon.
Code:
#!/system/bin/sh
# set vdd_levels on boot by tyween (XDA Developers)
echo '245000 850' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '384000 875' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '422400 900' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '460800 925' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '499200 950' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '537600 975' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '576000 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '614400 1025' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '652800 1050' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '691200 1075' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '729600 1100' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '768000 1100' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '806400 1125' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '844800 1150' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '883200 1150' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '921600 1175' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '960000 1175' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '998400 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1036800 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1075200 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1113600 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1152000 1250' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1190400 1275' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
I tested even lower values, but my phone was not stable.
I read that each single piece of hardware is unique and could have its own minimum values, so your device could accept lower values (i.e. you're lucky compared to me) or on the contrary higher values (here I am luckier than you are )
Tip "easy way to test a new set of undervolting values": If you want to test undervolting values, themadproducer recommends to use the CONSERVATIVE CPU profile. Why? Because CONSERVATIVE seems to use the full range of scaling frequencies as it climbs up to MAX and falls back down to MIN. This way, if any particular frequency is set too low, it will complain and freeze the CPU. ONDEMAND and SMARTASS would skip over these middle frequencies or at best, never use them for more than an instant.
4. Use "Setting Profiles" for location-based WiFi
10-15% of battery improvement
This soft enables you to switch on/off wifi according to your location (based on cell towers - which does not use battery!).
Be careful: if your location is determined by GPS (instead of cell towers) than you will use more battery through GPS than you save by switching off wifi!!!
Example: you can define to have wifi ON when you are at home, and OFF when you leave home. Same with "work" or any other place where you know there's a wifi network to which you can connect.
Setting Profiles can also be used for automatic phone profiles switching (all kind of opitions from volumes, ringtones to screen brightness airplane mode, etc...)
However, I recommend you let Setting Profiles governing the wifi only. For phone profiles, I use Pocket weaver which is better I think - it can trigger profiles according to Touchdown calendar for example. Moreover, I need wifi on/off independently from hour or calendar status and these apps don't do well when it comes to integrate several conditions together.
5. Use "Phone weaver" for a night phone profile
% of battery improvement depending on situation
I am using a night profiles which goes "Air plane mode" from 11pm to 7am. But usually, I plug my phone overnight, so battery consumption is irrelevant overnight - my night profile is just to prevent radio waves to kill my brain too prematurely as the phone is nearby for morning alarm!
6. Properly setup your Internet apps
% of battery improvement depending on situation
Sounds obvious, but still! Do you really need your phone to check e-mails each 5 minutes? Or would 15 minutes be ok and in return get instantly a lot more of battery life?
Seriously, you need to setup your apps wisely.
e.g.: for those who use Touchdown (exchange sync), this app has awsome options: you can define "peak hours" during which you have a certain setting and the rest (off-peak hours) you will have another setting + the "push" option is very clever: it does not use much battery and on the top of the push option, you setup a period when it will go and check e-mails...
7. Use Auto brightness for your screen
10% of battery improvement
If your are running CM7, there is a function that let you set your own auto-diming values.
First you need to enable auto-dimming in Settings/Brightness and then check the box. After that, go in Settings/CyanogenMod settings/Display/Automatic backlight and set the following:
Light sensor filter=enabled
- Activated: checked
- Window length = 10 s
- Reset Threshold = 400 lux
- Sample interval = 0.5 s
Light levels
- Use custom = checked
- Screen dim level = 1
- Edit other levels…
Lower / Upper / Screen / Buttons
0 / 10 / 1 / 255
11 / 149 / 20 / 255
150 / 229 / 40 / 0
230 / 499 / 50 / 0
500 / 999 / 60 / 0
1000 / 2999 / 100 / 0
3000 / 9999 / 200 / 0
10000 / infinite / 255 / 0
Set number of levels = 8 (you need to set this before editing levels above)
(hit Save & Apply)
- Allow light decrease = checked
- Decrease hysteresis = 20%
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you are not running a CM7 ROM, then just enable auto-dimming in Settings/Brightness and then check the box.
8. Use "Juice Defender Ultimate" + "Juice Plotter"
50% of battery improvement
All of the above tips are very useful. However, this one is the one tip! I came to it almost depressed by my battery life (I had all of the above tips in place already).
I did not believe this soft could really help, and I thought "ok, yeah, this app will just cut-off all communication etc... but then I will have no more auto-sync and/or push e-mail"... I thought it would be a kind of "well just don't use your phone and you will get great battery life!"...
I was wrong. This app is a must! There are all kind of options in settings. Of course the first time you have to go through it and read-read-read learn-learn-learn. But in basically 20 minutes, you are setup and you have a huge battery life improvement! I can share my own settings if anybody is interested.
And the beauty of it, is that in the huge amount of options available, Juice Defender sort out everything by itselft and as a result - I don't feel the difference from a usage point of view (K9 e-mail flowing, Touchdown is pushing e-mail, everything works like a clock). From a battery point of view: wow! The app says it increases my battery life by a 2.5 factor! And this is pretty much what I observe!!!
Juice plotter is also a must: it tells you how long you will last on your battery and I find it to be the most accurate app of this kind!
9. Condition / Calibrate your battery
This one is also a must – and you should do it time to time, let’s say once a month and always first thing to do after you flashed a new ROM!
1. Plug the phone overnight.
2. In the morning: don’t unplug! Check you have 100%, check you have CurrentWidget showing 0 mA if yes/yes, restart the phone / if not, wait until you got a yes/yes answer.
3. After reboot, don’t unplug! Wait again 15 minutes charging. Check you have 100%, check you have CurrentWidget showing 0 mA if yes/yes, go to step 4 / if not, wait until you got a yes/yes answer.
4. Don’t unplug! Clear battery statistics: use a small app named “BatteryCalibration” for that!
5. Unplug your phone, use throughout the day - Don’t charge until you reached 0% battery (when the phone switches-off itself).
6. Charge again overnight up to 100% and CurrentWidget at 0 mA.
7. You’re good to go, on daily use, you can charge upon need even if not at 0%.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
By the way, if you use GPS navigation and/or Bluetooth system in your car, you must invest in a car charger – and plug the phone every time you are in your car (if not the day during which you are calibrating)… it’s another way of increasing battery life – ok, I admit, it’s more a “trick”!
10. Use small apps that help switch on/off the screen when needed
I also tested 2 small apps that actually could help battery saving on the one side, but also increase the user experience on the other side.
Screebl pro: this app is just fantastic! According to screen orientation, it senses if you are using your phone or if it is resting (lying) on the table.
Before screebl: in order to save battery I had the screen timeout set to minimum (15sec). But each time I was reading a long e-mail, I was "playing" with the screen (up-down-up-down) in order to prevent the screen to switch-off and then unlock, etc... This was really annoying. And disturbing: I could not read an e-mail or a webpage without think: "oh, I need to play with the screen somehow or it will switch-off very soon"...
After screebl: the screen timeout is now 5sec! (through screebl) so if the phone is resting, it switches-off more rapidly = you save more battery! And when I read an e-mail or a webpage, I just relax, concentrate on the content! Anyway, the "ON" time is the same because you had to read this e-mail anyway...
ProximityScreenOff:this is also an app to have. It switches-off the screen according to the proximity sensor status: if proximity is detected, the screen goes off. If you are left-handed as I am, you need to take care of not hiding the proximity sensor when you drag the notification bar down, but it is manageable. Not only it is easier to switch-off screen now. It is also saving battery if the phone accidentally switches-on in your pocket! We already had the lockscreen which prevent your phone doing silly things in your pocket. Now even better: in your pocked, the screen switches-off almost instantly!
There is also an option to switch screen ON when proximity is detected, but warning! this drains battery - so I don't use it!
And last but not least...
11. Track any bad app
% of battery improvement depending on situation
Yes, you should know about the Email.apk bug (thanks to themadproducer - I think you learn me that). And generally: you should monitor what is going-on.
I use Watchdog which will alert you as soon as an app uses CPU above a certain threshold that you set. So you know for example that a particular app eats a lot of CPu, which means battery! Watchdog also has a "white list" function for those app that you know are consuming quite a bit of CPU but that you absolutely want to keep!
Go time to time in Spare parts / Battery history / partial wake usage and see which apps are preventing your phone to sleep - they are eating your battery instead!!!
Use CurrentWidget (with log if you want) in order to track instant high current consumption but remember you have to double check with the other above tools as current might be quite high time to time, but it is a normal situation.
Edit: I had an issue with CurrentWidget. In my case, I was logging too much and in Settings / About Phone / Battery usage, CurrentWidget was showing 12%!!! Unistalling / reinstalling might correct the issue (to be confirmed).
Use Battery Monitor Widget Pro: this will draw a graph with the battery % history in a widget, so that you can see at a glance if your battery have been decreasing with a higher rate than usual (by checking visually the slope of the curve). This also to alert you that there is something to track!
I recommend you read this thread which completely describes in a very comprehensive way how to track a battery drain!
Additional thoughts
Of course, if you are on this forum, there is a chance that you like flashing ROMs, tweak it, change settings, etc… All these activities of course use more battery than what I would call the “normal” use…
Also, some activities literally pump out the battery: games, movies, camera, camcorder, GPS navigation, bluetooth headset/earset/car system… There’s no much to do about that – just just need to be aware that they use a huge amount of battery to run; after that you make your choice: game or battery / movies or battery / do I really need the GPS navigation from work to home / etc…
Additional improvements for your phone
I strongly recommend the use of Tyween's Typhoon NAND ROM it is the most stable and complete ROM ever. I tested all of them and as soon as I flashed Typhoon, I understood it was the best... I then continued testing others, but eventually, I went back to this one!!! It is fast, reliable and updated very often! Tyween's Typhoon is here.
My Juice Defender settings
Status Tab
JuiceDefender Ultimate: Enabled
Profile: Advanced
Control Tab
Mobile Data: Enabled
WiFi: Enabled
Options: wifi preferred
3G: not working on Typhoon
AutoSync: ping
Keep enabled: none
Timeout: disabled
Keyguard: none
Home WiFi network: your home network
Brightness/CPU/Speeds/Governor: none
Schedules Tab
Schedule: enabled
Frequency: 1h
Duration: 2m
Controls: default
Night: enabled
Start/End: 0:00 -> 7:00
Adaptive start/end: start +1h max, end -1h max
Option: none
Peak/Frequency/Duration/Controls: disabled
Weekend: disabled
Triggers Tab
Battery: enabled
Battery threshold: 15%
Charger: usb ac
Screen: enabled
Options: ignore on low battery
Controls: default
Traffic: enabled
Traffic threshold: Normal / 15s
Apps: enabled
Configure: interactive
Controls: default
Location: enabled
Properly setup "SettingProfiles"
1. Open SettingProfiles
2. Go on the "Locations" tab
3. "Menu/New Location"
4. In the pop-up menu select "Cell Towers identified" (do not select "Lat/Lon Identified": this would deplete your battery)
5. A window opens-up with the current cell tower id open "Menu/Save as Cell Location"
6. In the pop-up menu, give a name to this location: e.g. "Home" or "Work" depending on the place you are right now
7. Still in this menu, you can check the "auto-save for 60 minutes". If you do so, then during the next hour, all new cells that are seen will be saved automatically as a cell for the just created location. Be careful: if you check this function, you need to be sure you will stay in this very location (e.g. stay at home) during the next hour.
You're done the "Location" is created and and several Cell Towers are saved for this location. Now it appears in the list in the Location tab.
After that, you need to do the following:
1. In the "Profiles" tab, create a profile named "Wifi ON" which leaves everything as it is except Wifi that it will switch-on
2. Still in the "Profiles" tab, create a profile named "Wifi OFF" which leaves everything as it is except Wifi that it will switch-off
3. In the "Rules" tab, create a new rule. Add condition: "Location" and then select the appropriate location where you want Wifi on. Add action: "Activate profile" and then select "Wifi ON". Back key: your rule is appearing now in the "Rules" tab.
4. Still in the "Rules" tab, create a new rule. Add condition: "Location" and then select the appropriate location where you want Wifi off and check "inverse logic". Add action: "Activate profile" and then select "Wifi OFF". Back key: your rule is appearing now in the "Rules" tab.
You're all set!
The beauty of SettingProfiles is that in the rules created on point 3 and 4, you can add several locations in the same rule. e.g. it will activate "Wifi ON" when you are at Home or at Work...
Follow-up: if in future you realize that SettingProfiles has selected "Wifi OFF" when it should have selected "Wifi ON", it means that there is a new Cell Tower accessible from (let's say) Home. In this case, go on the "Locations" tab, click on "Home" and if this Cell Tower is not in the list, there will be automatically a "save" button on the top of the list. Hit "save" to say to the app that this Tower is also part of "Home".
If you realize that SettingProfiles has selected "Wifi ON" when it should have selected "Wifi OFF", well that's nothing to do about. A Cell Tower that is accessible from (let's say) Home can also be accessible 1km from Home... However, this is not a major drawback: you are experiencing this situation only during commuting transitional times.
Extreme Users section
For those users who are ready to decrease their user experience (refer to disclaimer in post 1) here are additional settings!
Warning: if you apply these tips, you may not be happy with:
* too much involvement from your side (go switch-on switch-off things)
* widgets and other functions not properly working (i.e. auto location)
* e-mail that are not flowing / not syncing with the period you defined
Tips:
A. Turn off network location, GPS and auto sync (dorimanx)
B. South to 2g (dorimanx)
C. Set Juice Defender on "extreme" (beston94)
D. ... suggest yours!
Changelog
July 12th
* Added tip #10: Use small apps that help switch on/off the screen when needed
* Moved old tip #10 to #11: Track any bad app
July 6th
* Added the "Properly setup SettingProfiles" in post 2
July 1st
* Added disclaimer and "red %" signification in beginning of post 1
* Updated SetCPU profiles (Tip 2)
* Tips to test Undervolting values (Tip 3)
* Potential issue alert with CurrentWidget (Tip 10)
* Added JD stettings in post 2
* Added "Extreme Users" section is post 2
* Added Changelog in post 3
Nice thread.
I hope people look at this before posting "my battery life sucks.."
Do you have your statistics for the percentage gain/loss of the battery?
settings
Well you said anybody who is interested in settings on juicedefender ultimate?
Well i am on cmylxgo rom i got 37 hours on and still had 30% left with moderate usage.
But maybe your settings are better ;P
parker09 said:
Do you have your statistics for the percentage gain/loss of the battery?
Click to expand...
Click to collapse
The % I wrote are from "gut feeling"...
However, I know for sure that: before applying any tip, my battery was lasting 6 hours. Now with those tips, it lasts 18 hours!!!
You should try for yourself and report results!
beston94 said:
Well you said anybody who is interested in settings on juicedefender ultimate?
Well i am on cmylxgo rom i got 37 hours on and still had 30% left with moderate usage.
But maybe your settings are better ;P
Click to expand...
Click to collapse
Uh... So you mean that you drain your battery in 50+ hours? More than 2 full days?
Mmmmmm...
So if it's not fake, you would share with us your "tip" from another world... And also elaborate a little bit on what you mean by "moderate" usage!
We are listening to you...
Hmmm... you get over 50 hours on your battery... do you use it?
Wow i see you got a nice Tread WELL DONE!!! One more Step to perfect Phone!
And Thanks for adding my tread on your main PAGE! it's an Honor!
I am now your follower
By the way my phone cant go under 925 Voltage if i set 900 on 245MHZ it's stuck in 2 seconds!
But as you know i have configured the minimal voltage script that work for me in my tweaks. bummer that my CPU like more battery!
Good Job
Thanks for your support!
This evening, I plan to:
Update first post with new settings/information
Load my JD settings (will be in post 2)
Check it out!
Thank you. Very interesting thread!
Now i feel inspired to do something for my battery...
I have a tip for battery save.
turn off network location and GPS and auto sync and switch to 2g if you can.
then when you need one of the futures just turn it on and when finish turn off.
this can save 15% battery or more.
Sent from my HTC HD2 using XDA Premium App
Looki75 said:
Uh... So you mean that you drain your battery in 50+ hours? More than 2 full days?
Mmmmmm...
So if it's not fake, you would share with us your "tip" from another world... And also elaborate a little bit on what you mean by "moderate" usage!
We are listening to you...
Click to expand...
Click to collapse
Here are my secrets juice defender ultimate on extreme and I turn on wifi whenever I want to. I also have auto killer on strict mode don't remember the exact numbers and as for my moderate usage I took 6 1minute calls and 10message received and 3 sent and a Couple of times on xda 5 minute each. Lets not forget setcpu was on on demand not over or under clocked and my profile was screen off 245 499 and my charge was 245 1190 and when battery goes under 40 its undervolted to 245 to 780. Btw I was using cmylgxo rom the lite one since I'm on European HTC hd2.l
Press thanks if I helped anyone.
Sent from my HTC HD2 using XDA Premium App
If it is everything ok with yours builds/kernell everybody should have more than 24hours on moderate use...
I mean normal batterry consumption in stand-by should be around 3-10ma depending of reception and what is turned on...
If that is not the case than you have litlle bit more than 8 hours... i mean that sucks
I thought also it's imposible but some experimenting with different build's and kernells get me to this that i can use my device for almoust day and a half without turning wifi off.
p.s. juicedefender is enabled at balanced...
Hi everybody!
I just added a lot of things in the first 3 posts!
Check-out changelog in post 3!!!
* New SetCpu profiles
* My JD settings
* and much more... !!!
Check it out!!!
very nice tips here, but am struggling with JD atm as it says the rom i use doesnt support mobile data, does your 3g work with JD activated ? if so how do i get it working for me,
thanks, great thread btw
Found room for this useful thread in my signature
To enable JD notifications or not? Because I think notifications eat battery.
LaneyEFC said:
very nice tips here, but am struggling with JD atm as it says the rom i use doesnt support mobile data, does your 3g work with JD activated ? if so how do i get it working for me,
thanks, great thread btw
Found room for this useful thread in my signature
Click to expand...
Click to collapse
Thanks for linking to my thread in your signature
If you mean Controls Tab / 3G then JD asks you to "Proceed".
When you hit the "Proceed" button, it proposes you to install "Juice Defender AOSP Helper". You should install this app and then hit "enable" in Controls Tab / 3G.
However, some ROMs do not support this function and in this case, "Juice Defender AOSP Helper" will not install. Typhoon for example does not support this soft.
Now here is something for you: you can install a soft named "Toggle2G-update.zip" (the update through CWM if you are running Gingerbread 2.3.4).
"Toggle2G-update.zip" is in this thread, with all explanations:
http://forum.xda-developers.com/showthread.php?t=739530
You can also choose another similar app (there are a lot of them).
This will perform the same than JD / Controls Tab / 3G but with a separated software.
Cheers!
radee85 said:
To enable JD notifications or not? Because I think notifications eat battery.
Click to expand...
Click to collapse
Hello,
I enabled JD notifications.
Why? Because in a glance you can know what is JD status (I use the graphical notifications).
I never noticed any particular drain related to JD notifications, and let's say to any notifications... I also heard about that but could not reproduce the drain.
If you have any precise information about a notification-caused drain, this is an interesting information that you can share in this thread.
Thanks to report your observations!
Cheers!
Reference Thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-limit-battery-charge-level-tasker-t3668059
attached are the xml's that works for the OP5T Oreo. ive been using this for a week now and its seems reilable. you can change the values of battery level and wait times.
oops, mods please move to appropriate forum. thanks
Thank you. I was looking for it.
The battery don't charge more after unplugged and plugged again with 72%
Charging enable has a wait time of 1 hour. You can change this if you want to enable charging sooner. Wait time thats too short will toggle charge and discharge quickly if device is left plugged in. Not sure what that will do to the device. ?
jonahmt21 said:
Charging enable has a wait time of 1 hour. You can change this if you want to enable charging sooner. Wait time thats too short will toggle charge and discharge quickly if device is left plugged in. Not sure what that will do to the device.
Click to expand...
Click to collapse
OK. Great.
How should i use this ? ?
repulse said:
How should i use this ? ?
Click to expand...
Click to collapse
I didn't get it work either but as no one hasn't given any answers yet I'm going to try... This is what I tried:
1. Import the tasks to Tasker
2. Create a new profile. Select State -> Power -> Power. The source should be kept as "Any".
3. This one is a wild guess but I think you should use the Charge disabled task as the primary one.
4. Add an exit task to that newly created profile. I think it's the Charge enable task.
I left my phone plugged in to a charger and the charging stopped when the desired battery level was reached. However, it never started to charge again. My phone was plugged in for a couple of hours and I had to use my own task to edit the charging enabled file. Did I do something wrong? Any help would be much appreciated.
Edit. Got it working. The charge enable task was somehow corrupted in the import process.
jonahmt21 said:
Reference Thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-limit-battery-charge-level-tasker-t3668059
attached are the xml's that works for the OP5T Oreo. ive been using this for a week now and its seems reilable. you can change the values of battery level and wait times.
Click to expand...
Click to collapse
Could you please explain why actions 1 and 4 are needed in the charge disable task?
Please read the reference thread. It was already explained there. Thanks
How to change battery level? Do I need to edit the xml file or I can do it at tasker?
Thanks.
jonahmt21 said:
Reference Thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-limit-battery-charge-level-tasker-t3668059
attached are the xml's that works for the OP5T Oreo. ive been using this for a week now and its seems reilable. you can change the values of battery level and wait times.
Click to expand...
Click to collapse
lyrebird said:
How to change battery level? Do I need to edit the xml file or I can do it at tasker?
Thanks.
Click to expand...
Click to collapse
You can edit it with Tasker. Just change the percentage to your liking:
This doesn't seem to be working on OB9. It will stop charging at set level but it will enable charging again after a few seconds. Anybody have an idea why?
jonahmt21 said:
This doesn't seem to be working on OB9. It will stop charging at set level but it will enable charging again after a few seconds. Anybody have an idea why?
Click to expand...
Click to collapse
Have you tried narrowing down the issue? What happens if you manually edit the control file?
It's very unfortunate if Oneplus has started editing the charge control file periodically. I haven't upgraded to OB9 yet and will wait for results before upgrading.
A little more testing...
Removed the charge enable exit task to see if the charging will be permanently disabled, but the charging still enables after a few seconds. Seems like the device is detecting that the device is plugged in and the battery is not at 100% so it enables charging again. Not sure how to get around this. ?
Crap, nevermind, i had a magisk module messing up with tasker. Original tasks still work. Please disregard previous replies. Whew!
Work only on oos or custom rom too
?
Thanks, that's one fewer app.
Running on Liquid Remix.
Duduzinho16 said:
Work only on oos or custom rom too
?
Click to expand...
Click to collapse
Rom version shouldn't make any difference.
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?
i don't understand these current flow, voltages, etc... but i am sure it's not possible to charging battery in 3min the values are higher. is this ok ?.
just worried about my battery.
*Custom rom : { Havoc-os v4.19 }.
*Advanced charging controller : { magisk module }>
....... don't know why ?. but. if i use this module charging stops at 70%. and if i remove it will charging 100%. and after 50% the W goes down like 2.0 or 0.1 like that. and time also increase after 50% to 60%.
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
aospray said:
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
Click to expand...
Click to collapse
I am not using ACC as usually after sometime I experience some issue or the other. The GUI frontends are especially buggy and I am not a fan of using commands to tweak stuff. I am using Termux commands in Tasker to automate this. Best thing with the upgrade to 4.9 kernel was the ability to limit the maximum battery charging voltage which is the one of the best ways to prolong battery longevity. Thankfully even in A12 and A13 ROMs it continues to work. Some charging switch or the other should enable limiting voltage in ACC I think.
aospray said:
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
Click to expand...
Click to collapse
How to do that ?. ( by commands ? ). i want to limit it at 95%.
Maheshmahe said:
How to do that ?. ( by commands ? ). i want to limit it at 95%.
Click to expand...
Click to collapse
Root is necessary of course and use only ROMs based on kernel version 4.9.
In any proper file manager like Solid Explorer or Mixplorer etc. simply navigate to sys/class/power_supply/battery/voltage_max which is located in the root partition and open it as a text file after changing the file permissions to rw-rw-rw from the default read-only.
By default the max. charging voltage is set at 4.4V. It’s in milli Volts. So 4400. 4.05V corresponds to 75% battery charge. 4.15V to ~85% and 4.3V ~95%. I wouldn’t recommend going above 4.2V (which corresponds to 90%) as the battery will be at a constantly high voltage (as battery percentage won’t ever decline as long as it’s plugged in) all the time otherwise. Ideal range is 30-80%(15-90% in newer models). If the device will be used plugged in a lot shoot for 60% (3.95V).
su
echo 4300 > /sys/class/power_supply/battery/voltage_max
I kept the battery at around 80% for the first 3 years when it was used as a primary device and afterwards at 60% as it's plugged in most of the time. Probably that's why battery health is still above 80%, 6 years later. Still lasts almost 10 hours during offline video playback (indoors).
P.S. The voltage under voltage_max resets at every boot. That's where Tasker or Macrodroid or even a script comes in handy.