Related
PARTIAL WAKELOCKS
PWLs are a different beast. These are almost all caused by an app (with a couple of notable exceptions). For that reason, I won't go in-depth on too many of them, as the solution is usually to delete the app causing them. There are a few notable ones, and a few apps that merit mention.
AudioOut_1, AudioOut_2: This is an evil leech of a wakelock that will drain you dry if given the chance. For being such a pain in the app, it's surprisingly easy to get rid of. This wakelock is created whenever the phone's speaker plays a sound. With 99% of sounds, it goes away almost instantly. With keypad sounds, however, it doesn't go away so quickly, and it will sit there draining your battery for as long as it goes unnoticed.
To fix: Open Settings, then select sound. Turn off keytone sounds, touch sounds, screen lock sounds and vibrate on screen tap. It'll take some getting used to, but the extra battery you'll coax out just by solving this ridiculously simple problem is more than worth it. See DoctorQMM's post (#5), linked at the end of this one, for info on additional causes of this wakelock and how to fix them.
ConnectivityService: This will appear whenever your phone is trying to connect to a mobile data network. Excessive wakelocking here suggests that your phone is having a hard time finding a network, and an even harder time staying on it.
To fix: Test out different radios and see if one's better in your area. I personally have to use UCLF5, as UCLF6 is a mess out where I live. If you're able to control your radio bands and you don't live in an LTE area, setting your phone to hunt for GSM/HSPA connections only can save you a little bit of juice here. Not much, but every drop counts, and if you're not using LTE anyway...
AlarmManager: This isn't a wakelock unto itself so much as it's a compilation of app alarms and the time they held the device awake for. Seeing the wakelock alone doesn't tell you much, but here's where one of those features of BBS that I said we'd be using comes in.
To fix: Open BBS. Tap the menu button, then "More", then "Raw Alarms". That will show you which apps are waking up your phone, and how often they're doing so. Google will have a ton of wake-ups, but they're mostly innocuous. We'll discuss some of Google's problem apps later. Email clients will also have a ton of alarms. If anything else looks out of whack, though, first check the app settings to see how often it's refreshing. If the app is set to refresh every hour but it's set off 400 alarms in the last 30 minutes, get rid of that sucker and email the dev. You can't eliminate this wakelock, and it's constantly my #1 PWL at this point, but you can minimize it.
A special note about this wakelock: You will get all kinds of crazy numbers out of this wakelock. You may see as high as 20m on a 1h30m stretch of battery. You will want to kill this wakelock, and kill it with fire. Don't, I say, don't do it! Look at your deep sleep time vs. time awake - screen on. Odds are, it's far less than the 20m that this wakelock is showing. You may have a time awake - screen on time of less than 3 minutes. What's the reason for the discrepancy? Well, it's well-known that there are wakelocks out there, PWLs especially, that will hold your device awake even if it's already been woken up: i.e., you'll have a PWL registering while the screen is on. Alarms are certainly among those that do so, as they are designed to wake your device up, so that's the first thing they'll try and do. I suspect the remainder of the discrepancy is caused by the way BBS reports. I suspect every alarm is tallied differently, so that if you have two alarms go off at the same time and last for 2 minutes each, BBS will register 4m of wakelock even though it was only held awake for 2m. Make sense? It doesn't for me either, but that's the best pair of explanations I've got, and the numbers seem to back it up.
MediaScannerService: This is a wakelock created by the system as it scans your device for music, movies, pictures, etc. Once in a while, it will randomly get hung up and hold the phone at 384 MHz for...well...until you notice and do something about it. Like AudioOut_1, this is a heavy-drain wakelock. Luckily, like AudioOut_1, it's almost always easy to fix. A note about this wakelock: it's been shown to be an occasional, but serious, problem on Jellybean ROMs. We're still not entirely sure why, let alone how to solve it permanently. That said, haloeight has been able to beat it into submission on his phone.
To fix: Reboot. Ninety-nine times or so out of a hundred, this solves the problem. If the problem persists, go to Settings -> Applications -> Running then tap on "Show cached processes". Find the Media process and stop it manually to kill the wakelock. That's a short-term fix, though, as a persistent wakelock from this process most likely means you have a corrupt media file somewhere on your phone--and there are a lot of sounds, movies and images on your phone. This is one of the few wakelocks that, if it's a regular problem, justifies considering a full wipe and clean reinstall. That's not because it's doing any kind of damage to your phone, but more because sifting through every single media file on your phone to find the culprit isn't really a practical solution. If you've got a persistent wakelock here on a JB ROM, try haloeight's approach above.
SyncLoopWakeLock: This is exactly what it sounds like; your phone is being held awake while apps sync. There are two possible causes for this: apps syncing (duh) and a bad data connection.
To fix: Open BBS. Tap the menu button, then "More", then "Raw Network Stats". This will show you which apps are using the most data, and help you narrow down possible culprits. Once you've done so, check those app settings and make sure they're not set to constantly push notifications, refresh every five minutes or anything dumb like that. If they're set correctly and still holding sync open that long, try downloading the Speed Test app off of the Play Store and test your phone's connection. If your connection is on the slow side, it's possible that the apps are struggling to sync because of your bad data connection. Try flashing different radios to see if that solves it. If the troublesome apps remain so after you've found a better radio, it's best to just delete or freeze them.
ActivityManager family: This is a harmless wakelock. The typical cause is not exiting out of apps fully before turning the screen off.
To fix: Don't sweat this one too much. If it's a big issue for you, make sure that you're exiting out of apps fully (i.e., either use the back button to exit the app or FC it in Task Manager) before turning the screen off. Credit to the XDA Wiki on this one, as this is one of the PWLs I wasn't able to figure out for myself simply because I hardly ever saw it. I use the back key to exit apps.
GTALK_ASYNC_CONN family: Despite its name, this wakelock doesn't seem to be directly related to Google Talk. How do I know? I haven't had Google Talk on this phone in over a month, but the wakelock still pops up from time to time. This wakelock also seems to be related to a poor wifi connection, so keep an eye on that as well. These wakelocks can be absolute destroyers of your battery if given the chance, and unfortunately, there's no known root cause for them, and no reliable way of eliminating them.
To fix: These wakelocks will often disappear within a minute or so of generating. If one becomes persistent, check your wifi/data connection and make sure it's good. If it persists, reboot into recovery and wipe cache and Dalvik ASAFP. That solves the problem temporarily, but it will reoccur. Thanks, Google.
NetworkLocationLocator: What a lovely name for such a lovely wakelock. It's a minor annoyance usually, nothing more. If this one is persistent, it's because you're in an area with crappy cell coverage and very few Google-mapped Wifi networks.
To fix: Why, exactly, are you leaving Network Location on all the time anyway?
NetworkLocationCallbackRunner: Thanks to clankfu and mw86 to pointing this one out, and a huge thanks to promiseofcake for finding the solution. This is the first wakelock published here that's specific to a phone other than the Skyrocket; it's an S3 issue. Hooray, we've gone global! NetworkLocationCallbackRunner is another wakelock caused by that most wonderful of apps, Google Maps. If you're still using it, seriously, why?
To fix: Upon turning on your phone, don't open Google Maps or anything else that utilizes Google location data. Or, you know, you could just uninstall Google Maps and use an alternative program...details below.
show keyguard: This is a new one for me. It had always been there, but since switching ROMs, it's really started to show up. Not in massive quantities, but enough to make me scratch my head. I've already established that setting your lockscreen to not show user info, weather or calendar data will significantly reduce this. I'll play around with adding those back in more, and having sliders on your default lockscreen won't do much damage either. Still, the more people who've goofed around with this one, the better, as it makes this entry all the more accurate.
To fix: I'm testing several possibilities now, but the one that's worked best so far is turning calendar, weather and user info off. It seems that having those on causes the lockscreen to wake the phone to refresh itself, which creates the wakelock. Judging by my recent experience, this seems to be a pretty big leech.
Chekin Service: Thanks to epapsiou for finding this one and confirming my guess on it. Getting tough to test without my Skyrocket being used as a phone anymore. This wakelock, while a Google Services process, seems to be caused by Facebook. That kind of confirms my theory that Facebook "borrows" Google services.
To fix: Uninstall Facebook and use an alternative app, or just access Facebook through your mobile browser of choice.
SCREEN_FROZEN: Uh oh.
To fix: If this is high on your list, you've got bigger problems than a wakelock.
PWL OFFENDING APPS
We're almost done, I promise!
Down here, I'm going to list off for you apps that will cause you severe PWL migraines, and what to do about them.
A note when uninstalling Google built-ins: Google built-ins are often system packages, and deleting them can have unpredictable results. I highly recommend freezing them in Titanium Backup for several days to see how the phone runs before uninstalling them through there as well. Deleting system processes is inherently risky, and I assume no responsibility for your own decisions.
Facebook: Any social networking app will want to sync as often as it can, but you can overrule that by setting notification intervals. Thing is, Facebook doesn't respect those intervals, and wakes up the device for data exchanges pretty constantly (even though your news feed may only update every hour or so when you want it to). This app is no better than bloat, and should be treated as such when you clean house.
Alternative App: Friendcaster and Fast are both great alternatives that let you set how often the app wakes up, but I've taken to just accessing m.facebook.com through the browser of my choice lately.
Gmail: A running theme here will be that if there's a non-Google equivalent to a Google app, you should probably kill the Google and download the alternative. Gmail is an alarm fiend, and one of the main offenders if you have an excessive SyncLoopWakeLock problem.
Alternative App: How many email clients are out there? I've had the best luck with the stock Email app, but K-9, Kaiten, MailDroid, even Enhanced Email and Touchdown for the power users are all great alternatives. Speaking of which...
Whatever email client you're using: Email clients will always be high up on the list of alarms, and that's by their nature. Keep an eye with raw network stats on how long they're connected for, and don't be afraid to experiment. I tried K-9, Kaiten and MailDroid before settling back on the stock Email app as the one that gave me the best balance of battery life and necessary features.
Alternative Apps: Download and try out different clients until you find the one that works for you. Nothing ventured, nothing gained, right?
Google Latitude: Latitude is a tracking service. As such, it tracks you. Beyond the creepiness aspect of that, it holds your phone awake pretty often while doing so. Kill it. Kill it with fire.
Alternative App: Personally, I'm not into the whole stalking thing, but I've heard that Glympse works quite well.
Google Maps: Colossal waste of space and battery. You can do better. An important note on Google Maps: this app will still wake your device up even after being frozen in Titanium Backup. I don't know how it happens, but it does. To truly solve the alarms from Google Maps, you have no choice but to uninstall it. Do so at your own risk.
Alternative Apps: I'm a fan of Waze for navigation and MapQuest for a Google Maps-ish browseable interface. OSMAnd is also a great alternative, but it uses a ton of internal memory because of its offline nature. If you really love Google Maps, reinstalling it from the Play Store as a user app can reduce those wakelocks dramatically.
Google Play Music & Movies: Updates itself constantly and wakelocks. Even if you freeze it, it still somehow manages to tell you that there's an update available. It's the Google zombie.
Alternative App: There are literally 100+ music and/or movie players out there. I'm sure you can find one that works for you. I'm a big fan of RocketPlayer for music, and I just use the stock video app more often than not.
JuiceDefender: What's that you say? JD sets off tons of alarms and holds the device awake for more time than I'd care to discuss, largely because of its data control settings. More harm than good, in my opinion.
Alternative Apps: JuiceDefender's main goal in life is to minimize the amount of time your device is held awake. Therefore, if you've just gone through all this to clear out wakelocks, do you really need another wakelock-prone app to do what you've already done?
Skype: Occasionally, after a call, Skype will wakelock. This is not designed to happen, and is more a glitch in the app than a forced sync. Force-stopping the app and clearing its cache have solved it for me on the rare occasion that I've seen the wakelock occur.
Alternative Apps: No idea. I don't personally consider this a "replace" situation.
World Weather Clock Widget: Do you have this on your phone? Get rid of it. I installed it as an alternative to SiMi Clock Widget, and while it certainly looks pretty, it ignored my "Update every 3 hours" and tried to update 275 times in that 3 hour window. This drove AlarmManager, GSYNC_ACONN, and NetworkStats off the deep end, and left me at 82% deep sleep with 6% of my battery gone in 3 hours. Kill it. Kill it with flaming nuclear waste.
Alternative Apps: I liked SiMi Clock and wanted to try something new, basically. I'm back to SiMi, but there are literally hundreds of clock widgets out there.
Google Search: If you use Google Now, forget trying to fix this one. GNow is a battery hog, and there's nothing you can do about it without crippling the feature. If you don't use GNow, you can use Greenify to hibernate Google Search and stop the persistent alarms and wakelocks it creates. Greenify is a method I hadn't used in the past, but I've grown to like it for hibernating rogue Google apps.
Alternative Apps: A quick look at the Play Store revealed Quick Search to be the second most-popular option after Google Search. I've run devices without Google Search in the past without issue, but it is usually a system app, so freezing instead of deleting would be a safer option.
That's the bulk of what I've learned from clearing out wakelocks. Remember how, early on, I specified that the search engine of your choice was the third tool? Simple fact is, I haven't installed every app on the planet, so I haven't seen every PWL out there. Because of the way my phone's set up, there are KWLs that I've never seen and never will. If you've got a pesky wakelock that won't go away and it's causing noticeable battery drain, Google (or Bing, or Ask.com, or whatever) is your friend. Good luck, happy hunting, and enjoy the extra battery life you'll get just by spending a few hours over the course of a few days tracking down and killing those wakelocks.
Also, be sure to check out Jrockttu's thread on fixing your battery, as there's tons of great information in there.
Additional in-thread references below. If any of these posts helped you out, please click the link down here and send them a thanks.
DoctorQMM covers com.google.android.apps.maps, an alternate fix for AudioOut_1 and using CPU Spy to help track down wakelocks.
kishke tracks down an alternative cause for the sdio family of wakelocks (including sdio_al) and details it for us here.
polarbearno shares their experience with the mmc_detect family of wakelocks.
haloeight gives us some great steps on how to get rid of the MediaScannerService wakelock on AOKP-based ROMs.
promiseofcake solves the S3-specific NetworkLocationCallbackRunner PWL.
Hi,
I am trying to use smartcharging feature on my crdroid ROM. During the charge, when I reach the preset charging value, it is working well as the phone stop charging. However, at this time, I can see with betterbatterystat that a Kernel Wakelock appears and prohibit the deep sleep mode to be enable. The name of this kernel is c440000.qcom,spmi:qcom,[email protected]:qcom,qpnp,smb5.
As a result, the deep sleep consume a lot of battery and the next morning, when I unplug my phone, I can see a huge battery drain around 2-4% per hours, which is not ideal for a smartcharging feature...
Do you know why this kernel wakelock appears? Is it possible to do something to avoid that?
Thanks
A Comprehensive (but not by any means definitive) Guide to Wakelocks
OP edit, January 12, 2016: To say that I'm proud of what this guide grew into would be an understatement, given that drawing it up was a weekend project for me using my old Galaxy S2 Skyrocket and either ICS or JB.
Take that last little bit into account here. It was done over three years ago on an S2-variant phone using Android 4.0 or 4.1. A lot of the specifics here are no longer going to be 100% correct, even if the principles remain true. If you're a rookie de-wakelocking your phone for the first time ever, please take what you see in the OPs with a grain of salt and ask questions in the thread before making any drastic system changes or mucking around in a terminal emulator.
Thanks for stopping by, and I hope you know a little bit more about your phone when you're done here than you did coming in!
-TJ
----
Wakelocks suck. If you're trying to maximize your battery life, you know this already. Some wakelocks are happy, friendly things, but many are silent leeches, sucking away your battery life while you remain blissfully unaware of what's happening. The goal of this guide is to list some of the more common wakelocks you'll encounter and how to wipe them off of your system. As you encounter ones not on this guide, let me know and I'll add them to the list. For some reference, I typically have light to moderate use of my phone. Before de-wakelocking, I was getting maybe 24 hours on one charge. After de-wakelocking, I was up to 36. Then I bought the Galaxy Nexus Extended battery, and on that battery's third cycle, I went two and a half days on a single charge. Impressive, right?
First off, you have to understand the difference between kernel wakelocks (KWL) and partial wakelocks (PWL). KWLs are wakelocks caused at the kernel or hardware level. Some of these are benign, and some of them are vampires. The only way to solve them is to change how your phone behaves. You'll see examples of that below.
PWLs are wakelocks caused by an app. The solution to these, more often than not, is to freeze (or, in the case of Google apps, uninstall) the offending app. Before you do so, and this is critical, go in via Settings -> Apps, force close the app, and wipe its cache and data. If you don't, you'll almost certainly cause yourself more headaches about 30 seconds after killing the app.
Second, you need to know the tools involved in wakelock hunting. The first is Better Battery Stats. Google "better battery stats XDA" and the dev's post will come up; they give this app away to XDA members. That said, if BBS helps you out, show the dev some love and buy the paid version. It's only $2.89, and the dev will have more than earned it from you by the time you've finished de-wakelocking yourself. The other tools you'll need are (hopefully) this guide, and, of course, the Internet search engine of your choice. I won't cover everything simply because I haven't seen it all.
Two final notes before the guide: do not go wakelock hunting right after installing a new ROM or clean-wipe reinstalling your current one. New ROMs cause the phone to go nuts for a little while, as things decache and little behind-the-scenes tweaks are made. Wait one full battery cycle (100% to 0%, which you're probably doing to calibrate after a clean ROM install anyway) before trying this, or you'll drive yourself nuts. Also, remember that solving one wakelock will often create another, especially early in this process. That's normal and to be expected. God does not hate you, your ROM of choice is not crap, your phone is not glitched, and a clean install while your current ROM is still settling in will only make things worse.
So, how do you track these wakelocks down with BBS? This is a really complicated procedure, so make sure you're with me. First, open BBS. Then, see the dropdown menu at the top that probably says "Other" right now? Tap it, and then you'll see "Kernel Wakelocks" and "Partial Wakelocks" below. That was obscenely difficult, right?
Something to note with BBS: it seems to have a weird "counting" bug. While testing a ROM with BBS, I finally began to question why my PWL time would be considerably higher than my true wakelock time. "True wakelock time," simply put, is time awake - time awake with screen on. If your phone is awake for 45 minutes and the screen is on for 40, you have five minutes of true wakelock time.
So why does BBS say that you have 90 minutes of PWLs when you only have a true wakelock time of 45 minutes? Well, I have two theories to account for that. One, BBS counts wakelocks independently, even if they occur at the same time. For example, if AlarmManager wakes your phone up for two minutes and AudioOut_1 wakes your phone up for 30 seconds during that same time, BBS will register 2m30s of PWLs even though the device was only held awake for 2m total. Now throw 30s of wlan_rx_wake (KWL) in there, and BBS is registering 3 minutes of wakelocks when there were only two. Throw in the notion that you had the screen on for 30 seconds during that time frame, and suddenly you're showing 3m of wakelocks when really there was only 90 seconds of true wakelock time to begin with. BBS has effectively doubled the reported wakelock time, and thrown off your stats. Now, throw in several dozen mini-wakelocks happening at once with the screen on, and you can easily see, say, 6h of PWLs on a 24h run, even if your true wakelock time is only 45m. It seems that Android's battery screen in settings reports this the same way, so my advice to you is to use the true wakelock time when cleaning up and attack KWLs and rogue apps. Some PWLs (AlarmManager) will always be high.
The second theory is that alarms are given a minimum reporting duration; i.e., five seconds per alarm for the sake of demonstration. Now, let's say you have Facebook, Twitter, Google+, LinkedIn, Gmail, Email, News & Weather and BBC News all set to sync every 30 minutes. They'll each set off an alarm at the same time, and suddenly your five seconds of alarm reporting time becomes 40 seconds every half hour. Now, let's say you have 35 alarms going off every half hour (not out of the realm of possibility with Google Services Framework). 35 x 5 = 175 seconds of time awake (in the five seconds per alarm scenario), which is now 350 seconds per hour of wakelocks reported, even if the true wakelock time was only ten seconds. Just something else to keep in mind when attacking PWLs.
One more note on BBS and how it handles KWLs: There is no such thing as a 0-KWL cycle, regardless of what the BBS reporting screen says. If BBS is showing 0 KWLs, tap the menu button, then "More", then "Raw Kernel Wakelocks" to see them. KWLs are required to boot the phone. In essence, the only phone that has 0 KWLs since it was last charged is a phone that hasn't been turned on since its last charge.
There are a couple of other features of BBS that we'll make extensive use of later, but there's one you need to know right now. Tap your phone's menu button to get the BBS menu up. Tap on "More". See the button that says "Set Custom Ref."? You'll need it--you'll need it a lot.
Also, anytime new information about a certain wakelock or wakelock family comes to light elsewhere in the thread, I'll be sharing that information here. If it helps you out, please visit the post that gave us that information and thank the poster. I'll link to each post twice, once in the wakelock description and once at the bottom of the OP, so no excuses about not being able to find it!
Last, but certainly not least: modifying your system in any way, including altering or deleting processes needed to resolve wakelocks, can have unpredictable results. Use caution and make backups of your apps and data, as well as nandroid backups, frequently while finding and eliminating wakelocks. Any modifications you make are done at your own risk, and I assume no responsibility for any damage you may do to your phone while cleaning out wakelocks.
With that said, we'll get started with the KWLs, as they're the trickiest to get rid of. Use the guide below to identify your wakelock, what is causing it, and how to get rid of it.
KWLs in post #2
PWLs in post #3
KERNEL WAKELOCKS
wlan_rx, wlan_rx_wake, wlan_wake: This is a wakelock caused by network traffic. The easy solution would be to just turn off Wifi, but be careful doing so! If an app goes to sync and it sees that Wifi is off, it will search for a mobile data connection (which causes the ConnectivityService wakelock). If it can't find a mobile data connection, it will wait and search again at its next sync interval and/or automatically sync when the phone wakes up. This wakelock can also, deceptively, be caused by the Wifi network itself as it refreshes connections or refreshes IPs.
To fix: This is a tricky little sucker to fix, as there are so many possible causes for it. Airplane mode is a safe bet--syncing apps seem to "respect" airplane mode, whereas if Wifi alone is turned off, they'll just try to find a way around. But then, of course, you lose your ability to talk on the phone. If you're particularly unlucky, your Wifi network itself will be the problem. Mine was--between my wife and I, we have four computers, an iPad, three Androids, a Wii, a PS3 and a Wifi-enabled TV hooked into our home network. The "background noise" caused by all of that would wake my phone up constantly. The solution? I happened to have a spare Wifi router laying around, so I hooked it up, set it on a different channel from my main router, and we now use that network for two of our three smartphones. Period. It's not the easiest fix ever, but wlan_rx_wake is almost completely eliminated (I'm looking now and have 4m45s of it 12h27m into a charge).
PowerManagerService: This is probably your #1 or #2 kernel wakelock, and you'd probably love to get rid of it at all costs, right? Hate to say it, but there's not much that can be done about this one. PowerManagerService is a KWL that serves as a "catch-all" for your PWLs. It's a placeholder, nothing more, nothing less. Don't spend much time worrying about it.
To fix: Reduce PWLs. See below.
deleted_wake_locks: Remember what I said above about force-stopping an app and deleting its cache and data before uninstalling it? This wakelock is why. It's the PowerManagerService for deleted apps. Once the app is gone, the wakelocks it caused suddenly become unknown to the system, so they get lumped in here. This number can also go up as the system "looks for" deleted apps and/or finds more wakelocks associated with them, but not dramatically.
To fix: Make sure to force close apps and wipe their cache and data before deleting. A reboot should eliminate the wakelock entirely. If it's still showing up, wipe phone cache and Dalvik.
sdio_al, sdio_dmux, etc.: This is an annoying wakelock, as there are two potential causes for it. One's easy, and one sucks. The easy one is that you've fallen victim to the charger wakelock. The easiest way to tell is to download Jrockttu's Skyrocket Charger Test App. If your charger shows up as AC Regular Charge, there's your problem. If it's AC Fast Charge or USB Normal Charge, your wakelock could be caused by your SD card. That can be an irritating fix, but the SD card version of this wakelock is typically small enough that it's not worth addressing. Also, a huge thanks to kishke for discovering a third cause for the sdio family of wakelocks: data. It seems that the sdio family is also the wlan wakelock family equivalent for cell data, and can be caused by apps searching for a data connection.
To fix: Check your charger and adjust if needed. To test the cell data possibility, make note of the time on the sdio wakelock, then turn cell data and Wifi off and walk away for an hour. Check it upon your return, and if you have minimal to no sdio wakelock, that was it. Try out some different radios for a better connection, or leave cell data off and stick with Wifi only. If it's the SD card, it's probably not a strong enough wakelock to be worth fixing, but if you want to fix it, you'll have to format your SD card. If formatting doesn't work, format it again, then wipe cache and Dalvik.
alarm_rtc: This is your phone's internal alarm scheduler, set to wake up your phone for sync, push, etc. Closely related to the AlarmManager PWL.
To fix: Check your apps and make sure they're only set to sync when you want them to, not for constant push or stupid-short intervals.
mmc0_detect, mmc1_detect, mmc2_detect: I'll be honest, I have no idea what causes these. Fortunately, they seem to be minimal, so I've never wasted much time worrying about them. polarbearno, however, has had a great deal of experience with this wakelock, and traced the cause of excessive activity here to a faulty SD card.
To fix: Unmount your SD card and pull it, then reboot. Might want to clear cache and Dalvik for good measure. If your problem was caused by a faulty external SD, this should solve it. If your problem was not caused by a faulty external SD, we're back to the original solution of "good question".
vbus_present: This wakelock exists as long as the phone is plugged into a wall charger. This wakelock can also persist if you use an Apple-compatible charger, which registers as "slow USB" charging and will cause the wakelock to hold after you'e unplugged.
To fix: Check your phone. Is there a cord plugged into it? If so, does that cord lead to a source of power? If so, unplug your phone (after it's fully charged, of course). Is the wakelock still there? Plug your phone into an OEM charger for a few seconds, then unplug it to kill the wakelock, then consider ditching that piece of fruit you're charging with. I try to use OEM Samsung chargers as much as possible, as they're designed for the phone (and to not cause persistent wakelocks). Jrockttu has an awesome charger test app, linked to in the OP of his outstanding "fix your battery life" thread.
suspend_backoff: This is a difficult one to nail down. Very difficult. To make a very long story short, this wakelock is caused when your phone wants to sleep, but a running process blocks it from doing so. Typically, this is going to be Wifi. Make sure your Wifi is set to stay awake when the phone sleeps. Otherwise, you risk the Wifi going out of its way to keep the phone from sleeping. This can also, unfortunately, be caused by apps, making it hard to pin down.
To fix: Do the Wifi thing, then reboot into recovery and wipe your caches. If it persists after that, you have no choice but to look at a dmesg output to pin it down. Go into a terminal emulator app and type the following commands, one per line:
su
dmesg >/mnt/sdcard/dmesg.txt
Next, transfer the .txt file onto your computer and open in WordPad or a similar program that automatically cuts line (i.e., no Notepad). Search the document looking for the word "event". You should find a lot of strings that look like this:
eventX-XXXX
Where the X's are all numbers. See those last four numbers after the dash? You should see them repeated again and again. Write them down, then go back into your terminal emulator. They are your process ID (PID). Once there, type:
ps
This will show you all processes that have run since your last boot. If you look at the second column from the left hand side of the page, and you should see a sequence of four numbers. These are listed sequentially, lowest to highest, as you come down the page. Scroll around until you find the sequence of four numbers that matches the one you wrote down. The line below those four numbers is the name of the process causing the wakelock. If it's instantly recognizable as an app, delete the app and see what happens. If it's a hardware thing that can easily be fixed, like Wifi, change your settings to accommodate it. If it's com.android.process.acore, I smell a wipe in your future. If you don't know what the process is, don't go screwing with things to find out. You can brick your phone in terminal emulators. Instead, write it down and Google it. Someone has already written about what this process is and what it does. If it's something you can easily fix, go for it. If it's a deeply-embedded system process, I'd just do a full wipe and clean reinstall.
Remember, terminal emulators can brick your phone if you're not careful. If you use them and something bad happens, or if you wreck your phone trying to fix this or any other wakelock, it is your problem, not mine.
There are a number of other, lesser KWLs that I'm not going to worry about here because you shouldn't worry about them either. You might occasionally see a battery cycle with very low (sub-1%) KWLs, but that's the exception and not at all the rule.
PWLs in post #3
The phone doesn't sleep when its charging, some android thing, that specific wakelock is called vbus_present.
kishke said:
The phone doesn't sleep when its charging, some android thing, that specific wakelock is called vbus_present.
Click to expand...
Click to collapse
That one's in there. It's the last wakelock under KWL.
I know it's there but you wrote: "This is a weird one. I never could quite figure out what causes it, but it seems like it's there as long as the phone's plugged it."
So I just want to clarify it so you could give it a straight explanation. Also you have a small typo there it=in.
It's a great guide!
T.J. Bender: Good topic… good write-up. I can’t agree with you more regarding the frustration level chasing down “greased-pig” wakelocks! The key is to have the right tool-set for analysis. At a minimum, make sure you have CPU Spy, BBS, and a utility which will show you what processes and services are active. Here’s my approach to identify wakelock problems. Again using CPU Spy to check time in Deep Sleep.. and using BBS to check Count of Alarms as well as time (minutes/seconds) of wakelocks:
1) open BBS and set a “Custom Reference” point (basically, this will reset the clock)
2) open CPU Spy and “Reset Timers”
3) turn screen off and let it sit for your predetermined time (i.e., 15min, 30min, 60min, etc)
4) when you reach the first predetermined time checkpoint, turn screen on and first check CPU Spy. How much time did the phone NOT sleep?
5) open BBS and check “Partial Wakelocks” against “Custom Ref Point”. Also check “Alarms” against “Custom Ref Point”.
6) do this every predetermined time (i.e., 15/30/60 min).. and write down results
What I found was very interesting. First I found "com.google.android.apps.maps" Partial Wakelocks were running about 80 times an hour (and preventing Deep Sleep): SOLUTION (thanks Bruno2123), un-check "Google Location Service” in "Location Services" in system setup.
Second culprit: AudioOut_1 : I also had unchecked all the keytone and touch sound options in setup, however, I was still getting a boat-load of PWL for AudioOut_1. I tracked it down (trial-and-error) to PowerAmp. Even though PowerAmp was not actively running, I had checkmarks (in PowerAmp Settings… Headset) in “Pause on Headset Disconnect” and “Resume on Headset Connect”.. which were preventing Deep Sleep. By un-checking these, it stopped the PowerAmp AudioOut_1 PWLs… and allowed Deep Sleep.
Third: this was a surprising find. Started to continue to see excessive AudioOut_1 PWL times; however, fewer counts (number of occurrences). Turns out, every time I open PlayStore, AudioOut_1 PWLs incremented… every time I played certain games (even with sound turned OFF in the game’s settings), AudioOut_1 PWLs incremented. However, these did not interfere with Deep Sleep.. these PWLs incremented when screen was on anyway!
Anyway, hope others find this approach useful and hopefully will help you identify PWL/ Alarm problems and find solutions.
kishke said:
I know it's there but you wrote: "This is a weird one. I never could quite figure out what causes it, but it seems like it's there as long as the phone's plugged it."
So I just want to clarify it so you could give it a straight explanation. Also you have a small typo there it=in.
It's a great guide!
Click to expand...
Click to collapse
Sarcasm is a fine art, mastered only by years of practice.
DoctorQMM said:
snip
Click to expand...
Click to collapse
I completely forgot to mention CPU Spy! Honestly, I did almost all of my hunting using the BBS "Other" timers, which show the percentage of time in deep sleep, awake, screen on, PWL and KWL. That's not to say CPU Spy isn't a valuable tool, because it is, but I had plenty of luck with BBS alone.
I kind of hinted at the benefits of leaving all Location Services off unless you need them. That said, I'm going to link this post from the OP, because you've kind of underscored the need to do so here.
And yeah, again, good catch on wakelock times. I was thrown for a loop the first time I had 94% deep sleep and 9.8% PWL until I realized that a lot of those PWLs were coming from apps that were running only when the screen was on.
This is an informative post. Thanks op
Sent from my SGH-I727 using xda premium
Good stuff...
Too bad your findings point to Google in a lot of ways as far as battery drain... maps, gmail, etc...
I don't mind Maps that much. It has been pretty accurate from me. When I ran BBS last time, it showed no problems on my phone as far as wakelocks, etc... I had more problems with BBS than anything.. WEIRD....
Every time I unplug my phone, it will ask for root permissions about 5-6 times before I get to my home screen even.... I just don't have time to be hitting allow that many times... (yes, remember is checked...)
Thanks for the posting! I subscribed and will check back here often!
onealvideo said:
Too bad your findings point to Google in a lot of ways as far as battery drain... maps, gmail, etc...
I don't mind Maps that much. It has been pretty accurate from me. When I ran BBS last time, it showed no problems on my phone as far as wakelocks, etc... I had more problems with BBS than anything.. WEIRD....
Every time I unplug my phone, it will ask for root permissions about 5-6 times before I get to my home screen even.... I just don't have time to be hitting allow that many times... (yes, remember is checked...)
Click to expand...
Click to collapse
Almost sounds like you've got a ROM issue. I've also read that switching from Superuser to SuperSU can solve a root permissions "loop" like that.
Unfortunately, yeah, a lot of the PWL headaches I've come across can ultimately be traced back to a Google app. That said, I set out looking to make a battery last as long as possible. If you get to a point where you're happy with your battery life, I'd stop there regardless of what apps are still on the phone. The more you change, the more you can potentially screw up.
Can someone post the link to xda bettery stats, I search for it and find nothing.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
specter07 said:
Can someone post the link to xda bettery stats, I search for it and find nothing.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately you don't know how to search my friend.
http://bit.ly/NuHF7q
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jyazzie110 said:
Unfortunately you don't know how to search my friend.
http://bit.ly/NuHF7q
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Seems you don't know how to google either. Where's the free better bettery stats for xda members? That just shows the link to the store for the paid one.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
No at the bottom of the second post is dl link I just grabbed it
Sent from my SGH-I727 using Tapatalk 2
specter07 said:
Seems you don't know how to google either. Where's the free better bettery stats for xda members? That just shows the link to the store for the paid one.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I know how to google....your the one who cant search or read! Haha
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jyazzie110 said:
I know how to google....your the one who cant search or read! Haha
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Be nice
Sent from my SGH-I727 using Tapatalk 2
Illnevertell said:
Be nice
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Wow, when he says it... u have issues lmao
Illnevertell said:
No at the bottom of the second post is dl link I just grabbed it
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I kept scrolling pass it since on my phone you can hardly even see the attachment on the broswer.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Come on, guys, please keep this thread on topic.
Wanted to share some results with you. Screenshots below. No KWLs in 24 hours since being unplugged...not half bad. PWLs are within reason, especially considering that Alarm Manager is one of those PWLs that will hold even if your screen is on. The only thing that strikes me is Twitter alarming my phone 6 times, when it's set to never auto-refresh. Not a huge deal, but worth investigating.
70% battery 24 hours into a charge, screen-on time of 31m. Granted, I have barely used my phone today outside of sending a few texts, checking into XDA once and playing a few quick hands of Blackjack, but I'm still pretty stoked with this run.
**EDIT: Good thing I checked! Twitter had automatically updated earlier in the day, and when it did, it reset itself to sync every hour. Switched it back to never sync, and that should solve it.
Hi, I really did some research but I find alot of ROMs and Kernels and I always get lost. I just need a good safe way to better the battery life of my Nexus 5 and keep it's stability and all the functions it has. So I wanted to ask what you guys recommend as Kernels, apps and lastly (I dont want to change unless its worth it) ROMs.
Sorry, its been hard without a PC to do decent research.
Enviado do meu Nexus 5 através de Tapatalk
The ROM has very little to do with battery life. It's all about the kernel or the apps.
We can't recommend kernels (or roms) as this is against the rules. They will all pretty much help with battery life. Just try them all- yourself.
Apps:
Greenify
Better battery Stats
That's it. Anything else I would recommend is going through all your settings and turning off things you dont need like location reporting etc
if battery life is all you are looking for... the difference are ... not much
Just disable google apps that you do not use, then you are good to go.
Locations settings, always off, activate only when needed. uncheck all under Google Location Reporting.
Disable NFC if not needed.
If you don't have good LTE coverage, change it to 3G under mobile networks.
For maximum battery life, do NOT activate Google Now.
eg. (These are apps I've disabled)
Drive
Earth
Email
Exchange Services
Face Unlock
Gallery (I use QuickPic as alternative)
Gmail
Google Hindi input (These ones gets disabled once you uncheck them from input settings)
Google Play books
Google Play Games
Google Play Magazines
Google Play Movies & TV
Google Play Music (I use Poweramp *Paid)
Google+
Keep
Maps
News & weather
Quickoffice
Street View
Tags
TalkBack
Hangouts (I use HoverChat *Paid)
Check this thread mate...
http://forum.xda-developers.com/google-nexus-5/general/nexus-5-battery-results-t2509132/
CitizenLee said:
Check this thread mate...
http://forum.xda-developers.com/google-nexus-5/general/nexus-5-battery-results-t2509132/
Click to expand...
Click to collapse
What he said ^^^^
It doesn't matter what's on your phone....you should be able to get good battery life. Its all about setup and usage.
Just gotta troubleshoot issues occasionally.
Please check the thread linked above, and read read read. . (Start on last page and read back for a bit....a lot of good info)
On my phone it certainly seems to have something to do with signal quality. At home, I can put the phone next to the bed at night with it fully charged and wake up with it at about 95 or 96%.
At work a fully charged phone just sitting on my desk drops to about 90% in only a couple of hours.
The signal quality in my building at work is pretty poor, so I'm guessing the phone is using a lot of extra energy desperately searching for a better signal .
Claghorn said:
On my phone it certainly seems to have something to do with signal quality. At home, I can put the phone next to the bed at night with it fully charged and wake up with it at about 95 or 96%.
At work a fully charged phone just sitting on my desk drops to about 90% in only a couple of hours.
The signal quality in my building at work is pretty poor, so I'm guessing the phone is using a lot of extra energy desperately searching for a better signal .
Click to expand...
Click to collapse
Poor and searching for signal is probably the biggest battery drain there can be.
Get gsam. And after your at work a few hours, open and click on "phone radio". It will say how long your phone was actually searching for a signal. That's a huge battery killer.
The only cures, get on WiFi. Or go into airplane mode. Toggle off data might help, then you'd still get texts and phone calls.
kj2112 said:
The only cures, get on WiFi.
Click to expand...
Click to collapse
I do have wifi on in both locations, so the wifi part of this doesn't help. I suspect data isn't the issue, just the cell connection. My old phone used to randomly reboot inside this building when trying to get a signal . I guess I should install gsam just to verify, but the signal is really the only difference between work and home, so I'm pretty sure that is the issue.
Claghorn said:
I do have wifi on in both locations, so the wifi part of this doesn't help. I suspect data isn't the issue, just the cell connection. My old phone used to randomly reboot inside this building when trying to get a signal . I guess I should install gsam just to verify, but the signal is really the only difference between work and home, so I'm pretty sure that is the issue.
Click to expand...
Click to collapse
Usually battery drain from a low or bad signal is only a big issue while on data. On WiFi it doesn't affect the battery much , if any. Its from apps trying to sync through data on a bad or no signal. So on WiFi, that's not an issue.
At home I get fairly poor reception...sometimes only a bar...with some time spent searching for signal, but my battery times are at their best at home. On WiFi.
It could be a network issue. Some devices on networks can affect your device by spam polling your phone....might want to also get wakelock detector to see that. If the LAN is draining your battery, there will be wakelocks from it.
Try gsam and compare work results to home results. Especially good would be trying at least a few hours of total standby to see the difference at both locations. You'd have to reset gsam stats to start your standby test at all zeros though. A reboot will reset gsam.
Good luck!
Remove all google [email protected]%# ...
And disable autostart from programs like poweramp which start on boot...use romtoolbox and autostart manager
Of course, pay attention to what you're going to disable
If You will try and You have some doubt ask here
I use a lightweight aosp ROM, a minimal gapps package, stock kernel, disabled some programs from boot and run in background...and battery duration is good
Don't ask to us roms/kernel combo, please Questions like your are not allowed on xda
Always read the users feedback and make Your choice
And... My doubt..is it really needed to change the kernel ??
Give stock kernel a chance... That's all I can say...
And make sure to charge your phone the right way
Hi! Anyone knows if I can disable the processes that Viber starts every so often? Like the in-app processes, it keeps on running in the background consuming a huge chunk of my battery. I already emailed Viber about it but unfortunately they don't have a fix for it.
Sent from my Nexus 5 using Tapatalk
natadecocolococo said:
Hi! Anyone knows if I can disable the processes that Viber starts every so often? Like the in-app processes, it keeps on running in the background consuming a huge chunk of my battery. I already emailed Viber about it but unfortunately they don't have a fix for it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Greenify?
rootSU said:
Greenify?
Click to expand...
Click to collapse
I'll try that. Thanks.
kj2112 said:
Try gsam and compare work results to home results. Especially good would be trying at least a few hours of total standby to see the difference at both locations. You'd have to reset gsam stats to start your standby test at all zeros though. A reboot will reset gsam.
Click to expand...
Click to collapse
OK, I turned the phone off, charged it to 100%, then pretty much let it sit doing nothing after rebooting. After sitting overnight at home (where the battery doesn't drain much) the "Phone" app was way down in the list:
GSam Labs - Battery Monitor - Export Data
Phone
Apr 30, 2014 9:55:45 AM
Usage Details
CPU Usage:2s
CPU Usage (Background Only):2s
Keep Awake:19s
Number of Wake Locks:177
Number of times waking device:2
App UID:1001
Wakelock Detail
RILJ8.8s(136)...
Did the same recharge with phone off at work, rebooted, then let it sit on my desk for just a couple of hours, and "Phone" is now the 2nd biggest culprit in the apps list:
GSam Labs - Battery Monitor - Export Data
Phone
May 1, 2014 10:35:57 AM
Usage Details
CPU Usage:3m 24s
CPU Usage (Background Only):3m 24s
Keep Awake:12m 1s
Number of Wake Locks:1167
Number of times waking device:141
App UID:1001
Wakelock Detail
RILJ11.9m(1031)...
Wifi was on in both locations (with a good signal), I even turned off location to prevent that overhead. It just hates the environment at work .
Claghorn said:
OK, I turned the phone off, charged it to 100%, then pretty much let it sit doing nothing after rebooting. After sitting overnight at home (where the battery doesn't drain much) the "Phone" app was way down in the list:
GSam Labs - Battery Monitor - Export Data
Phone
Apr 30, 2014 9:55:45 AM
Usage Details
CPU Usage:2s
CPU Usage (Background Only):2s
Keep Awake:19s
Number of Wake Locks:177
Number of times waking device:2
App UID:1001
Wakelock Detail
RILJ8.8s(136)...
Did the same recharge with phone off at work, rebooted, then let it sit on my desk for just a couple of hours, and "Phone" is now the 2nd biggest culprit in the apps list:
GSam Labs - Battery Monitor - Export Data
Phone
May 1, 2014 10:35:57 AM
Usage Details
CPU Usage:3m 24s
CPU Usage (Background Only):3m 24s
Keep Awake:12m 1s
Number of Wake Locks:1167
Number of times waking device:141
App UID:1001
Wakelock Detail
RILJ11.9m(1031)...
Wifi was on in both locations (with a good signal), I even turned off location to prevent that overhead. It just hates the environment at work .
Click to expand...
Click to collapse
I think that is just the difference in signal quality. It seems to be pretty common to get degraded signal at work places due to larger structure sizes as well as more users per cell tower.
Phone Idle is from the voice network, Cell Standby is from the data connection.
Is it normal for Google Play Services to be running in the background always? The gcm and the location service is always on.
Sent from my Nexus 5 using Tapatalk
natadecocolococo said:
Is it normal for Google Play Services to be running in the background always? The gcm and the location service is always on.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup
And its worse with location on for sure....battery wise anyway.
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.
MFirst of all i want to apologyze for my bad English.
After the nougat update i start getting a really bad battery life and have to charge the phone 3 times a day. I start digging in the problem and do test in search for a better battery. I managed to improve my 3hous SoT to get between 4.30 to 6 hours SoT.
The tweaks in this guide are not magical, there are just tips that help me improve a lot my battery life. There is no need to unlock bootloader or to root the phone. The idea is to make a good balance between functionality and battery life. Everyone can choose what thinks they want to sacrifice for battery life and what they want to keep. All the steps that are listed here are reversible and can't harm your device in any way. It is pointed to people that do not know a lot of this subject.
My advice is to full apply all the steps and after getting a good battery life start to enabling the features that you want to have on the phone one by one and test battery.
At the end of this guide there is a section with improvements wich aim is to make the moto x style look like more like the news motorola Phones.
Simple Tips for Battery life:
-After a major OS upgrade it is important to do a full factory reset, full wipe. When logging with your google acount start the device as a new device. Do not restore apps!
-Try to not use the Turbocharger. Based on my own experience, a good 1-2 Amp charger get a lot more juyce that the turbo charger. It may sound weird to you but i tested this a lot of times and really see and important difference. I only use the turbocharge when i am in a hurry.
-Do a full calibration of your battery. Let the battery get to 0%. Turn the phone off and let it charge to 100% and left it plugged a little bit more. After that unplugg the phone, restart it and see if the % is still 100%. If not plugg the phone again after a 100% charge and repeat the process until you get a full 100% charge or near that number.
-A good advice if to left the phone charging in the nigth, or when you think it is a good moment. After get to 100% of the charge, unplugg the phone, restart it and plug it again. For my the battery is not getting a good reading after Nougat update. After a restart i always "lost" like 8% of charge. I do this every time i charge the phone.
-The NOUGAT room is draining battery very very fast when there is bad celular signal. So if you are not having a good celular signal it is a good advice to put the phone in airplane mode until you change your location. Also, there is drain with bad wi-fi signal so try to avoid that too. It is not strong like the celular drain but can influence in your final results.
-Turn off location when you are not using it. If you have to use it try to use the "battery saver mode" and put high accuaricy when you are going to use the GPS for a precise fix or navigation. Google Play Services have and excess use of wackelocks due to location, they are listed ass NLPcollectorwackelock and NLPwackelock.
-If you are on Wifi turn off data and if you are in data turn off Wifi. If you can use both try to use Wifi with a good wifi signal. It uses a little bit less battery that 4G for me.
-Unninstall apps that you are not using or going to use in a short-mid time. They may be running in the background and eating
juice.
-Turn off automatic brigthness. Put your brigth to the minimun you are happy with. I used mine almost in the minimun and i see the screen perfect. Also remember that the power scale is non linear. Putting the wheel in the half of the brigthness bar is not getting you "half the brigthness of the screen".
Download autobrigth switch https://play.google.com/store/apps/details?id=com.abrody.brightness&hl=es_419 .This make you turn autobrigthness on with a click. This is very usefull if you are outside, let you see the screen with 100% and then let turn it off when you are inside. It is a easy way to manage brigthness.
IMPORTANT:When you are not using your device it must go to sleep mode. It is a mode where the CPU is almost turned off and it doens't drain much battery. Later in this guide i will explain how to properly install a Battery monitor program. It is very important to watch if the device is sleeping ok and there aren't apps with bad behaviours keeping the device awake and draining your battery. This can be seem in GSAM Battery monitor watching the held awake tab. If an app is keeping your device awake you have to uninstall or contact the developer and tell him about your problem with his app.
Tunning the system to Optimize the Battery and Performance:
For this part you will need to have installed ADB drivers, you can download and install from here:
https://forum.xda-developers.com/showthread.php?t=2588979
You have to activated debug mode on the phone:
Go to settings, about phone, tap 7 times the Compilation Number until you see a message saying that you are a developper. Now go to settingss, developer and activated USB DEBUG mode. To see what apps are running in the background on your phone go to settings, developer, in execution.
Also you will need to install 4 more free apps, later they can be uninstalled if you want:
App inspector to know the name of certain package:
https://play.google.com/store/apps/details?id=bg.projectoria.appinspector
App Ops to manage special permissions of apps:
https://play.google.com/store/apps/details?id=com.findsdk.apppermission&hl=es
Shizuku Manager is needed to give the permissions necesary to App Ops:
https://play.google.com/store/apps/details?id=moe.shizuku.privileged.api
Gsam battery Monitor for monitoring apps usage:
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm&hl=es
The aim of this part of the guide is to disable all the features and apps that may be drainning your battery.
All of this can be reverted one by one after getting a good battery and testing the results and the impact on battery life:
-Turn off location, bluetooth, NFC.
-Go to moto app and turn off Moto Voice, Moto screen, Wave to wake. I keep the flaslight and the cam gesture on but you can dissable them if you want.
-Go to settingss, Motorola privacy and turn off enhancet device support and help us with bla bla.
-Go to settings, security, back up and turn off data back up.
-Go to settings, location, turn of Google location History and share location of google. In the Rigth upper corner tap on the 3 dots and turn of bluetooth scanning and wifi scanning.
-Go to settings, google, search, and turn off all the features like feed, nearby, voice detection, notifications, doodles, google fit, firebase App Indexing.
-Go to settings, google, security, dissable google play protect,etc. (If you consider this ass important do not disable it)
-Go to settings, apps, tap the 3 dots in the upper rigth corner and tap on show system apps. Disable Motorola device manager and Motorola notifications. Also delete the apps data.
-Go to accounts and turn off syncronizations of all the things you really don't need. For instance in google account i left on contacts, Chrome and Contacts info only.
-If you are using chrome go to settingss, site configuration. Turn off location, notifications, sync in the background. In the sync settings just let the chrome sync only what you need.
-Disable all google and motorola apps that you are not using. For instance Google Duo, hangouts, play music, play books, play games, carrier services, Motorola connect, talkback, devices help, etc.
-Search for apps that ask for permission you think they don't need it. Speacially location.
-Turn off special permission that you think apps don't need. The special permission can be managed going to settings, apps, tap the wheel, advance-special acces:Look to "change system settings" and "get over other aplications". Also turn off acces to data usage for Google Play and Google Play services.
-Go to settingss, security, trusted agents, disable smartlock.
-If you have apps like greenify installed, uninstall them.
-If you have home widgets be sure that they are not using your location and also if it posible put the refresh time to the minimum.
-I don't use GBOARD, it was not working ok for me and also draining battery. So i search in the internet and donwload the latest google keyboard version before GBOARD, it works perfect. I do not recommend GBOARD as it is not working ok and it is not propperly optimized.
Using ADB for Background process:
The next step consist of disabling System process and apps that you no not need to run in the background, for example MotoCare:
Motocare is a system process that runs in the background and collects info of your device use even if you turn off motorola privacy features. That not makes much sense but it is there and can't be disable in a easy way.
After installing ADB, drivers and turning on USB DEBUG MODE, plug the phone, go to the search bar in windows and search for CMD. Open it.
Write:
abd devices
Is everything is ok you will see a device in the list that is your Moto x Style. If not figure out what is the problem, make sure DEBUG MODE is on and that you give the propper permission in the phone.
Then write:
adb -d shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
This will let you see full wakelock list in GSAM Battery Monitor app. This is very important to know if there is an app keeping your device awake.
next:
abd shell
cmd appops set "com.motorola.motocare" RUN_IN_BACKGROUND ignore
cmd appops set "com.motorola.motocare.internal" RUN_IN_BACKGROUND ignore
This last two lines will stop motocare. After this go to apps, with "show system apps" on search motocare and motocareint and delete all the data. After that check that motocare is not running in the background.
cmd appops set "com.motorola.ccc.ota" RUN_IN_BACKGROUND ignore
cmd appops set "com.motorola.ccc.checkin" RUN_IN_BACKGROUND ignore
This will turn off OTA services. If you want to take an OTA after this, (if motorola ever send another OTA for our device) you can just go to settingss, about phone and check for update manually. (After enabling Motorola device Manager and Motorola Notification). Anyway is there is a new OTA you probably are going to know it from XDA forums.
You can use the same command to disable apps that you don't need to run in the background but you want to use.
To use this commands just open app inspector, search the app you want. Copy the package name and use the command with that package. Anyway in the next step i will show you a easy way to do the same with other apps that are not from the system.
If you want to re enable and app to run in the background just reinstall it or write the same sentence changing "ignore" for "allow":
For example with Facebook. If you search it in app ops the package name is com.facebook.katana . The name of the package is "katana" because it is like smashing your battery with a Katana lol.
adb shell
cmd appops set "com.facebook.katana" RUN_IN_BACKGROUND ignore
to enable it:
cmd appops set "com.facebook.katana" RUN_IN_BACKGROUND allow
My advice is to not use this command with google services or with system apps you don't know what they do in your phone. It may get you in a problem.
Now we are going to see another way to stop apps for running in the background. This is usefull with apps that you want to keep and don't want to run in the background.
For example in my case, i use facebook app but don't want it to run in the background. Also i disable all navitagion apps to run in the background, Here we go and google maps in my case. They both work perfect when I open they, don't need them running in the background. I let apps like WhatsApp, Instagram, Tinder, Facebook Messenger to run in the background because i want to know when someone send a message and don't want to wait until i open the app. If you don't need the notifications my advice is to don't let run in the background. That will get you a considerable amount of battery. Whatsapp have a lot of battery drain. For some reasons it has the acelerometer turn on a ridiculous amount of time and it triggers google play services wackelock PackageMeasuremntservice.
Connect the phone via usb and launch terminal as we did before, search bar and search button, type CMD and open it. Open Shizuku Manager
Wrote in the terminal:
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh
if you do it rigth you will see that the server starts running. Now unplugg your phone, close shizuku manager and open App Ops. If you turn off your phone you will have to repeat the process in order to get app ops running again.
Search for apps that you don't want to run in the background. In the permission settings there is "run in the background", you can turn it off or on from there. It has exact the same effect that doing it in the ADB terminal ass we did it in the previous step. But motocare can't be disabled from the app.
Also you can manage all the permission from the apps one by one in a lot better detailed way than from the stock app settings..
There is also a trick with google play services and location. I am getting a big wake up with NLPcollector and variants. If you turn off the network location permission in google play services it will stop the wakelock even if you have your location ON. That make google play services almost drainless. The problem is that some apps may not get a correct location in "battery saving mode" because they use google play services. This is fixed turning on high presition mode or device only mode and letting the GPS do the location work only when you need it.
Finally you can tweak all your apps permissions and see the battery results. The two most important permission related to battery life are the location and the background one. Try to disable location for everything you don't need to be tracking you.
Tunning your Moto X Style:
To get the new Camera app from motorola:
Go to apps, search for stock camera app and disable it. Delete all the app data. Go to settings, security and turn on "Unkown Sources".After that donwload the moded camera app from this tread:
https://forum.xda-developers.com/moto-x-style/themes-apps/moto-camera-6-0-43-10-modded-apk-t3459690
Restart your phonr and Install it! Now you have the new camera app . It work almost perfect, the only things that are not working for me are: Twist to change to selfie mode, shutter time in pro mode and white balance in pro mode. Don't forget to thanks the developer for this great app. Also turn off Unkonw Sources after the installation.
To get the Moto Z command Widget:
Donwload and install this app:
https://forum.xda-developers.com/moto-maxx/themes-apps/moto-z-command-center-widget-t3417171
Don't forget to turn location of the widget off, you can put your location manually and save battery.
Launcher 3:
https://forum.xda-developers.com/moto-z-play/themes/moto-z2-play-launcher-google-root-t3623608
It is the new Motorola Stock Launcher. You can try the Moto G5 Launcher too, it is in XDA.
Unlock Method:
The phone doesn't have fingerprint scanner but a good alternative is to use face unlock. LG and Samsung do a lot of marketing of something that is build in on android stock and work almost perfect. Go to security, turn smartlock on.Then go to smartlock and turn on face detection. It works like a charm, is almost instantaneous. My advice is to do this after getting a good battery life as smartlock features can affect battery. Make sure you don't have on trusted places on Smartlock as it drains your battery. Also if you have location ON it may drain your battery even if you don't have trusted place on, so take care. The trusted face feature on its own drains a negligible % of battery.
As i stated in the beggining:
If you want the best battery life you always have to do a compromise between it and features of the phone. For example i love moto display and the wave to wake feature but it takes so much juice of my phone.
My advice is to do all the steps, make sure you are getting a good battery life and after that start reenabling one by one the features you need and watching the impact of them in your battery life. Also i know that some of the stuff i mention may have a negligible impact in battery for themselves but when you put all together they do make a difference. My phone is draining almost 0% on stand by mode with doze. I let it with a %, go to sleep and when i wake up i have the same %.
At this moment i am testing battery on my phone and seeying wich features do make a big diference in battery life.
For instance i am using smartlock, face unlock with location off and in security settings i have android device manager enabled. They seems to not affect the battery performance so much. I will continue testing features to see wich ones are the main offenders.
Any suggestion or any question is welcome! Also if this helps you please let me know and post your battery life before and after.
Great guide, although might a bit extreme for some people to do all of these things.
I can tell you the biggest increase in battery life i have seen is to disable the Moto Display and Moto Gesture to wave over the display... My idle usage has stopped in half and maintains around 2% with it all off.
acejavelin said:
Great guide, although might a bit extreme for some people to do all of these things.
I can tell you the biggest increase in battery life i have seen is to disable the Moto Display and Moto Gesture to wave over the display... My idle usage has stopped in half and maintains around 2% with it all off.
Click to expand...
Click to collapse
Yes, i know that for some people it may be too much, but the guide is divided in parts so anyone can take what they seem comfortable with.
I agree with you, wave to wake and moto display are the main offenders and i feel that with nougat the battery drain of this features get agravated a lot more. It is a shame because i really like that features but they drain your battery even with the screen on..
Great guide, thanks
With the Nougat update my sot is way better up to 4 h, while on mm it was around 3.5h.
I just wonder why buy a phone with features like wave hand, etc. and not using them?
That's a pity that Moto doesn't have d2w like lg phones, it's very handy.
I don't like to look for button to press it every time.
I know that's everybody's choice. Just my 2 cents.
Does turning off all location stuff that you mentioned affects any usability, notifications, etc?
Sent from my XT1572 using XDA-Developers Legacy app
2be3_80 said:
Great guide, thanks
With the Nougat update my sot is way better up to 4 h, while on mm it was around 3.5h.
I just wonder why buy a phone with features like wave hand, etc. and not using them?
That's a pity that Moto doesn't have d2w like lg phones, it's very handy.
I don't like to look for button to press it every time.
I know that's everybody's choice. Just my 2 cents.
Does turning off all location stuff that you mentioned affects any usability, notifications, etc?
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
If your SOT increased on Nougat, it is because the OS is more efficient elsewhere... hardware power draw cannot be changed with software.
Why not use the gestures? Like anything else, they are unnecessary for normal operation and consume extra battery, waiting for detect you waving your hand over the display takes some power, not a lot, but over 10-12 hours it is noticeable... Why buy a phone with gestures if your just going to turn them off? Because the pluses outweigh the negative and there is no perfect device.
Moto probably doesn't implement DT2W because the screen technology they use would require the screen (digitizer actually) to be powered all the time, increasing idle battery draw from 2-5% per hour. It is implemented in some 3rd party kernels and ROMs, but few people use it because over 12 hours of sleeping time, it consumes 25%-50% of your battery capacity. :/
I'm not going to get into the other stuff, things like disabling Google Play services and location services and stuff like that, just take away too much functionality for my taste for what you gain. In general when not traveling, I need 3 hours of SOT in a day and this device generally makes that. When traveling (which I did on very regular basis for years until this week) I was under 50% before 9am and near dead by noon if I didn't charge or connect to battery pack. So in general these optimization are not enough to do what I need, so I just skip them.
2be3_80 said:
Great guide, thanks
With the Nougat update my sot is way better up to 4 h, while on mm it was around 3.5h.
I just wonder why buy a phone with features like wave hand, etc. and not using them?
That's a pity that Moto doesn't have d2w like lg phones, it's very handy.
I don't like to look for button to press it every time.
I know that's everybody's choice. Just my 2 cents.
Does turning off all location stuff that you mentioned affects any usability, notifications, etc?
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
For my after nougat update the battery life go to Hell. I was getting 3hs lf SoT wich is unaceptable for me.
I understand your point and i really like wave to wake. It is nice. For my is nicer to have 5hs or more of SoT. In nougat my wave to wake eats battery like crazy and i really don't need it much. Answering your question, disabling motocare only disable motorola remote support. All the other moto stuff doesn't affect the phone, only disable the OTAs. There is nothing in the guide that compromise basic functionality of the phone, maybe only disabling location permission on google play services with app ops can affect location on some apps. As i stated in the end, everyone have to chose between functionalitis and battery life.
After i managed to get 6hs SoT i start to enabling things and test how was my battery life. I will stop in the 5 hours SoT limit.
At this moment i reenable: moto voice, location in saving mode, smart lock with face unlock, android administrator to lock the device remotely and i am getting between 5hs to 5:20hs SoT. Next step is to try with moto display.
NahuelMS said:
For my after nougat update the battery life go to Hell. I was getting 3hs lf SoT wich is unaceptable for me.
I understand your point and i really like wave to wake. It is nice. For my is nicer to have 5hs or more of SoT. In nougat my wave to wake eats battery like crazy and i really don't need it much. Answering your question, disabling motocare only disable motorola remote support. All the other moto stuff doesn't affect the phone, only disable the OTAs. There is nothing in the guide that compromise basic functionality of the phone, maybe only disabling location permission on google play services with app ops can affect location on some apps. As i stated in the end, everyone have to chose between functionalitis and battery life.
After i managed to get 6hs SoT i start to enabling things and test how was my battery life. I will stop in the 5 hours SoT limit.
At this moment i reenable: moto voice, location in saving mode, smart lock with face unlock, android administrator to lock the device remotely and i am getting between 5hs to 5:20hs SoT. Next step is to try with moto display.
Click to expand...
Click to collapse
I have run ADB commands and after each and everyone I had no confirmation dialogue nor anything.
I have rebooted device and how can I check if I had done everything right?
Sent from my XT1572 using XDA-Developers Legacy app
2be3_80 said:
I have run ADB commands and after each and everyone I had no confirmation dialogue nor anything.
I have rebooted device and how can I check if I had done everything right?
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you have done everything rigth you wont see the apps running unless you open they. To see process in execution you have to go to seetings, about device, tap 7 times build number until you get the message that you are a developer.
Go to seeting again, you will see developer option. In there you search for in execution. If you do everything rigth you wont see motocare or moto things runnings. Same with the apps like facebook, etc. They only appear in execution when you open they or have they in recent apps.
Let me know if your battery get improved.
This if from last test:
Enabled moto display, moto voice, face unlock, location in battery saving mode. Disabling background things really help with battety life.
NahuelMS said:
This if from last test:
Enabled moto display, moto voice, face unlock, location in battery saving mode. Disabling background things really help with battety life.
Click to expand...
Click to collapse
That's really good achievement.
I can't get close to your results.
I have disabled moto apps running in background, location off, Moto display on, wave hand on.
I only use WiFi/network when needed.
Hmm what could be the culprit?
On this charge I think I will get about 4h sot.
Sent from my XT1572 using XDA-Developers Legacy app
2be3_80 said:
That's really good achievement.
I can't get close to your results.
I have disabled moto apps running in background, location off, Moto display on, wave hand on.
I only use WiFi/network when needed.
Hmm what could be the culprit?
On this charge I think I will get about 4h sot.
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, i think the average for those conditions is 5 hs (mine conditions)
Are you using turbocharger? How old is your phone? Maybe the battery is getting bad? Did you disable apps like facebook running in the background? Installed Gsam Battery monitor amd check there isn't an app eating your juice or keeping your device awake? Do you have good signal? My best advice is to do all the steps of the guide and see how much of battery life are you getting in that condition. Them start reenabling things like moto voice, moto display and finaly wave to wake. Did your battery got improved dissabling moto stuff?
Wave to wake for my on Nougat was a battery hog. Maybe try to disable it and see how much your battery improves!
My phone is from February 2017, never used turbocharger (I believe it's killing battery over time). Not using Facebook.
When updated to Nougat I did factory reset and disabled various Google apps that I don't use, like Duo, Google+, etc.
My sot was around 4 h with Moto display and wave hand gesture. After disabling Moto stuff from your guide though ADB I haven't noticed any improvements. I will observe few more days. I don't have any Moto update processes running in background.
I use Gboard and like it very much, so it's a keeper for me.
Thanks
Sent from my XT1572 using XDA-Developers Legacy app
2be3_80 said:
My phone is from February 2017, never used turbocharger (I believe it's killing battery over time). Not using Facebook.
When updated to Nougat I did factory reset and disabled various Google apps that I don't use, like Duo, Google+, etc.
My sot was around 4 h with Moto display and wave hand gesture. After disabling Moto stuff from your guide though ADB I haven't noticed any improvements. I will observe few more days. I don't have any Moto update processes running in background.
I use Gboard and like it very much, so it's a keeper for me.
Thanks
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Try one or two days without wave to wake and see how much battery you can get. I don't think Gboard should be a deal breaker in battery life in comparison with google keyboard, i don't think it is the problem. Maybe there is an app keepping your device awake? Your phone is almost new so i doubt from battery problems. Can you post a screenshot of battery usage and signal, awake time, etc, from your android battery usage?
This is from today with mid usage and time with low signal:
Today I did factory reset and will observe how it goes without tweaks but with most apps shipped with phone disabled that I don't use
2be3_80 said:
Today I did factory reset and will observe how it goes without tweaks but with most apps shipped with phone disabled that I don't use
Click to expand...
Click to collapse
If you allready did a factory reset i don't think it will give much battery in same conditions and take into account that android take some cycles to calibrate the system and the apps, so battery duration should getting extended during the first week until it reach a plateau.
Just an FYI... Up until a week or so ago, I was averaging 2h 45m to 3h screen on time in an average day and since I started using my phone for work (BYOD program, always had a separate work device before) the battery life started really mattering so I made the following changes...
- Dropped Facebook and Messenger (MASSIVE battery hog apps, always at the top of the list) and moved to Facebook Lite (yes, you can get it in the US, just have to use APKMirror, and it includes Messenger services in the same app)
- Dropped Accuweather (was keeping device awake and accessing location dozens to hundreds of times per hour) and switched to 1Weather
- Dropped Microsoft Outlook (keeping device awake and using background data, and a Device Administrator I didn't want) and switched to Nine
- Dropped OpenSignal (was using background data and waking device very frequently)
- Disabled Moto Display entirely
- Disabled Moto Action Wave to Wake
These 6 things are all I have done... I keep all services active, high accuracy location, all accounts and services syncing, no background data restrictions, no disabled apps, backup and other services like Motorola services all running, no adjustments in permissions, using Gboard as my default keyboard, and I have ~120 apps installed, 80% of which are occasional use only. I use a Quick Charger about 50% of the time for boost charging at work or when traveling, but overnights it is on a standard (5v/1.8A) charger and not QC. I have seen my Doze and Deep Sleep times increase significantly, with Deep Sleep time approaching to 75%... And Screen On Time over a normal day increasing by nearly an hour on average... In fact, yesterday I had my best SoT in over a year with 4h 28m over a 16 hour day in mixed use, including a 6 hour YuGiOh tournament where I used the phone to keep score of my matches (with marginal LTE service and no WiFi), going out to eat 20 minutes away, and then back home for some video game time with friends and still have 20% battery remaining when it went back on the charger, probably could have gotten 5.5 hours if I pushed it near zero. Making it sufficient for daily use for me again.
Am I saying this is the answer for everyone? No, but install a good battery monitoring tool like GSAM Battery Monitor and see what is using your battery (make sure to enable advanced reporting, requires ADB connection)... and don't just look at the default screens, dig into the app after some use. The "View % Power Used" screen only tells part of the story... Make sure to look at View Number Times Waking Device, View GPS Time Used, and View Time Held Awake because some things are not always so obvious. Accuweather for one was "hiding" some of it's usage in Android System and Google services in the View % Power Screen, but when you looked in View Time Held Awake and View GPS Time Used, it became evident it was doing something.
Some other apps which can be culprits are shopping apps, they often track where you are frequently... such as Walmart, Sam's Club, Best Buy, CVS, and most other dedicated apps for shopping. Alternative messaging apps like Messenger, Whatsapp, Kik, Skype, Viber, SnapChat (currently the #1 battery killer out there according to several sources), etc. often keep the device awake and use background data. Airline and other travel apps often check your location every minute or even more frequently even when not open. "Optimizer" apps like LionMobi Power Battery, CleanMaster, and similar tools are worthless and usually consume more resources than they help with. News apps like BBC News often use background data and keep the device awake... Some of these apps might be worth it's battery consumption for your usage, maybe not, the point is to know the problem and decide if it's needs to be fixed or not.
All I am saying here is that before you blame the device or hardware, make sure it isn't your software or usage that is the real culprit, but sometimes it does take some digging.
The last update to the clock app is buggy for me. It is using massive CPU and kepping my device awake for hours. It is important to check if it is working ok.
NahuelMS said:
The last update to the clock app is buggy for me. It is using massive CPU and kepping my device awake for hours. It is important to check if it is working ok.
Click to expand...
Click to collapse
I would try clearing the clock cache / data
On Gsam the clock doesn't even show up on my CPU usage.
Hemidrosis said:
I would try clearing the clock cache / data
On Gsam the clock doesn't even show up on my CPU usage.
Click to expand...
Click to collapse
Allready did that but it didn't fix it. The problem was sporadiclly. Finally uninnstaled the update, cleared all the data and updated again, no sign of the problem for now! Thanks!
Facebook lite and messenger lite if you use those services help a ton all by themselves. Shopping apps I disallow them using background data and location. It's doesn't take that long to grab location once open. Saves a great deal of data and battery.. Amazon apps turn off background data takes care of most battery drain issues related to them.
Hello everyone,
So I was wondering how to get good battery life?
I am on stock firmware latest update. No root.
Installed system wakelock detection but only whatsapp waking up like 5 times.
But, still draining a lot of percentage when the device is idle.
I used greenify to hibernate some apps.
Downgrading cpu is maybe an option.
I hope anyone has an idea!
Depends what you define as "good battery life." I find some people think they should be getting 12 hours SOT and 0% overnight drain because they read a post by someone who has their phone running with half the functions disabled and 5% screen brightness.
There are a couple of kernels that cap CPU performance if that's what you want. But you're probably better off figuring out what apps are using battery and optimize/remove them. Battery life is typically a userspace issue.
iElvis said:
Depends what you define as "good battery life." I find some people think they should be getting 12 hours SOT and 0% overnight drain because they read a post by someone who has their phone running with half the functions disabled and 5% screen brightness.
There are a couple of kernels that cap CPU performance if that's what you want. But you're probably better off figuring out what apps are using battery and optimize/remove them. Battery life is typically a userspace issue.
Click to expand...
Click to collapse
Now I am getting 3 hours of SOT max.
I do have quite a lot apps (127 apps)
But I can't figure out which ones are taking battery.
Read one of the battery guides posted in the forums, they might help you out.
With root you can detect drain eazy with betterbatterystats, if you wish to go that road.
Disable functions you don't need currently. Some apps track you with gps even when you don't use them wich drains a lot of battery. Especially from Apps that don't need this to function normally this is very uncool. Take away the permissions Apps don't need if possible.
Also look up Settings/ Battery for your battery consumption
Why not search the forum bro? Someone made a special post on how to get the best battery life...... i know its hard to use the search function but please try
ItsCrewz said:
Hello everyone,
So I was wondering how to get good battery life?
I am on stock firmware latest update. No root.
Installed system wakelock detection but only whatsapp waking up like 5 times.
But, still draining a lot of percentage when the device is idle.
I used greenify to hibernate some apps.
Downgrading cpu is maybe an option.
I hope anyone has an idea!
Click to expand...
Click to collapse
Stop using apps like Greenify and wakelock detector, they honestly do more harm than good with the newer versions of Android. OnePlus has this built in anyways, called battery optimization. Turn on advanced optimization and only allow apps you NEED to get real time notifications for, I get great battery life with that setup.
Lightbird said:
Disable functions you don't need currently. Some apps track you with gps even when you don't use them wich drains a lot of battery. Especially from Apps that don't need this to function normally this is very uncool. Take away the permissions Apps don't need if possible.
Also look up Settings/ Battery for your battery consumption
Click to expand...
Click to collapse
Thanks ill try!
geoff5093 said:
Stop using apps like Greenify and wakelock detector, they honestly do more harm than good with the newer versions of Android. OnePlus has this built in anyways, called battery optimization. Turn on advanced optimization and only allow apps you NEED to get real time notifications for, I get great battery life with that setup.
Click to expand...
Click to collapse
I have battery optimization turned on!
ItsCrewz said:
I have battery optimization turned on!
Click to expand...
Click to collapse
The advanced one as well?
ItsCrewz said:
I have battery optimization turned on!
Click to expand...
Click to collapse
I go to settings>accounts>google and turnoff all the syncing options. For calendar and contacts, when I add any, I go into there and just turn them on, let them sync and then turn them back off. Why just let them sync all day long with nothing to sync? Doesn't make sense to me. Also in Setting>Data Usage>Cellular Data Usage i tap each thing and disable background data for each individual app that I don't need doing anything. I leave apps like email, messaging apps (Textra, What'sApp web browser, Google Play Services, Solid Explorer, DropBox, Weather Android OS ) with background on so they work properly. So you know, things like Web Browsers and Solid Explorer you need their background data on so if you are downloading from the net or moving files with the file manager they will fail, so you have to leave those on. Likewise with Google Play Services, you can't download from the play store with background data disabled.
Also, you can turn off location permissions to all apps that don't need it. Go to settings>apps>App Permissions and you can select Location and it will list all apps that have the ability to request Location Permissions. Right now mine says 4 of 30 has location permissions. I have Samsung Internet, Google, Maps and Weather. I have all other apps location turned off. Here you can just go down the list instead have having to go into each app. I also Keep Location set to battery saving unless I need Maps and I just turn it to High Accuracy.
With this and keeping screen brightness on auto I get 9-11 hours SOT. Maybe a little less now since I just bought a gear S3 Frontier watch so my Bluetooth is always active now and communicating to the watch. Oh and a couple other things. I have work email set to push and personal email to sync every 3 hours and weather sync every 6 hours. These are things that are personal preferences and will cause battery life to vary. But setting up background data usage and Location permissions can go a long way for battery life.
Eric214 said:
I go to settings>accounts>google and turnoff all the syncing options. For calendar and contacts, when I add any, I go into there and just turn them on, let them sync and then turn them back off. Why just let them sync all day long with nothing to sync? Doesn't make sense to me. Also in Setting>Data Usage>Cellular Data Usage i tap each thing and disable background data for each individual app that I don't need doing anything. I leave apps like email, messaging apps (Textra, What'sApp web browser, Google Play Services, Solid Explorer, DropBox, Weather Android OS ) with background on so they work properly. So you know, things like Web Browsers and Solid Explorer you need their background data on so if you are downloading from the net or moving files with the file manager they will fail, so you have to leave those on. Likewise with Google Play Services, you can't download from the play store with background data disabled.
Also, you can turn off location permissions to all apps that don't need it. Go to settings>apps>App Permissions and you can select Location and it will list all apps that have the ability to request Location Permissions. Right now mine says 4 of 30 has location permissions. I have Samsung Internet, Google, Maps and Weather. I have all other apps location turned off. Here you can just go down the list instead have having to go into each app. I also Keep Location set to battery saving unless I need Maps and I just turn it to High Accuracy.
With this and keeping screen brightness on auto I get 9-11 hours SOT. Maybe a little less now since I just bought a gear S3 Frontier watch so my Bluetooth is always active now and communicating to the watch. Oh and a couple other things. I have work email set to push and personal email to sync every 3 hours and weather sync every 6 hours. These are things that are personal preferences and will cause battery life to vary. But setting up background data usage and Location permissions can go a long way for battery life.
Click to expand...
Click to collapse
How do you do to setting up the email to sync every 3 hours? For example with Gmail or outlook
cellular signal booster is the best solution to significantly reduce battery drawing.
AOSP with fully manual control of each and everyone app and service on your phone.
mf117 said:
How do you do to setting up the email to sync every 3 hours? For example with Gmail or outlook
Click to expand...
Click to collapse
I use blue mail. It's free and works with exchange for my work email. I don't use Gmail as it sucks for tweaking. I rarely use Google apps. I use Google calendar, YouTube, Google sheets and Google docs and that's it.
In blue mail there are sync settings
geoff5093 said:
The advanced one as well?
Click to expand...
Click to collapse
Yes
Eric214 said:
I go to settings>accounts>google and turnoff all the syncing options. For calendar and contacts, when I add any, I go into there and just turn them on, let them sync and then turn them back off. Why just let them sync all day long with nothing to sync? Doesn't make sense to me. Also in Setting>Data Usage>Cellular Data Usage i tap each thing and disable background data for each individual app that I don't need doing anything. I leave apps like email, messaging apps (Textra, What'sApp web browser, Google Play Services, Solid Explorer, DropBox, Weather Android OS ) with background on so they work properly. So you know, things like Web Browsers and Solid Explorer you need their background data on so if you are downloading from the net or moving files with the file manager they will fail, so you have to leave those on. Likewise with Google Play Services, you can't download from the play store with background data disabled.
Also, you can turn off location permissions to all apps that don't need it. Go to settings>apps>App Permissions and you can select Location and it will list all apps that have the ability to request Location Permissions. Right now mine says 4 of 30 has location permissions. I have Samsung Internet, Google, Maps and Weather. I have all other apps location turned off. Here you can just go down the list instead have having to go into each app. I also Keep Location set to battery saving unless I need Maps and I just turn it to High Accuracy.
With this and keeping screen brightness on auto I get 9-11 hours SOT. Maybe a little less now since I just bought a gear S3 Frontier watch so my Bluetooth is always active now and communicating to the watch. Oh and a couple other things. I have work email set to push and personal email to sync every 3 hours and weather sync every 6 hours. These are things that are personal preferences and will cause battery life to vary. But setting up background data usage and Location permissions can go a long way for battery life.
Click to expand...
Click to collapse
Thanks a lot! I did everything. Lets see if it works!
ItsCrewz said:
Thanks a lot! I did everything. Lets see if it works!
Click to expand...
Click to collapse
Let me know how it works out for you.
maybe you could try
1. going to developer option and decreasing the animation to 0.5x from 1x
2. disabling auto sync in accounts
3. enabling dark theme
4. using wifi more, than using 4G
you will significantly see improvement in the battery life, though the battery is already kickass in the first place
prawalhaina said:
maybe you could try
1. going to developer option and decreasing the animation to 0.5x from 1x
2. disabling auto sync in accounts
3. enabling dark theme
4. using wifi more, than using 4G
you will significantly see improvement in the battery life, though the battery is already kickass in the first place
Click to expand...
Click to collapse
Yep having all that already
geoff5093 said:
Stop using apps like Greenify and wakelock detector, they honestly do more harm than good with the newer versions of Android. OnePlus has this built in anyways, called battery optimization. Turn on advanced optimization and only allow apps you NEED to get real time notifications for, I get great battery life with that setup.
Click to expand...
Click to collapse
You sure because when i use greenify i get way better battery life and greenify also adopts to the newer version of android with shallow sleep.