I’ve observed much the same with WhatsApp and Molly (Signal): both devour battery life.
I developed a Python script to monitor and adjust parameters like RUN_IN_BG, Doze mode, wake locks, and the like—per app—paired with a quick ncurses interface to disable them. Yet, given the Kompakt’s lack of a native battery saver, I question whether any of this matters in the end.
After weeks of testing, it’s clear these tweaks are insufficient for meaningful autonomy. My battery still falls from 80% to 10-14% within 24 hours—a single day’s use, nothing more.
I attempted to force Android’s battery saver via ADB, only to find the dark mode seemingly hardcoded, resistant to override. A petty but persistent obstacle.
Recently I installed: https://superfreezz.gitlab.io/ which helps group-killing unwanted apps.
You can define strategies (auto/smart, freeze, ignore) for each app and with one button kill them all.
I don’t know if that can be made automatic, i haven’t been successful in doing so yet.
But so far, that seems to be the most efficient way to preserve battery.
Once all the apps are killed, the battery seems steady and doesn’t drain so fast. I’m hopeful.
Has anybody successfully automated something like this?
IIUC, one of the cleanest way would be to fix the “battery saver” mode so it doesn’t go dark mode in a lot of places (like settings, etc, which are barely readable when it’s on), right?
i tried Low power mode on Kompakt - #3 by jalucky13 but for me it’s not enough to fix the dark mode