yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] bradipovsky:
Nicely done guide, even though the easy part can look a little oversimplified, it sounds a little bit like "if you turn off your device, it will use less battery".

I'll add a couple of things that don't seem to have been said yet. If you have the Xposed framework and XBlast tools, you can tweak the wifi scan interval up to 7 minutes, that way I have wifi always on and it uses less than 5% of battery. Why would I need wifi always on? Because it's useful for setting up Tasker profiles, which can be used to save battery while keeping your phone syncronized even outside.

Also, if I had a decent CPU (which I have not, so what I'm saying comes from my imagination and not from my experience) I would try to set Tasker up to clock it to the right frequency for what I'm using: that could be done with app-based profiles, time-the-screen-has-been-on-based profiles or even with manual toggles. Tasker can also be used to set up a customized night mode (for example, a night mode that automatically kicks in only if you're home) or CPU profiles that depend on the screen been on or off, which could be useful if you don't have a CPU governor that does that on its own.

EDIT: You added the rotation one in the easy post: Xposed module App Settings allows to turn the automatic rotation (and many other things) on and off for every app, which can save some time.
[Android Q&A, Help & Troubleshooting] Vlad Paul:
First i want to thanx for this usseful thread.

Using many times hardware butons the baterry is draining fast, i think. I use Gravity screen(using only proximity sensor for turning on my display) and my baterry life is more better.
[Android Q&A, Help & Troubleshooting] rirozizo:
added to OP:

and thanks for the tasker ideas! i'll see if i will put tasker ways to improve battery in the guide. Also thanks for reminding me about xposed... i'll consider both of them to be added :)
[Android Q&A, Help & Troubleshooting] Crostantin:
Great guide!!

To be honest I have the same idea about greenify...I blocked it two days ago...

Instead I am trying some wakelock manager like autorun manager... What do you think about??

Purity + myKernel
[Android Q&A, Help & Troubleshooting] rirozizo:
autorun manager is good, but can cause some stability problems if you make a mistake... be sure to test the app your modifying everytime you do something with it

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] Crostantin:
I think that all the user app without root permission can be modified (facebook, twitter, tapatalk, etc...)

For system app is better to do some test before?

Purity + myKernel
[Android Q&A, Help & Troubleshooting] peter-k:
Suggestions

My phones specs:

Stand-by	Up to 300 h (2G) / Up to 400 h (3G)

Talk time	Up to 7 h (2G) / Up to 7 h (3G)

Which translates to Sony saying that my phone uses lower power in 3G stand by.

If it is a weak signal and only temporary, I'd let the radio on. The system will use full power for up 10 s to find and login to a cell , and then negotiate a meaningful (lower) transmission power with the tower. Of course if a position is very weak for a long time, or on the move, this advice will help.
[Android Q&A, Help & Troubleshooting] rirozizo:
yes, just checked the 3G/2G thing... sorry for that
[Android Q&A, Help & Troubleshooting] mbirth:
Let's not forget Android uses WiFi for coarse location which needs way less power than getting a GPS Fix. It also assists in getting a GPS Fix much faster by providing an approximate location. So if you use anything that uses your location (Tasker profiles, MOVES App, Location in camera shots, Google Maps) it can help to save some battery.
[Android Q&A, Help & Troubleshooting] peter-k:
In particular if one of the sync services has an explanation mark (failed), it will keep on retrying.

---------- Post added at 11:19 PM ---------- Previous post was at 11:11 PM ----------

No need to feel sorry. I appreciate your work and hope you will get many other suggestions. My advice would be, install a battery monitoring app to verify, or use the vendor specs as a basis for this decision.

---------- Post added at 11:22 PM ---------- Previous post was at 11:19 PM ----------

Another idea regarding widgets: Installing those which come with a manual refresh option.

In general in many cases it is better doing things manually. That also keep me in control of the system.
[Android Q&A, Help & Troubleshooting] rirozizo:
great idea! will be considered...

out of thanks for today :/
[Android Q&A, Help & Troubleshooting] Tzfardaya:
Sony's Stamina mode and Samsungs Power-saver mode, just underclock the cpu generally... with a few more power saving tweaks as well...

great ideas, although, if you gain the knowledge and are comfortable with editing system files (build.prop for instance) you can set the wifi scan time to anything you want, I usually set my scan to 15-20 minutes. (at the cost of losing OTA functionality normally) Tasker lets you turn autorotate on and off in it's profiles as well... for those who run ART or don't want to run Xposed.. Since Xposed doesn't work with ART...

Careful with wakelock managers, disabling some wakelocks can cause some apps to misbehave... (I know, it's vague, but I'm just passing on the warnings I've received... not that I've encountered any yet)

I personally use greenify on apps that throw unnecessary wakelocks....

but track the battery usage and let us know if it used more or less battery than previously.
[Android Q&A, Help & Troubleshooting] admiraljkb:
I'll add to that, since one of my areas of reasonable expertise is battery tech since I've been building my own packs for my hobby (SLA, NIMH, LiPoly, LiFE) for the last 13 years. As long as you are charging at 0.5C or less, the battery will thank you for it regardless of tech. (Where "C" = Capacity ) A 1A battery can typically be charged at 500mah OK, and a 3A battery can be charged at 1.5A. With that said, as noted, the slower you can charge the battery is good. I routinely charge my Nex7 on a 700mah charger. As you feed more juice in for charging, the more that gets wasted as heat. Conversely, discharge works the same way, so if your GPS and screen are running and sucking down more than 0.5C, you might want to upgrade your battery capacity to ensure more juice goes to the phone rather than wasted as heat. Better batteries are rated for higher charge and discharge cycles, but unfortunately we typically don't know the REAL ratings on our batteries, so presume 0.5C for charge and discharge.

There is a glaring error on the article though. Do NOT take the battery down to 20% routinely on purpose. This only applies to NIMH and NICAD chemistries, which are no longer in use on phones. For LiPoly, what I was told from my supplier is a cycle is counted on how many times the cell's capacity has been discharged, not necessarily at one time though. So if you charge at 90%, then charge at 50% and then at 60%, that is ONE cycle ultimately. However, if you go below 30%, you WILL start damaging the battery, so that isn't recommended. In fact they don't recommend going below 50% if you can help it since slight damage starts there, but doesn't go hockey stick for cell damage until 30%. Conversely - charging when the phone is above 90% is not recommended either. Let it go below 90, and keep it above 50% to charge for maximum lifetime performance.

Charging details for various types:

SLA and LiIon, LiPoly, LiFE - don't leave discharged, don't run them down and leave them that way. They like to be charged and happy. (if storing, don't store fully charged)

NiCAD and NiMH - let them discharge to a reasonable low point before charging, and then do periodic charge/discharge cycles on a purpose made smart charger like what is used in the R/C communities. Do NOT let them completely discharge, as this can reverse the poles, which is a pain to repair, and many times can't be repaired. (the reason I still have dumb chargers around...)
[Android Q&A, Help & Troubleshooting] rirozizo:
that's all good to know.... noted, will be considered too... thanks

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] peter-k:
Just informative, your post can be misread. Sony's Stamina Mode switches some background services off after a number of minutes not using the device. And Wifi, too. Present tasks will be still completed. It is not throttling the CPU, but a relevant number of wakelocks.
[Android Q&A, Help & Troubleshooting] Tzfardaya:
Perfect, thank you, I'm a rank amateur with the tech, but I have some small knowledge.

Since all our Cell Phones use LiPoly (LiPo) batteries these days, Which means a max charge is 4.2V, Drained is 3V hopefully our phones have circuitry that shut them down before they reach 3V... but just to be safe, it's probably best never to let them drain below 2-5%. I can't remember if LiPo batteries benefit from charging and draining to and from various charge points.... Hopefully The Admiral can shed some light on that too, or if they should be drained low and charged high...

