What is Reddit's opinion of Wakelock Detector [LITE]?

From 3.5 billion Reddit comments

Assuming you are fully stock and not rooted:

Install Wakelock Detector Lite, connect the phone to your PC and issue the following commands (you'll need the USB Drivers, and Developer Options enabled):

adb tcpip 5555 adb shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS

Now open the app and check the top culprits. Tap on the individual items to expand, and see which specific wakelocks are taking up the most time. This should narrow it down quite a bit more than the built-in Battery screens.

I have location services turned off all the time. After the April update, android OS was always second to screen on mine, but still high consumption (20+% of total battery usage throughout a day).

Mine is usually caused by a Bluetooth process keeping the phone awake even after toggling Bluetooth off (after listening to music via Bluetooth).

There are so many things going through android OS that regular battery stats aren't granular enough to find. I'd recommend people download the non-root version of wakelock detector (https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot) and after enabling usb debugging, connect your phone to your computer, then at a command prompt (assuming you have adb installed on your computer) type this:

Adb tcpip 5555

This gives the application access to read the wake lock status for processes and services. Note; if you restart your phone then you have to redo the above step for the app to have access to the info.

I noticed a remarkable improvement in idle battery life with 7.1.1. I made it 48 hours on a single charge when before I would have needed to charge again after ~36 hours. [Yes... these are lite usage days for me, which is common during the week].

Get Wakelock Detector Lite to see if any specific app is high, but not showing up no the normal Android Battery view. https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

I've always used Wakelock Detector Lite and then used their ADB workaround for non-rooted devices in order to get in-depth information about wakelocks and the apps/services causing them. Just a few ADB commands and you're set; it presists through reboots so you don't have to worry about it losing access if you restart your phone. I can dig up the guide, just gotta look for it

Edit: Here's the guide from XDA

You can also find wakelocks by using Wakelock Detector. Install it, and then follow the instructions. It requires plugging it into your computer and installing a companion Chrome extension, but it gives you a pretty easy breakdown of which apps are waking your phone up, how many times it's done so, etc.

I posted this in another s7/edge thread about android drain and wake locks, it's very pertinent.

>There are so many things going through android OS that regular battery stats aren't granular enough to find. I'd recommend people download the non-root version of wakelock detector (https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot) and after enabling usb debugging, connect your phone to your computer, then at a command prompt (assuming you have adb installed on your computer) type this:

>Adb tcpip 5555

>This gives the application access to read the wake lock status for processes and services. Note; if you restart your phone then you have to redo the above step for the app to have access to the info.

WakeLockDetector [Lite] should help clear up whether or not it's an app causing the issue. Generally speaking, fewer wakelocks are better. However, you might find that the number of wakelocks you have is not correlated to your battery life. In which case, it's a system issue and you could try a factory reset.

Many people say to factory reset after any OTA so bare that in mind next OTA.

I've also been experiencing bad battery life on my Moto G4 in the last month. Looking at the battery stats in the phone's settings it seemed as if my phone spent most of its time awake ( I don't know if it started after the nougat upgrade ). I downloaded Wakelock Detector ( https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en_GB ) and managed to get it working via the instructions provided. After a day or so of profiling it provided a list of the apps that it thought were causing the phone to stay awake. Turns out that the #1 culprit was GMail which woke my phone up over 1000 times per day! I deleted all accounts from the phone settings, leaving Gmail installed and downloaded a different email app and so far battery has been significantly better. Other apps that I've removed which also keep my phone awake include Evernote & APKPure. The last biggy seems to be the Google app. I guess it keeps switching the phone on so that It can track where you are and provide suggestions.

Battery drain seems to be higher on Nougat when I'm using the phone but at least now the battery is draining slower when I'm not.

Android system should not be higher than the screen usage. I would recommend checking for wake lock with wakelock detector. If you can't find any wakelocks, I would recommend doing a factory reset.

I found a few apps I installed after getting the Pixel would check location WAY too frequently and just disabling their location access fixed some of my idle battery issues. I've also used the following two apps, 1 works without root to see what apps are working in the background. The other I use to hunt down apps with low APIs (below Marshmallow) and I uninstall any that I don't absolutely need. Sometimes I do this with Marshmallow apps too. I'm not convinced Facebook is a big issue (my opinion). Mine were Walmart pinging location a ton, Best Buy pinging location a ton, and some other random location requests.

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

https://play.google.com/store/apps/details?id=com.kroegerama.appchecker

I've also found just occasionally, something is in a funky state and a reboot fixes it. Although 20+ days with 7.1.1 and I have not needed to reboot my phone.

Use this app, works without root. I learned that the worst app for me was Google+ with constantly a TON of awake time in the background. https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

I'm not sure, GSAM wasn't much more helpful for me than the built-in battery stats.

For wakelock I used: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot since I'm not root, and just follow the instructions for setting up battery monitoring.

It showed I was getting thousands of hits on NlpWakeLock (under Google Services) per hour so I'm curious to see if anyone else was having this issue.

Edit: Looks like GSAM might have that capability if you're root, but that's not something I can confirm personally.

Have you tried installing an app such as WLD Light?

I used it to track down that Facebook and Instagram were using a lot of battery with my phone on standby.

Reset the phone and don't restore from a backup. If that doesn't fix it, download Wakelock Detector to see what's eating your battery. Enable "Advanced Mode" in settings to see kernel processes as well as that is most likely where you'll find your rogue process.

For me, the stock launcher's quick search box was eating my battery. That was a while ago though so it might have been patched since.

The absolute easiest way to figure out which app(s) are doing this is by using Wakelock Detector Lite. This is the non-root version, which means all you need to do is give the app permissions to read what's causing problems by plugging it into your pc and then following the instructions it gives you. It takes 20 seconds.

Then you can open the app at any time to see exactly which apps have been causing the most wakeups and using resources that hide behind "Android System" and "Android OS."

For me, Android Messages was causing an absurd amount of wakelocks and I never would have known it was that app until I used WD. Deleted it and moved to Textra and my phone sleeps much better now.

Try using Wakelock Detector Lite and their ADB workaround for non-rooted devices in order to get in-depth information about what specifically is causing your wakelocks. From there, we can figure out a solution (hopefully). Here's a guide from XDA

I always have it on. In terms of battery life it makes little to no difference assuming it's not stuck. It's helpful if you need to factory reset, you can restore apps, data, etc..

You don't need to root to get Wakelock Detector (Lite) working fyi. Just a computer with adb to grant battery stats permissions. Check the Play Store listing description and there will be a guide with 2 methods: via chrome extension and via adb.

I used this app: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

It pointed to one of my apps keeping the phone awake. I removed it, and battery is back to normal.

Note that unless you are rooted, you will need to give the app additional permissions via adb. The app provides a chrome extension that can do this for you, but you will still need to connect the phone to your computer for it to grant permissions.

Yeah, doesn't look good.

You can use Wakelock Detector or other apps to check for wakelocks.

Also, do you really use the camera that much?

Have you tried looking at wakelock info? You can use this app even if you don't have root.

I was able to see that a few apps were slamming my phone with wakelocks, that I then either uninstalled or changed their settings. Battery has been good since.

This is very likely a third party app.

Android has relatively useless battery reporting statistics. What I mean by this, is that "Android OS," "Android System" and "Google Play Services" are all huge umbrella categories that contain a bunch of system services and resources that may be being used/called upon by a third party app.

Example: Waze starts spamming the shit out of location requests. This would very likely show up under "Google Play Services" because that's where the API lives that reports your location back to Waze.

It's kind of a shitty system, but the best way I've found to diagnose these random drains is to download Wakelock Detector Lite. This is the non-root version. All you need to do is plug your phone into your PC and follow the on-screen directions within the app to get it working. It takes like all of 45 seconds, and then it'll show you exactly which apps are using up system resources.

If the phone is warm while not doing something intensive like a game or.. Maps let's say and ESPECIALLY if while the screen is off then you have a wakelock (or several). This can be said of any phone- not simply ones with mediocre battery life such as the S6.

 

Without root the best way I've found to track them down is with Wakelock Detector Lite. Whether you'll always be able to do something with the knowledge of what's killing your battery is another story unfortunately.

There is always a reason for battery drain. It is hard to help without further information. The easiest way to gain more info would be with wakelock detector. There is also a non-root version https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

If you don't want to root, follow the given steps and monitor your battery with it after a full charge + reboot. Afterwards you can post the needed info here with screenshots:

• Display-WakeLock
• CPU-WakeLock
• WakeUp-Trigger
• Kernel-WakeLock

Additionally post a screenshot taken from the battery detail view. Go to settings - battery - tap on the graphic

I did not have any issues at all since updating to Nougat. That was back on Beta 8 (first N Beta). I used every single beta build and did a direct update from Beta 11 to stable 4.0.3 just yesterday. No issues at all on my end. I have all additional "battery-saving options" disabled on my device and don't use any other "optimization" tools.

Battery Historian is great as u/baldthumbtack has mentioned, but if you're interested in diagnosing it on your device, I recently downloaded Wakelock Detector Lite which has been tremendously helpful in showing me which apps are using up resources.

You don't have to be rooted to use it, but you do need to have ADB installed on a computer so that you can give it permissions to run that it otherwise normally wouldn't have. It will have instructions in the app to guide you through this process.

Have you investigated wakelocks?

I was finding my battery draining constantly and it was supposedly "Android System" doing it, but using a wakelock detector, I could see that there was a game that I'd installed that basically kept the device awake all the time.

I'd recommend https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot You have to connect over adb and run a command to give it permission to watch other apps, but I think better that than give some random app full root access.

Try wakelock detector [LITE] and use the chrome extension to grant it access to battery stats.

Follow the instructions in the app description: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

Seconding this. Google makes it so hard to detect battery drain.

I recently found an app called Wakelock Detector which uses some workaround with a Chrome extension over adb to allow you to see a wakelock breakdown from each app. But this should really be something built in. It's a huge issue in Android.

There is a "lite" version of WakeLock Detector that does work w/o root: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

There are a few steps involved, but once I got it working (involving a Chrome add-on, USB cable to PC), it did help me find wakelocks.

There is a version of Wakelock Detector (LIGHT)! that was designed for those of us without root. I'm using it on my Nexus 6p. Just need to install a chrome extension, connect phone to computer and run it.

There is a powerpoint in the description on the play store as to the steps needed to get it working. Not too difficult, but let me know if you have questions.

I doubt it is normal, but it's so long since I had a phone that wasn't connected to a watch I don't know.

Is this a new setup for you? I'd suggest restarting both watch and phone if it is.

What apps do you have on your watch that need your phone to do stuff? Remember your watch needs your phone to get internet access, so things like constant updates of weather, automation apps like Tasker, etc etc all use your phone.

How sure are you that this is anything to do with your watch, and not just a phone issue? Something like an app update downloading over and over due to a problem?

Given I only get about 3.5 hours of screen time on my phone anyway, a drop of 3 hours seems huge and more than enough to identify with any of the apps that tell you about battery usage. I've used Wake Lock Detector successfully to identify such things in the past.

Yup, I remember when it happened with the Facebook app like 10 years ago.

Try Wakelock Detector and see if the app detects it https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

From the second screen it looks like there is no deep sleep at all,

Pokemon go is a heavy gps battery drainer.

Install this https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot activate it using the instructions in app/in the description and post screenshots after few hours, don't let battery drain too much or wakelock detector will give you errors

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

App is a bit buggy at times but it's great for showing you which apps are killing battery in the background. One of the worst offenders for me was the tmobile app that showed no battery usage but was used 100% of the time in the background. On top of this it also showed me how some apps were set up to work in the background too often like maps and all its traffic updates.

download https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en give it adb permissions check for Gservices wakelocks and disable the services using https://play.google.com/store/apps/details?id=cn.wq.myandroidtools&hl=en

but maybe first you can clear cache and whitelist google apps in adhell if you are using it

It definitely looks like you've got some wakelocks happening on your device that are draining your battery a lot faster than it should.

You don't need root to use a wakelock detector, although if you're rooted, the process is more straight-forward than what I'm about to show you.

Wakelock Detector [LITE] will work without root, but it takes a little work to get it working on your device. It's a one-time procedure, though, unless you factory-reset your device. Follow the instructions in the app itself, as well as the store page, and you'll be well on your way to tracking down what is keeping your device awake and draining its battery.

Let me know how the setup process goes, and I can help you out where I can. I'm at school, though, so I might not be able to answer any questions right away.

Good luck!

Guys I've fixed the problem with the standby time!! I got a wakelock detector. Instead of root I used the PC workaround (the app explains it nicely) and after that, I sleep for 7 hours at 100% and wake up to no or 2-3% battery loss

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dwakelock+detector+ter&pcampaignid=APPU_1_-ZD7WYKPLsGZkwWrkpLYAg

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

This worked for me since I have a Verizon phone and no root. It's a little tricky to install. I used the Chrome Extension method. My main issue was S Health trying to count my steps with my phone instead of just my Gear Fit2. My work wifi also seems to drain my battery so I don't use it anymore.

Wakelock Detector Lite try that if you wanna diagnose it further than that. My drain is from "phone" in GSAM, also. Mine is due to "lmsService" which has a suggestion or two but nothing I'm willing to go through in order to fix it.

I turned off Wifi calling and my idle drain is back to ~.5% an hour. It isn't a great solution but it's better than waking up to the phone being warm in the middle of the night. Perhaps you have a similar issue.

You can use wake lock detector lite which doesn't require root and take a look with the battery historian tool. I come back with an edit for like is to both.

Edit 1: Battery Historian: I run this on my own Linux VM and works well, PM me if you need help setting this up and bring a bug report in there

Edit 2: [Wakelock Detector Wakelock Detector [Lite]: Use the chrome extension to enable the apps needed permissions without root.

Wakelock Detector Lite if you have access to a computer and can follow a few instructions is your best bet at tracking down wakelocks that fall under "Android OS." You can't always do something about them unfortunately, but you will be able to pinpoint them.

Your phone stayed awake for most of the time. You should probably check that out. Intall wakelock detector to figure out what's causing it to stay awake.

Yeah, unfortunately Android battery stats aren't very helpful if you're trying to diagnose the source of battery drain, since the most common things you'll see (Android System, Android OS, Google Play Services) are all sort of umbrella categories for services that third party apps may be using.

Some people will tell you to use Battery Historian. In my experience, Battery Historian is helpful in letting you diagnose exactly when drain occurred (in case you may have unknowingly triggered high drain by connecting to a certain wifi network, etc), or observing standby drain stats over certain time periods, but I actually find it pretty unhelpful in tracing the source of a wakelock or offending app in the background.

Instead, I highly recommend downloading and using Wakelock Detector Lite. This is the non root version, you just need to follow the instructions in the app and connect your phone to your PC to get it working. It literally takes 45 seconds.

It's been a godsend to me in figuring out which apps are doing a bunch of stuff I don't want them to do in the background.

Learn how to use wakelock detector lite & ADB commands. Instructions are on the play store. Should help you track down the problem.

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

Hey man, you can use WakeLock Detector [LITE] w/o root. It works, but you have to use an adb console and a plugin for Google Chrome. Not hard to do and there are instructions.

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

I presume the low ratings are from people that were too stupid to follow the instructions.

> Unfortunately the backup functionality isn't as comprehensive as apples system via iTunes.

Not true. Samsung's Smart Switch is quite easy and fairly comprehensive when backing up and restoring. Smart Switch

OP, the best way that I've found to identify Android System (without root) drains is with Wakelock Detector Lite. If you have a PC there's instructions on how to set it up and get it working without root. I, for instance, had large Android System drain on AT&T's September security patch for the S6. With Wakelock Detector I was able to track it down to IMS Service, and stop it by disabling Enhanced LTE Services. Back to ~.5-.7% idle drain per hour as I'm more used to.

>I dont really want to root and flash anything because I still have like 9 months of warranty left.

Rooting and unrooting a D855 is so easy that I did it, and when the phone stopped reading my sd card, I simply unrooted it and handed it back for warranty repair. Hey presto phone fixed. There's a heap of tutorials out there. It comes down to "if you can be bothered".

>But do you have any idea why "Android System" is eating up so much battery?

It could be anything. Try using Wakelock Detector lite to see whats keeping you'r phone awake, and theres some steps to follow to set it up

Actually the wakelocks can be read without rooting/unlocking using Wakelock Detector Lite and adding the required permission via ADB by typing the following in the ADB shell:

adb pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS

Does not persist over reboots though. I've tried it and it worked for me, however results were inconclusive.

The description in this app has a workaround to let wakelock detector check without root, though you'll need to follow the steps and use a PC.

So, as it turns out.. the severe wake lock was being caused by the T-Mobile My Account App.

I used the no-root version of Wakelock Detector where it uses ADB to allow the stats to be collected. I could tell within an hour because the app hasn't been opened in several days and my phone was awake from the time it was off the charger til about 15 minutes ago, I checked the app and sure enough, the thing keeping my phone awake was the T-Mobile app.

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

When you open Wakelock Detector Light, what does it show you? It should display some sort of error message if it isn't properly installed.

If so, and you don't have a rooted phone, you need to perform the proper steps outlined in the presentation they created (linked in the Play Store description or here : http://goo.gl/Yqdh2F). Be sure it is the Light version (link!)

Post if you have questions.

Google Play services seems to be the culprit from the images you shared.

If your phone isn't rooted, install Wakelock detector light (https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot)

And then let the phone run for awhile, and report back with stats from Wakelock Detector.

There seems to be a bug with Google's own data backup feature which lives inside Google Play Services. It keeps the phone awake, not letting it go into deep sleep state or Doze. Greenify and Amplify don't help because this wakelock is only acquired once, and is never released until a reboot.

While on the same Settings -> Battery screen, tap on the graph and look at the "Awake" stats. If you see a solid green line it means something's keeping the phone awake, and the "*backup*" wakelock is the likely culprit. To confirm if you are rooted, use any number of wakelock detector apps. Folks without root can use the Wakelock Detector Light app with work-around instructions.

You can try disabling the Backup feature in Settings -> Backup & reset -> Back up my data, and toggling it off. After a reboot that wakelock should disappear and allow battery saving features of your phone to work properly.

Here is my sot of today (22.07): http://m.imgur.com/wDbwYuI Copying my thread OP here: Hello guys! It has been a long time since I have been trying to sort out my drain issues on my S6 Edge+ , a couple of days ago I finally figured out to use Wakelock Detector without root then it comes out that it was actually the maps keeping the phone awake via "NLPWakelock" through Android OS. I will cover out the process step by step to found out which app is causing the drain and why! We will need ABD, so we must have a computer.

1)First we are gonna need the app; "Wakelock Detector [Lite]" root users may use normal version too. Play store link: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=tr

2) We should open USB Debugging option in developer settings. And connect our phone to computer via USB.

3) To check if we have adb installed, you can simply run command promt ( windows/run/cmd ) and write Code: adb devices If the output is similar to the image below, it means you have ADB installed and if you have device entry you have your ADB device drivers installed too.

