Sigh... Battery drain and probably wakelock issues - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

Hi,
I have an unrooted Note 4 that is updated to the latest marshmallow. Lately I have been having battery drain issues. I have GSam Battery Monitor to see if I could figure out what was going on. The only thing that it is telling me is that my phone is pretty much staying awake all the time. Unfortunately I cannot tell much more than that.
My question - is there any way at all for me to figure out the culprit? I looked online for a while and saw references to using Wakelock Detector on unrooted phones with a couple of ADB commands, but that doesn't seem to be an option with Marshmallow.
So, short of rooting, is there any way for me to figure out my battery issues and what's keeping it awake?

Ha! I'll answer my own question. It turns out that you can do this with GSam Battery monitor and a few ADB commands. I updated the app to the latest and went through the settings and it had a little tutorial built in. It took me just a couple of minutes and now I can view wakelocks, both app and kernel, in the app.
If only I could do this with wakelock detector. Still, I'm happy with GSam Battery Monitor.
I'm assuming that I'll have to redo this after every reboot, but that's cool

usmaak said:
Ha! I'll answer my own question. It turns out that you can do this with GSam Battery monitor and a few ADB commands. I updated the app to the latest and went through the settings and it had a little tutorial built in. It took me just a couple of minutes and now I can view wakelocks, both app and kernel, in the app.
If only I could do this with wakelock detector. Still, I'm happy with GSam Battery Monitor.
I'm assuming that I'll have to redo this after every reboot, but that's cool
Click to expand...
Click to collapse
did you calibrate your battery since your last update? is that when issue began ?im not on stock, but ive had major battery issues in the past. the issue was caused from flash . the solution ended up being charging phone to full then calibrating battery via an app i used root essentials but not applicable in your case

Related

[Q] something is draining my battery - how can i tell what it is?

So i rooted my evo and installed a custom rom pretty much as soon as I had it out of the box. And then started installing apps. And i've pretty much NEVER had a fully charged battery last for a whole day even with very little to no usage of the phone.
A few days ago my friend also got an evo but hasn't rooted it or installed any apps yet. And he is easily getting TWO days or more out of a charge.
so i decided to do a full wipe of my phone, and what do you know, I'm suddenly getting 2 days out of the battery, maybe even a little more then 2 days.
Previously, i had setcpu installed as well as system panel. And i was never able to figure out what was draining the battery. When i looked in system panel the only thing that was using the cpu a little bit was system. Pretty much every other app listed was showing 0.1% of cpu usage.
So i'd like to know if there's a better method to figure out what's draining the battery. Do I have to install apps one at a time and wait a few hours/a day to see if the battery starts going down? or is there a better method?
thanks
I always check the awake time versus the time on. If the wake time is very high that means there is an app acting up.
What I'll do to investigate which app is I'll just go to the little stock battery report thing and look at what is using my battery.
Also, it should be noted that be wary of the facebook app. That thing is a complete and total battery hog. It was draining my battery from 20% over the course of an hour.
I was checking the stock battery report - it wasn't showing me anything useful when the battery was going dead.
right now i'm getting amazing battery life compared to before.
90 minutes since the phone was unplugged and it's only down to 96% and that's with me using it a bit. Previously, it would have been down to 85-80% by now.
I just have no clue at all what was causing the drain. I was hoping there was a better method other then installing apps one at a time until the battery starts draining to figure out the culprit.
There's an app called Watchdog and it monitors the background activity happening on your phone. If some seems to be getting out of hand it will notify you.
I had the same problem I installed Smobile security and it was KILLING my battery. Watchdog was able to tell what it was.
Hope this helps.
It looks like watchdog does basically the same thing that system panel does. and system panel wasn't showing me anything unusual. System panel shows the cpu usage of apps - and none of my apps were showing high cpu usage.
I guess there's really no app that can actually show you the battery usage per app - it can only show you the cpu usage.
You can try SpareParts from the Market,it may help you see if you have a wakelock issue of some kind and its free so no harm if it doesn't help.
BrianBusby2038 said:
You can try SpareParts from the Market,it may help you see if you have a wakelock issue of some kind and its free so no harm if it doesn't help.
Click to expand...
Click to collapse
actually, the rom i am using already has spareparts in it. I'm not sure what you mean by wakelock though. How do i determine that? What is it?