And my apologies for using the wrong terminology when there is a battery master around :P Trickle charging is not good for lipo batteries (trickle charging being a very slow charge to just keep the battery topped off...

I should have used slow charging instead... :(
[Android Q&A, Help & Troubleshooting] admiraljkb:
I knew what you meant on trickle, it gets used rather liberally nowadays anyway. :) LiPO just doesn't really care about charge/discharge points overall, until you get below 50%, but that isn't noticeable. 30% and below however can noticeably degrade the cell capacity. They've been working on the chemistry to keep that part in check, and from what I've seen on newer quality packs from the last couple of years, it *may* be in check, but I still don't recommend going below 30% regularly since there isn't a good reason to deplete them that far unless you're caught out without a charger nearby.

Modern Lithium Ion variants have protection circuitry built onto the pack, unless you are rolling your own packs, at which YOU add the protection circuit onto it. The protection circuit does prevent you from fully discharging (which can result in a not so nice fire). Thanks to the protection circuitry, the charging is actually handled by the battery itself rather than the charger, although the phone and charger both also have some smarts on them as well for protecting the end user from a terminal case of hot pants or a burning house.

Basically for:

optimal usage you would charge at points below 90% and above 50%.

OK would be 100% and 30% (which is where I fall truthfully...)

Bad would be 100% to 0%

<edit>on the points - if you are building your own protection circuit, or doing charging without a protection circuit, you would use the voltage as your points, but I'm using the percentages as reported by the circuit/phone's logic since that is a little more in keeping with the audience reading this. I'm presuming most folks here aren't building their own combat robots and need to know minutiae like that. :) </edit>
[Android Q&A, Help & Troubleshooting] sourcex:
where are the Medium and advance part ?

The easy part included basic known tips ....waiting for some advance battery saving tips!:highfive:
[Android Q&A, Help & Troubleshooting] rirozizo:
not sure if kidding... but did you look at the second and the third posts?

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] sourcex:
Frankly if those were the Little advance Tips then I think this thread didn't make me learn anything new:confused:

Anyways Nice Post for someone New to Android

I have tried Freezing "npl_wakelock" and Google Services for getting a better battery but ended up Messing up my battery and GCM ..any tips on this ?

Would Love a post from about How battery Chargers can affect Battery life !!
[Android Q&A, Help & Troubleshooting] rirozizo:
what da hell?

is anybody else reading the same sentences that i'm reading?

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] sourcex:
I am repeating myself that this thread wasn't helpful for someone like me who is an android geek:D

Don't get me wrong ....and its nice that you made effort to put all the battery saving tips at one place :good:

Cheers for that!
[Android Q&A, Help & Troubleshooting] rirozizo:
then please don't post it... if it isn't helpful just ignore and move on

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] aavvaallooss:
Don´t bother!!!

We, no-geeks (aka normal people) , appreciate your job.

Thnak you very much!!!
[Android Q&A, Help & Troubleshooting] Tzfardaya:
Any Battery tweaks you can think of that haven't been added yet?

npl_wakelock is reduced with the next version of play services (4.1 or so) rolling out now, or you can track down the apk on android police...

And I understood that this thread is a great place to start learning about battery saving. If you want to be able to go beyond this, then you have to start moding system files... Installing Custom Kernels, learning to tweak those kernels..

This is a great thread, but it shouldn't be assumed to be the end all and be all of battery saving...

[MENTION=2722834]Riro Zizo[/MENTION]

One more thing to add to it, wakelock checking... find those nasty apps that are running when they shouldn't be and keeping the device from sleeping when it should be in deep sleep.... Better Battery Stats is a good app for that....

edit -:- nevermind, missed it in the first read through... :P

I'll track down a few more system wakelocks for you to post for ignoring... not much we can do about them....
[Android Q&A, Help & Troubleshooting] Beatsleigher:
I personally recommend overclocking. It's a common mistake people make, that underclocking reduces battery usage. The processor still uses the same amount of power, if you set the voltage values correctly. For example:

If you set the processor to use 700mV when at 1GHz clock speed, the processor will use 700mV. If you set the processor to use 700mV at 1.8GHz clock speed, the processor will get stuff done faster, and will use the same 700mV, but for a shorter amount of time, and if you use these example settings over the course of a week, you will effectively use less battery power. The only reason you should ever underclock a processor, is when that processor has heat problems.

Think about it this way:

Say 90% of smartphone users are moderate users, and have a wake-time of 1hour a day. Why do you think OEMs keep upping the processor speed? They know for a fact, that the faster the processor, the better the battery. That way they could even put in the same battery as last year's model, and say it has a better battery life. That's how Apple has presumably been doing things for years. But other OEMs put in bigger batteries AND a faster CPU, giving users even better battery life. So even if you barely use your phone at all, you should still overclock the processor as much as you can, without damaging it. Over a long period of time, you can save a butt-load of battery power.

If you still don't get what I mean:

You have a car and have to drive to work everyday. And that drive to work takes 25 minutes and you use 4l diesel each trip.

You then find a shorter and a faster route. Using the shorter root may have more traffic lights (underclocking the processor) where the drive will take the same amount of time and will use either still 4l diesel or potentially more.

Taking the fast route (overclocking the processor) will take you 15 minutes and you only use 3.9l diesel. Over a long period of time, using the faster route will save you a lot of diesel.

I hope I made this matter clear and didn't make things more complicated. I'll make a chart some day, to solve this matter once and for all.
[Android Q&A, Help & Troubleshooting] juliatan:
Greenify also does wonders on my devices. Even once clean stock Android is becoming bloated G-droid. With all those Google apps among others running and restarting themselves all the time when not using them. With Greenidy not needing to disable and miss hem totally. Wish Google would kick them out of system and let users install their for the most part bloatware as user-app.(Simply removing them from system and install as user-app lets future OTA crash).

Wifi settings I have set to always go off when screen goes off/sleep mode. On both my devices downloads however will always complete when screen goes off before turning off wifi. And playing music via wifi (samba and cloud) will keep wifi on when screen goes off until playlist is finished. Screen on and wifi is connected in a second. My devices use almost zero to nothing battery when in standby. For me the best setting wifi off when screen goes off instead of doing that manually all the time..
[Android Q&A, Help & Troubleshooting] fishwithlungs:
Then I must consider myself lucky having Note 1 behaving like this :)
[Android Q&A, Help & Troubleshooting] BleuZ:
[Mega-Guide][12/01/14] Get a (Battery) Life! Every possible way to save your ...

I find that incredibly hard to believe, so I'd consider you very lucky then, yeah :)

Are you sure you didn't charge your phone in the meantime battery? You didn't post a screenshot of that and of course that's hard to tell from the other side of the internet :)

If I'm wrong, then good for you. I hope your device keeps behaving that way!
[Android Q&A, Help & Troubleshooting] Tzfardaya:
It's called "race to idle" finish the task as quickly as possible to go back to deep sleep...

Overclocking isn't always the best, since overclocking most cpu's requires you to pump the voltage a bit (at that frequency) to keep the phone stable.... sometimes it saves battery, sometimes it doesn't... (completeing the task quickly enough to compensate for the reduced voltage...

each frequency step has a voltage applied to it, faster speeds require more power to maintain stability...

the reason why newer phones with higher frequencies use less power is more to do with better engineering, less power for the same frequency, rather than faster speeds being inherently more battery efficient....

the trick is to find the frequency/voltage combination that accomplishes the task using the least power...

Your car analogy was quite apt, except you didn't take it quite far enough...

by overclocking, you're effectively driving your "car" (phone cpu) over the engine red line, stressing it more than it was designed for...

best to stick to stock cpu speeds at most... uv a bit, then test to see what frequency provides the best balance...
[Android Q&A, Help & Troubleshooting] pirate11n11:
Excellent guide :) :)

I'm not trying to be offensive so please correct me if am wrong :|.

I don't agree with your point 'Charge Your Battery Correctly'. Li-po/Li-ion batteries are top-up batteries. A cycle is defined as 100% top-up charge.. even if you top-up from 50% to 75% 4 times, that completes a single cycle. The battery longevity depends greatly on battery temperature. So if you charge from 10-100 on a single charge it will raise the battery temp which is quite harmful for the battery and again maintaining charge less than 10% and equal to 100% (in charger for long time) reduces the battery life (both puts a kind of stress on battery).