If ADB is not installed, please kindly check Snoop05's thread to use his perfect tool - 15 Seconds ADB installer ( Yes, 15 seconds, actually less )

4) Once you make sure you have your device entry after writing " adb devices" , we gonna need to write this command to give Wakelock Detector battery history permissions: Code: adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS At this point we may see a popup dialog on our phone like this:

You need to allow it and preferably you can check always allow option.

5) That's it guys. Now we have Wakelock detector working!

Most of the important drains caused by CPU wakelocks and Kernel Wakelocks. With or without root, the things we can do to kernel wakelocks are limited, afaik. So lets come to CPU Wakelocks. What you should do is use your phone regularly a couple hours after you gave permissions to the app and run it. Then you will see which apps , and which wakelocks they have called both individually. After that you can pinpoint the issue with a google search! Hope it helps you guys. I fixed my drain, I was getting 3hours of SOT before now I have more than 4-4.5 hours through my daily usage.

Notes: Here is an awesome guide about wakelocks by T.J. Bender , you can check your wakelock there too.

Please feel free to ask any questions or unclear points. Hope your phones deeper sleeps!

There is a way to get okay-ish wakelock detection without root by using adb to grant certain permissions to the detector apps.

Some hints: https://www.xda-developers.com/stop-wakelocks-android-without-root/

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en_IN

