3 ms·
Sadly the battery issue is painfully generic, and the built in battery UI hopelessly inaccurate. I have experienced that the UI claimed that Play services were
by digi_owl 12y ago
Sadly the battery issue is painfully generic, and the built in battery UI hopelessly inaccurate.
I have experienced that the UI claimed that Play services were eating battery. But when i brought up a good old top report and looked at CPU time i find that Facebook was blocking the CPU from reaching sleep state.
killed the Facebook process and the problem went away rapidly.
And recently i have seen Plume having a similar issue. I can actually observe the CPU time rising when it is nowhere to be found outside of the top readout (no entry in the task switcher etc). But checking the Android battery readout i see nothing about Plume being a battery hog.
- joshstrange 12y agoI think that's the real problem. A tool designed to help you determine what is chewing up your battery seems to be fundamentally broken and is not being addressed.