Database Users

[GUIDE] How to make your battery last longer on Android

Be warned that this thread is now outdated. There might be more current guides available…
THE ULTIMATE GUIDE TO MAKING YOUR BATTERY LAST LONGER ON YOUR HTC HD2 WITH ANDROID
OK I suppose this should be stickied as I've found numerous threads saying various stuff, but not a single thread, dedicated solely to this, providing useful and organized info.
Note: This guide is by no means definitive. Please feel free to correct me and add more tips, I'll be sure to add them to this post.
STEPS:
1. Try out a few ROMs and Radios to see which combination works best for keeping Android run as long as possible.
I have yet to find the best combo for my phone, but generally, the lightest ROMs with not much bloat in them (lots of items removed, fast startup) work best. With Radios it's all trial and error – a Radio that works miracles for one user is useless for another. You just have to try and see.
I know this is probably driving you crazy as you can read it everywhere around, but this can't be stressed enough: Don't flash your phone with a ROM/Radio you're not absolutely sure won't brick it. No one wants you to brick your expensive device. Read the flashing guides very carefully before you go on and do it.
Updating your build's Kernel is also a good idea.
2. Make sure you boot Android up as fast after running Windows as possible.
This one is crucial as it seems to affect your battery a lot.
To aid this, you can:
Download and install this (free) app (Exceller Multiple Build Loader is what I use, but you can choose something else) for the WM6. It enables you to autoboot into Android in the timespan of three seconds after running Windows, which is what you ideally want to do.
Disable HTC Sense in WM, it's unnecessary if you just want to boot into Android and takes a lot of time to load up. To do this, go to System settings, press Home, go to the Items tab and uncheck HTC Sense. You may want to check Windows Default to have at least the Zune-style interface to start from, but this isn't necessary if you're ok with an empty homescreen in WM.
3. Decrease the system load by automatically killing apps you no longer use.
This one gives a fair battery boost. By default, Android keeps all apps ready in RAM even if you press Home or Back to exit them to make them start quickly next time you need them and to keep their state. Most apps have a suspend mode which enables them to demand close to zero system resources as they run in the background, but some don't and close to zero isn't zero.
Download and install Automatic Task Killer (free) from the Market.
It gives you a list of the installed apps and enables you to uncheck those you don't want to autokill. It can also add your new apps to the list automatically.
Don't forget to uncheck applications you need to be running constantly, such as SetCPU (see below).
According to hastarin, this doesn't give you a battery boost. See the "What DOESN'T improve battery life" section. You can use AutoKiller Memory Optimizer, if you want to tweak your RAM – this app lets you set the limits for automatically killing apps only when you're low on RAM, which in turn may give you a battery boost.
4. Decrease the CPU performance when it doesn't need to perform at full speed.
I'm sure you're proud of your HD2's Snapdragon running at 1 GHz, I know I am, but it also drains a lot of battery when running on full speed.
NOTE: Using SetCPU with hastarin's R8 Kernel makes it redundant as the Kernel already has an interactive CPU governor in it. Thanks to socrated13 and atticus182 for this tip.
Download and install SetCPU ($1.99) from the Market.
It allows you to underclock your CPU to save battery. You can set profiles and play around with them. Generally, you don't want to set the minimum frequency too low as some tasks may then consume significantly more time to complete, wasting the energy you gained.
If you just want to try the app first to see if it helps, you can get it for free (search for SetCPU here at xda) and donate later by buying it on the Market (and please do, the developer put a lot of effort into it).
5. [INFORMATIVE] See how much energy your phone drains.
This one is not compulsory, but helps to get a general idea of how much energy your phone drains when you do such and such.
Download and install the Current Widget (free) from this forum. Just do a search on "current widget" and it should be the first post that comes up (don't worry, yes it's under Samsung Vibrant, but it works just as good for the HD2)
It allows you to put a widget on one of your home screens, where you can see the current your phone is currently draining. Can be set to update at various intervals. I prefer 30 s as it gives me enough time to shut down an app and look at it to see how much current the app itself is draining.
6. Decrease the brightness of your display.
This saves an incredible amount of battery life. I know you love your AutoBrightness, but it sets the brightness unnecessarily high, so until someone makes an AutoBrightness app with customizable overall brightness (once I get into programming apps for the Droid a bit, I might do it), you're left with doing this yourself.
Download and install the Brightness Rocker Lite (free) app from the market.
It displays a brightness bar everytime you bring up the volume control and thus lets you quickly change the brightness. Use the minimum brightness to see everything clearly and you should conserve a lot of juice.
7. Only use wireless functions when needed.
Having the mobile data connection, wifi, GPS or bluetooth enabled all the time causes severe battery drain. Sometimes even after you disconnect, the data connection connects again without you even knowing, downloading Over-the-Air updates or Weather, draining your battery unnecessarily.
Have a quick way to monitor which services are on and to turn them off (preferrably, have a widget/widgets on your home screen - I recommend the native Android widgets).
8. Recondition your phone for your battery after flashing each new Android build. (Thanks to t1h5ta3 for this tip)
Flashing a new Android build erases the battery stats and automatically rebuilds them based on voltages it sees, i.e. you need to recondition after each flash to get max battery life. The values are stored in the following file: data/system/batterystats.bin – if you delete this file, you set the new ground for making a new one from the value you want.
You can use the "battery life" widget by curvefish to show you temperature, voltage etc. What you're going for is voltage larger than 4.2 V on full charge.
To recondition:
Turn off the phone, plug it in, preferably overnight.
Boot the phone up while still pluged in.
Delete the batterystats.bin file ether through adb or terminal.
Drain the battery fully, until it powers down. Wait a minute or two and reboot it to drain it completely.
Congrats... your phone now knows corect voltage values for 100% and dead.
To delete the batterystats.bin file:
Find the means to be able to punch in lines of code. You can do this either by downloading and setting up the Android SDK or using a simplifying app like Droid Explorer. Do a google search for whichever you prefer.
Punch in the following code:
Code:
rm data/system/batterystats.bin
Or just find the file in Droid Explorer and delete it.
What DOESN'T improve battery life:
Getting a slower (and thus presumably less power-consuming) SD Card – because a slower SD card actually makes things worse as it needs more time to perform a task and thus keep the CPU busy a longer time.
Underclocking your CPU too much – similar reasons
Killing tasks automatically immediately after closing them – this apparently makes battery life worse, because when a program is in RAM, it doesn't consume system resources, but when you run it again, it does. Thanks to hastarin for the clarification.
Useful threads concerning battery life:
[REF] UPDATE: ALL GOVERNORS! Save battery while running ANY Android build (featured by the xda crew)
battery voltage / wipe batt stats
Battery Solution the **FINAL POST**
Time to Recharge to Full Battery
[TIPS] Thoughts on improving battery life for Android on the HD2
[UPD] 48hours + battery with mDeejay Froyo Z v1.7
Best SD Card for Overall Android Battery Life
Increase Battery Life [WinMo registry tweaks - Need confirmation] (do give this a try)
Hope this helps. If you have more tips or on-topic threads, I'll be delighted to add.

also see http://forum.xda-developers.com/showthread.php?t=827355
a properly conditioned battery does wonders for battery life. a fully charged battery shuld be over 4.2v . i was finding that depending on the the true state of charge when flashing, that is the level that was being assumed by the phone as " 100%" charged. ie: when i flashed my current rom it quit charging @ only 3.7xx volts... far from fully charged.
see my thread on the file to delete etc.
edit: after doing alot more research; heres what ive found...
for what its worth: Li-Io battery technology realy isnt different whether it be a phone, rc car, etc...
our batterys are a single cell. ie: rated 3.7v
4.2-4.25v is concidered by the industry as fully charged
3.7v is nominal voltage
3.2v "shorted" voltage : ie: voltage sag due to max discharge @nominal voltage
3.0v discharged
2.5v protection circuitry kicks in.
this jives with what i am now seeing on my phone after wipeing stats and calibrating...
it is also a industry standard to fully discharge ( 3.0v )about every 30 discharge cycles.
edit

