[Xperia Z5 Q&A, Help & Troubleshooting] LolaPalocz:
Hello,

(Owning Z5 compact, currently on E5823_Customized FR_1299-1743_32.1.A.1.163_R5C, stock kernel repacked to get root).

I too am struggling to get good standby battery drain.

I tried a lot of things, and I never lose less than 1% / hour (testing different things every night, during 6-7 hours).

A friend's HTC One A9 on 6.0.1 lose 1% every 3-5 hours... I'd like to get that.

I also wait to get below 95% to begin a test (if just full charged, one can stick to 100% for hours, so let it unstick from that to get correct numbers).

I have no background app (no facebook/whatsapp & co). All sync'ing disabled. All wifi/bluetooth/nfc/gps/mobile data disabled. Sticking to 2G, signal 'great'.

I tried airplane mode, wifi off. I also tried a night in safe mode (you lose ur widget settings, but at least no market app is running) with 2G : always 1%/h.

Even when Doze activates, it changes nothing ; I tried agressive doze, i even tried disabling doze (thinking motion detection could be the culprit) by setting a high 'inactive_to' value : no change, always 1%/h.

CPU Spy and alike apps report 99% deep sleep.

I tried activating powersave governor (all core stuck to 340 Mhz) : still 1%/h.

I tried some analysis with GSam battery monitor, BetterBatteryStats, Wakelock Detector, nothing shocking.

Found yesterday another more detailed way to analyse battery stats :

(oups, can't post links, so search google for "batterystats historian")

adb shell dumpsys batterystats > batterystats.txt

You can get a python script that will make a nice HTML page from that batterystats.txt, so you can see everything that happened in the night :

(go to the github link, click on '18 commits', find 'Sync with internal version 44.', click on it, then view, and you can get historian.py , the latest python standalone single script, before they made something bigger in Go).

The sad things is that not much happens ! A dozen wakelocks and alarms for some google apps, some broadcast of GCM_RECONNECT, never actvating for more than 1 second.

And my friend's HTC One A9 gets the same events during the night, and dont lose as many % !

So, my conclusions with all this :

- The drain is not due to Android system and its activity (even Google's apps). So, no greenify/amplify/doze tweak will change anything.

- I checked linux processes after 24 hours, really not much process accounting for more than 10s cpu use.

- I tested for a few days with AndroPlus kernel v20: same 1%/h

- I dont really understand this mobile data bug. I dont use mobile data, always on 2G, only wifi when needed : does that mean i can't be impacted by this bug, and that we can rule it out ?

I think that during the few days I was on Lollipop, I got the feeling of great standby low-drain. But i may have started at 100% and rejoice when seeing 99% in the morning.

Could it be that the radio/baseband firmware that was updated with MM is now draining ? Does airplace mode really shut radio chip off ? (it may drain without being accounted by android's battery stats).

Do people that updated to 32.1.A.1.185 noticed a change (baseband version was updated in .185) ?

I'd like people that do NOT observe > 1%/h standby drain to tell their versions (LL, MM, region, stock kernel or else, rooted or not), even if Z5/Z5P, not only Z5C ?

Could it be that some cpu cores are not offline or sleeping when the system is inactive ? (I dont know how cpuspy/cpuZ report some single cpu states, when we have 8 cores that can all be in different states) ?

Or is it some other piece of hardware that is draining ? Or the battery itself ?

Thanks for the feedback.

(a bit tired struggling with this, if nobody gets less drain, at least I can admit it's the phone, and focus on something else)