Two-Level Rejuvenation for Android Smartphones and Its Optimization

Yu, Qiao; Zhang, Zheng; Fang, Yunyu; Qin, Fangyun; Trivedi, Kishor S.; Cai, Kai-Yuan

doi:10.1109/tr.2018.2881306

Cited by 24 publications

(9 citation statements)

References 62 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The timeliness fault delays the execution of the stop_activity method by several seconds. This kind of fault occur when the device is overloaded (for example, due to a CPU hog app [41], [42]), or because of a performance bug in the System Server (e.g., due to software aging [40], [43]). When this timeliness fault is injected, the System UI process becomes not responsive (see Figure 10a).…”

Section: E Fault Injection In the System Servermentioning

confidence: 99%

Dependability Assessment of the Android OS Through Fault Injection

et al. 2021

View full text Add to dashboard Cite

The reliability of mobile devices is a challenge for vendors, since the mobile software stack has significantly grown in complexity. In this paper, we study how to assess the impact of faults on the quality of user experience in the Android mobile OS through fault injection. We first address the problem of identifying a realistic fault model for the Android OS, by providing to developers a set of lightweight and systematic guidelines for fault modeling. Then, we present an extensible fault injection tool (AndroFIT) to apply such fault model on actual, commercial Android devices. Finally, we present a large fault injection experimentation on three Android products from major vendors, and point out several reliability issues and opportunities for improving the Android OS. 2

show abstract

Section: E Fault Injection In the System Servermentioning

confidence: 99%

Dependability Assessment of the Android OS Through Fault Injection

et al. 2021

View full text Add to dashboard Cite

show abstract

“…Most of the research on software rejuvenation focuses on when to perform rejuvenation, i.e., on determining the optimal rejuvenation time; this is achieved either by analytic models (time-based rejuvenation) [14,15], or by measurements (inspection-based rejuvenation) [16,17,18]. Fewer studies investigate how rejuvenation should be performed for the best performance.…”

Section: Related Workmentioning

confidence: 99%

Software Micro-Rejuvenation for Android Mobile Systems

Cotroneo,

De Simone,

Natella

et al. 2021

Preprint

View full text Add to dashboard Cite

Software aging -the phenomenon affecting many long-running systems, causing performance degradation or an increasing failure rate over mission time, and eventually leading to failure -is known to affect mobile devices and their operating systems, too. Software rejuvenation -the technique typically used to counteract aging -may compromise the user's perception of availability and reliability of the personal device, if applied at a coarse grain, e.g., by restarting applications or, worse, rebooting the entire device.This article proposes a configurable micro-rejuvenation technique to counteract software aging in Android-based mobile devices, acting at a fine-grained level, namely on in-memory system data structures. The technique is engineered in two phases. Before releasing the (customized) Android version, a heap profiling facility is used by the manufacturer's developers to identify potentially bloating data structures in Android services and to instrument their code. After release, an aging detection and rejuvenation service will safely clean up the bloating data structures, with a negligible impact on user perception and device availability, as neither the device nor operating system's processes are restarted. The results of experiments show the ability of the technique to provide significant gains in aging mobile operating system responsiveness and time to failure.

show abstract

“…Memory leaks may cause the heap utilization ratio to continuously increase. As a result, garbage collection (GC) is frequently triggered, with the consequent increasing in the response time of the application [26].…”

Section: Background On Memory Leaks Due To Android Activity Lifecmentioning

confidence: 99%

Do Memories Haunt You? An Automated Black Box Testing Approach for Detecting Memory Leaks in Android Apps

et al. 2020

View full text Add to dashboard Cite

Memory leaks represent a remarkable problem for mobile app developers since a waste of memory due to bad programming practices may reduce the available memory of the device, slow down the apps, reduce their responsiveness and, in the worst cases, they may cause the crash of the app. A common cause of memory leaks in the specific context of Android apps is the bad handling of the events tied to the Activity Lifecycle. In order to detect and characterize these memory leaks, we present FunesDroid, a toolsupported black box technique for the automatic detection of memory leaks tied to the Activity Lifecycle in Android apps. FunesDroid implements a testing approach that can find memory leaks by analyzing unnecessary heap object replications after the execution of three different sequences of Activity Lifecycle events. In the paper, we present an exploratory study that shows the capability of the proposed technique to detect memory leaks and to characterize them in terms of their size, persistence and growth trend. The study also illustrates how memory leak causes can be detected with the support of the information provided by the FunesDroid tool. INDEX TERMS Android, Android activity lifecycle, memory leak, resource leak, Android testing.

show abstract

Two-Level Rejuvenation for Android Smartphones and Its Optimization

Cited by 24 publications

References 62 publications

Dependability Assessment of the Android OS Through Fault Injection

Dependability Assessment of the Android OS Through Fault Injection

Software Micro-Rejuvenation for Android Mobile Systems

Do Memories Haunt You? An Automated Black Box Testing Approach for Detecting Memory Leaks in Android Apps

Contact Info

Product

Resources

About