[Q] Titanium Backup Causing Partial Wakelocks?

I am on stock AT&T 4.0.4, and just rooted a few days ago so I could take a backup with Titanium Backup. This morning I went for a 2 hr bike ride using Strava as my GPS app (it only used 2%). In the several hours before and after the ride, I see that Titanium Backup has a 4.27 hr partial wakelock having taken 35% of my battery life.
I'm new to Titanium Backup, and backed all of my apps and settings up yesterday. I have no automated backups scheduled at all. It shouldn't even have been running, I have no "frozen" apps set or anything. Why would it be causing these partial wakelocks? Is there anything I can do without having to uninstall the app? I am using the latest free version from the Google Play Store.
I get fairly good battery life on my GS3, considering that on the weekends I run or ride for several hours at a time, sometimes streaming music the entire time (and GPS always on). This is the first time I've had a "rogue" process really chew up the battery. I'd hate to have to uninstall Titanium Backup because it eats my battery with partial wakelocks.
Thanks in advance for the help
While i have never seen Titanium backup do this, and cant offer much help as to fix this, but a process running in the background, using up battery is not a wake lock.
TRusselo said:
While i have never seen Titanium backup do this, and cant offer much help as to fix this, but a process running in the background, using up battery is not a wake lock.
Click to expand...
Click to collapse
Thanks for the response. So in Better Battery Saver (attached screenshot), when I am looking at "Partial Wakelocks" under "Since Unplugged" and the top item is com.keramidas.TitaniumBackup.service.WorkerService -- that's not a wakelock? Am I to assume that's what's eating the battery though? Sorry, I'm new to the Android planet.
tekchic said:
Thanks for the response. So in Better Battery Saver (attached screenshot), when I am looking at "Partial Wakelocks" under "Since Unplugged" and the top item is com.keramidas.TitaniumBackup.service.WorkerService -- that's not a wakelock? Am I to assume that's what's eating the battery though? Sorry, I'm new to the Android planet.
Click to expand...
Click to collapse
Even if it's not actively doing anything, keeping the phone from going to deep sleep would be a big drain on the battery. I would say that's definitely the cause of your issue.

[Q] Help debugging excessive battery drain

Ok, so I've been dealing with this issue for a few months now, seems software related because it will go away when I flash a new rom, but then come back eventually.
I use Battery Monitor Widget to see my current charge/drain status in mA (only widget I've seen that does so), and even plugged in, the battery is draining (USB or AC). Looking at my battery usage this morning it was something like 5.5 hours on battery, with 70% coming from screen, which had only an on time of 50min. I had it plugged into USB (no AC adapter here at work) and was watching the battery drain a percent every 30-40sec, with a usage of -900mA. I can't for the life of me fathom what could be drawing an amp on a phone that's just been sitting doing nothing all day.
I don't understand the wakelocks, partial wakelocks, alarms, etc that most of the battery threads are talking about - I know I need to install Better Battery Stats to get at them. But how do I track what's using all this juice?
Thanks!
What ROM are you on currently?
Sent from my SPH-D710 using XDA Premium 4 mobile app
Currently running Touched by S4 2.1. Same issue on Blue Kuban, PA, PACman, and a couple others. Again, starts days or weeks after. Today, even after a restart, it kept draining, even on the USB charger. But I turned it off, let it charge to about half while off, turned it on, and it continued to charge. Its haunted I tell ya.
cmags said:
I don't understand the wakelocks, partial wakelocks, alarms, etc that most of the battery threads are talking about - I know I need to install Better Battery Stats to get at them. But how do I track what's using all this juice?
Thanks!
Click to expand...
Click to collapse
I would install Better Battery Stats fully charge your phone and then check the app when the battery is low. You can check all the options. Other, Kernel Wakelock, Partial, Alarms, What you should see is a time of how long each app/process has had a wakelock. For alarms it will show you how long each app has woken up the phone. You want to look at the items that show the most time usage and most wakeups. If the name is not recognizable you should Google it. Sometimes it could be messaging or social apps keeping your phone awake or anything else. If you need help you can post screenshots of your results.
The app has little question marks you can click on to get explanations for some things. Partial wakelocks is the first place to look, imo.

Battery Drain

Ever since I updated to 8.1.0 with December security patch, I've noticed my battery draining faster than normal. I was getting 4-5 hours of SOT with around 45-50% battery left. This was after being off the charger for 12-16 hours. Now I'm getting about half the SOT at similar numbers. Anyone have any ideas?
Sent from my Nexus 6 using Tapatalk
andrewjt19 said:
Ever since I updated to 8.1.0 with December security patch, I've noticed my battery draining faster than normal. I was getting 4-5 hours of SOT with around 45-50% battery left. This was after being off the charger for 12-16 hours. Now I'm getting about half the SOT at similar numbers. Anyone have any ideas?
Click to expand...
Click to collapse
Excuse my stating the obvious, but you need to find what process or app is using the battery. You should be able to get a rough idea just using the new features under Settings>>Battery. It will identify which apps are using the most juice. Run the phone in Safe Mode to see if your battery life goes back to normal. It could also be a service like Google Play Service which sometimes wigs out and starts chewing battery. Are you rooted? If you need more detailed information there are battery drain apps available to help isolate the problem (BBS and GSam). These apps require root to give the best results.
v12xke said:
Excuse my stating the obvious, but you need to find what process or app is using the battery. You should be able to get a rough idea just using the new features under Settings>>Battery. It will identify which apps are using the most juice. Run the phone in Safe Mode to see if your battery life goes back to normal. It could also be a service like Google Play Service which sometimes wigs out and starts chewing battery. Are you rooted? If you need more detailed information there are battery drain apps available to help isolate the problem (BBS and GSam). These apps require root to give the best results.
Click to expand...
Click to collapse
Not rooted and currently locked. I've downloaded GSAM and have adb permissions and it simply says things like Chrome, RCS Phone and Play services. If you see from the photos below you can see what I'm talking about. Chrome currently isn't that bad, but yesterday and the past couple days it's been like 9% or more of the battery.
https://photos.app.goo.gl/hFvQKO7q3pZTHFNb2
Sorry the screenshots were too large for uploading.
Sent from my Nexus 6 using Tapatalk
andrewjt19 said:
Not rooted and currently locked. I've downloaded GSAM and have adb permissions and it simply says things like Chrome, RCS Phone and Play services. If you see from the photos below you can see what I'm talking about. Chrome currently isn't that bad, but yesterday and the past couple days it's been like 9% or more of the battery.
Click to expand...
Click to collapse
Two things: I've never seen phone or kernel use that much battery. On one page phone usage is 33 seconds, yet it used 9% ? I think RCS is running the background all the time. See if you can toggle it to not run in the background under Settings>>Apps>. High kernel I'm guessing is a kernel wakelock or multiple. You've probably loaded app(s) that are creating the problem, but you need to find out which one is causing the wakelocks. There is a wakelock detector "lite" app that doesn't need root but I don't know how well it works. I know the root version works well. Lastly, on the first screenshot with the battery, scroll to the bottom of the page and see which apps are listed there. I'd be willing to bet if you ran the phone in Safe Mode, your battery drain would disappear, meaning your user apps are causing it.
v12xke said:
Two things: I've never seen phone or kernel use that much battery. On one page phone usage is 33 seconds, yet it used 9% ? I think RCS is running the background all the time. See if you can toggle it to not run in the background under Settings>>Apps>. High kernel I'm guessing is a kernel wakelock or multiple. You've probably loaded app(s) that are creating the problem, but you need to find out which one is causing the wakelocks. There is a wakelock detector "lite" app that doesn't need root but I don't know how well it works. I know the root version works well. Lastly, on the first screenshot with the battery, scroll to the bottom of the page and see which apps are listed there. I'd be willing to bet if you ran the phone in Safe Mode, your battery drain would disappear, meaning your user apps are causing it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/4v8seKwMJnceaVUG3
Well in safe mode my drain is gone so I'm not sure which app is doing it, but to directly answer your question about the RCS it is an overall app meaning it is related to several Google play services. I'll upload a photo of it. I have to reboot into normal mode.
Edit: I'm wrong about that it was the play services.. I'll have to start uninstalling the apps to determine which one is draining the battery I guess.
andrewjt19 said:
https://photos.app.goo.gl/4v8seKwMJnceaVUG3
Well in safe mode my drain is gone so I'm not sure which app is doing it, but to directly answer your question about the RCS it is an overall app meaning it is related to several Google play services. I'll upload a photo of it. I have to reboot into normal mode.
Edit: I'm wrong about that it was the play services.. I'll have to start uninstalling the apps to determine which one is draining the battery I guess.
Click to expand...
Click to collapse
RCS can be a real battery hog, but I don't know why. I don't have RCS on AT&T. Do you use Messages as your primary SMS? Open Settings>>Advanced and see if you can toggle off "Enhanced Features". Open properties and check if it is using battery optimization. If it is not, set Messages to battery optimization. You can always turn these back on later if the battery drain remains.
My battery life has been restored to pretty much the same as it was with 8.0. I also noticed poor battery life after installing the 8.1 update, even though they changed the way battery life is estimated with this update (supposedly). Something just felt off, but now everything feels great! I am fairly certain what changed is installing the Greenify Magisk module and/or the Google play services doze module (this enables battery optimization on the Google play services app). Not sure which one really made the difference because I installed them at the same time. However, there is definitely a major difference!!
js042507 said:
My battery life has been restored to pretty much the same as it was with 8.0. I also noticed poor battery life after installing the 8.1 update, even though they changed the way battery life is estimated with this update (supposedly). Something just felt off, but now everything feels great! I am fairly certain what changed is installing the Greenify Magisk module and/or the Google play services doze module (this enables battery optimization on the Google play services app). Not sure which one really made the difference because I installed them at the same time. However, there is definitely a major difference!!
Click to expand...
Click to collapse
Here's proof!!
js042507 said:
Here's proof!!
Click to expand...
Click to collapse
In my experience that's really good.
Before 8.1 I noticed about 11% per hour during screen on use and about 0.33% per hour while on stand by in my pocket or a little bit better if it's just sitting on my night stand not moving while I'm sleeping (I think doze is more extreme in that situation) which seems to match what you are getting. Based on that screen shot I think that's like 8 hours screen on time over like 35 hours for a full charge. I've done a little bit better but not much. That's excellent battery life.
Since 8.1 it has dropped. Best now is maybe 7 to MAYBE 7.5 hours over maybe 26-28 hours. In my experience battery life always drops after an update but this case is far from the worst. I remember when my Nexus 5 updated from KitKat to Lollipop. The battery drop was awful and to make matters worse the battery life of the Nexus 5 was pretty bad to begin with.
js042507 said:
Here's proof!!
Click to expand...
Click to collapse
Which font is that?
MarwanTamer said:
Which font is that?
Click to expand...
Click to collapse
Default. I didn't change the system font.
js042507 said:
Here's proof!!
Click to expand...
Click to collapse
What are your settings for Greenify
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
What are your settings for Greenify
Click to expand...
Click to collapse
Here...
So in my last reply I thought I was wrong about RCS Phone app being a conglomerate of several apps in the phone. For some reason I couldn't find the information I needed at that time. I wiped my phone and started over after posting this thread. I was trying to isolate the misbehaving app. I thought it might have been greenify actually, but no the drain has returned to a lesser extent though. Here's some photos of this RCS app from GSAM.
https://photos.app.goo.gl/rvw077mBfNULbsRE3
I'm not sure what is causing the drain at this point. I've installed Better Battery Stats to locate the wakelocks so I can ignore them through ADB.
Sent from my Nexus 6 using Tapatalk
andrewjt19 said:
So in my last reply I thought I was wrong about RCS Phone app being a conglomerate of several apps in the phone. For some reason I couldn't find the information I needed at that time. I wiped my phone and started over after posting this thread. I was trying to isolate the misbehaving app. I thought it might have been greenify actually, but no the drain has returned to a lesser extent though. Here's some photos of this RCS app from GSAM.
Click to expand...
Click to collapse
Have you tried disabling RCS ? (Post #6). BBS is good for idle drain, active drain not so much. It's best run overnight without touching the phone for 8 hours or so. Pick the phone up in the morning and create/save a log file as quickly as possible. Post the log to the BBS thread if you need help deciphering.
v12xke said:
Have you tried disabling RCS ? (Post #6). BBS is good for idle drain, active drain not so much. It's best run overnight without touching the phone for 8 hours or so. Pick the phone up in the morning and create/save a log file as quickly as possible. Post the log to the BBS thread if you need help deciphering.
Click to expand...
Click to collapse
I cannot disable it since it is comprised of multiple apps. You can see it in the pics on my last post.
Sent from my Nexus 6 using Tapatalk

Question GSAM Battery Monitor - How to find wakelocks? What is preventing me from deep sleep?

Hello everyone,
initially I had great battery life on my P6P. I then later started to root, add a 2nd SIM card and installed more and more apps (the same ones I already had on my P4 XL).
I can't really say when deep sleep stopped working, but it does not work at the moment.
I am at the stock ROM and Kernel atm, but rooted.
Usually I would start BBS and figure out which wakelock is preventing me from going to deep sleep.
However, BBS doesn't seem to work on Android 12. So I tries GSAM Battery Monitor.
Attached are screenshots from 2 days with GSM Battery Monitor.
It can be seen that the device does not go to deep sleep at all.
The only way to get it into deep sleep atm, is to enable battery saver.
This causes a huge battery drain over a whole day.
This post will contain the screenshots from day #1.
The next post will contain the screenshots from day #2.
Can anyone tell me how to figure out which wakelock / which app / feature / whatever is preventing my phone from going into deep sleep?
Thanks in advance!
And this is day #2 with more detailed screenshots.
@Lughnasadh @RetroTech07 Maybe you can help me here? :S
Thanks!
I also just "Force stopped" pretty much everything under Settings -> All apps (user apps and the few system/google apps that are in the user apps list).
Still no deep sleep
Utini said:
Still no deep sleep
Click to expand...
Click to collapse
BBS works.. sometimes. You need to stick with it and get the alarms tab to show stats. That should tell you what is keeping it awake. Kernel wakelocks are useless imo. Partial wakelocks and alarms and even network usage perhaps. I have it working but it's sketchy.
Finding a needle in a haystack.
Factory reset and don't restore backup.
bobby janow said:
BBS works.. sometimes. You need to stick with it and get the alarms tab to show stats. That should tell you what is keeping it awake. Kernel wakelocks are useless imo. Partial wakelocks and alarms and even network usage perhaps. I have it working but it's sketchy.
Click to expand...
Click to collapse
So you basically install it, grant it root, and then wait until somehow magically starts to show stats?
therock3181 said:
Finding a needle in a haystack.
Factory reset and don't restore backup.
Click to expand...
Click to collapse
Ye well there must be a way to troubleshoot this.
Can't just always factory reset because something gets bugged?
Utini said:
So you basically install it, grant it root, and then wait until somehow magically starts to show stats?
Click to expand...
Click to collapse
Haha, no I don't have root. I just grant the permissions via adb. But "magically" is the key word actually. Here are a few screenshots from just now. The first 2 are pretty usual for a few of the stats but that changes. The second 2 are what I can sometimes get although that varies as well. Every other stat on the app is like the first two, not stats collected. That's what I mean by you have to stick with it. It will magically show randomly. lol Unfortunately, this round didn't show partial wakelocks which means a bunch to me. Tomorrow morning it will show.
Thanks.. I just flashed kirisakura kernel from @Freak07 since I believe that it also block some wakelocks which are enabled on stock kernel. Will try that tomorrow together with AccuBattery.
If that doesn't work, then I will try to get magic by BBS.
Utini said:
Thanks.. I just flashed kirisakura kernel from @Freak07 since I believe that it also block some wakelocks which are enabled on stock kernel. Will try that tomorrow together with AccuBattery.
If that doesn't work, then I will try to get magic by BBS.
Click to expand...
Click to collapse
If your issue is caused by an app or service (which it sounds like it probably is) constantly running in the background flashing the kernel won't help at all.
Your best bet might be BBS, battery historian (you can take a bug report and then view it there, just google it) or maybe top command.
Freak07 said:
If your issue is caused by an app or service (which it sounds like it probably is) constantly running in the background flashing the kernel won't help at all.
Your best bet might be BBS, battery historian (you can take a bug report and then view it there, just google it) or maybe top command.
Click to expand...
Click to collapse
Well, for now it seems like your kernel fixed the issue though.
I am on 70% deep sleep while screen is off according to accubattery. So I will monitor this through the rest of this day and report back.
Utini said:
Well, for now it seems like your kernel fixed the issue though.
I am on 70% deep sleep while screen is off according to accubattery. So I will monitor this through the rest of this day and report back.
Click to expand...
Click to collapse
Flashing a kernel can't fix issues with apps or services getting stuck in the background.
I guess it was the reboot that helped in the end or whatever was stuck got updated or unstuck some other way.
Freak07 said:
Flashing a kernel can't fix issues with apps or services getting stuck in the background.
I guess it was the reboot that helped in the end or whatever was stuck got updated or unstuck some other way.
Click to expand...
Click to collapse
Hmm really weird. My deep sleep is now also slowly dropping (only at 50% now).
But will see how it ends up after a working day.
I did try reboots before already. It didn't help.
But maybe so far I was working with a mix of several wakelocks which I can now narrow down.
Will try battery historian as recommend by you. Just need to find a decent guide for it first
Utini said:
Hmm really weird. My deep sleep is now also slowly dropping (only at 50% now).
But will see how it ends up after a working day.
I did try reboots before already. It didn't help.
But maybe so far I was working with a mix of several wakelocks which I can now narrow down.
Will try battery historian as recommend by you. Just need to find a decent guide for it first
Click to expand...
Click to collapse
Install better battery stats ( only kernel wakelocks tab is not working)...to check wakelocks and alarms
whats the differencd between doze and deep sleep? and is there a way in accubattery to find out, if the device is sleeping?
cultofluna said:
Install better battery stats ( only kernel wakelocks tab is not working)...to check wakelocks and alarms
Click to expand...
Click to collapse
It didn't work for me at all and I just installed it and it still isn't working for me at all.
It has root and according to the permissions tab in the app everything seems to be granted.
I downloaded the RC 2.6-382 from here: https://install.appcenter.ms/users/...stats-xda-edition/distribution_groups/testers
I will let it run for a few hours and check again.
Edit: Oh I just noticed under the permissions tab:
STATUS: Failed: Transaction failed on small parcel; remote process probably died
Any ideas?
xflowy said:
whats the differencd between doze and deep sleep? and is there a way in accubattery to find out, if the device is sleeping?
Click to expand...
Click to collapse
In Accubattery under "discharging" check for "deep sleep while screen off".
Utini said:
In Accubattery under "discharging" check for "deep sleep while screen off".
Click to expand...
Click to collapse
just found it. is 37% of it, good?
Utini said:
It didn't work for me at all and I just installed it and it still isn't working for me at all.
It has root and according to the permissions tab in the app everything seems to be granted.
I downloaded the RC 2.6-382 from here: https://install.appcenter.ms/users/...stats-xda-edition/distribution_groups/testers
I will let it run for a few hours and check again.
Edit: Oh I just noticed under the permissions tab:
STATUS: Failed: Transaction failed on small parcel; remote process probably died
Any ideas?
Click to expand...
Click to collapse
Working for me properly... besides kernel wakelocks

Categories

Resources