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 all
I've tried 2 Surface RT's now, and both have horrendous battery problems. I've tried refreshing them, resetting them, installing all updates, turning off Bluetooth and many of the live tiles, but still the battery lasts at most 24 hours. There's nothing much installed, just a few apps (ebay, Flixster, a book reader), I have two email accounts (Hotmail and an exchange account), and that's about the lot. All updates have been performed, but still, on two separate units, the battery life is so bad that I'm thinking I can't use this as my daily tablet.
I've done the powercfg -energy test, and I get 2 errors - one is that the Nvidia Wave Device driver is preventing the system from sleeping, and the other being for high utilisation (between 18%-30%). If I turn the volume off, the Nvidia driver warning disappears, but the battery life is still poor and I don't know why the volume would need to be off when not in use. I can't find any other apps that rely on this driver (it's a speaker driver as far as I can tell), so I'm well and truly stumped.
Does anyone have any ideas on how to fix this Nvidia driver problem?
Thanks
Do you use any music apps or web pages on the tablet? If music is playing, or even paused, the app may prevent sleep. However, generally speaking, such apps should be suspended when idle for any meaningful period of time.
Even with some third-party Win32 programs running in the background on my Surface RT ("jailbroken" and then installing things like MirandaIM, which don't get suspended automatically) the tablet lasts at least three days if fully charged when I put it to sleep (I don't usually try to push the battery life, so I'm not sure what the max is) and without background network-connected processes it lasts for over a week.
Hi
Thanks for taking the time to reply. No music apps are or have been running. Since wiping it all and starting from scratch just last Thursday I've only used it for emails, web browsing and reading books on a book reader. Just can't understand why I've had such bad battery results with two separate units!
My guess would be along the lines of what GoodDayToDie said, some app you use is probably holding a wakelock on the device.
Can you list out the non-MS apps you're using to see if we might be able to find out if it is one or not?
Morning
The only apps I've installed from the store are ebay, Flixster, Book Bazaar Reader and Facebook.
Maybe I'll try to uninstall these, running the powercfg -energy report after every uninstallation. I'll report back!
tjjpowles said:
Morning
The only apps I've installed from the store are ebay, Flixster, Book Bazaar Reader and Facebook.
Maybe I'll try to uninstall these, running the powercfg -energy report after every uninstallation. I'll report back!
Click to expand...
Click to collapse
Right, all apps listed above removed, ran the powercfg -energy report and still getting the Nvidia driver error, and processor utilisation at over 20%. No apps were running in background, and same results even when volume was off.
Am completely at a loss now!
Have you run Windows Update? Normally it's not even optional (you can disable it if you use the registry, but that's the only way) but the only thing that comes to mind is that your tablet may be missing some required driver update or something... that's very odd though; I haven't heard of any such problem from anybody else.
Given that the nominal runtime of Surface RT when not in sleep mode is 8-12 hours, you're definitely not going to have a good experience if sleep mode isn't working. Technically you *can* shut down the tablet between uses - it boots up very quickly, at least - but that's a pain compared to sleep mode.
GoodDayToDie said:
Have you run Windows Update? Normally it's not even optional (you can disable it if you use the registry, but that's the only way) but the only thing that comes to mind is that your tablet may be missing some required driver update or something... that's very odd though; I haven't heard of any such problem from anybody else.
Given that the nominal runtime of Surface RT when not in sleep mode is 8-12 hours, you're definitely not going to have a good experience if sleep mode isn't working. Technically you *can* shut down the tablet between uses - it boots up very quickly, at least - but that's a pain compared to sleep mode.
Click to expand...
Click to collapse
Hi
Yes, I have run all updates, including the firmware update dated early April. I have looked for updates in both the normal 'tablet' mode and also by going into the update section of the desktop. So everything is uptodate, all of my apps from the app store have been uninstalled, but still the Nvidia driver error reports that it won't enter sleep mode and processor utilisation remains high.
As stated in my first post, I currently have two of these tablets to play with, and I have exactly the same issue on both, so I think we can rule out hardware problems, leaving some sort of software glitch. I did see this Nvidia problem on another forum, but the guy who posted it later reported that it simply went away, so that doesn't ger me anywhere.
It seems like a great piece of kit, but it'll be going if I can't resolve the battery issue.
Hi
Although I don't have any battery drainage I have to confirm that I have the same 2 errors despite the fact that I have all the updates. Can anyone else confirm if they have these errors?
That's odd. If you have the same errors but not the same battery drainage, I wonder what is causing my battery drainage and how I could check this out?
It does definitely seem to be linked to my driver error. The same problem has returned - the Nvidia driver error reporting its preventing sleep mode when the volume is on. When volume is off, that error disappears and battery life seems a little better.
Have played around with it some more, but same issue still present on both of the Surface RT's I have - battery drain unbearable. I have to ensure volume is off whenever closing the lid/pressing power button to put it into sleep mode just to try and see sleep mode actually kicking in.
If I had installed lots of third party apps I could understand some battery loss, but given they have both had full wipes, all updates installed and haven't got any apps installed other than pre-loaded ones, I just don't understand how I have the same issue on both machines. Only other thing to try would be removing my email accounts, but then there would be no point at all in keeping it!
Does anyone have any suggestions at all? If not, I think it will be time to see them going.
My only thought is incredibly bad luck and both devices have the same hardware fault.
My surface sips battery. Have never had any issues with battery
cx1 said:
My surface sips battery. Have never had any issues with battery
Click to expand...
Click to collapse
That must be nice, both of mine use so much juice they render themselves useless!
I can't think it's a hardware issue on both, especially as the huge loss of power seems linked to when the volume is on 2 or above and sleep mode is for some reason prevented.
Anyway it seems there may be no solution to whatever software glitch I have, and all of this has very much made me look at the Surface with a huge amount of disgust, so I think I'll go back to my Galaxy Note which just doesn't have such ridiculous issues as these units.
Well no-one else seems to be experiencing these issues so whatever is wrong is something with your devices. I would contact the vendor.
SixSixSevenSeven said:
Well no-one else seems to be experiencing these issues so whatever is wrong is something with your devices. I would contact the vendor.
Click to expand...
Click to collapse
The same hardware fault on two devices when the error report is linked to Nvidia wave device driver error preventing the units from going into sleep mode? Doesn't seem all that likely to me. I still think it's a software error, as this was reported also by somebody on a different forum, but with no clear resolution.
Thanks anyway.
Apart from the error, good practice for saving battery life can also be setting the screen brightness to low. In your Nvidia settings do you have the option to enable and disable power saving?
tjjpowles said:
The same hardware fault on two devices when the error report is linked to Nvidia wave device driver error preventing the units from going into sleep mode? Doesn't seem all that likely to me. I still think it's a software error, as this was reported also by somebody on a different forum, but with no clear resolution.
Thanks anyway.
Click to expand...
Click to collapse
One could argue that the software error is environmental, as it only seems to be a minority experiencing this issue. There could be a hardware fault though, don't discount just because it is two devices, you could have been incredibly unlucky and received two devices that just happen to have the exact same fault.
Well I've done some more playing about with the device, and it seems my battery drain issue seems linked with my work email account. If I am just running my normal Hotmail account, battery drain seems fine. When I add my work Exchange email/diary account, the battery drains like nothing on earth. Not sure if this has anything to do with the fact that to even get this work email account working, I had to get our IT chap to send me the security certificate for me to install.
Not sure if anyone might be able to suggest a way of having push emails still running on my work email account without the battery draining hugely?
Sony xperia Z3 Dual D6633 Android 5.0.2 Build 23.1.1.E.0.1
Hi there,
Upgraded my Z3 to lollipop last week and, despite the fact that the upgrade itself was flawless, I think I went from a device that used to work like a charm to one full of annoyances.
On day #1, noticed the batt drain skyrocket. 3h after disconnecting it, it was at 68%, half way through the morning. WTF? was my first thought. On a typical day on kitkat, I was able to end the day at 40% at least.
The second thing I´ve noticed was the phone app. It starts giving me errors, saying that the "network could not be reached" when I try to dial a number. If I insist for 4, 5 more times, it crashes. Dialing is only possible again if I reset the phone.
The third thing is the lock screen. It seems that lollipop has a drop down menu that makes it possible to enable/disable lots of things, like communications and even setting the phone in airplane mode. Imho that´s a huge liability / security risk and it appears that there is no way around that.
Still about the lock screen, it seems to have a bug: if you have any activesync account setup, not notifications will show up, no matter how you configure it (to show all or hide sensitive content).
So, I had only one thing to do, after reading forums etc... factory reseting it.
Surprise! All problems are still there.
Does any1 have any tips on those?
Thanks in advance.
There will be a widget on one of the screens which keeps refreshing itself and I found that to be the battery killer on my 6603.
Did you use any specific app to pinpoint the culprit?
1. It is possible that the battery levels are calibrating and will be imprecise for a while after the update, using the device normally for a couple of days will fix it, or at least this is what I observed in many phones I owned.
2. This is very weird and I can't help you with. If not even factory reset did help you may have some corrupted data on one of your contacts maybe? Try to make a thread about this issue on the Sony forum.
3. I noticed that as well, but even on pervious versions you could turn off the phone so I don't think it changes anything. Make sure to disable the multi user options that would allowanyone to add a new user from the lock screen.
4. Another weird thing, I use exchange accounts on my phone and I don't have any problem on mine. See point 2.
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
ozzy lion said:
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
Click to expand...
Click to collapse
That's not a smartphone anymore, with all functions shut down and brightness low.
This phone has the best screen, use it at least 50% brightness.
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
ozzy lion said:
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
Click to expand...
Click to collapse
You said stamina.
Stamina means already some functions off.
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Hi, if problems are persistant you can always downgrad software at KitKat by using FlashTool and wait Lollipop 5.1 (5.1 will probably solve many problems).
StealthNet said:
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Click to expand...
Click to collapse
A new firmware version has dropped for the Z3 which I think fixes your issues with notifications.
I received it OTA yesterday, I'm running the Balkans customisation.
Thank you for the tip! I hope it does! Will keep it posted here just for the reference. I am starting to feel other "symptoms" as well, like bluetooth instability (you pair a device and it stops working, have to pair again).
.
Just hit another weird thing.
I am not being able to create a new vpn connection. I am trying to use the PureVPN and IPVanish client software, but when I try to setup the conection, I receive a disclaimer, saying that my traffic might be monitored, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
My device is encrypted and I have also noticed that I am not able to decrypt it.
Also, If I go to Accessibility and try to enable a service, the same thing happens: a disclaimer appears, saying that the service might observe my actions, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
Any ideas?
Ok, just a quick fup: the ability to create VPNs from apps is disabled if you encrypt the phone. It seems that if you create if before encrypting, it won´t be disabled; but you wont be able to create a new vpn from an app downloaded, after encryption.
Regarding the Accessibility > Services, after a *lot* of research, I have found that Twilight was the culprit. For the reference:
https://code.google.com/p/android/issues/detail?id=79637
Hello guys. This topic is pretty long and it is hard to read all of it but try to read all of it till end.
Well, let me begin. The main problem of the nougat update is the dramatic increase of battery consumption (for me at least) But why this is happening?
Actually this is a matter of battery managers. Huawei had created a great phone but obviously they messed things up in the software side. Google announced "Doze" feature with Marshmallow. If we could have a brief explanation of "what doze is" is it is basically a battery protection policy created by google. In Android, apps have the ability to use what’s called a “wakelock” to prevent your phone from going into a power-saving deep sleep mode. This deep sleep mode usually kicks in when your phone’s screen is off, but that can get in the way of how some apps work. For example, if you’re using a fitness tracker, you don’t want your phone turning off GPS or your accelerometer just because your phone is in your pocket with the screen turned off.
In principle, this is a good concept. Apps keep your phone awake and working when they need to, and let it sleep when they don’t. This is a problem, though, when every developer thinks their app is important enough to keep your phone on all the time. That’s why apps like Facebook kill your battery, even when you’re not using them.
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device). Here is a graphical explanation of how doze works versus time:
http://itresan.com/wp-content/uploads/2016/05/doze-header.jpg
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device)
If we turn back to the main topic, as I mentioned before, Huawei has some difficulties combining it's own features with google's. Huawei has its own battery manager. That's why you are not receiving some notifications from facebook or whatsapp. That is because that freaking battery manager shuts everything off but still, since it has a very poor approach, the system drains battery. It is basically a matter of doze does not kicking in. As you can see, the battery usage when the screen is turned on is about the same. However, the same thing cannot be seem when the screen is off.
So what to do in order to save some juice?
-There is some workarounds for doze kicking in like these ones:
https://play.google.com/store/apps/details?id=com.yirgalab.dzzz
https://play.google.com/store/apps/details?id=com.suyashsrijan.forcedoze
These two apps have different approaches. I prefer ForceDoze as it seems the google's intended way.
I want to highlight this item because this might be the most important thing in this topic. If you don’t do anything with your phone, Doze will still do its job. It runs almost invisibly in the background. Occasionally you’ll get a few messages at once, rather than spread over a few minutes, but for the most part there’s no noticeable change. In other words this is a bit different from the conventional full deep sleep and you do not have to afraid from doze as you do with the full deep sleep.
-DO NOT CLEAN YOUR RAM TOO OFTEN. This will cause closed apps re-open and hence, more cpu usage.
-No! Cleaners, Task managers and other stuff does not work! As I mention before, they even lead more battery consumptions.
-Huawei has poor google service implementations. Even one or two implementation has some bugs that causing battery drain(for example: google backup). Try to turn them off.
-Know when to reboot your phone. Too frequent reboots may do the same thing as you cleaning your ram. However, rebooting cleans app caches so the system will work smoother. Once a week or two weeks is fine I suppose.
Please hit the "Thanks" button if you like and please point out the missing things and if you see a mistake please warn me for correcting it. I hope you liked the topic.
Have a nice day!
Doze is problem for me. I don't have push notification by the night.
darrr1 said:
Doze is problem for me. I don't have push notification by the night.
Click to expand...
Click to collapse
It's probably not because of the doze but the huawei's power manager itself.
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
darrr1 said:
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
Click to expand...
Click to collapse
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
I did everything what I can without succes.
furkey said:
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
Click to expand...
Click to collapse
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
xtcislove said:
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
Click to expand...
Click to collapse
Doze is not on kernel level but it is on software level. Programmatically we can activate what is left from doze or at least simulate it. However, if there is a certain need for doze we should cook a whole new rom and yes, it requires open source too.
But, let's clear a thing here: Huawei did not completely removed doze. Actually, I think they can't do that if they wish to use Android. Just some settings of Huawei conflicts with doze and prevent its functioning.
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
antimatter.web said:
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
Click to expand...
Click to collapse
Could you finally solve this?
I also have and Honor 9, and have the same problem with aplicacition radardroid. Is getting killed, and also have all configured to prevent this...
Try by having both in the Settings
-Battery/Close apps after lock screen (uncheck in the list)
-Apps/Settings gear/Special access/Ignore battery optimization (make it allowed)
Thank szgfg,
Both are already well configured, but still closing the app.
mikicl said:
Thank szgfg,
Both are already well configured, but still closing the app.
Click to expand...
Click to collapse
Check also is not being closed by the automatic cleanup (so add it to clean whitelisted apps) and that is not being closed due to high consumption...disable that on battery settings... Let the advertisement but do not let phone administrator close that apps automatically
Enviado desde mi EVA-L09 mediante Tapatalk
Hi jcalderonv74,
Thanks for your answer. I didn't know about the clean whitelisted apps, was a surprise to find it. But unfortunetly, everything was well configured.
Option to avoid being closed due to high consumption was already OK.
So nothing to change, everything was as it has to be. Seems more a software problem in EMUI 5.0
After some days without touching anything in the phone's configuration, finally observed that everything is working fine. All aplications configured keep opened, and it's only Radardroid aplication that sometimes closes alone (only sporadically after a recent update)
Seems more an error in Radardroid aplication that in telephone's software. So I'm not worring more about that.
First off, I love the phone and I'll keep it, but ever since I got the phone I've been wondering why it's draining so much in standby. It's my first Samsung phone since 2011, so naturally I assume it's Samsung apps/services that drain? Especially since I don't use any new apps than on my other phones and in the battery stats it doesn't really show any user apps that use a lot.
Anyone has way to measure what system/user apps drain during standby? Or even better, any dev that could do a deeper dive into this?
For example, I just lost 32% battery while sleeping for about 8h, it has never been this much on any other of my previous phones (OnePlus Nord/Pixel 3a/Pixel 3/Pixel 2).
In fact, my OnePlus Nord with 815mAh more than the Flip3 is currently on last charge 3 days ago (it doesn't show me hours anymore) and 2h35m SOT and 25% battery left. On the Flip I just now got 17h with 1h30m SOT and 5% left. Settings all similar besides location accuracy turned off for the Flip as that was a massive drain.
Something must be unintentionally draining the battery during standby and I really hope one of you smart guys can find it. Or Samsung fixes it with an update..
I disabled AOD and any unnecessary account sync processes. It's only drained about 2% in standby the last 5 hours, but there are still some things to finish configuring.
twistedumbrella said:
I disabled AOD and any unnecessary account sync processes. It's only drained about 2% in standby the last 5 hours, but there are still some things to finish configuring.
Click to expand...
Click to collapse
If have AOD on a schedule so it's turned off during sleeping, account syncing I don't have anything that I can turn off and I never did on any previous phone
M4-NOOB said:
If have AOD on a schedule so it's turned off during sleeping, account syncing I don't have anything that I can turn off and I never did on any previous phone
Click to expand...
Click to collapse
How old is your device? You got to give it some time to settle. I had 15% battery drain the first night, after that it went down to 5%.
M4-NOOB said:
If have AOD on a schedule so it's turned off during sleeping, account syncing I don't have anything that I can turn off and I never did on any previous phone
Click to expand...
Click to collapse
The first step in improving the battery is to remember that this isn't any other phone. You may want to explore what options are available and what all you have enabled. By default, almost everything is on to show off all the cool new features that make this a Flip 3, not a OnePlus Nord.
ione2380 said:
How old is your device? You got to give it some time to settle. I had 15% battery drain the first night, after that it went down to 5%.
Click to expand...
Click to collapse
Got it 4 days ago
twistedumbrella said:
The first step in improving the battery is to remember that this isn't any other phone. You may want to explore what options are available and what all you have enabled. By default, almost everything is on to show off all the cool new features that make this a Flip 3, not a OnePlus Nord.
Click to expand...
Click to collapse
Which Flip features are in use during standby though? During standby it's just another phone
M4-NOOB said:
Which Flip features are in use during standby though? During standby it's just another phone
Click to expand...
Click to collapse
Not true. Samsung has a bunch of features still in use.
Settings -> Advanced features -> Motions and gestures has a whole collection of things that are still running when the screen is off (and most aren't useful to the Flip, but came from "another phone").
Settings -> Cover screen allows you to disable turning on the screen when notifications arrive, if that is not something you need.
Also, unless you are using the app to lower the refresh rate, you may be running a bit high when idle.
twistedumbrella said:
Settings -> Advanced features -> Motions and gestures has a whole collection of things that are still running when the screen is off (and most aren't useful to the Flip, but came from "another phone").
Click to expand...
Click to collapse
I've turned a few things off there, but a lot of them OnePlus has too + a few more, which I had all enabled
twistedumbrella said:
Settings -> Cover screen allows you to disable turning on the screen when notifications arrive, if that is not something you need.
Click to expand...
Click to collapse
I didn't really get any notification during last night, so I doubt this was the culprit
twistedumbrella said:
Also, unless you are using the app to lower the refresh rate, you may be running a bit high when idle.
Click to expand...
Click to collapse
Yes I'm using that app and have it set to 48-96Hz
Appreciate the help, I believe there must be something that's unintentionally draining and while I went through every single setting in the beginning, I'm still very new to OneUI (and also impressed how far it came from the TouchWiz ****show)
One thing I always forget is that a lot of those features are running services and polling when they're enabled. Even though I'm not touching the screen with the tap to wake enabled, it's constantly waiting for that tap when it's asleep. Any one isn't a big impact, but Samsung has so many "convenience" features that I end up wasting battery to never use.
The calibration period is also horrible. Android 11 is slow to calibrate the battery and Samsung is worse. You can get a good idea of what is draining battery by going to Settings -> Battery and device care -> Battery. That may help find out if it's a renegade app.
One thing Asus does that I wish Samsung would embrace is Auto-start management. Some apps aren't efficient at polling for notifications and more than once have been the cause of major drain.
Another one even Samsung admits to be a source of drain is the edge panels. If you don't use them, it's best to kill the entire feature.
twistedumbrella said:
Even though I'm not touching the screen with the tap to wake enabled, it's constantly waiting for that tap when it's asleep. Any one isn't a big impact, but Samsung has so many "convenience" features that I end up wasting battery to never use.
Click to expand...
Click to collapse
I just assumed it's not a big impact as OnePlus has those as well, for example draw a "V" on screen for flashlight or ">" to skip song besides the regular double tap to wake and it never appeared to be a battery issue for me before.
twistedumbrella said:
You can get a good idea of what is draining battery by going to Settings -> Battery and device care -> Battery. That may help find out if it's a renegade app.
Click to expand...
Click to collapse
Do I assume correctly that some system apps or similar are hidden there? I just did the calculations and the percentages only make up 43.6%. I attached a screenshot
M4-NOOB said:
I just assumed it's not a big impact as OnePlus has those as well, for example draw a "V" on screen for flashlight or ">" to skip song besides the regular double tap to wake and it never appeared to be a battery issue for me before.
Do I assume correctly that some system apps or similar are hidden there? I just did the calculations and the percentages only make up 43.6%. I attached a screenshot
Click to expand...
Click to collapse
OnePlus also optimizes them better than brand new Samsung firmware. I had a lot of stuff enabled on the Note 20 Ultra that I won't be using for a month or two now.
Some apps are excluded, but it will let you know if it's something not included with the phone.
Another good idea is to uninstall, disable, or "adb uninstall" any bloat you don't use. Besides clearing up space in the app drawer, it kills off services you don't use. A lot of the apps will run services even before you sign in, even though they aren't actually handling any data.
twistedumbrella said:
Another good idea is to uninstall, disable, or "adb uninstall" any bloat you don't use. Besides clearing up space in the app drawer, it kills off services you don't use. A lot of the apps will run services even before you sign in, even though they aren't actually handling any data.
Click to expand...
Click to collapse
I already went through the list and uninstalled which I 100% knew what it was and that it's not needed, but not sure about 99% of Samsung stuff. Some Samsung apps on the phone I don't even know what they are and when I start them it just prompts to agree to some terms before starting the app... I'll have a look around for a Samsung debloat list
M4-NOOB said:
I already went through the list and uninstalled which I 100% knew what it was and that it's not needed, but not sure about 99% of Samsung stuff. Some Samsung apps on the phone I don't even know what they are and when I start them it just prompts to agree to some terms before starting the app... I'll have a look around for a Samsung debloat list
Click to expand...
Click to collapse
If you have the unlocked version, they allowed uninstall for a lot of apps that were previously locked. A lot can also be downloaded later from Google Play or the Galaxy Store if you change your mind.
I use Firefox, so I uninstall Samsung Internet and Chrome. Members and Health are two big ones that like to run those "please enable us" services. It's a lot of deciding what you might use versus what you can live without.
Another good idea is to add anything you won't use, but didn't remove to deep sleeping apps to kill it's ability to run in the background. It's the closest thing to auto start management without rooting.
[HOW-TO][DEBLOAT][ADB] The ultimate ADB debloating thread for the S20/+/U series
Hi, i´ve seen some threads and questions about debloating in the s20 forum, but by having a quick look at them, theres not much information for beginners. Thats why I decided to sign up and join the xda community. I would like to make this the...
forum.xda-developers.com
twistedumbrella said:
Another good idea is to add anything you won't use, but didn't remove to deep sleeping apps to kill it's ability to run in the background. It's the closest thing to auto start management without rooting.
Click to expand...
Click to collapse
Yeah I do have 57 apps there already
I just removed 85 apps/services via adb, let's see how it is tonight and I'll report back tomorrow
M4-NOOB said:
Yeah I do have 57 apps there already
I just removed 85 apps/services via adb, let's see how it is tonight and I'll report back tomorrow
Click to expand...
Click to collapse
Thank you for taking the time, mine is also going down %30 overnight. would love to hear about your result.
ShayMagen said:
Thank you for taking the time, mine is also going down %30 overnight. would love to hear about your result.
Click to expand...
Click to collapse
So far I don't have much hope sadly. Whole day currently at home and not using the phone much and it's looking like in the screenshot (screen off, loosing almost 2.7% per hour, as comparison my OnePlus is at 0.9% per hour)
https://imgur.com/RLITZwQ
It's 21:21 at the moment and I'm at 54% after 9h 42m (comparison OnePlus with 815mAh more: 7% after 79h with 2h54m SOT)
https://imgur.com/M9zO2hV
I'll probably head to bed in a few hours and then report back tomorrow morning how much I lost during the night..
I'm not claiming to have amazing battery life, since I almost considered keeping my trade-in and returning this one over it. I am interested why it is so bad for others, though.
twistedumbrella said:
I'm not claiming to have amazing battery life, since I almost considered keeping my trade-in and returning this one over it. I am interested why it is so bad for others, though.
Click to expand...
Click to collapse
HOLY **** I would love to have this battery life. I'm literally not doing anything with the phone and just loosing so much. I'm pretty much the opposite of a power user, so my phone is in standby most of the time and loosing so much is pretty frustrating.
EDIT: I might have an idea why it's so bad for me, I don't really have reception in my apartment (as you can see on my screenshots), so I assume it's constantly trying to get better receptions, I see 2 bars sometimes, but most of the time 0. I'll keep my phone at the window where I have reception for the rest of the day and see if it makes a difference. (Although the OnePlus has also bad reception, but does have a different carriers SIM card)
M4-NOOB said:
Yeah I do have 57 apps there already
I just removed 85 apps/services via adb, let's see how it is tonight and I'll report back tomorrow
Click to expand...
Click to collapse
Dependencies, dependencies, dependencies... some of those apks just sit there unless needed.
Do not disable apks/services unless you know what they do and what, if any, their dependencies are. Go too far and you'll end up in a boot loop.
What works for others probably isn't ideal for you.
Package Disabler is a better option as you easily toggle apks on/off as needed.
Screen off the serial offenders tend to be Google backup Transport, Framework and any cloud apps.
Try disabling Google play Services at night and see if that helps. You may need to disable Find my Device first as System Administrator if disable is greyed out.
Disabling play services also kills Gmaps and Playstore which are know hogs. Gmail as well to a lesser extent.
Google Firebase, do you need it? If not disable.
Carrier, Google, Samsung and app feedback, disable.
Using power management can cause erratic behavior and not solve the problem. Treat each power hog on a case by case basis instead. It takes a lot longer but yields a cleaner, more stable setup.
Play with it, go through -all- the settings. It's actually quit fun to explore and almost impossible to crash and burn.
Try this trick to stop ads globally: