[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
No problem that is what this forum is for, discussions and helping one-another 🙂

So from what I can tell, it don't look too bad. I can only "guesstimate" what is good or bad from the "Screen off" time and % used. As screen on % is highly dependent on actual app usage, screen brightness enabled connectivity features (BT, WiFi, etc.) etc..

But looking at the numbers:

- it says you had the test done within 13h 25m

- out of 13h 25m the screen was off for 9h 53m

- out of 9h 53m it was in deep sleep for 8h 19m

- out of 9h 53m it was awake for 1h 33m

- it says it used 3.1%/hr while in deep sleep with screen off

- it says it used 5.8%/hr while awake but screen off

- it says it used 3.5%/hr with awake/deep sleep while screen was off

The 9% "awake" number is kind of high I'm thinking. Though maybe not too bad...it says only 366 mAh was used - which isn't bad IDT. Problem is this is dependent on if you were turning the screen on to do something before or after the phone went into "deep sleep" for the 8h 19m.

See doze won't kick in for probably 15 minutes I think (if it is working correctly and not having wakelocks). So if the screen is off for a few minutes then turned back on then off then back on, like that all day it will never go into deep sleep. So it's slightly hard to tell what the "awake" could be from.

As for "rouge" apps, nothing really looks out of the ordinary. I assume you were using maps, messenger, spotify & facebook throughout this test? If so then yea, nothing really looks bad, like it drained a bunch of battery.

The 3.5%/hr was a combined deep sleep and awake while screen was off, 3.1% was just deep sleep. But TBH, I think 3.1%/hr is high. While in deep sleep it should be closer to 1.5% maybe 2%/hr tops.

Though some of the deep sleep % is also dependent on enabled connectivity as well - like WiFi constantly trying to connect to a bad signal, BT, NFC... there is a feature in the DevTools called "WiFi Scan Throttling" which will help reduce the amount of times the WiFi is looking for a network (while WiFi is enabled) and I believe reduce how much it scans while connected to a poor signal (looking for a better signal). Enabling that may help. Also the "Mobile data always active" you could turn off (if it's on). It will be slower to connect back to your cell network when leaving the WiFi connection but this way while connected to a WiFi network the cell/modem won't be in use. This will help with power drain.

Another way to see what is going on is to wait like an hour of not using the phone and check adb logcat (already have logcat running). If you see a constant same lines spamming the log, it could be something that you understand and might be able to resolve (maybe it IS some app doing something). If the log is slow, not doing much, then that is weird. I feel like something is going on there to have it at 3.1%/hr while in "deep sleep". With some more changes/research that should be able to come down some.

I still think the best test you could do is to do this while overnight, like don't use the phone from 10PM to 7AM then at 7AM take the screenshot and check the numbers. This way, the stats will be clearer and there won't be "daily use" skewing the numbers. If you get something like 1.5% overnight, then something during the day is causing background drain and most likely adb logcat will be your best help in pinpointing what is really going on while it is sleeping.

Yikes...these long posts lol. But hopefully this was thorough enough to help...

Oh and a side note: jeeze it looks like you got yourself a great battery still! Looks like it's still around the original 4000mAh. That's really good for a 3+yr old phone. (I can tell because it says you used 3577mAh and it was at 88% - which I guesstimate from those numbers to be around 4k at 100% used).