Thanks, I added your tip in the first post (will add the link to your thread too, forgot to do it now and can't edit within 5 minutes of last edit yet)

no problem.
im new to playing with the hd2, but been playing with android for well, just about 2 years (early G1 adopter)
it shocked me coming to this forum and seeing the same question worded diferently atleast 7 times on the first page.
lets hope mod's will sticky this..

I'm no expert but from what I've been seeing the difference setCPU makes with the new hastarin kernel's is negligible. In fact I don't think you can use setCPU with with r8 anymore...

Excellent thread! All info was scattered throughout the forums, and this is a nice thread to sum up everything!
Indeed, using hastarin's R8 you won't need to use setCPU since hastarin has included an interactive governor in his kernel
R8 is a vast improvement over the older kernels, I would reccommend it to everybody that uses Android on his/her HD2!

Slampisko,
Very nicely done and there should be more informative guides like this!
Should be made an instant sticky.

PLEASE do yourself a favor and don't use an automatic task killer. Just because an app is in memory doesn't mean it's using CPU and therefore battery but it will use it to run it again after you killed it.
If you must tweak things here use Autokiller Memory Optimizer to change the levels the out of memory optimizer kicks in at.
Of course if you have an app that refuses to close or is just chewing cpu for no reason then manually killing it is fine.
More info linked in my FAQ in my sig.
Sent from my HTC HD2

Thanks for all the feedback! I'll edit the first post to include the additional info...

Hey guys, cool guide
I tried somes tuff, and read various posts, but somehow I cant figure out why my HD2 with MDJ FroYo Sense Clean v. 2.2 [kernel: hastarin R8] keeps sucking the battery empty so far.
Only program i installed in addition to the Android version mentioned above, is the Current Widget to the how much mA it drains.
Those are my settings:
MDJ FroYo Sense Clean v. 2.2 [kernel: hastarin R8]
GSM only (2G)
Data disabled
Wifi disabled
GPS disabled
Bluetooth disabled
syncing disabled (Background data + auto sync both disabled)
I also killed all running things that i think i dont need and still Current Widget shows me, battery drains in standby 55mA-60mA
So i was wondering what i am missing??? since most of the users get a standby mA of 8 or below... I tried for several days now, but somehow i cant find a solution...

just an update from me....
after conditioning the battery, im currently @27 hours since unplugging, gps, and wifi turned on the entire time, im @ 3.873v or 61%! granted, its been light usage its my secondary phone right now, but i am on the outskirts of service, and the week signal usualy sucks the battery...
ill update again , probably this time tomorow once it finaly dies...
<edit> as you can see in post #2, after 27 hours of up time, i still have higher battery voltage than what the phone was assuming was 100% on initial flashing of the rom...... just food for thought...

That's very interesting, t1h5ta3... Trying it right now, will edit post with results

<Quote>Killing tasks automatically immediately after closing them – this apparently makes battery life worse, because when a program is in RAM, it doesn't consume system resources, but when you run it again, it does. Thanks to hastarin for the clarification.<End>
Do not necessaryly agree. A 'program' is a collection of endless conditions and calculations that puts strain on the CPU. Unless a 'freeze program' function is built in to Android to literally freeze a program when its idle in ram the, the program will still continue to consume valueble cpu power just to stay idle albeit at a reduced rate. But having many program in memory in this state can tax the system performance draining the battery.

I don't have the file batterystats.bin in data/sytem!!!
Any help?
Edit: In fact i found it with root explorer search however i am enabling view of hidden files and i don't see it!
Does deleting it While in android by root explorer will cause any problem?!

@Life Engineer: Nope, I deleted it by Droid Explorer's console while having android up and running and nothing bad happened.

Slampisko said:
@Life Engineer: Nope, I deleted it by Droid Explorer's console while having android up and running and nothing bad happened.
Click to expand...
Click to collapse
BTW i don't agree saying that conservative is the best governor; i guess many accept with me; latest tests showed that interactive is the best and it worked for me!
You may consider putting it in the thread

@Life Governor: I was thinking about that too. Will edit thread.

Question when it comes to draining the battery which side do I drain it on win or Android?

@WCENIGHTCRAWLER: Android I suppose, as Android needs to know the correct voltage for drained battery.

Slampisko said:
@WCENIGHTCRAWLER: Android I suppose, as Android needs to know the correct voltage for drained battery.
Click to expand...
Click to collapse
I'm unsure on this as well. Maybe I'm a bit behind on all the dev that's happened. But I remember if draining battery in Android, it messes up with the build on the SD card.
Might give this a go tonight and see.

Battery issue (AndroidOS "bug") - workaround (3% loss over 9 hours!!!) - final update

Battery issue (AndroidOS "bug") - workaround (3% loss over 9 hours!!!) - final update
Yes, I know, another battery thread. But after scouring many other threads for scraps of information, I feel I still have something to contribute on this widely talked about topic. If you’re not interested, don’t read or write on this thread – save your time, and mine. If it is useful to you, then great, please let us know. Here goes.
Like many people, I’ve been plagued with poor battery life on my SGS2. There are plenty of threads out there discussing how to trace the battery consumption back to the “Android OS” processes, specifically the “events” & “suspend” processes. Unfortunately, once isolating those processes, there’s not much we can do. Some say that when we get Android 2.3.4, battery issues might be solved, however:
My first Android phone was a HTC HD2, which was actually a WinMo phone that some clever people had managed to get a working Android ROM for. I started with Android 2.2.1, and as updates were released, upgraded to 2.2.2, 2.2.3, 2.3.1, 2.3.2, 2.3.3, and then I moved on to a new phone. All throughout these different Android versions, I had excellent battery life. The power draw on standby would be between 4ma – 6ma. (Unfortunately we can’t measure the power draw on our SGS2s.) If my phone was fully charged at night, I would wake about 8 hours later, to around 92% battery left. My SGS2 has more like 40-70% after that timeframe. The HD2 had great battery life before 2.3.4. We can all theorise about whether 2.3.4 will fix the issues, but I don’t know, you don’t know, and life goes on. (Personally, I suspect the Samsung base rather than the Android build, but that’s just a guess.)
So I decided to do a systematic approach to troubleshooting the battery issue on my phone, and identified the following possible causes & possible resolutions, based on other people’s comments, and a bit of logic:
• Battery itself
• Battery calibration
• Data connection
• Wifi
• Bluetooth
• GPS
• Location-awareness
• Latitude
• FastDormancy
• Phone connection
• SD card
• Kernel
• CPU speed
• Task killer
• Live Wallpaper
• Launcher
• Widgets
• Applications
• Stock vs custom ROM
• Hard-reset/data-wipe
Some details about my SGS2.I have a lot of applications installed, including the following that are always running (as services):
• WhatsApp
• PhoneWeaver
• Enhanced SMS & Caller ID
• NetQin Anti-virus
• Extended Controls
• Executive Assistant
• Enhanced Email
• Droidin
• Astrid Tasks
• SystemPanel
• SwiftKey X Beta
As well as the standard Samsung & Google background services.
I have used various versions of VillainROM, LiteningROM, and am now on CognitionROM 1.06. (All similar battery usage for me.)
I use LauncherPro Plus home launcher, and also have plenty of widgets on my screens:
• Beautiful Weather
• Agenda Plus
• Jorte
• Extended Controls
• Elixir (updating every 10 secs)
• LauncherPro Plus Facebook
• BBC News
• SetCPU (updating every 30 secs)
• 4 other miscellaneous small widgets
Ok, so here are my results, after testing most of the possibilities, for at least a couple of hours each, and some of them for longer:
Battery itself
I have 3 batteries, and all perform similarly, high drain occurs.
Battery calibration
I have used a battery calibration app several times, and followed the instructions to the letter, high drain still occurs.
This is however, still a useful process when changing ROMs, to help your battery stats be more accurate.
Data connection (tested for 8 hours multiple times)
Data connection turned off, high drain still occurs.
Wifi (tested for 8 hours multiple times)
Wifi turned off, high drain still occurs.
Bluetooth (I usually keep this off)
Bluetooth turned off, high drain still occurs.
GPS
GPS disabled, high drain still occurs.
Location-awareness
All location-awareness methods disabled, high drain still occurs.
Latitude
Never joined, high drain still occurs.
FastDormancy (tested for more than 8 hours in all 3 modes)
1. Default settings, high drain still occurs.
2. Configured for correct settings (my network supports FD) in /data/data/com.android.providers.telephony/databases, high-drain still occurs.
3. Disabled FD completely, high drain still occurs.
Phone connection (tested for 10 hours)
1. Set to GSM only, high drain still occurs.
2. Flight mode enabled (ie all network off), high drain still occurs. This is significant!
SD card
Removed external SD card, high drain still occurs.
Kernel
1. CF-Root KE7, KE8, KF1, KF2, KF4, high drain still occurs.
2. Cognition 1.03, 1.04, 1.05, 1.06, high drain still occurs.
CPU speed
Throttled to maximum 800mhz, high drain still occurs.
Task killer
1. Advanced Task Killer auto-kill when screen off, high drain still occurs.
2. Advanced Task Killer auto-kill disabled, high drain still occurs.
3. Advanced Task Killer auto-kill every hour, untested.
Live Wallpaper
I use a LWP that I have written, and am fairly satisfied that the code is efficient, and does not take up any noticeable amount of CPU when the phone is in standby. However, untested.
Launcher
Tried using LauncherPro, high drain still occurs.
Tried using TouchWiz, high drain still occurs.
Widgets
Removed all my widgets, <insert fanfare> high drain disappeared!!!
WiFi Sharing
Not exactly the "Android OS bug", but it can cause other battery drainage issues. I freeze it with Titanium Backup to prevent any grief.
Applications
Untested.
Stock vs custom ROM
Untested.
Hard-reset/data-wipe
I am sceptical of this approach, as it changes too many settings. Yes, everything will be faster, with less issues, more battery life, etc, when you do a data-wipe. However, once you configure everything back to how it was before, you’re in the same boat as when you started, and none the wiser.
So! A couple of important findings:
1. With Flight-mode enabled, I get poor battery. This pretty much eliminates any possibilities of 2G vs 3G, FastDromancy, and anything else that uses phone/WiFI/BT type stuff.
2. Widgets are what trigger the issues for me. I use a lot of them, and some of them update frequently. Android should be able to handle this, but something (probably either Android or Samsung code) is adding some battery overhead. This may be fixed by Google or Samsung in the future, but until then, I need a workaround. The next step for me is to add my widgets back in gradually, and see which ones trigger the battery grief. I'll update this thread with my findings regarding which widgets cause me grief, once I have them.
I'm back to having all my location services, data, phone, HSDPA/3G, SD card, and other basic services enabled. The only thing I don't have, is widgets on my homescreen, and battery performance is good.
Hopefully this will be of some help to those people still struggling with battery issues! If you're having battery issues, remove your widgets, monitor for at least a few hours, and report back!
------------------------------------------------
Update - 23/06/11
Every night at 10pm, my Data, AutoSync, & WiFi, are all switched off by PhoneWeaver. This should mean that minimal battery life is being used. I still usually get 30-60% drain though, which as we all know, is due to the "Android OS bug".
Last night, after having removed all my widgets, I charged my phone to 98%, and it entered its usual "Night mode" at 10pm. At 7am this morning, it automatically (via PhoneWeaver) went back in to "Home mode", which enabled AutoSync & WiFi. At 7:15am, my alarm went off, woke me up, and I checked the battery usage. It was down to 95%.
That's 3% drainage over 9 hours and 15 minutes!!!
This is the battery life that we should be expecting when we have things like Data & WiFi turned off.
I value my widgets, but I also value battery life. I'm going to keep working to find a decent compromise between the two. In the meantime, if you need battery life now, maybe consider removing some or all of your widgets.
------------------------------------------------
Update - 24/06/11
Last night, I re-added all of my widgets except Elixir, charged the phone to 100%, and let my phone enter "Night mode" (Data & WiFi off). Again, 9 hours later, WiFi auto-enabled, sync operations completed, etc. I checked it at 9 hours 15 minutes, and battery remaining was down to 96% - only 4% drop over the 9 hours. Similar to the night before. Very happy with that.
I've done a couple of tests today, and have found that adding the Elixir widget back on, brings back the "Android OS bug" for me. I have a lot of items configured in my Elixir widget (including some that show internal storage usage and SD card usage), and although I had set it to update only every hour, it still seems to trigger the hogging of my CPU by "Android OS". I'm going to try some different configurations of the Elixir widget (as it is a useful app), but at this stage, I've narrowed the battery issue trigger on my phone, to Elixir.
I haven't really heard of any confirmations from anyone else, that removing widgets has helped with their battery issues, so if you do have success with this, please let me know. I doubt it's specific to Elixir, but if you're affected, then the trigger may be something similar on your phone. If you want to test, I suggest the following:
1. Freeze the "Wi-Fi Sharing" app in Titanium Backup, as it commonly causes other battery drain issues. (Use "Wireless Tether" if you need that functionality.)
2. Remove all widgets from your home screen.
3. Turn off Data & WiFi connections.
4. Stop any running foreground applications (such as games etc), or reboot your phone.
5. Charge your phone, and note your battery percentage.
6. Turn off your screen, and leave it off for at least 2 hours.
7. Turn your screen back on, and check your percentage.
8. If there has still been a high drain (any more that 1 or 2%), check your battery usage to see if "Android OS" is the culprit.
9. If it's something else, target that. If it's still "Android OS", then I guess widgets are not your trigger.
10. Let us know whether it worked for you or not!
------------------------------------------------
Update - 28/06/11
Probably the last update from me, as my battery usage is nice and stable now, and I have no other information to give.
Happy to hear success stories from a few people - removing widgets has improved their battery life. Obviously we don't want to be removing all of our widgets, as if we wanted to cripple our phones, we'd probably just get evil iPhones, instead of the powerhouse that is the SGSII. For me, I've been able to add all my widgets back in, and narrowed down the drain to Elixir. Fortunately, I've found that I can use Elixir without any issues, as long as I take out the CPU & storage card stats icons. Even though I had it set to update only ever hour, it would still drain my battery way too quickly. I can live without a running commentary on how much free space I have on my SD card, and how much CPU I'm currently using. (SystemPanel gives me all the monitoring I need.)
So if you're still having trouble, my advice is to:
first calibrate your battery with a battery calibration tool (or manually delete your battery stats file)
second, freeze the "Wi-Fi Sharing" app, and
third, check your widgets. Most widgets probably won't impact your battery noticeably, and shortcuts shouldn't either. Once you've tracked down the problem widget(s), try to determine whether you can reconfigure it/them to avoid the drain (perhaps with less updates).
Some battery usage results from posters:
lindsaytheflint - 0.32% per hour, over 9.5 hours, in flight-mode.
JJEgan - 0.08% per hour, over 13 hours, in flight-mode.
sjedwardz - 1.77% per hour, over 22 hours.
So we can get good battery life with these phones, even without 2.3.4, and with only a little bit of tweaking. Obviously, using the phones (i.e. screen on) will (and should) use the battery faster, so the important test is while the phone is in standby. Good luck!

lindsaytheflint said:
Yes, I know, another battery thread. But after scouring many other threads for scraps of information, I feel I still have something to contribute on this widely talked about topic. If you’re not interested, don’t read or write on this thread – save your time, and mine. If it is useful to you, then great, please let us know. Here goes.
Like many people, I’ve been plagued with poor battery life on my SGS2. There are plenty of threads out there discussing how to trace the battery consumption back to the “Android OS” processes, specifically the “events” & “suspend” processes. Unfortunately, once isolating those processes, there’s not much we can do. Some say that when we get Android 2.3.4, battery issues might be solved, however:
My first Android phone was a HTC HD2, which was actually a WinMo phone that some clever people had managed to get a working Android ROM for. I started with Android 2.2.1, and as updates were released, upgraded to 2.2.2, 2.2.3, 2.3.1, 2.3.2, 2.3.3, and then I moved on to a new phone. All throughout these different Android versions, I had excellent battery life. The power draw on standby would be between 4ma – 6ma. (Unfortunately we can’t measure the power draw on our SGS2s.) If my phone was fully charged at night, I would wake about 8 hours later, to around 92% battery left. My SGS2 has more like 40-70% after that timeframe. The HD2 had great battery life before 2.3.4. We can all theorise about whether 2.3.4 will fix the issues, but I don’t know, you don’t know, and life goes on. (Personally, I suspect the Samsung base rather than the Android build, but that’s just a guess.)
So I decided to do a systematic approach to troubleshooting the battery issue on my phone, and identified the following possible causes & possible resolutions, based on other people’s comments, and a bit of logic:
• Battery itself
• Battery calibration
• Data connection
• Wifi
• Bluetooth
• GPS
• Location-awareness
• Latitude
• FastDormancy
• Phone connection
• SD card
• Kernel
• CPU speed
• Task killer
• Live Wallpaper
• Widgets
• Applications
• Stock vs custom ROM
• Hard-reset/data-wipe
Some details about my SGS2.I have a lot of applications installed, including the following that are always running (as services):
• WhatsApp
• PhoneWeaver
• Enhanced SMS & Caller ID
• NetQin Anti-virus
• Extended Controls
• Executive Assistant
• Enhanced Email
• Droidin
• Astrid Tasks
• SystemPanel
• SwiftKey X Beta
As well as the standard Samsung & Google background services.
I have used various versions of VillainROM, LiteningROM, and am now on CognitionROM 1.06. (All similar battery usage for me.)
I use LauncherPro Plus home launcher, and also have plenty of widgets on my screens:
• Beautiful Weather
• Agenda Plus
• Jorte
• Extended Controls
• Elixir (updating every 10 secs)
• LauncherPro Plus Facebook
• BBC News
• SetCPU (updating every 30 secs)
• 4 other miscellaneous small widgets
Ok, so here are my results, after testing most of the possibilities, for at least a couple of hours each, and some of them for longer:
Battery itself
I have 3 batteries, and all perform similarly, high drain occurs.
Battery calibration
I have used a battery calibration app several times, and followed the instructions to the letter, high drain still occurs.
Data connection (tested for 8 hours multiple times)
Data connection turned off, high drain still occurs.
Wifi (tested for 8 hours multiple times)
Wifi turned off, high drain still occurs.
Bluetooth (I usually keep this off)
Bluetooth turned off, high drain still occurs.
GPS
GPS disabled, high drain still occurs.
Location-awareness
All location-awareness methods disabled, high drain still occurs.
Latitude
Never joined, high drain still occurs.
FastDormancy (tested for more than 8 hours in all 3 modes)
1. Default settings, high drain still occurs.
2. Configured for correct settings (my network supports FD) in /data/data/com.android.providers.telephony/databases, high-drain still occurs.
3. Disabled FD completely, high drain still occurs.
Phone connection (tested for 10 hours)
1. Set to GSM only, high drain still occurs.
2. Flight mode enabled (ie all network off), high drain still occurs. This is significant!
SD card
Removed external SD card, high drain still occurs.
Kernel
1. CF-Root KE7, KE8, KF1, KF2, KF4, high drain still occurs.
2. Cognition 1.03, 1.04, 1.05, 1.06, high drain still occurs.
CPU speed
Throttled to maximum 800mhz, high drain still occurs.
Task killer
1. Advanced Task Killer auto-kill when screen off, high drain still occurs.
2. Advanced Task Killer auto-kill disabled, high drain still occurs.
3. Advanced Task Killer auto-kill every hour, untested.
Live Wallpaper
I use a LWP that I have written, and am fairly satisfied that the code is efficient, and does not take up any noticeable amount of CPU when the phone is in standby. However, untested.
Widgets
Removed all my widgets, <insert fanfare> high drain disappeared!!!
Applications
Untested.
Stock vs custom ROM
Untested.
Hard-reset/data-wipe
I am sceptical of this approach, as it changes too many settings. Yes, everything will be faster, with less issues, more battery life, etc, when you do a data-wipe. However, once you configure everything back to how it was before, you’re in the same boat as when you started, and none the wiser.
So! A couple of important findings:
1. With Flight-mode enabled, I get poor battery. This pretty much eliminates any possibilities of 2G vs 3G, FastDromancy, and anything else that uses phone/WiFI/BT type stuff.
2. Widgets are what trigger the issues for me. I use a lot of them, and some of them update frequently. Android should be able to handle this, but something (probably either Android or Samsung code) is adding some battery overhead. This may be fixed by Google or Samsung in the future, but until then, I need a workaround. The next step for me is to add my widgets back in gradually, and see which ones trigger the battery grief. I'll update this thread with my findings regarding which widgets cause me grief, once I have them.
I'm back to having all my location services, data, phone, HSDPA/3G, SD card, and other basic services enabled. The only thing I don't have, is widgets on my homescreen, and battery performance is good.
Hopefully this will be of some help to those people still struggling with battery issues! If you're having battery issues, remove your widgets, monitor for at least a few hours, and report back!
Click to expand...
Click to collapse
Thanks for the in-depth analysis.
I figured it as much that it had to be Active Widgets that cause a higher drain than normal. I dont have any widgets active and dont have any drain, but I can see them running as a service.
I always wondered that if they were removed from the service, will the battery life improve or not make any difference, since the widget isnt really running, only the service. Force Quiting the Widget Service only has them come back shortly after.

Ok I jump in. I've the same issues. Now I disabled my lockscreen (widget locker) and deleted all my widgets. I'll report later if this was the key. BTW what about the screen settings for the brightness? I've set my brightness to 40% static.
Sent from my GT-I9100 using XDA App

What kind of router do you have? Your drain is to high to be just the android-os bug.
Sent from my GT-I9100 using XDA Premium App

[germany]merlot said:
BTW what about the screen settings for the brightness? I've set my brightness to 40% static.
Click to expand...
Click to collapse
I haven't looked at the brightness, as I've been troubleshooting the drain issue purely for when the phone is in standby (i.e. screen off). My display is set to automatic brightness.

TheGhost1233 said:
What kind of router do you have? Your drain is to high to be just the android-os bug.
Click to expand...
Click to collapse
My home WiFi router is not the issue. I only have WiFi enabled for a few hours each day, but my drain is always. My tests included disabling all network connections.
A drain of 30-60% (i.e. resulting in 40-70% left after 8 hours from a 100% charge) is typical of the kind of issues a lot of people have been having. If it wasn't so bad, so many of us wouldn't be so desperate to have it fixed. And yes, my battery usage in both the built-in battery tracking, & SystemPanel, both indicate "Android OS".

Hmm..it could be because I also have high drain and I currently have 13 widgets on my homescreens:Simple calendar, Simi Clock, Spotify, 7xHangping chinese, Snowstorm (update every 3h), CNN(update every 6h), Pure messenger(update every 6hours).
I wouldn't want to get rid of any of those widgets because after all these are the main difference compared to iPhone. What is the point of having Android if you just want the icons on your homescreen.
On the other hand I have been wondering one other issue with the battery drain. When I used to have Touch Pro 2, I used many different ROMs and there the battery was hugely affected by which radio it had. For example I live in Finland and if I used chinese rom with chinese radio the phone did work but the signal was never as good as with European/Finnish radio and also more drain affected.
I noticed similarity when updated to Hong Kong firmware, I didn't get so good signal in any place and I think I lost more battery.
Of course this isn't the whole solution if the battery drain is high also with the airplane mode. But for me even if I turn the data off and use only 2G I get pretty decent battery. So I think there is more than one problem effecting this.
I THINK that CNN widget might be quite bad for the battery..that I could try to get rid off..

There have been plenty of reports of people with a specific router that, once connected just one time, will cause high drain until you do a factory reset. And yes it also displays under android-os but it's a second bug.
Sent from my GT-I9100 using XDA Premium App

I lost 30% battery from 100 to 70 in 8 hours i slept. The only thing that was on was the yahoo mail push service. I deleted all the widgets that came pre-installed except the time/date one on the home screen. The phone was locked with screen off and brightness set to 0.
Is this normal? I have frozen a lot of samsung apps and services that are not needed.

Maybe its launcher pro, I might try deleting that and see how it goes for a while

Hi TS,
good effort here. i am wondering, after you removed all the widget and experiencing better battery life, does Android OS still use high usage?
this is the first android phone that i notice Android OS taking up such a significant portion. all my previous phones, one hardly notices it's usage in the battery stats.

Great list with tests! Although I don't think widgets are causing the high drain. It's something more deep underlying in the stock ROM... All working ROMs are based on the stock one and that's why we all have the Android OS bug.
I've seen people that report no Android OS drain on AOSP ROM (which someone only got booting, it's not usable but there is no battery drain). On the MUIUI ROM which we also got booting is also no battery drain...
What we can do now is WAITING... until we either 1. get a new updated ROM from samsung which solves the issue. or 2. we get a clean and stable CM7 ROM
Thanks my opinion...

