How to survive on Android and don't get killed
summary
Claims that manufacturers (Samsung, Huawei, OnePlus, Xiaomi) add aggressive task killers that abruptly stop alarms, break wake locks and kill foreground services; gives concrete workarounds and per‑OEM toggle steps via the Don't Kill My App website and a test app that runs a benchmarked foreground service + alarms to measure executions. Project records 16 million visits and ~50,000 daily users, helped trigger Nokia to remove EvenWell, and seeks to upstream a CTS benchmark to force vendor compliance.
AI-written summary · about
chapters (20)
- 0:00Introduction to survival
- 1:06Our team and projects
- 2:10Lord Business and Android restrictions
- 4:59Background processing evolution
- 8:49Foreground service challenges
- 11:07Adaptive battery and background limits
- 13:14Android 10 and 11 restrictions
- 14:18Android 12 and future pain
- 15:20Impact on indie developers
- 16:03Manufacturer app killers
- 19:57History of app killers
- 22:02Don't Kill My App project
- 23:50OEM scores and solutions
- 25:35Top three offenders
- 28:46Don't Kill My App app
- 30:11Achievements and growth
- 31:57Nokia's EvenWell recall
- 32:19CTS benchmark contribution
- 33:43How to contribute
- 34:34Closing song
related talks
34mDon't Kill My App: Android survival guide
35mHow to survive on Android and don't get killed
33mIs my application taking up too much power?
28mAndroid Zombies: How to Not Get Bit
21mImproving battery life with restrictions
40mAndroid vitals: Debug app performance and reap rewards
36mBackground Work in Android: Strategies and Best Practices
11mEffective background tasks on Android