Detecting energy-greedy anomalies and mobile malware variants
Proceedings of the 6th international conference on Mobile systems, applications, and services
An analysis of power consumption in a smartphone
USENIXATC'10 Proceedings of the 2010 USENIX conference on USENIX annual technical conference
Bootstrapping energy debugging on smartphones: a first look at energy bugs in mobile devices
Proceedings of the 10th ACM Workshop on Hot Topics in Networks
Proceedings of the 10th international conference on Mobile systems, applications, and services
Collaborative energy debugging for mobile devices
HotDep'12 Proceedings of the Eighth USENIX conference on Hot Topics in System Dependability
Towards verifying android apps for the absence of no-sleep energy bugs
HotPower'12 Proceedings of the 2012 USENIX conference on Power-Aware Computing and Systems
eDoctor: automatically diagnosing abnormal battery drain issues on smartphones
nsdi'13 Proceedings of the 10th USENIX conference on Networked Systems Design and Implementation
| Hi-index | 0.00 |
Android provides a WakeLock mechanism for application developers to ensure the proper execution of applications without having to enter the sleep state of a device. When using the WakeLock mechanism, application developers should bear the responsibility of adequately releasing the acquired lock. Otherwise, the energy will unnecessarily be wasted due to a locked application. This paper presents a scheme, called WakeScope, to handle WakeLock misuse. The scheme is designed to detect and notify of a misuse case of WakeLock handling, which may arise with an application and even with an Android runtime system, and thus provides a practical tool to prevent energy waste in mobile devices. Our experiments with real applications show that WakeScope accurately detects the misused case, with runtime overhead of approximately 1.2% in CPU usage.