Think I'm going to post this everywhere as there seems to be huge amout of people that blame poor battery life on this bug even if it's not the case.
The example of my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

djfatrod said:
Maybe its launcher pro, I might try deleting that and see how it goes for a while
Click to expand...
Click to collapse
Yes, next thing I was going to try was a different launcher. I may still try switch to TouchWiz, and putting on all my widgets. Launcher Pro doesn't have any such issues with other Android phones I've had, but there may be something in the SGS2 code that causes an incompatibility.

sunwee said:
Hi TS,
good effort here. i am wondering, after you removed all the widget and experiencing better battery life, does Android OS still use high usage?
this is the first android phone that i notice Android OS taking up such a significant portion. all my previous phones, one hardly notices it's usage in the battery stats.
Click to expand...
Click to collapse
After removing the widgets, Android OS is no longer high. Other things are now higher (such as when I use the phone etc) which is what you'd expect in Android.
I agree with you - I haven't had this issue on other phones either.
(TS?)

d3sm0nd said:
Great list with tests! Although I don't think widgets are causing the high drain. It's something more deep underlying in the stock ROM... All working ROMs are based on the stock one and that's why we all have the Android OS bug.
I've seen people that report no Android OS drain on AOSP ROM (which someone only got booting, it's not usable but there is no battery drain). On the MUIUI ROM which we also got booting is also no battery drain...
What we can do now is WAITING... until we either 1. get a new updated ROM from samsung which solves the issue. or 2. we get a clean and stable CM7 ROM
Thanks my opinion...
Click to expand...
Click to collapse
I agree - I don't believe the widgets are the cause, but I do think having widgets is triggering the high drain. Something in Samsung's build is doing it.
I'm sure on a AOSP, MIUI, or CM7 the issue won't occur. It doesn't occur on proper builds on other phones. Just something in Samsung's build.
Definitely looking forward to a working non-Samsung build!

Personally I doubt, that the Battery usage stats from android give enough details about the battery usage. Therefore I think its misleading...
Btw, I am on stock rom KE7, no bug/drain here...

aurelm said:
Think I'm going to post this everywhere as there seems to be huge amout of people that blame poor battery life on this bug even if it's not the case.
The example of my phone:
Click to expand...
Click to collapse
I'm not sure what this adds, or how it's relevant. I don't think you read my first post properly, or if I was unclear, then I apologise.
The issue I was having, was that my phone was discharging very rapidly, even under various different scenarios, including my phone display being switched off for 8 hours, and flight-mode being enabled, etc. After this 8 hours of non-use, the battery would have discharged by 30-60%, and the "Android OS" processes (specifically, "suspend" and "events") were taking up around 90% of the usage.
This thread is not about debating the existence of the "Android OS bug", nor about how to identify it. This thread is about testing to see what can be done to workaround the "bug".
I think you also missed my statement in the first post: "If you’re not interested, don’t read or write on this thread – save your time, and mine."

pik1 said:
Personally I doubt, that the Battery usage stats from android give enough details about the battery usage. Therefore I think its misleading...
Btw, I am on stock rom KE7, no bug/drain here...
Click to expand...
Click to collapse
System Panel gives quite a bit of useful detail around things like CPU usage, which is a significant factor in battery usage.

lindsaytheflint said:
System Panel gives quite a bit of useful detail around things like CPU usage, which is a significant factor in battery usage.
Click to expand...
Click to collapse
It is actually interesting to see that there is Accu weather, AP mobile, digital clock and all those rest apps in the memory even thou I dont use them and never even opened them.
Sight...maybe I have to root the phone once again and freeze those apps after all even thou I was wishing that I could just keep my phone close to stock.

[Tips & Tricks & Discussion] Battery Calibration/Improving Battery life

Battery Calibration/Improving Battery life
Requirements:
Device needs to be rooted "Obviously".
Need to have Rom Tool Box Lite or Rom Tool Box Pro.
Some Basic Knowledge on how to use the app.
Note: Turn off Wi-Fi, Bluetooth, GPS, and Auto-sync if they are not in use. Hold down the notifications bar to disable them and activate the Power Saving mode which will make the device conserve energy under low battery state.
Battery Calibration Procedure.
1. Use your phone until the phone battery drains out completely and device gets switched off
2. Switch on the Device to make sure battery really is 0%.
3. Now plug in charger (Device turned off, Dont turn on the device)& leave it for charging until it reaches 100%
4. When the battery is full, switch on the phone, unplug the charger & check if the battery drops by 1 or 2% immediately.
5. If you notice battery drops immediately plug in charger once more (while the phone is on) & let it charge completely.
6. Once charging to 100% is done, don't disconnect the charger, open your root explorer, Provice RW permissions.
7.Search for 'DATA' Folder then 'SYSTEM' Folder.
8.In the 'System' folder you will find 'batterystats.bin' delete this file.
9.Exit Root Explorer and Use your phone normally unless it completly drains the battery(Dont connect your charger)
10.Power On your device and charge your device untill it reached 100%
11.Now you should enjoy the Samsung long Battery Life!!
Note: These methods are not permanent this worked for me so sharing with you.
Greenify your Apps:
NEW: Non-root working mode is now supported in 2.0+, Greenify is a convenient utility that will consequently hibernate battery hoarding applications that wait out of sight after you're done utilizing them.
Google Playstore & Thread
Titanium Backup:
Great battery life, wonderful execution and cool customization— we have seen one or more applications for these things. Presently we should see an alternate must have and a standout amongst the most evaluated applications for established Android gadgets. On the off chance that you got root benefits on your gadget, Titanium Backup is an exceptionally suggested application for you. You may discover various reinforcement applications at the Google Play Store, however none of them does the employment so splendidly and pleasantly.
Google playstore

