Affiliation:
1. University of California at Riverside, USA
2. New Jersey Institute of Technology, USA
Abstract
Mobile operating systems, especially Android, expose apps to a volatile runtime environment. The app state that reflects past user interaction and system environment updates (e.g., battery status changes) can be destroyed implicitly, in response to runtime configuration changes (e.g., screen rotations) or memory pressure. Developers are therefore responsible for identifying app state affected by volatility and preserving it across app lifecycles. When handled inappropriately, the app may lose state or end up in an inconsistent state after a runtime configuration change or when users return to the app.
To free developers from this tedious and error-prone task, we propose a systematic solution, LiveDroid, which precisely identifies the
necessary
part of the app state that needs to be preserved across app lifecycles, and automatically saves and restores it. LiveDroid consists of: (i) a static analyzer that reasons about app source code and resource files to pinpoint the program variables and GUI properties that represent the necessary app state, and (ii) a runtime system that manages the state saving and recovering. We implemented LiveDroid as a plugin in Android Studio and a patching tool for APKs. Our evaluation shows that LiveDroid can be successfully applied to 966 Android apps. A focused study with 36 Android apps shows that LiveDroid identifies app state much more precisely than an existing solution that includes all mutable program variables but ignores GUI properties. As a result, on average, LiveDroid is able to reduce the costs of state saving and restoring by 16.6X (1.7X - 141.1X) and 9.5X (1.1X - 43.8X), respectively. Furthermore, compared with the manual state handling performed by developers, our analysis reveals a set of 46 issues due to incomplete state saving/restoring, all of which can be successfully eliminated by LiveDroid.
Funder
National Science Foundation
Google
Publisher
Association for Computing Machinery (ACM)
Subject
Safety, Risk, Reliability and Quality,Software
Reference67 articles.
1. 2020. Glucosio for Android. https://github.com/Glucosio/glucosio-android. Accessed: 2020-07-22. 2020. Glucosio for Android. https://github.com/Glucosio/glucosio-android. Accessed: 2020-07-22.
2. 2020. K-9 Mail. https://github.com/k9mail/k-9. Accessed: 2020-07-22. 2020. K-9 Mail. https://github.com/k9mail/k-9. Accessed: 2020-07-22.
3. 2020. MapBox. https://github.com/mapbox/mapbox-gl-native. Accessed: 2020-09-08. 2020. MapBox. https://github.com/mapbox/mapbox-gl-native. Accessed: 2020-09-08.
4. 2020. Open MF. https://github.com/openMF/android-client. Accessed: 2020-09-08. 2020. Open MF. https://github.com/openMF/android-client. Accessed: 2020-09-08.
5. 2020. StackOveflow Question 456211. https://stackoverflow.com/questions/456211/activity-restart-on-rotation-android. Accessed: 2020-09-08. 2020. StackOveflow Question 456211. https://stackoverflow.com/questions/456211/activity-restart-on-rotation-android. Accessed: 2020-09-08.
Cited by
9 articles.
订阅此论文施引文献
订阅此论文施引文献,注册后可以免费订阅5篇论文的施引文献,订阅后可以查看论文全部施引文献
1. DDLDroid: A Static Analyzer for Automatically Detecting Data Loss Issues in Android Applications;Proceedings of the 32nd ACM SIGSOFT International Symposium on Software Testing and Analysis;2023-07-12
2. An Empirical Study of Functional Bugs in Android Apps;Proceedings of the 32nd ACM SIGSOFT International Symposium on Software Testing and Analysis;2023-07-12
3. DDLDroid: Efficiently Detecting Data Loss Issues in Android Apps;Proceedings of the 32nd ACM SIGSOFT International Symposium on Software Testing and Analysis;2023-07-12
4. Detecting Potential User-data Save & Export Losses due to Android App Termination;2023 IEEE/ACM International Conference on Automation of Software Test (AST);2023-05
5. Linker Code Size Optimization for Native Mobile Applications;Proceedings of the 32nd ACM SIGPLAN International Conference on Compiler Construction;2023-02-17