Develop Bugs

Constantly awake

Hi guys,
My phone is constantly "awake" despite rarely even turning on the screen.
Would you know what could be causing this?
I'm currently running Caulkins rom and whatever kernel it came with.
My battery life is ~15 hours so I dont think it's affecting my battery too much.
Either way, is there an app that can tell me whats causing the drain?

First of all, to see if your CPU is sleeping properly when the screen is off, download CPU spy… it is an app that gives you total time the CPU has spent in each scaling frequency available.
Then download watchdog, this app tells you which programs are polling the CPU for usage.
Then download “better battery stats”.. this app tells you if there are wakelocks.
With those 3 apps running at the same time, you will find out any abnormalities in your system caused by applications.
Side note – disregard info that either of the apps report about each other (obviously)

Doze hasn't worked since 6.0.1 OTA - anyone else?

Since getting the OTA, Doze hasn't worked at all. I haven't installed any new apps, and am stock/unrooted. Here's the battery graph from last night with the phone sitting on the nightstand.
Any ideas?

Same here. So you had a flat line before the update?

Yep, flat line before the update. Here's the detailed battery view (4% after my first screenshot, but serves the same purpose). Looks like something is keeping the phone awake but nothing else changed outside of updating the OS.
I restarted and that didn't help. Maybe it has to re-optimize.

Doze appears to be working on mine but I've only had it for a day and am using it a lot. When not in use for an extended period of time the battery graph completely levels out and doesn't decrease at all. Then again I think I've only gone about 20 minutes without touching it since I took it off of the charger this morning.

Check your Developer Options > Running Services for any suspicious activity.
I had Google Maps "offline Maps service" hammering my device during sleep the other day even though I've never saved an offline map yet.

See attachment for Doze. It works better on my 5x than 6p. I'm not sure why. Total flatline.

Looks solid to me

Hi,
You can see if Doze is active if you have any app that records data periodically. Leave it running over night and you should be able to see a reduction in samples in the early morning. For example, when logging current usage with "Current Widget", when Doze kicks in the sampling slows way down. If I leave it on overnight set to take a sample about once a minute by the time I wake it is 2 to 3 hours between samples. I've had higher current drain when I though Doze wasn't working, but upon looking at the Current Widget log file, I could see that Doze was active.
Frank

mtca said:
Hi,
You can see if Doze is active if you have any app that records data periodically. Leave it running over night and you should be able to see a reduction in samples in the early morning. For example, when logging current usage with "Current Widget", when Doze kicks in the sampling slows way down. If I leave it on overnight set to take a sample about once a minute by the time I wake it is 2 to 3 hours between samples. I've had higher current drain when I though Doze wasn't working, but upon looking at the Current Widget log file, I could see that Doze was active.
Frank
Click to expand...
Click to collapse
Wait, Current Widget actually works properly with you with the 5x? It rarely updates for me. All software current monitoring tools seem to do so.
I figured it must be something with how the power regulation works on this device.
With my Nexus 5 it would update exactly as intended and could be plotted on the graph, until the phone entered deep sleep then the updates became infrequent. This was on Lollipop before Doze existed, so that tells me that it is because of Deep Sleep not Doze.

bblzd said:
Check your Developer Options > Running Services for any suspicious activity.
I had Google Maps "offline Maps service" hammering my device during sleep the other day even though I've never saved an offline map yet.
Click to expand...
Click to collapse
You may have solved my problem. Using Wakelock Detector, I saw that Google Maps was slamming my phone too keeping from dozing. I deleted my offline maps and disabled the option. Hopefully that fixes it for me

Chroma + ElementalNX + Open Gapps: 1.3-1.5% battery drain screen off. Help,wakelocks!

Background:
5X 16GB
Chroma 12/10/2015 release
ElementalX 1.04 (DT2W disabled. Sweep2Wake enabled)
Open Gapps Mini ARM64: Google Now Launcher installed but disabled. Ok Google disabled, GPS disabled. 2G (Data off)
Interactive governor tweaks applied as explained in this widely famous thread by soniCron
I am witnessing 1.3-1.5% drop per hour when the phone is in deep sleep (!). Have a look at the screenshots attached, especially the one with graph. That screen off time is 1.5 hours when I was asleep.
Phone configs: WiFi on throughout. Maps + Google Now Launcer force stopped. Chrome, AdAway, Telegram, ES Explorer added in Greenify. Whatsapp was the only app running in background. No Hangouts, Facebook, Kik, Pushbullet or other memory intensive apps.
After tweaking the governor as per thread above, my CPU clock speeds are working awesome, mostly 384Mhz. Touchboost disabled via /sys/mns_performance/modules/parameters/touchboost. It's only the wakelocks which needs to be fixed now otherwise everything is near perfection.
My questions:
In the 3rd image, you'll notice the screen was off for a long time and then turned on once in between. However, I didn't do it because I was asleep. I have Ambient display and wake on notifications disabled, there was no missed call so why did it turn on the screen? I have noticed this other times happening in front of me. The phone will suddenly wake up and sleep immediately within half a second ever since I came to ElementalX.
In the same image you see so many wakelocks while the screen is off. Have a look at the other images to see what's causing this. I believe it's mostly point number 3 (below)
PowerManagerService.Wakelock taking up 51%! while qpnp-smbcharger and qpnp_memaccess take around 30%.
I read PMS.Wakelock is cumulative of Partial wakelocks, I have attached it's screen shot as well but the graphs there are 0%. Am I reading something wrong?
I am not particularly familiar with BetterBatteryStats and dealing with wakelocks in general so looking for some pointers here. Thanks for your help!

You have sweep2wake enabled. It drains 1.3 to 1.5% per hour on idle. The screen flashing on and off is a timeout to disable sweep2wake. After that, idle drain returns to normal.

LineageOS: Battery drain with active Google location history

Hello,
I have installed the latest version of LineageOS and Open GApps on my LG G3s. (jagnm)
But now I have a battery issue. In the battery statistics the first entry is IDLE, with round abound 20% in 24 hours.
After some testing and checking i found the problem. The processor is always in the 300 MHz mode and not in deep sleep mode, when the screen is off. (Checked with the app CPU Spy)
I think the source of the problem is the Google location history. When i disable this function, the processor uses the deep sleep mode when the screen is off.
Does anyone else have this problem, or does someone know how to fix this?

I have a somewhat similar issue with my Mi 4W (cancro), after flashing the recent Lineage OS build battery drains to 0% overnight, guess someone resolve this issue in the upcoming builds

from cm to lineage i look my stats are too bad :/ device jagnm and i say this. only 16-23hr 1 day. on old cm 2-3 day internet 3g network.
really too many options lose on new nugart but get fm working i try the cpu spy app and post the results
ok Thanks boy if google localitation services on = no deep Sleep on Jagnm device

Possible issue with Deep Sleep on 8.1?

So - I'm not sure if I have a problem or not yet, but I thought I'd see if others have noticed anything strange. I just happened to open CPU Spy and noticed my Pixel XL (unlocked, rooted with MAGISK v 16, stock) had a very low 7% deep sleep after about 4 hours off the charger. The lowest 307 mHz CPU level had about 45% and the remainder was sprinkled throughout the various ranges with another 20% or so at the highest speed. This seemed strange to me as whenever I have checked on this in the past, Deep Sleep was always a large portion of the total CPU time...I can't say for certain if I have checked this on 8.1 or not until now. A quick Google search yielded some reddit and XDA threads specific to Deep Sleep issues on the Essential device and they seem to have concluded the issue lies within their stock kernel on 8.1. (Some resolved by switching to the Elemental X kernel based on 8.0 base). Anyways, I have tweaked my app "Background Check" settings to turn off for most non-essential apps and am preparing to more fully test this. But wanted to see if anyone else was having similar issues on their OG Pixel XL. I should also note that I am running the MAGISK module that allows you to "Optimize Battery use" for Google Play Services. And it appears to be working as Google Play Services is no longer a top culprit within WakeLock Detector. When this did not yield improved battery performance, that is what started me digging into this further.
Thanks,
S