The KERNEL can do some important things to help with battery saving as it is the controller of all things working in your phone:
1. Underclocking - if you feel your phone is fast enough, go ahead and lower the maximum frequency of your CPU, it will save power as the faster the CPU goes, the more energy it uses.
2. Undervolting - it's more complicated; every CPU requires certain amount of supplied voltage to run and the amount increases with the speed of CPU (clock frequency). For example 200Mhz requires only 0.9V while 1600Mhz requires 1.25V by default. The thing is, the higher the voltage, the higher the heat and of course power consumption. So the best way to lower it is to lower voltage - Samsung had to set voltage at the high enough level that every CPU they produce would work correctly but every CPU is different and some of them allow for lowering voltage and still remaining fully stable thus using less power to do the same work. Typically you can save about 0.05V but some CPU will allow as much as 0.1V to be saved. The same really goes for our GPU part, it can be undervolted as well. There are other parts in our phone that can be undervolted, like memory or controllers of various part but I have found (well in my phone) that saving were very small and caused instability so I would not recommend playing with them. We could think about undervolting our display as it is the biggest consumer of energy in our phone but actually we are doing it all the time The voltage supplied to the screen decides its brightness so if we were to lower the voltage it would just get dimmer
3. There are small savings to be had in various other parts controlled by the kernel:
- first and second thing are tied with SDcard - using it carries high power requirements - the less we use it, the better. Now we can't reduce to completely as all our data, apps and whole system is on it but we can reduce it's use by setting various caches.
a) read cache for internal and external SD combined with scheduler that minimizes reads and writes - so far the best scheduler created specifically for mobile SD use is FIOPS, so using that with a large buffer (maximum of 4096) is actually the best from energy standpoint.
b) system swap space - some kernels allow for creating a very specific kind of swap space, Android will use it once the free memory falls below certain point. Normally this swap space would be placed on SDcard but in this case it's inside a specific region of RAM. Why it is created like this? Because it can be easily compressed to keep more data, so basically we are using Android mechanisms and compressing memory so we can run more apps and keep them in physical RAM That means they are accessible faster than if we were to read them from SDcard and they use less power. Compressing and decompressing data as they go in and out of swap space is still far less energy consuming process then reading them from SDcard.
- third is governor configuration - governor is a system service that decides at what frequency should the CPU be working at every moment and how much cores should be enabled - this of course has great impact on energy consumption and on the smoothness of our experience with our phone. There are two schools of setting up governor and they base their decisions on two premises:
a) sharply increase CPU speed to get the work done fast and sharply decrease speed once it's not needed.
b) slowly increase speed and only so much to do what must be don then slowly decrease speed once you are done because you may have to do something again in a moment
There are pros and cons of both ways - way A means jumping to high frequency for a short time but high frequency uses comparatively large amount of energy, way B means slow increase but also means remaining in intermediate states for longer actually using energy for longer. I don't have any way to actually measure the resulting energy consumption but way A has a distinct advantage of creating much smoother experience so I use that myself.
- fourth is hotplug configuration - our CPU can dynamically enable and disable additional cores - the process is called hotplugging. Some governors are created specifically for controlling this process, the best, as far as I have tested, in this is Lulzactiveq. Hotplugging has to be wise as to the IF and WHEN to enable and disable additional cores, it measures how many "packets" of data are in queue to be processed and based on short history anticipates increase and decrease of workload.
All those interesting options are configured in scripts created for main contemporary kernels: Nadia, Devil and Agni and available HERE.
Latest OC / UV Scripts for Devil / Agni and Nadia Kernels for Note 2 are HERE
Guide to EXT4 to F2FS migration for Note 2 is HERE
CourtesyMat9V

Reserverd

very useful info , thanks :good:

rraaka said:
very useful info , thanks :good:
Click to expand...
Click to collapse
Your welcome :good:

Very briefly stated.
Thanks for sharing
I read all your posts, This will help me in my next configuration for Emotion V7, Nadia with mat's script.
Now on Emotion V6 ....AGNi Pure Stock v4.2.2

yogi909 said:
Very briefly stated.
Thanks for sharing
I read all your posts, This will help me in my next configuration for Emotion V7, Nadia with mat's script.
Now on Emotion V6 ....AGNi Pure Stock v4.2.2
Click to expand...
Click to collapse
Glad you liked it.

The android system, unlike other OS's actually displays the battery reading from a written data config, known as battery stats in general. While there is, in perception no disadvantage to this method of reporting the average remaining battery life, it isn't the actual battery life you are getting, but the percentage read from your daily usage and then sends the information to the OS for displaying the battery life. Due to this, you can have the percentage misreported, so it is suggested to factory reset every 6 months on stock unrooted and if rooted wipe battery stats using rom toolbox free/pro every 2 weeks to ensure correct reporting of your battery life.
Note - This won't increase battery life, but will ensure correct reporting of battery percentage, which gets messed up quite quickly on custom roms(for some unknow reason).
Undervolting can cause battery drain or better battery life depending on your configurations, if you have the CPU set to running high many of the times(like from a governor or background apps that need regular wakelocks for syncing content) it will slow down the ramping up of frequencies during deep sleep(no effect when screen on) and thus it will hold a longer wakelock for the purpose, so undervolt carefully depending on your usage - mild to mid(medium to high undervolt), mid to high(low to medium undervolt), heavy(low to no undervolt).
Different governors have different scaling methods for CPU, thus will give better or worse battery life depending on your config and usage. A governor ramping up faster and scaling down slower will give better battery life in scenario of heavy usage because the device can go to deep sleep state faster and perform background syncs in an instant; while someone with low to mid(or a bit high also) would like to have a governor that ramps up slower and scales down slowly too so as to complete the syncing of files and media scan(if running) and make the device perform smoother and go into deep-sleep and remain in the state for longer times(though going to DS mode will be a bit slower than a fast downscaling governor) and will occasionally wake up for background syncs, but those will be longer, but won't have much effect on battery life because of lower frequencies being used and syncing complete before high frequency threshold is reached.
Depending on what a user needs for his daily usage it is a good idea to keep the rest of apps(preferably facebook, musixmatch, instagram and shazam) hibernated using something like greenify(which now supports auto-hibernation without root in the beta versions). Auto sync should only be enabled for apps that need it, like E-Mail, Google+, Gmail etc.and rest should be set onto manual sync.
Samsung has a habit of throwing in a lot of features onto their device, so keeping motions enabled, which you don't even use, except for a show-off, is a bad idea because it will drain battery. Exploring the settings menu to disable unneeded things can pay-off as a positive fruit for patience.
Keeping the storage clean is also a good way. A corrupted or highly filled up storage requires more passes to be read and thus keeps the media scanner process running for longer, which puts a strain on the battery life. Also, android OS is based of the 32-bit kernel of linux(for now, 64-bit is planned to be introduced after some time), so the media scanner has to look for data linearly in the storage blocks on the internal and external SD, unlike 64-bit where the data is arranged into random blocks which are then brought together as one and the media scanner can be informed of the address of the blocks due to more threads allowed to be run for same process and also a higher memory bandwidth allocated to each process so as to make it perform faster. Due to this reason, the media scanned isn't informed of all the addresses on the time of data writing and thus has to scan linearly looking for bits of data. So keep the storage clean and minimal. Cloud is a good way if you have decent internet and won't need access to the files stored there in regular period of times.
If using a custom rom make sure that it either comes with the modem for your region or flash the modem of your region after that, so as to ensure better signal stability and thus better lasting battery life. A correct modem can give more dBm of signal at the same place as compared to a wrong one.
A good way to have stable battery life is to enable power saving mode in areas with low signal and when on low battery life only, keep it disabled otherwise or it will slow down the race-to-idle for Deep sleep mode and hence cause a bit more battery drain just before deep-sleep state.
Having location services enabled all the time isn't a good idea either, use it only when needed and keep GPS off otherwise. Samsung allows toggling of most things from notification panel so use it.
Smart stay, smart pause, smart scroll all use the front camera for detection, which requires high voltage for operation(separate from CPU, uncontrollable by software) so keep them off unless needed.
Make sure to keep your device clean. How does this affect battery life? Dust and other things when collected around pins, sockets and connectors prevent efficient passing of electricity and thus forces the device to demand more energy, around half of which is taken away by these. Even metallic dust can have adverse effect due to it making the transfer more rapid and forcing the battery to supply the power, which is most probably wasted.
Automatic brightness is good during daytime, but useless during late evening and night, because brightness level doesn't need to be changed and it keeps the light sensor activated. Disable it after 7 Pm(you can also set up tasker or some other automation tool for this).
An Odexed rom provides more battery life as compared to deodexed, but at the cost of available customization as no mods will work and will instead crash the file related to them. Choose your side wisely and patiently.
If you're going to use some app, check if it uses GCM for providing notifications(usually google search at your service), if not look for an alternative which does. GCM doesn't even use marginal amount of battery and is more efficient in providing the notifications at time and also doesn't need a persistent notification.
Check for wakelocks thoroughly and remove the misbehaving apps or hibernate them if you need them on your device. Also, be sure to update the apps for receiving any fixes and optimizations, which can sometimes also decrease the required wakelock frequency for an app and thus preserve battery life.
Don't keep too much of auto updating widgets on homescreen, these only serve to drain the battery further by auto syncing.
if rooted, use Xposed and boot-manager to disable unneeded apps at boot time and thus preserve battery and time required for full boot-up.
If on a custom kernel use DAC direct(if available) for sounds. This bypasses the output mixer and thus preserves a little bit of battery required to produce and refine the sounds, instead utilize 128x oversampling and FLL tuning for an even better quality.
Don't reboot on a regular basis unless needed, this will eat up battery life quicker.
Don't use any task killer( a long debate on uselessness of those can be found on many sites, with a simple google search), the Android system's LMK is itself more than enough.
Be sure to research carefully on what you really need and what you don't and then use it. Don't go on downloading useless things which you'll delete later on because it creates a small entry in /data/data which gets scanned by media scanner due to being present in its path and thus will make the process longer and more battery hungry.
Some custom kernels allow for controlling deep sleep type. Usually these types are already defined in the kernel tweaking app itself. A person with heavy usage should use the IDLE deep sleep more so the device is able to wake up quickly and doesn't drain much battery in case of many wakelocks. Similarly a light user will benefit with AFTR+LPA due to CPU deep sleep, but this isn't advised for medium to heavy usage(use IDLE+LPA instead) because the wakelocks require a high power to even wake up the device, which will drain more battery if you use your mobile more, because many apps will try to acquire a partial/complete wakelock.
I know this is quite long, but read through carefully and you'll surely get better battery life.
Source : Experience and Google groups

Good knowledge
Thanx

cartmanez said:
Good knowledge
Thanx
Click to expand...
Click to collapse
People are still spreading the batterystats.bin myth? *facepalm*
This has been totally and utterly disproven many, many times, including by core Android developer
So delete away. It doesn't calibrate or improve your battery life though.

I cannot study myself all technically like you what you mentioned in "[Experience][Share]My Usage and Testing of Custom kernels for Touchwiz Kitkat".
But above is well informative and now i get why i was getting worse battery life & longer wakelock by OC and UV with selective governer.
By testing different setting in AgniPureStock 4.2.2 today i reach 25 hr + battery life with my moderate usage.
I am sure above valued information, i will get most out of my battery.
Thank you very much KNIGHT97 for sharing.

aukhan, Hi mate, do i need to install greenify too?

botski said:
aukhan, Hi mate, do i need to install greenify too?
Click to expand...
Click to collapse
Yes
Sent from my GT-N7100 using Tapatalk

aukhan said:
Yes
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
if i use greenify i need to install xposed framework too?

botski said:
if i use greenify i need to install xposed framework too?
Click to expand...
Click to collapse
Xposed is optional. It is only for the experimental features. However, the developer has got 1 or 2 of those working without Xposed in the latest beta(you'll need to join the greenify G+ community for getting the beta, though)
Sent from my RPG with auto targeting

非常有用的信息，谢谢 ：好：

thanks for the info man.....its very helpful
aukhan said:
The KERNEL can do some important things to help with battery saving as it is the controller of all things working in your phone:
1. Underclocking - if you feel your phone is fast enough, go ahead and lower the maximum frequency of your CPU, it will save power as the faster the CPU goes, the more energy it uses.
2. Undervolting - it's more complicated; every CPU requires certain amount of supplied voltage to run and the amount increases with the speed of CPU (clock frequency). For example 200Mhz requires only 0.9V while 1600Mhz requires 1.25V by default. The thing is, the higher the voltage, the higher the heat and of course power consumption. So the best way to lower it is to lower voltage - Samsung had to set voltage at the high enough level that every CPU they produce would work correctly but every CPU is different and some of them allow for lowering voltage and still remaining fully stable thus using less power to do the same work. Typically you can save about 0.05V but some CPU will allow as much as 0.1V to be saved. The same really goes for our GPU part, it can be undervolted as well. There are other parts in our phone that can be undervolted, like memory or controllers of various part but I have found (well in my phone) that saving were very small and caused instability so I would not recommend playing with them. We could think about undervolting our display as it is the biggest consumer of energy in our phone but actually we are doing it all the time The voltage supplied to the screen decides its brightness so if we were to lower the voltage it would just get dimmer
3. There are small savings to be had in various other parts controlled by the kernel:
- first and second thing are tied with SDcard - using it carries high power requirements - the less we use it, the better. Now we can't reduce to completely as all our data, apps and whole system is on it but we can reduce it's use by setting various caches.
a) read cache for internal and external SD combined with scheduler that minimizes reads and writes - so far the best scheduler created specifically for mobile SD use is FIOPS, so using that with a large buffer (maximum of 4096) is actually the best from energy standpoint.
b) system swap space - some kernels allow for creating a very specific kind of swap space, Android will use it once the free memory falls below certain point. Normally this swap space would be placed on SDcard but in this case it's inside a specific region of RAM. Why it is created like this? Because it can be easily compressed to keep more data, so basically we are using Android mechanisms and compressing memory so we can run more apps and keep them in physical RAM That means they are accessible faster than if we were to read them from SDcard and they use less power. Compressing and decompressing data as they go in and out of swap space is still far less energy consuming process then reading them from SDcard.
- third is governor configuration - governor is a system service that decides at what frequency should the CPU be working at every moment and how much cores should be enabled - this of course has great impact on energy consumption and on the smoothness of our experience with our phone. There are two schools of setting up governor and they base their decisions on two premises:
a) sharply increase CPU speed to get the work done fast and sharply decrease speed once it's not needed.
b) slowly increase speed and only so much to do what must be don then slowly decrease speed once you are done because you may have to do something again in a moment
There are pros and cons of both ways - way A means jumping to high frequency for a short time but high frequency uses comparatively large amount of energy, way B means slow increase but also means remaining in intermediate states for longer actually using energy for longer. I don't have any way to actually measure the resulting energy consumption but way A has a distinct advantage of creating much smoother experience so I use that myself.
- fourth is hotplug configuration - our CPU can dynamically enable and disable additional cores - the process is called hotplugging. Some governors are created specifically for controlling this process, the best, as far as I have tested, in this is Lulzactiveq. Hotplugging has to be wise as to the IF and WHEN to enable and disable additional cores, it measures how many "packets" of data are in queue to be processed and based on short history anticipates increase and decrease of workload.
All those interesting options are configured in scripts created for main contemporary kernels: Nadia, Devil and Agni and available HERE.
Latest OC / UV Scripts for Devil / Agni and Nadia Kernels for Note 2 are HERE
Guide to EXT4 to F2FS migration for Note 2 is HERE
CourtesyMat9V
Click to expand...
Click to collapse
Thanks man....you rock:good::good:

What about using Juice Defender (available in play store)? I used the basic one first and then ended up buying ultimate because I saw good results. Now the location (using cell tower) based WiFi enable/disable extends my battery life significantly.
The is one of the first apps I install once I feel a new flash is stable.

If you have the Samsung "Toolbox" utility, that floats a button on the screen to access your choice of five apps from anywhere - turn it off. It causes the "security storage" process to peg at 20% all the time the screen is on if "Toolbox" is enabled. When "Toolbox" is disabled, "security storage" process drops to a couple of percent when the device is idle. There's quite a saving on battery drain.

Battery calibration
I have a rooted Nook HD+ running Android 7.1 and I decided to calibrate its battery.
I ran it down to zero as recommended then attached it to the mains.
All I have had for several hours is a black screen with just the charging symbol (battery with lightning inside it). Nothing else, no progress bar, no charge %, nothing Androidy.
Is this as it should be and should I just wait for several more hours or is there something wrong?
Many thanks.

[GUIDE] MIUIv6 tuning

