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

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
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
preprint

Measuring What Kills Your App: A Methodology for Detecting Background Execution Failures in Production Android Apps

Sagar Ghag
Zenodo (CERN European Organization for Nuclear Research)
Mobile and Web Applications
preprint

Measuring What Kills Your App: A Methodology for Detecting Background Execution Failures in Production Android Apps

Sagar Ghag
preprint en

Abstract

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.

Zenodo (CERN European Organization for Nuclear Research)
Mobile and Web Applications
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon