Don't Kill My App: Android survival guide
summary
Project documents that OEM "app killers" stop alarms, wake locks and foreground services; tests run a foreground service, acquire wake locks and schedule alarms every 10 minutes, then score expected vs performed to quantify failures. The site and app attract ~32 million visits (≈50,000/day) and list worst OEMs (Huawei, OnePlus, Samsung), note Nokia removed Evenwell, and the benchmark is accepted into a developer-powered CTS module after a year-long review. Practical fixes, user guides and a drop-in SDK are available.
AI-written summary · about
chapters (11)
- 0:00Welcome and introduction
- 1:52Android evolution and Lord Business
- 5:04Background task restrictions
- 11:07Android Pie and adaptive battery
- 15:23Impact on indie developers
- 16:49App killers and OEMs
- 21:49Don't Kill My App initiative
- 26:22Achievements and growth
- 29:54CTS benchmark integration
- 30:57How to contribute
- 31:18Song performance
related talks
37mHow to survive on Android and don't get killed
35mHow to survive on Android and don't get killed
34mPowering up your app performance & stability using App Vitals
40mAndroid vitals: Debug app performance and reap rewards
21mUnlocking Mobile App Security- Key Insights for Navigating a Rapidly Evolving Threat Landscape
33mIs my application taking up too much power?
22mLocking, blocking and rocking Android for Self-service Kiosks
23mAre Bad Manufacturer Overlays a Thing of the Past?