I used to charge my battery just like you said (allow it to touch 15% and then charge fully) and then I learnt a lesson when my s2 battery bulged and became unusable within 18 months. My friends who have the same device just top up every time (40-50% and never allow it to go less than 30%) and their battery life is great even after 3 years. This made me research a bit on Li-ion battery from number of sites and knew that what my friends were doing is the exact way to charge Li-ion batteries. Maintaining charge between 20-90% and topping up 30-50% is the ideal way to keep the battery strong.

Ref:

http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries

http://www.techrepublic.com/blog/five-apps/five-tips-for-extending-lithium-ion-battery-life/
[Android Q&A, Help & Troubleshooting] rirozizo:
thank you!

considered for editing.

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] drsamratroy:
I use Lux for screen brightness... I think u sud give it a go too... really helps with screen brightness issue... btw thanks for the guide...
[Android Q&A, Help & Troubleshooting] fatboyslimerr:
Absolutely amazing guide! I've read and re-read the first few posts multiple times and keep learning things.

I've tried using wakelock detector but it says awake 96%, since 8 hours.

Some apps are in red and some apps have long times associated with them.

Facebook app for example says 39s x145 and is in red. Is this bad?

Are there any risks to using ART on a custom ROM, especially on an older phones such as my HTC One S?

Thanks again for the amazing guide.

EDIT: Also how do you reset wakelock detector to see if you have improved/fixed things?
[Android Q&A, Help & Troubleshooting] rirozizo:
yes, this is bad, check facebook's settings and see if there are sync frequency so you could make them lower. or just disable notifications from Facebook, they take a lot of wakelocks.

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] Xipe_Totec:
Thank you for this step-by-step guide. Really useful and complete.
[Android Q&A, Help & Troubleshooting] ajanu:
There seem to be a lot of true battery geeks in this thread, maybe someone knows the answer to this. Generally when you restart a phone, if it was at 10% before you rebooted, it will be at ~8% when it comes back on. Since I got my wireless charger my phone has sometimes gone from 10% to 12% battery after rebooting, when not charging. Losing battery makes sense, takes a lot of CPU power to restart. Gaining power confuses me, but I have seen it a few times. I have only noticed it at low power, but over 20-25% I am not paying too much attention. I also tend to tweak my phone at night when I am lower on power.

Location has been using a lot of my battery. I updated to PlayServices4.1 and that hasn't helped much. I realized Beautiful Widgets was set to update every hour, so I changed that. I also used ApOps to remove wakelock permission from search and playservices, and removed location from Facebook and some other apps that don't need to know where I am. Hopefully this helps as I like having location enabled.

Thanks for the thread!
[Android Q&A, Help & Troubleshooting] HaYaHa:
In the guide they say, that I need to use the home button instead of the back button, so I tried it but the battery usage has been a lot worser since I use the home button. Instagram used 33% of my battery even I just opened it and then pressed the home button. My screen 'only' used 29% of my battery. What am I doing wrong?
[Android Q&A, Help & Troubleshooting] fishwithlungs:
Well I have some from another day,close, but not as good.The 6 hours was the best( I go down to 1% battery quite rarely :D).

And I do not compete with anyone in terms how long screen time I get,but if it was 2 hours,I would be quite disappointed.

Sorry for duplicity,the screenshots have been posted in thread dedicated to ROM I am running on my Note as well.
[Android Q&A, Help & Troubleshooting] steakhutzeee:
In battery stats, what's the difference between Android System (i've 33%/35%), and Android Operative System (2%) ?
[Android Q&A, Help & Troubleshooting] rirozizo:
click on it, you should see the services using the CPU and the battery

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] steakhutzeee:
Android System-Total CPU 6m 31s-Keep active 9h 14m 0s

Android operative System-Total CPU 7m 49s
[Android Q&A, Help & Troubleshooting] rirozizo:
no i meant the included packages part which is just under those, but i think they're not there.

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] steakhutzeee:
Uhm i don't understand.. what's their difference?
[Android Q&A, Help & Troubleshooting] Silentdoom:
Great guide!! Thank you