After charging phone always keeps awake

After charging phone always keeps awake. Does anyone have the same problem. Phone in stock rom, not rooted.
If I reboot phone everything becomes in normal. Phone starts going in to sleeping state.

Attached Thumbnails

 

[Guide] How to fix Android OS battery drain (stay awake) without root!

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/d...r.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 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!

Screen won't stay awake when charging

I have enabled Developer Options. When I tell the screen to stay awake when charging it technically stays awake, but it dims down considerably. I am looking for a way to keep the screen on at it's set brightness while charging. I'd prefer not to use an app for this purpose if it is possible to do this within the phone settings. Am I missing something?

i9500 Always Awake when Charging

I'm having some issues with my phone being awake when it is charging. I've checked the most obvious causes such as daydream, and the keep awake setting, but neither were active.

I'm not sure what actually keeps it awake as battery stats end up being erased at 100%. I have Wakelock Detector installed but that doesn't give me any conclusive evidence either since again, the stats are gone once the phone is fully charged. This is mostly an inconvenience as after disconnecting the charger, the battery use is about normal and I can control the wakelocks through Greenify, Amplify and the Privacy Guard's keep awake function.

Has anyone else experienced/solved this issue before and what did you do?

My current setup is:
Android 6.0.1
Resurrection Remix ROM
Nevermore Kernel

I have noticed that most ROMs above 4.4 seem to have an adverse effect on battery life on my S4 and my Galaxy Tab 2. 6.0 seems to be giving me the same standby time of 4.4 however on my tab, so I was hoping that it'd do the same for my S4 as I want to move away from using the Davlik runtime.

Are there any alternative ways of finding out what is keeping my phone awake without

*without rooting ( don't know how to edit incorrect title)

The title pretty much says it all but this is why I was asking 👇

XT1064 Android 6.0 will not go into deep sleep, CPU stuck awake

I have a Moto G 2014 (XT1064) running Android 6.0 that will not go into deep sleep. I could see that the CPU was never going into the deep sleep state even when the phone was not being used and no user apps were actively running in the background. This is causing abysmal battery life as expected. The phone was updated to Android 6.0 via regular OTA updates. I haven't flashed any third party ROMs onto it at all since I bought it.

The first thing I did to investigate was to unlock the bootloader (it was still locked since purchase prior to this) so that I could obtain root access to see what was going on. This also had the additional affect of wiping the phone to stock Andoird 6.0, which I had hoped would maybe solve the problem but it did not.

My first thought was that it was a user app that was holding a wakelock keeping the phone awake. I looked at the user and kernel wakelock counts via BetterBatteryStats and WakeLockDetector, but from what I can tell it is not any user app that is holding a wakelock at all. Instead it must be some kernel level app keeping the CPU awake, but I can't determine what it is. There isn't any single entry in the wakelock list that sticks out as the culprit.

I have done some other investigative tests such as turning WiFi off while the phone sits unused overnight. This did not have any effect as the phone still remained awake the whole time. I also repeated this test with the phone in airplane mode (WiFi + cellular radios off) and again it had no affect. From this I could only conclude that it was not the wireless radios that were keeping the phone awake. The wakelock counts also didn't show any evidence that WiFi, cellular or GPS were holding wakelocks.

Here are two screenshots I took of the BetterBatteryStats and WakeLockDetector apps showing the highest count kernel wakelocks over a roughly 17 hour period:
(I'd link them in properly but I am prevented from posting outside links on this forum until I have 10 cumulative posts...)
i.imgur.com/nPAY3S6.png
i.imgur.com/5VfgFv1.png

You can see that the phone has been awake 96% of the time during this period, and that the highest count kernel wakelocks are from "event8-1877", "event9-1877", "qpnp_soc_wake" and "qpnp-vadc-e4a28400". I could not find any information as to what these entries mean or what they're related to. Whatever they are, they appear to have abnormally large wakelock counts which leads me to believe that they are related to this problem. The other thing that puzzles me is that the total time for the top four entries in that list only sum to about 2 hours, yet the phone has been awake for almost 17 hours within the same period.

If anyone has any idea about this I'd appreciate the help. I may be completely wrong about the root cause here but I'm running out of ways to debug this.