http://techsalsa.com/detect-wakelocks-android-device-without-root/

It depends on how your use your phone and even "light to moderate usage" is meaningless because your "light to moderate usage" might be my "heavy usage". Other things like "Screen on Time" are basically bullshit measurements as well because staring at your phone screen browsing Reddit text posts on WiFi for 8 hours straight and then not touching your phone at all for another 12 hours will make it seem like the user is getting amazing battery life whereas the person who does something on their phone 1 minute, 10 times/hour for 16 hours only have 2.5-3 hours of screen on time and end up with the same amount of remaining battery life as the person with 8 hours of SoT.

The reason this is possible is the phone with 8 hours of SoT entered a deep sleep state (Doze) after it sat there untouched and it only woke itself up every once it a while for it's scheduled maintenance window where all apps updated in the background at once. On the other hand, the phone with 2.5-3 hours of screen on time never entered deep sleep (doze) as the user constantly keep waking the phone up before it could enter deep sleep; this allowed all the apps to constantly update themselves whenever they wanted to in the background.

If you look at your battery usage and "Android System" or "Android OS" are your the largest source of battery usage or even more than 15-20% of total battery usage combined something is wrong with your setup. If "Android System" is really high usage, you may have something like CarrierIQ phoning home to your carrier a lot and draining your battery; system services like CarrierIQ get lumped into "Android System" for battery usage. Ideally, "Android System/OS" should be at least no higher than 3rd or 4th biggest consumers of your battery; "Screen" should nearly always be #1 unless you are on your 2nd or 3rd day of standby time in which case "Cell Standby" should probably be #1 or possibly even "Device Idle". "Google Play Services" should also be nowhere near the top, if it is, you likely have an account syncing issue that needs to be resolved. For example, my phone has been off the charger for 7 hours and I have 1.5 hours of SoT and 80% battery: "Screen" is 5% of my usage; "Cell Standby" is 5% of my usage; "Android System" and "Android OS" are each 2% of usage; and "Chrome," "Google Play Services," and "Device Idle" are each 1% of my usage.

