Paper
AppFlow: Memory Scheduling for Cold Launch of Large Apps on Mobile and Vehicle Systems
Authors
Xiaochen Li, Sicong Liu, Bin Guo, Yu Ouyang, Fengmin Wu, Yuan Xu, Zhiwen Yu
Abstract
GB-scale large apps like on-device LLMs and rich media editors are becoming the next-generation trend, but their heavy memory and I/O demands, especially during multitasking, cause devices to reclaim or kill processes, turning warm apps into cold launches. The challenge lies not in storing them, but in fast, accurate launching. For users, 1s is the usability cliff, yet our measurements show 86.6\% of GB-scale cold launches exceed it. Also, Android Vitals flags only $\geq$ 5s as slow, exposing a large satisfaction gap. Existing optimizations are designed in isolation and conflict. For example, preloading reduces I/O stalls but consumes scarce memory and is undone by reclamation, while reclamation and killing free memory but sacrifice background survivability, leading to repeated cold relaunches. Our key insight is that, although multitasking makes runtime behavior complex, each app's file access pattern remains predictable. The challenge lies in exploiting this predictability, i.e., preloading without exhausting memory, reclaiming without undoing gains, and killing selectively to preserve background survivability. We introduce AppFlow, a prediction-based system-wide scheduler that integrates a Selective File Preloader, an Adaptive Memory Reclaimer, and a Context-Aware Process Killer. Implemented across the Android framework and Linux kernel without app changes, AppFlow cuts GB-scale cold-launch latency by 66.5\% (e.g., 2s$\rightarrow$690ms) and sustains 95\% of launches within 1s over a 100-day test, significantly improving responsiveness and multitasking experience.
Metadata
Related papers
Fractal universe and quantum gravity made simple
Fabio Briscese, Gianluca Calcagni • 2026-03-25
POLY-SIM: Polyglot Speaker Identification with Missing Modality Grand Challenge 2026 Evaluation Plan
Marta Moscati, Muhammad Saad Saeed, Marina Zanoni, Mubashir Noman, Rohan Kuma... • 2026-03-25
LensWalk: Agentic Video Understanding by Planning How You See in Videos
Keliang Li, Yansong Li, Hongze Shen, Mengdi Liu, Hong Chang, Shiguang Shan • 2026-03-25
Orientation Reconstruction of Proteins using Coulomb Explosions
Tomas André, Alfredo Bellisario, Nicusor Timneanu, Carl Caleman • 2026-03-25
The role of spatial context and multitask learning in the detection of organic and conventional farming systems based on Sentinel-2 time series
Jan Hemmerling, Marcel Schwieder, Philippe Rufin, Leon-Friedrich Thomas, Mire... • 2026-03-25
Raw Data (Debug)
{
"raw_xml": "<entry>\n <id>http://arxiv.org/abs/2603.17259v1</id>\n <title>AppFlow: Memory Scheduling for Cold Launch of Large Apps on Mobile and Vehicle Systems</title>\n <updated>2026-03-18T01:35:25Z</updated>\n <link href='https://arxiv.org/abs/2603.17259v1' rel='alternate' type='text/html'/>\n <link href='https://arxiv.org/pdf/2603.17259v1' rel='related' title='pdf' type='application/pdf'/>\n <summary>GB-scale large apps like on-device LLMs and rich media editors are becoming the next-generation trend, but their heavy memory and I/O demands, especially during multitasking, cause devices to reclaim or kill processes, turning warm apps into cold launches. The challenge lies not in storing them, but in fast, accurate launching. For users, 1s is the usability cliff, yet our measurements show 86.6\\% of GB-scale cold launches exceed it. Also, Android Vitals flags only $\\geq$ 5s as slow, exposing a large satisfaction gap. Existing optimizations are designed in isolation and conflict. For example, preloading reduces I/O stalls but consumes scarce memory and is undone by reclamation, while reclamation and killing free memory but sacrifice background survivability, leading to repeated cold relaunches. Our key insight is that, although multitasking makes runtime behavior complex, each app's file access pattern remains predictable. The challenge lies in exploiting this predictability, i.e., preloading without exhausting memory, reclaiming without undoing gains, and killing selectively to preserve background survivability. We introduce AppFlow, a prediction-based system-wide scheduler that integrates a Selective File Preloader, an Adaptive Memory Reclaimer, and a Context-Aware Process Killer. Implemented across the Android framework and Linux kernel without app changes, AppFlow cuts GB-scale cold-launch latency by 66.5\\% (e.g., 2s$\\rightarrow$690ms) and sustains 95\\% of launches within 1s over a 100-day test, significantly improving responsiveness and multitasking experience.</summary>\n <category scheme='http://arxiv.org/schemas/atom' term='cs.OS'/>\n <published>2026-03-18T01:35:25Z</published>\n <arxiv:comment>13 page, 21 figures, Mobicom 2026</arxiv:comment>\n <arxiv:primary_category term='cs.OS'/>\n <author>\n <name>Xiaochen Li</name>\n </author>\n <author>\n <name>Sicong Liu</name>\n </author>\n <author>\n <name>Bin Guo</name>\n </author>\n <author>\n <name>Yu Ouyang</name>\n </author>\n <author>\n <name>Fengmin Wu</name>\n </author>\n <author>\n <name>Yuan Xu</name>\n </author>\n <author>\n <name>Zhiwen Yu</name>\n </author>\n <arxiv:doi>10.1145/3795866.3796690</arxiv:doi>\n <link href='https://doi.org/10.1145/3795866.3796690' rel='related' title='doi'/>\n </entry>"
}