Related
Better Battery Life Tips
I've been using (and tweaking) Android devices since the original HTC Dream (aka G1, Android Dev Phone) was released, and I've had devices that are both good and bad at power consumption. In this thread I will share what I have learned and invite you to share what you have learned as well so that we can all get the most out of our devices.
Please note that I like to keep my smartphones "smart" and don't like to be manually toggling things on and off throughout the day. If you like to geek out 24x7 you can manually turn on/off every feature of your phone every time you use it to conserve juice... that's not me though!
Here we go...
-Consider a Different Browser
It seems like Opera Mobile and Mini are the kings of battery conservation. I tried Dolphin, Boat, Firefox, Chrome, the stock browser, and about 10 others... I didn't see significant differences in battery with any of them, but with Opera I noticed the difference. It makes sense since Opera renders the pages and optimizes the images remotely and then sends the bare minimum amount of data to your device to display the page.
-Location, Location, Location
Android's location related services can be a big drain. There are 3 different location settings you need to know about.
1) Location Access (Settings -> Location access): For maximum savings, you can turn off "Access to my location". However, there are many apps that make good use of your location. If you don't want to cripple them, leave this option turned on but at the very least uncheck "GPS Satellites" to save some juice.
2) Google Apps Location Settings (Settings -> Accounts:Google -> Location settings): Allows Google apps, such as Google Maps, to access your location. Why this needs to be separate from #1 above is beyond me, but turning it on requires the above setting to be on as well. If you don't use Google Maps, Now, Plus, or any other Google services that use your location you can turn this off.
3) Location Reporting aka Latitude (Settings -> Accounts:Google -> Maps & Latitude -> Location Reporting): This is the bad one. Really bad. Wakelock and battery drain city. I don't even know why anybody would want this. Kill it with fire. Set it so that it does not update or report your location.
-Turn off stuff you don't use
This should be common knowledge by now... if you aren't using GPS, Bluetooth, or even 4G... turn them off. If you don't need instant notifications and app updates you can even turn off Auto-Sync. If you decide to do that, I recommend the Synker widget from the Play Store. It is nice and configurable so that you can sync on demand with one touch.
-ROMs and Kernels
I'm not going to go into these too much here... there's a whole development section devoted to them with tons of info. Generally you get the best life from the stock based ROMs. Liquid Nitro and HO!NO!'s v20f (+Wind kernel) are quite good. Next best is probably HO!NO!'s CM9. The CM10.1 ROMS and kernels have a bit of catching up to do at battery consumption, but they keep getting better.
-Kill Google Talk!
If you don't use this program, disable it. It is always trying to do something on the network. Even if you turn off data and wifi you can still get NetworkConnectivity wakelocks from this app trying to do its business! Killing it is the first thing I do after flashing a ROM, especially CM10.1. From home hit: Menu -> Manage Apps -> All -> Talk -> Disable.
*Some report that disabling apps through the Android OS might not stick. If this is a concern for you, download NoBloat or Titanium Backup and freeze this app. Or if you're a nerd like me, use a root file explorer and move or rename the .apk file in /system/app
-Kill Google+ (Plus)
Just like the above, if you don't use it, deactivate it. It also uses data and location services pretty regularly. Disable it in the same way, or use NoBloat or Titanium.
-Kill Google Now
If you don't use it, deactivate it. It uses data and location services pretty regularly. I like its features and keep it enabled on my N7, but leave it off on my phone. To turn it off, go into the Google Search app (long-touch menu/search button), hit Menu -> Settings -> Google Now. You'll see the option to disable it.
-Data-Toggling Battery Saver Apps
These are pretty controversial, almost as much as app-killers were when they were very popular. In a nutshell they turn your data connections on or off based on whether your screen is on or off. They usually will check to see if you are downloading or streaming anything before they shut off the connection. Then, they periodically turn the connection on while the screen is off so that the device can perform a sync to get emails, etc.
Should you use one? If you are running CM10/10.1/AOKP4x then YES USE ONE!! EDIT: THE LATEST VERSIONS OF QUATTRIMUS AND WIND FOR CM10.1 HAVE RESOLVED THE BATTERY DRAIN ISSUE. Use of a battery saver is no longer essential. If you still want to use one, read on...
Whether or not you use a battery saver depends on how you use your phone, and if you are willing to accept the trade-offs. These apps get their savings from maximizing deep sleep time for extended periods with zero data concerns or interruptions. If your usage habits allow the app to do its job, use it. If not, don't use it.
[What follows here is some long drawn out jibber jabber about the pros/cons of these apps. Read it if you like]
Some people love these battery saver apps and swear by them; others hate them. The reason some like them is because they get a few more hours of battery life. The reason why some people hate them is because:
1) They wake the device periodically to do their job... which negates some of the power savings you get from having them. To some people these tiny wakelocks are the most horrible thing ever... even if their impact is quite small compared to the power being saved. These people are usually the ones who live and die by their BBS logs. I'll admit, I was one of those people
2) Syncs are delayed, so messages and notifications do not arrive instantly but when either of the following conditions are met-
a) The screen gets turned on (which triggers data on and autosync)
b) The program hits a scheduled time trigger (usually at user selectable intervals)
3) There's a small lag while data connects when the screen gets turned on. If the screen gets turned on very frequently the constant on/off/syncing can actually hurt the battery more than it helps.
But, if you are ok with the delayed syncs and you set up the sync intervals long enough apart you WILL see a gain in battery life. Your phone will sleep much more soundly as well. With one of these apps my Nitro HD on CM10.1 can sleep all night and will only lose maybe a percent or two.
*Note that these will NOT help you at all when the screen is on, which is a bummer because the Nitro screen sucks down a LOT of power. Also, your usage patterns may make them ineffective for you... in which case you are probably better off without them.
Personally I get about an hour or 2 of extra life if I use one, but it's a trade-off since I lose instant notifications and a there's a slight delay while it reconnects to the network when the screen gets turned on. And the more you turn your screen on/off, the more it disconnects/reconnects/syncs... meaning it is using a bit MORE power than usual for those seconds.
[/jibberjabber]
The following are my favorite data-toggling battery-saver apps. All of them have "free" versions and more advanced "pro/prime/advanced/whatever" paid-for versions. These are not the only ones out there; feel free to report back on ones you prefer. If you find one that you really like, I suggest buying the pro version not only for the additional customization they offer, but to support the devs for a job well done.
1) DS Battery Saver - Super easy to configure and since it kills background tasks before sleeping it puts your device into a nice deep sleep. Also combines the feature of CPU Sleeper if you are rooted... it'll shut off a CPU core when sleeping.
2) Green Power - Works really well. The interface is simple and well laid out. I used it for years before I discovered DSBS.
3) Juice Defender - Another decent app, similar to Green Power. I personally preferred the options and the interface of GP better, but you may not.
4) CleverConnectivity +++Battery - The interface is a bit weak, and I had problems with the full data on/off features working on my P930 w/CM10.1... BUT this program has one very cool feature- it has an option for dropping the connection speed down to 2G/EDGE when the screen is off instead of disabling it completely. This allows syncs to still occur while still saving some power in 2G. I've even streamed Pandora on 2G, so in theory you could do stuff like that too. This feature worked fine on my P930 dispite the normal data on/off failing intermittently. There is a moment of zero data while it toggles between 2G/3G. I think this app might be awesome when development advances some more.
-Underclocking (rooted users)
Capping your max CPU frequency at a lower limit can save power. Quite honestly, for 99% of my daily use I can't tell the difference between the CPU clocked at 1.2ghz and 1.8ghz except that at 1.8ghz my battery bar laughs at me and gives me a wedgie. On custom ROMs there is often a built-in method to set the CPU clock frequency (Settings -> Performance -> Processor). On stock-based ROMs you'll need a 3rd party app like Kernel Tuner, SetCPU, or any of the other 50 options in the Play Store. You can usually safely set your minimum frequency to 192mhz, but some phone/ROM/kernel/voltage combos will cause stability or lag issues with doing this. YMMV.
*If you are using a CPU controlling app like SetCPU that allows for profiles, you might be tempted to set the screen-off frequencies to the absolute lowest setting of 192/192... be careful! This setting could end up costing more power consumption because the CPU has to work for a much longer time to handle the tasks at hand at such a low clock speed. If it was allowed to ramp up a bit the task would be done more quickly and efficiently. Honestly I gave up on setting screen-off profiles. I just use governors based on smartass which have their own screen-off settings integrated. Less adjustments needed, similar results. This leads us to...
-Changing governors (rooted users with custom kernel)
There's about 50 different governors floating around out there. If you don't know what a governor is or what each one does, read this thread: http://forum.xda-developers.com/showthread.php?t=1736168
In short: Any governor that is based on smartass, ondemand or interactive is going to be pretty light on battery, and you may not be able to tell the difference between them in normal use. I like smartassv2 and badass, which are both based on smartass. Conservative may sound the most battery friendly, but usually ondemand does better and is less laggy.
Try some out. Have fun with it. Eventually you'll want to start tinkering with the I/O Scheduler... that's a topic for another thread. There's not much battery life to be gained there anyway.
-Undervolting (rooted users with custom kernel)
WARNING: This can cause instability if done improperly. MAKE A CWM BACKUP BEFORE TINKERING WITH UNDERVOLTING!!! I've never seen *drastic* gains on any device, but you do get a little bit more life, and every little bit helps, right?
So if you want to do it, read this: http://bigfatreality.blogspot.com/2012/03/guide-to-undervolt-android-safely.html and then proceed with caution.
Generally you can aggressively undervolt at lower frequencies, but be careful at higher frequencies because your device needs more power under load and will not like it if it can't get it. If you're a car guy this is like running too lean of a fuel mixture
Kernel Tuner and IncrediControl have nice GUIs for fiddling with voltages. Remember, adjust in tiny increments, followed by thorough testing! If you get a crash or reboot then you've gone too far. DO NOT ENABLE "SET ON BOOT" UNTIL YOU ARE SURE YOU'VE GOT STABLE VOLTAGES!!!
-Screen dimming
Screen backlights use lots of power. This ain't no AMOLED where you can save power by using dark backgrounds- LCDs light up the entire display regardless of what is on them.
I suggest turning off auto-adjust and set your brightness at a level that is just bright enough to be comfortable. I keep mind around 30-40%. Auto-adjust periodically polls the sensor to get light data, and uses a small bit of power to do it each time.
Turn on the 'Status Bar Brightness Control' if your ROM supports it so that you can easily swipe your finger along the top of the screen to brighten or dim the display on the fly. In CM9/10(.1) this option is under Menu -> Settings -> System -> Status Bar -> Brightness Control.
If you MUST use the auto-adjust, consider adjusting the levels that it uses. Make them as dim as is comfortable for you. For stock-based ROMs you'll need a third party app like this: https://play.google.com/store/apps/...wsMSwyLDEsImNvbS52aXRvY2Fzc2lzaS5sdXhsaXRlIl0.
For CM/AOKP based ROMs this can be done from the Display -> Brightness sub-menu of your device's settings area. CM10.1 has an excellent and simple adjustment interface.
-Build.prop Tweaks (rooted users)
You can add the tweaks below into your build.prop file that may or may not help with battery life. Download BuildProp Editor from the Play Store and add them. They seem to help a bit, but it could be placebo effect. They certainly don't hurt anything so give them a shot and report back what you get. These seem to work with ICS and JB:
ro.config.hw_fast_dormancy=1
ro.ril.fast.dormancy.rule=0
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
^ this forum keeps adding a space near the 16384... there shouldn't be any spaces. I think they get disregarded anyway if they are put in the file, so no biggy.
^some of these have presets in BuildProp Editor, some you have to enter yourself. I copy/paste them individually. Don't paste the "=" signs though. Everything before the "=" goes under "Property Name", everything after it goes under "Property Value". If you are experienced you can edit the build.prop file directly using a text editor. Just back it up first and don't screw with the permissions.
-Some other useful apps that help with battery life:
*CPU Sleeper (root users)- Shuts off all but one cpu core when the screen is off. This probably isn't required with a good kernel and governor setup (and a stable phone that sleeps well), and if you are running DS Battery Saver this feature is built-in to it. It uses barely any resources whatsoever, so give it a shot.
*Greenify (root users)- This essentially freezes selected apps when they are not in use. They cannot do background tasks or wake your phone when they are not active. When you attempt to open one of the apps it instantly thaws them for use. After you are done with them it freezes them back up. It is quite brilliant really! It eliminates a lot of wakelocks and battery drain from apps trying to update, gather location data, etc. Use with caution though- don't greenify apps that you actually need to have a data flow from or ones that you use widgets for.
*RootDim (root users) - You know how when you are using your phone in bed at night and the screen is just too bright, even on the dimmest setting? This app lets you go even dimmer. Less brightness means less power, so it will reduce battery usage in the process.
-Apps that help diagnose battery drains
*Better Battery Stats - Good for discovering the cause of battery-draining wakelocks. Just uninstall it when you're done using it to diagnose- otherwise it is constantly doing its thing which is not going to help battery life any!
*OS Monitor - See if your CPU is settling down like it should and see what is keeping it busy. It also has a ton of other advanced options and features.
...there's too many apps to list here! Share the ones you like I'll add more later.
-Adjust your advanced Wifi settings
Go to Settings -> Wifi, then hit Menu -> Advanced
Most people agree that Network Notification should be UNCHECKED, Keep WiFi during sleep should be 'Always', and 'Avoid poor connections' and 'WiFi optimization' should be CHECKED.
If you have a noisy wifi router (some Netgears are guilty) that keeps waking your device from sleep with wifi packets you may get better results if you change Wifi During Sleep to 'Never' or 'Only when plugged in'.
-Watch the reboots!
Every time your phone reboots, Android checks the SD card for errors and then runs the Media Scanner to take inventory of all media files. Both processes consume power, so try to limit unplugged reboots. The more files on your SD card, the longer Media Scanner has to work, so get rid of unnecessary files cluttering up your card. You may have some luck using .nomedia files to tag directories to be skipped during scanning. You can also use an app like this to disable the automatic Media Scanning Service. It also lets you scan on demand. Caution- If you don't ever do a scan, then new pictures won't appear in your gallery nor will new music appear in your player.
I'm sure I'll think of some things later that I have forgotten, and I'll discover new things... I'll update this when I do.
Please share your findings so that this can be the best battery saving thread... In the world.
Very interesting and helpful info.
Thank you very much !!! :good::good::good:
Couple things I'd add, especially if you're running a CM-based ROM
Get NoBloat and disable the following:
SuperUser - Get SuperSU instead, less battery drain.
CM Update Checker - Every time I use my phone to go online (I don't have data on 24/7) this thing pops up and wants to check for updates, but never properly gets flushed. Disabling this one app dropped my hourly drain by about 1.5% on CM10
jekostas said:
Couple things I'd add, especially if you're running a CM-based ROM
Get NoBloat and disable the following:
SuperUser - Get SuperSU instead, less battery drain.
CM Update Checker - Every time I use my phone to go online (I don't have data on 24/7) this thing pops up and wants to check for updates, but never properly gets flushed. Disabling this one app dropped my hourly drain by about 1.5% on CM10
Click to expand...
Click to collapse
Thanks for this- I just disabled CM Updater.
BTW with JB there's no need to download NoBloat- you can disable most apps (including this one) from the built-in App manager. Settings -> Apps -> All -> CM Updater -> Disable
Here's another trick for a specific type of battery drain: (you don't apply the fix in on your phone though)
Symptoms:
1) Your phone drains its battery while doing basically nothing while connected to your wifi router.
2) BBS shows massive amounts of wlan_rx_wake wakelocks
3) Android OS seems to be a high contributor to battery use
Fix #1: (Found HERE) "Change DTIM value in your router configuration from 1 (default) to 255. This value is usually in Advanced->Wireless tab on most routers."
^Seems to help a lot.
Fix #2: Set a static IP on your phone for your home network. The easiest way to do this is to find out what address range your router uses when it hands out IP address via DHCP, then hard-set an IP on your phone that is not in that range so that there won't be any conflicts with other devices that connect to your network. You'll need to consult your internets and googles to figure out how to get this information from your router, if you don't know how. Once you know a clear address you can use, go into your phones Wifi Settings, long-touch your network name, hit 'Modify', 'Advanced', punch in the static IP you wish to use. This might not be an option on corporate or shared housing wireless routers.
Fix #3: Check ALL computers on your network for the presence of the Dropbox software. Mac, Windows and Linux computers alike. If it is running in the system tray, click it, go into preferences, turn off 'LAN Sync'. This little booger wreaks havoc with wifi locks on some Android devices.
mpsantiago said:
Thanks for this- I just disabled CM Updater.
BTW with JB there's no need to download NoBloat- you can disable most apps (including this one) from the built-in App manager. Settings -> Apps -> All -> CM Updater -> Disable
Click to expand...
Click to collapse
I've found that for whatever reason the built-in app disabler doesn't always work. I still like using NoBloat better.
Second to this, once you do disable a bunch of apps it's good to boot back in to recovery and wipe dalvik/fix permissions.
jekostas said:
I've found that for whatever reason the built-in app disabler doesn't always work. I still like using NoBloat better.
Second to this, once you do disable a bunch of apps it's good to boot back in to recovery and wipe dalvik/fix permissions.
Click to expand...
Click to collapse
I agree.
Thanks for all the info it is very interesting! I'll be trying this
---------- Post added at 01:17 PM ---------- Previous post was at 12:59 PM ----------
Thanks for all the info it is very interesting! I'll be trying this
thanks you. it greats:good:
LTE battery drain
Any good tips for reducing battery drain in LTE and Wifi for 20c?
Updated the OP... from now on I'll just put new tips at the top of the list.
frankshi said:
Any good tips for reducing battery drain in LTE and Wifi for 20c?
Click to expand...
Click to collapse
What ROM are you using and is LTE available in your area?
Awesome guide man, +thanks:good:
Oh this is kinda off-topic but Mattman86 I wanted to ask you, I just installed your Hono CM9 Full Throttle rom and I'm having some issues putting the apps onto my SD-Card. Whenever I move them (through titanium backup or just standard move to sd in settings) whenever my phone restarts the apps disappear and or say "app not installed" then they are a green default android icon and just don't work :\ Also does Wind Kernal work with your 4.0.4 Rom?
alainmona said:
Awesome guide man, +thanks:good:
Oh this is kinda off-topic but Mattman86 I wanted to ask you, I just installed your Hono CM9 Full Throttle rom and I'm having some issues putting the apps onto my SD-Card. Whenever I move them (through titanium backup or just standard move to sd in settings) whenever my phone restarts the apps disappear and or say "app not installed" then they are a green default android icon and just don't work :\ Also does Wind Kernal work with your 4.0.4 Rom?
Click to expand...
Click to collapse
I haven't done anything with CM9.
I currently have the ROM in my signature with Wind Kernel 3.5 and Battery Guru along with SetCPU installed and I get roughly 23 hours of battery.
mattman86 said:
I haven't done anything with CM9.
I currently have the ROM in my signature with Wind Kernel 3.5 and Battery Guru along with SetCPU installed and I get roughly 23 hours of battery.
Click to expand...
Click to collapse
Oh then I'm tripping then haha, I have a question though. I tried installing Liquid Nitro and every time I tend to wipe data, wipe cache, wipe dalvik, and wipe system. It just hangs at the LG logo and I haven't had the ability to try out your v7 or for that matter any of the other previous Liquid Nitro. I'll send you a PM since I can't really post in the development section due to my lack of postage xD :cyclops:
On the CM 10.1M3 with wind kernel 1.8, after one day of normal use with WiFi off and Data Off and Location services off I got Google Maps being the worst offender battery wise, the weird part is that I didn't really used maps that day. So even with everything off some service is still eating bat in background.
Sent from my Nexus 4 using xda app-developers app
Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock detector, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks
I had the very same problem until yesterday myself but think I found a solution on the web.. Uninstall Google Search and Google Play Services and the goto the Play Store and wait for them to reinstall and that's it....! As I found that there is a bug in Google Services (Nlpwakelock and Location service)
Hope this helps...?
Sent from my GT-N7100 using xda app-developers app
terzisc said:
Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock defender, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks
Click to expand...
Click to collapse
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app
yeminswe said:
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app[/
Thanks. I already have Wakelock Detector on. I mistakenly wrote "defender" instead of detector on the original post. It gives me Viber and Messenger as the most active wakelock apps. But they both were not installed when the problem started. Besides, on the 4.1.2 they created no problems. In essence I believe that Wakelock Detector cannot help much. Whatever this problem is , it is well hidden. Thanks for your interest and help anyway. Much appreciated.
Click to expand...
Click to collapse
In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk
Manjunath324 said:
In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thanks, but I have checked and it was not ticked in the first place...unfortunately...
terzisc said:
Thanks, but I have checked and it was not ticked in the first place...unfortunately...
Click to expand...
Click to collapse
Which kernel you are using? And also i recommend using Greenify. Widgets usually eat a lot of battery, I went from battery lasting only 8 hours to get my battery use only 30% in 8 hours.
What i did: installed wakelock detector, gsam battery monitor and better battery stats.
Monitorized the wakelocks.
Applied greenify to the apps which were waking most
Removed widgets which were waking alot
Installed Toggle 2G.
Kernel settings: 200-1600mhz | zzmoove | AFTR+LPA | Multicore power saving (SCHED_MC) = 0 | GPU = stock settings
Works like a charm for me. Hope it helps! Any question, ask!
I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.
Nukkels said:
I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.
Click to expand...
Click to collapse
Thank you for the suggestion. I have already taken the battery on and off several times. It had no improvement. The phone is only a year old, that is why I don't believe the battery is the culprit. Besides, problems started only after the 4.3 update. Before that it was working perfect. Too much of a coincidence.
Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.
Nukkels said:
Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.[/Q
Thanks mate
I think you are right. It is probably a combination of many things. I have opened the Developer options some time back. The one thing that I do for sure in there is limit background processes to 4. Besides that I don't experiment much, exept maybe to change transition animation scale. I am actually thinking of rooting the phone and downgrading to 4.1.2. It was just fine before. I can live without the 4.3 add ons.
Click to expand...
Click to collapse
Problem still persists, even with Google+ and most other Google applications disabled
Sent from my GT-N7100 using xda app-developers app Some screenshots taken from 3 different apps. Wakelock detector, Better battery stats and Gsam battery monitor
Sent from my GT-N7100 using xda app-developers app
The only battery apps on my phone are the 3 mentioned above, so I don't know what the battery monitor that keeps my phone awake is. The drain existed before I installed these apps. I have read that Chrome could prevent the phone from going to sleep but it is disabled on my phone.
Sent from my GT-N7100 using xda app-developers app
http://www.youtube.com/watch?v=ak1sYWRaEKg
I faced same battery drainage issue, after installing wanam kernel and freezing all bloatwares through Titanium Backup. I'm satisfied with my battery now.
You can try.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Here is detail-
Disable sync always, enable when needed.
Disable wifi always scan from settings
Display set to auto
Uninstall apps of playstore you rarely use
Use widgets on lock and homescreen as less as you can (I don't use any)
Disable motion on settings
Freeze all bloatwares by TB except allshare and samsung content agent
Install Agni kernel, from agni control app-
profile: normal
Governor: pegasusq
Scheduler: cfq
Don't touch other tweaks, hardly you can tweak sound boost.
THIS GIVES ME A SATISFIED BATTERY STATUS.
regards.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Wew 4.3 does have may bugs
Hey guys, need some help. I have an AT&T H810 rooted 10o. My little cores seem to be running full out at 1440mhz even though my governor is set to Interactive. This is causing it to heat up incredible, to 70c+, and is draining the battery quickly. It seems to have only started occurring in the last few days! I can run it in powersave governor which fixes it to 384mhz, and it fixes the problem, but I don't understand why it is running at full speed under interactive now. The big cores do NOT have this problem AT ALL.
I've removed any apps I installed during that time, cleared my phones cache, cleared the memory, I have tried running it in airplane mode, I've looked into what apps were running and it seems to be very few. Turned location off. I've tried freezing the play services because I have been getting a very intermittent force close. I have also tried to disable all xposed modules, and used avg to scan for any malware. Possibly init.d? Possibly the new xposed v79? I'm at a loss as to what is causing this!
Does anyone have any other ideas as to what could be happening?
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
spartan268 said:
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
Click to expand...
Click to collapse
Battery usage Android OS is highest at 33, followed by screen at 16%.
Wakelocks, I seem to have them under control with amplify, and I don't see any new ones.
Question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
elementalfusion said:
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
Click to expand...
Click to collapse
Doesn't solve why it's running at full speed, but I'll keep that in mind.
question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Personally I never done a factory reset myself yet so i cannot comment.
For the most part it does look like you have something to work with seeing Android OS is taking up the most battery. The hard part is tracking down which process. I'm not the best at this so maybe someone else can chime in. Try taking a look at your currently running processes and see if there's anything odd
Well, after a few factory resets which did not affect xposed, I was able to resolve it to where the cores now return to 384mhz idle. It was something that was installed, and it took 3 or 4 resets after restoring my app backups, and I'm still not sure which app was the culprit. I'm possibly wondering if it was the Amplify module
Sorry for bumping this. I just suffered from this problem and it seems for me it was antutu. For some reasons it was running the background keeping the 4 small cores at 1,2-1,4 cuz constantly. I stopped it and now it's back to normal. Just wondering why it started itself in the first place.
Sent from my LG-H815 using XDA-Developers mobile app
I even broke my phone with App Ops trying to figure it out, disabling wake permissions for most apps which caused FC's and even reboots. I have since restored all permissions but I still get FC's whenever I leave an app or switch out of it. Not sure if it's really crashing, but I get a FC message every time. So much so that Substratum turned off its theming for Files because it "crashed" after every screenshot was successfully uploaded to this post. Btw I just removed CrossBreed Lite and it seems to have helped. So far no reboots doing the same stuff that caused reboots! Not sure why it caused problems though. I used it for a few days with no issues.
Anyway, back to my battery woes. 30-40% kernel system usage. Why is this happening? Even Snapchat which is abusing wake locks is nothing compared to kernel system.
I'm running the latest build of AIM 8.1 with EX Kernel. I have just visited the other thread about tweaking governer values to optimize battery life so I'll report back with results although I doubt that's relevant to my battery drain.
I've Googled quite a bit on the subject and it seems that each case is different. Usually caused by a certain bug, although a lot of people say it's "normal" which I strongly disagree with.
Update: optimizing the CPU has definitely made an improvement, but the kernel battery drain still exists.
Could it really be pick up to wake and wifi search behind the drain? Isn't this phone supposed to have a sensor hub that allegedly allows for all sensors to constantly be on while using minimal power? I never noticed this drain on any other phone with both of these features on.
Anyway, I disabled pick up to wake and I'll start trying to remember to turn off wifi when not in use.
I think you're trying too hard and running a bunch of stuff. The kernal usage looks about right. I wouldn't run Gsam and BBS at the same time. They can fight each other. What makes you think there's a problem? Nothing jumps out at me.
Sent from my [device_name] using XDA-Developers Legacy app
I also can't see anything out of the ordinary, except this one picture where it shows the phone being active while dozing. I don't know how to understand that because I don't use that app, maybe I'm reading it wrong. What does Android's built-in battery monitor show? Is it dozing properly while screen is off? What is your average SOT? Is your mobile signal strong? I'm also using AIM 8.1+EX combination with satisfying results. Is your radio up to date?
maybe Wakelock Detektor or Greenify can help you.
And if you currently have things crashing all the time, start with a factory reset. Much easier to diagnose the cause when the apps aren't doing random stuff.
So I've been having this issue for quite some time, but i guess i got used to it so it didn't pose much of a problem untill now. All of my Whatsapp messages are delayed when screen off and WiFi on, and they come through from 2-4 all the way up to 20+ min after they are sent. As soon as i turn screen on, they pop up on screen.
I assumed that it was due to greenifys rigorous doze settings, so i uninstalled it. Some threads suggested Titanium backup may be culprit, so i uninstalled it too. I also added Whatsapp to battery optimization whitelist and ticked on run in background and unrestricted data usage, but with no success, and also completely reinstalling Whatsapp.
I even reflashed stock pie and oreo, but same thing happens. I suspected that deep sleep might be interfering with cloud messaging services, but even on stock pie device enters deep sleep even with WiFi on in minutes after screen off, so im pretty confused with it all.
I am running Pie v10.0.9.0.PLDMIXM with magisk, busybox, xposed, substratum, gravitybox installed. Apart from that there are no other apps interfering with the system whatsoever.
Any help would be much appreciated.
CrimosUmbro said:
So I've been having this issue for quite some time, but i guess i got used to it so it didn't pose much of a problem untill now. All of my Whatsapp messages are delayed when screen off and WiFi on, and they come through from 2-4 all the way up to 20+ min after they are sent. As soon as i turn screen on, they pop up on screen.
I assumed that it was due to greenifys rigorous doze settings, so i uninstalled it. Some threads suggested Titanium backup may be culprit, so i uninstalled it too. I also added Whatsapp to battery optimization whitelist and ticked on run in background and unrestricted data usage, but with no success, and also completely reinstalling Whatsapp.
I even reflashed stock pie and oreo, but same thing happens. I suspected that deep sleep might be interfering with cloud messaging services, but even on stock pie device enters deep sleep even with WiFi on in minutes after screen off, so im pretty confused with it all.
I am running Pie v10.0.9.0.PLDMIXM with magisk, busybox, xposed, substratum, gravitybox installed. Apart from that there are no other apps interfering with the system whatsoever.
Any help would be much appreciated.
Click to expand...
Click to collapse
It's the system power and ram management. That system kills the processes and doesn't allow them to revive for instant notification. Same happens with facebook and facebook messenger, not only watsapp. Instagram does this also. I receive a follow notification on my iPhone and the notification appears on the Mi A2 Lite only after the screen is on and unlocked.
TheoXSD said:
It's the system power and ram management. That system kills the processes and doesn't allow them to revive for instant notification. Same happens with facebook and facebook messenger, not only watsapp. Instagram does this also. I receive a follow notification on my iPhone and the notification appears on the Mi A2 Lite only after the screen is on and unlocked.
Click to expand...
Click to collapse
Oh i see. i totally get that over agressive ram managment, because even with 4 tabs open, it kills them very soon, to a no avail have i tried to fix it, it seems to be rooted issue...
Do you know any possible fix or workaround for this? Maybe to convert these apps to privileged, e.g. system apps or something? There must be some kind of solution for this.
CrimosUmbro said:
Oh i see. i totally get that over agressive ram managment, because even with 4 tabs open, it kills them very soon, to a no avail have i tried to fix it, it seems to be rooted issue...
Do you know any possible fix or workaround for this? Maybe to convert these apps to privileged, e.g. system apps or something? There must be some kind of solution for this.
Click to expand...
Click to collapse
Nope. Some said that this is purely Xiaomi's fault. But no. I have another Allview phone doing the exact same stuff. This may be an unmodified kernel for the said chipset. Companies like Samsung, Sony, HTC etc. may edit that kernel to be more mild, while Xiaomi, to reduce the costs doesn't.