To figure out what is gobbling up your battery, the first thing you need to do is install Wakelock Detector Light; it doesn't require root but you will have to plug it into a PC to set it up. Wakelock Detector will show you which apps you have installed that are constantly waking the phone up to do something. It may be an app that you use a ton and you need it to constantly wake your phone to get push notifications, it could just be a really poorly coded app that you want to keep but not have it use as much battery (notorious offenders are Snapchat and Facebook), or it could be an app/service that you don't really use/care about or even definitely don't want on your phone (like CarrierIQ) and simply uninstalling it (or disabling it if it is a system app/service) will solve your problem.

The best way to disable any "System" app/service on a Samsung phone is to install AdHell3 (/r/adhell); it doesn't require root but requires about 10 minutes of setup up front (mainly signing up for a free Samsung Knox Developer account and getting a Knox API key). AdHell3 is free, open-source, and it is also a system wide adblocker if you are interested in blocking ads as well. You can use it to disable any system app or service; when I say "any" I really do mean any so make sure you don't disable a critical service your phone depends on to function properly. If you disable the wrong thing, you won't brick your phone, but you may have to do a factory reset to get it up and running again. If you Google your model # and carrier, I'm sure you will easily be able to find a list of safe apps/services you can disable.

Other tips to increase battery life (depending on how you use your phone, some of these may be more tolerable for day-to-day use):

• Turn off Always On Display that thing uses a ton of battery
  
• Set your display resolution is set to FHD+ instead of WQHD+; this won't increase your standby battery, but it will give you a little boost of SoT.
  
• Go to: "Settings > Device Maintenance > Battery > Always Sleeping Apps" and add every single app that you don't instantaneous push notifications for to the "Always Sleeping Apps" list. Samsung's version of Android will aggressively put apps on this list to sleep as soon as you are done using them so notifications from them could be delayed or stopped completely until you open the app again. This is basically a forced deep sleep (Doze) mode and it will allow apps to wake up only at scheduled intervals.
  
• Make sure your brightness is not cranked all the way up or set to auto.
  
• Turn off location services

If you really, really want maximum battery life (I wouldn't recommend for day-to-day use):

• Disable all background network data; apps won't be able to use the phone's radios for anything unless you are actively using them.
• Turn on the phone's CPU limiter; Samsung will allow you to limit the CPU max usage to 60%.

I had a few days of pretty bad battery life, and after checking AccuBattery, it turns out that my phone wasn't going into deep sleep. If you don't already have AccuBattery, I recommend downloading it and seeing if you have a similar problem.

So I restarted my phone, charged to 90%, and installed Wakelock Detector Lite using their method for installing without root.

Wakelock Detector will allow you to see if an app or service is preventing your phone from going into deep sleep when your screen is off. Here's a short guide about how to interpret readings that you get from Wakelock Detector.

Note: There are a few key things that weren't so obvious from Wakelock Detector install directions:

1. Using Windows to unlock Wakelock Detector Lite, I installed UniversalAdbDriver, not Minimal Adb.
2. Then I had to use the Start Menu shortcut "Start Adb Server" before the unlocker Chrome app recognized my phone.
3. I needed to have Wakelock Detector Lite installed and open on my phone for the unlocker to work.

The first steps are to identify the sources of drain. The best method I've found is to use a PC and follow the steps to get Wakelock Detector Lite up and running. GSAM is easier to use, and if you have any programs just BLATANTLY killing your battery (which.. you very well might with a 1% per minute of screen on time loss) it will lead you to it.

How much battery do you lose per hour while idle?

Edit: Also, it's helpful to know the health of your battery. I've only recently looked into that stuff.. I haven't tried any alternatives but AccuBattery seems to do the trick.

Search for the non root version

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

WLD non root - https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

gsam - https://play.google.com/store/apps/details?id=com.gsamlabs.bbm

Wakelock detector

Wakelock detector lite. No root needed. Useful sometimes to me for finding a rogue app.

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

give this a shot and come back to us

Install Wakelock Detector Lite onto your phone

Install the Minimal ADB Drivers onto your PC

Then read this document, on page 9 it shows you the command to enter to enable Wakelock Detector without rooting. You will then be able to see exactly what is keeping your phone awake within the OS. I've used this in conjunction with Package Disabler and I have noticed a marked improvement on battery life.

Copying my thread OP here: Hello guys! It has been a long time since I have been trying to sort out my drain issues on my S6 Edge+ , a couple of days ago I finally figured out to use Wakelock Detector without root then it comes out that it was actually the maps keeping the phone awake via "NLPWakelock" through Android OS. I will cover out the process step by step to found out which app is causing the drain and why! We will need ABD, so we must have a computer.

1)First we are gonna need the app; "Wakelock Detector [Lite]" root users may use normal version too. Play store link: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=tr

2) We should open USB Debugging option in developer settings. And connect our phone to computer via USB.

3) To check if we have adb installed, you can simply run command promt ( windows/run/cmd ) and write Code: adb devices If the output is similar to the image below, it means you have ADB installed and if you have device entry you have your ADB device drivers installed too.

If ADB is not installed, please kindly check Snoop05's thread to use his perfect tool - 15 Seconds ADB installer ( Yes, 15 seconds, actually less )

4) Once you make sure you have your device entry after writing " adb devices" , we gonna need to write this command to give Wakelock Detector battery history permissions: Code: adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS At this point we may see a popup dialog on our phone like this:

You need to allow it and preferably you can check always allow option.

5) That's it guys. Now we have Wakelock detector working!

Most of the important drains caused by CPU wakelocks and Kernel Wakelocks. With or without root, the things we can do to kernel wakelocks are limited, afaik. So lets come to CPU Wakelocks. What you should do is use your phone regularly a couple hours after you gave permissions to the app and run it. Then you will see which apps , and which wakelocks they have called both individually. After that you can pinpoint the issue with a google search! Hope it helps you guys. I fixed my drain, I was getting 3hours of SOT before now I have more than 4-4.5 hours through my daily usage.

Notes: Here is an awesome guide about wakelocks by T.J. Bender , you can check your wakelock there too.

Please feel free to ask any questions or unclear points. Hope your phones deeper sleeps!

Copying my thread OP here: Hello guys! It has been a long time since I have been trying to sort out my drain issues on my S6 Edge+ , a couple of days ago I finally figured out to use Wakelock Detector without root then it comes out that it was actually the maps keeping the phone awake via "NLPWakelock" through Android OS. I will cover out the process step by step to found out which app is causing the drain and why! We will need ABD, so we must have a computer.

1)First we are gonna need the app; "Wakelock Detector [Lite]" root users may use normal version too. Play store link: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=tr

2) We should open USB Debugging option in developer settings. And connect our phone to computer via USB.

3) To check if we have adb installed, you can simply run command promt ( windows/run/cmd ) and write Code: adb devices If the output is similar to the image below, it means you have ADB installed and if you have device entry you have your ADB device drivers installed too.

If ADB is not installed, please kindly check Snoop05's thread to use his perfect tool - 15 Seconds ADB installer ( Yes, 15 seconds, actually less )

4) Once you make sure you have your device entry after writing " adb devices" , we gonna need to write this command to give Wakelock Detector battery history permissions: Code: adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS At this point we may see a popup dialog on our phone like this:

You need to allow it and preferably you can check always allow option.

5) That's it guys. Now we have Wakelock detector working!

Most of the important drains caused by CPU wakelocks and Kernel Wakelocks. With or without root, the things we can do to kernel wakelocks are limited, afaik. So lets come to CPU Wakelocks. What you should do is use your phone regularly a couple hours after you gave permissions to the app and run it. Then you will see which apps , and which wakelocks they have called both individually. After that you can pinpoint the issue with a google search! Hope it helps you guys. I fixed my drain, I was getting 3hours of SOT before now I have more than 4-4.5 hours through my daily usage.

Notes: Here is an awesome guide about wakelocks by T.J. Bender , you can check your wakelock there too.

Please feel free to ask any questions or unclear points. Hope your phones deeper sleeps!

Probably the right answer.

If the problem persists, thy this: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

you can give adb permission to those apps you dont need root

edit: wakelock detector lite https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

I was using wakelockdetector.

Edit: I can't seem to properly use the LinkMe Bot.. https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

Do you have facebook or facebook messenger?

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

Wakelock Detector Lite.

Wakelock Detector Lite.

It looks like Wakelock Detector

I haven't rooted the phone. Is this the right app and will the lite version be (no root) be enough?

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

Also wake lock detector?

Learn how to use Wakelock Detector Lite & the ADB feature. Instructions on the playstore page: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

Learn about WakeLocks, and install WakeLock Detector

Check out the lite version, works without root. https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

You can use Wakelock Detector (no-root) to check all the wakelocks. https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=en

You can use wake lock detector lite which doesn't require root and take a look with the battery historian tool. I come back with an edit for like is to both.

Edit 1: Battery Historian: I run this on my own Linux VM and works well, PM me if you need help setting this up and bring a bug report in there

Edit 2: [Wakelock Detector Wakelock Detector [Lite]: Use the chrome extension to enable the apps needed permissions without root.

OP, you're getting a lot of useless talk about signal strength and data connection type. This is irrelevant...your issue is the massive wakelock. I have no idea why this is getting downvoted...

In your battery stats list, what is using your battery. That's a good place to start.

Also, does this persist awith a restart? And try clearing the device cache.

If none of this helps to indicate the problem, download Wakelock Detector LITE and then FOLLOW THE INSTRUCTIONS IN THE APP DESCRIPTION ON THE PLAY STORE ABOUT PAGE TO GIVE SUFFICIENT ACCESS VIA AN ADB COMMAND Enable advanced (system services) reporting in the settings.

Charge your phone to full, disconnect from the power and use it as normal. The app will begin to pull relevant wakelock info (but this takes some time of use to generate anything of importance).

Post back with screenshots of the walelocks.

But first, check the other battery stats windows for what apps are using battery and list them here, this will be the best place with the lady account of work. If it's android OS or android system, then we'll need wakelock detector info.

Also, there was a recent thread here where someone had a similar issue and found that the maps app was the cause. I'd also recommend killing all apps, rebooting, and seeing if that helps.