3 ms·
Did you even bother reading the complaints? These "background killers" kill background applications the user wants to run and has specifically asked for e.g. al
by masklinn 8y ago
Did you even bother reading the complaints? These "background killers" kill background applications the user wants to run and has specifically asked for e.g. alarms, health/fitness trackers, …, usually in the most harmful way possible (e.g. straight kill -9) meaning the application can't even tell the user what the issue is, and with complex steps users have to take (possibly repeatedly) to whitelist specific applications.
Hell there are comments in this thread testifying that these built-in "battery savers" even kill the built-in alarm application.
- PunchTornado 8y agobeen using android since forever. Now I'm on a s8+. I never had a case like this. maybe I didn't noticed it. But my alarm always went on like it should. my music always played. is this a bug that sometimes happens? how rare is it?
- shittyadmin 8y agoSeems it's mainly an issue with Nokia devices, the other manufacturers were minor problems in comparisons.
- Piskvorrr 8y agoS8 has this, but can be opted out (plus it has what I assume is a whitelist of pre-approved apps, but even those can be opted in, IIRC). It's clumsy, but sort-of works. It does break some old apps that rely on scheduled wakeups, though :(
- AstralStorm 8y agoAlso the Samsung variant will not kill the app or service that is showing a notification as it should. So the three problem is limited to apps relying on dumb running in background. Alarm scheduled wakeups get rounded to a minute in power saving mode though.