Measuring What Kills Your App: A Methodology for Detecting Background Execution Failures in Production Android Apps
Background location tracking apps die in the field. Doze mode suspends them. OEM battery killers terminate their foreground services. Users revoke location permissions mid-shift. Practitioners know this from dontkillmyapp.com and production firefighting, but there is no published methodology for systematically detecting, classifying, and measuring these failures in a running app. We present a measurement methodology for background execution failures on Android comprising a kill-cause taxonomy (five categories), an instrumentation specification, and a classification procedure. We validate against a production Flutter app (104,886 lines, 86 physical devices, two months of field deployment). The audit found six detection signals present and twelve gaps. Analysis of 159 tracking sessions and 14,094 waypoints revealed 509 timestamp gaps exceeding five minutes, 65 sessions (40.9%) with three or fewer waypoints, and 25 sessions (15.7%) running until server timeout. The methodology is framework-agnostic; instrumentation examples use Flutter and Android.
Authors
- Sagar Ghag
Publication Details
- Journal
- Zenodo (CERN European Organization for Nuclear Research)
- Published
- 2026-11-16
- DOI
- https://doi.org/10.5281/zenodo.24262951
- Primary Topic
- Mobile and Web Applications
- Type
- preprint