I love MIUI but was very dissapointed when the S4 mini ROMS (MIUI6_5.5..29v2_Multi - KK.4.4.4 and Unoficial MIUIv5 KitKat 4.8.24 from s4 mini (i9190/i9195) left me with a battery drain of 10% per hour.
I know that most people here seem to be running fine on this ROM, but maybe this can help someone who encounters similar problems. I have the I9195 black edition euro, and after fiddling around for days I am now at ~2% battery drain per hour.
Always on LTE heavy bandwith usage (bright green in battery manager)
Had to set up a custom battery usage profile with the switch 2G/3G on. (Power->Power Settings->Profiles)
This didn't really made the system switch between networks, but it changed it to LTE low bandwith usage (olive green)
Smart Network is a feature rich tool to setup connectivity profiles for screen off and on.
IMO better than Intelli3G. With screen off 2G I connect to EDGE, which still provides minimal data for checking IMAP or whatsapp.
Google Services battery drain
I prefer Disable Service, since it shows which processes are active (blue) and can sort them according to CPU time.
There are different guides and lists on the web what services are safe to disable.
Make a backup in CWM, then go to battery usage and look what consumes battery.
Consult lists and use Disable Services to stop the processes.
Delete MIUI apps
System App Remover is your friend. You might have to stop the process first in order to be able to uninstall the app.
There are bloatware lists and system apps which are safe to remove. It depends on what features you want to use.
In my case "backup", "blocklist" and "assistant" were often running.
Battery Guides
Here is another useful guide. There are more topics like kernels with different governors or even undervolting, but I think these will have a minor impact on battery life.
Greenify
Didn't work for me. For 3€ you can use the experimental features of this app to freeze system apps, but I was more sucsessful in optimizing manual.
I want to thank all the people who put their effort into ROM development or creating useful guides.
Peace out.

I have same problem. Battery draining %1 per minute. When I use the my phone 5 minutes, the screen is too hot. So i can't touch the screen. I tyr al lot of methods. But I can't solve the problems. I have 9190. I'll try your methods. I hope this will solve my important problem.

set battery mode on efficient

[Guide] Optimizing Battery Life

Hey Guys, Kyuubi10 back again with a quick guide on improving the battery life of the HTC One M8.
Let's be honest, this phone is getting quite old now. You can already start to feel it lagging, and slowing down. And the battery doesn't last as much as it once used to.
But don't give up hope...your M8 isn't dead yet, and with some good management it can even rival 2016 flagships.
Let's begin with Marshmallow...
If you have not updated your M8 to Android 6.0 yet, WHAT ARE YOU WAITING FOR?
Marshmallow is the best version of Android yet, the efficiency of Lollipop with the Stability of KitKat, and a very fresh take on Battery saving!
Reasons why you should update ASAP:
1 - Lollipop's memory leaks 99% fixed (Don't want to say 100% due to the possibility of some existing out of my limited knowledge, but for all intents and purposes there are no more memory leaks.) This is very important, because the memory leaks were both draining battery life, and slowing down the device...which in turn keeps the screen on longer and wastes even more battery.
2 - Doze!!! It's the latest battery saving feature to be added to Android, and it's basically a SUPER idle state, where the phone if left untouched with screen off for long periods of time will not waste any battery whatsoever! I tested this when going to sleep, phone was in airplane mode, battery saver turned on, screen brightness at minimum...I left it at 100% charge, I woke up it was still at 100%. With airplane mode off, and battery saver turned off the phone lost only 3% battery overnight.
This being said, true battery saving is measured while using the phone right?
It's not about how long it can last without being used, but how long it can last while being used.
But what if you already are on Marshmallow, and your battery life is still not cutting it?
The following solutions are organized from simpler to more complex.
1 - Follow this official HTC guide: Tips for extending battery life. It provides tips on reducing screen brightness, keeping connections off when you're not using them (Wi-Fi, Data, BT, GPS, NFC etc...), lowering volume and vibration strength and using power saver mode.
While their advice is quite obvious stuff, and most of you probably do it anyways, I would like to stress the use of power saver mode when you are out and about away from a convenient power source. Doesn't matter if your battery is at 90%, turn PS mode on, you will barely even feel a difference, but your battery will last you much more than before!
2 - Buy yourself a smartwatch. While it may seem counter-productive to keep Bluetooth on constantly to keep connected to the watch, it actually improves battery life by helping you avoid turning on your phone's screen. At the end of the day the battery saving that comes from it may be equivalent to the drain caused by bluetooth being on, or even greater than the drain. Thus effectively saving you battery life, and being convenient while doing it.
3 - Here comes the big one...ROOT your device and install a custom ROM and Kernel. Just by installing an optimized ROM and optimized Kernel you will get battery savings + better performance. Often you will also have settings you can tweak to optimize battery savings at the cost of performance or vice versa. And with a custom Kernel you can choose one with battery saving CPU governors.
4 - CPU Governors. CPUs, just after your screen, is the second most battery consuming hardware part in your device. Especially since it is on most of the time. Choosing a governor that can make it's job more efficient can save you bucket loads of battery.
The most common one for battery life is called "Conservative", and it will provide you with considerable battery life at the cost of performance. But if you want both good performance and good battery life then you are probably looking for a governor which employs the "Race to Idle" ideology. (If you don't know what it is, do a quick google, it's easy to understand.)
A good option I like to recommend is Wheatley, but if your kernel choice lacks it then interactive will be good enough...but you will have to tweak it's settings yourself to make it most efficient. Couple months ago I created this guide which you may find helpful when tweaking the interactive governor.
5 - Since we have spoken about Rooting then let's start adding some ROOT apps to the mix. Greenify would be my first recommendation.
For 2 main reasons... 1, It helps you stop annoying, battery draining apps which keep themselves running in the background. 2, It's latest versions have included a feature where you can set Doze to start sooner than default. Thus allowing you to reap Doze's benefits earlier and for longer.
Talking about the annoying apps, there's one in particular which comes to mind....Facebook.
Personally, while I don't like it's battery draining, I also don't want to uninstall it...since it's quite useful. Thus in Greenify I found my answer!
6 - Last but not least, if you are noticing unusual battery drainage, but you can't find which app is causing it (or may even be a system app), or if you notice that Doze is not having any effect... it might mean that a wakelock is not letting your device idle for long enough for Doze to start.
For this you will need an app called "Wakelock Detector". Charge your phone to around 80-100% and place it on a desk and let it idle for a couple hours (e.g. When you are asleep). When you are back check what WD found, and it might surprise you. (I found an app called HTC Mode which was keeping my device awake and preventing Doze from starting.)
Another advantage of this app is that once you find the wakelock it links you to Greenify through which you can put that specific app to sleep. Thus preventing it from setting the wakelock again.
If you follow all these steps, you should be able to feel the considerable difference in battery life. Reminding you why you fell in love with this device
I hope I have been of help, I noticed that there weren't any Battery Guides specifically made for the M8, so I thought I would leave one here in case anyone is looking for one!
If I have helped you make sure to hit that :good: button, I will greatly appreciate it, and you will be helping the community find this guide more easily.
Thanks for reading! Enjoy your longer lasting M8!

Thank you for the Info! Before marshmallow I used "app ops" but this doesn't work on Android M. Because of the app wakelock detector I removed the messenger app from facebook. It drained my battery. Thank you.
Sent from my htc_m8 using XDA-Developers mobile app

adgadg15 said:
Thank you for the Info! Before marshmallow I used "app ops" but this doesn't work on Android M. Because of the app wakelock detector I removed the messenger app from facebook. It drained my battery. Thank you.
Sent from my htc_m8 using XDA-Developers mobile app
Click to expand...
Click to collapse
App ops is good for permissions, and stopping an app from connecting to the internet. Android M already has a permissions feature natively included.
What you want is to stop it from running in the background.
While you can uninstall it (and probably find another app which you can use facebook messenger in. e.g. Disa), I would personally recommend you simply use greenify to put it to sleep.
All official facebook apps are huge battery drainers, but greenify will keep them in check, so that you don't have to use another app with less functionality.
Obviously I am not forcing you lol, but it is my recommendation.