[Android General] Celestial Fury:
[0.0%/h] New Screenshots - 10 hours idle period!

Firstly, to add more than 4 attachments, WAIT until the first four have been added. Then, in the SAME window, keep adding as many as you like. :o

So, I've gotten my phone back from repairs. Good news is the camera doesn't occasionally fail with third party camera apps like before. The motherboard was changed but not sure if it came with a new camera or they just fixed in the old one. Either way, something changed for the better. They DID NOT change the battery.

Bad news is, I could restore a backup and everything works - EXCEPT the camera most likely due to Sony DRM keys. So, I had to reinstall everything from scratch. Now that mostly everything has been set up, I took some screenshots after 7 hours idle period. It was [0.0%/h] (before amplifying stuff it was above [1.0%/h]). Then I went out for 2.5 hours (with no WiFi connection) and took some more screenshots after 10 hours idle period. It was STILL [0.0%/h]. I had WhatsApp greenified but not amplified and quite a number of items in the guide (like Greenify, Sony Stamina mode, and others related to syncing)

were NOT

amplified this time around.

Here are the 10 hours idle period screenshots

1st screenshot: Nearly 10 mins awake - there's usually drain for such an awake period but surprisingly, none.

2nd screenshot: Low periods of radio-interface and PowerManagerService kernel wakelocks. High periods of these two usually cause drain so low periods, low drain - as expected. Kernel, sleeping like a baby.

3rd screenshot: Partial wakelocks - I've got some syncing of 2 items over 1 min. This usually causes a little drain but surprisingly, none.

4th screenshot: Alarms - Everything is low as expected for low to no drain.

5th screenshot: Network - the syncing took about 1 Mb, confirming that WiFi was on and data exchange was taking place.

6th screenshot: CPU States - and here we have it. Despite the syncing, it's the low CPU usage that leads to the no drain. Hardly a minute, which means the syncing was done efficiently. CPU, sleeping like a baby.

7th screenshot: Processes - nothing much going on. Kworker seems to correspond with the low kernel wakelocks.

8th screenshot: GSam Battery Monitor - just to double check. Yes, also 0.0%/h but it probably gets the stats just the same as BBS. I had installed it as I was thinking it would be useful to track down poor radio signal as a cause of drain as BBS doesn't seem to focus on phone radio.

9th screenshot: Battery usage - I didn't manage to finish charging before letting the phone go idle so focus on the area where the battery stops increasing.

10th screenshot: History details - also focus on the area after the battery stops increasing. Not surprisingly, I've got very bad radio signal (in the bedroom) but surprising that the phone didn't drain more trying to get a (better) signal as common wisdom would say.

Conclusion - reading battery drain still seems to be an art. I started this guide because I wanted a place to store all my amplified setting as the app didn't have a save/restore function and felt it could benefit others too. Also, as further encouragement, someone had posted a 15 hour period [0.

1

%/h] idle drain but when I checked he had most stuff turned off as per conventional wisdom to turn stuff off to lower drain. However, this guide is proof that it doesn't have to be that way. The evidence speaks for itself.

We've come some ways since the amplified *backup* rebooting wakelock that nearly scuppered my faith in my [0.0%/h] goal and the tinkering with play services permission (to find further ways to reduce drain) that blew my motherboard. I'm particularly thankful that others have discovered how limiting AlarmManager and CalendarProv ider2 can stop the alarm clock and calendar alarm respectively from working properly which led to the discovery that there are other calendar apps that will play nice which meant that CalendarProv ider2 could be re-limited.

Now, my phone's back. GPS is near instantaneous. Notifications come through. And drain is basically none. :highfive: