Mining energy-greedy API usage patterns in Android apps: an empirical study

Linares‐Vásquez, Mario; Bavota, Gabriele; Bernal-Cárdenas, Carlos; Oliveto, Rocco; Penta, Massimiliano Di; Poshyvanyk, Denys

doi:10.1145/2597073.2597085

Cited by 184 publications

(178 citation statements)

References 34 publications

Supporting

Mentioning

178

Contrasting

Order By: Relevance

“…Except privacy leaks detection, there has been a rich body of work on other Android security issues [9], [12], [18], [20], [23], [51] such as energy bugs [15], [32] and SSL vulnerabilities [19], [41]. Our work can complement their research by providing a highly precise control-flow graph to enable them to perform inter-component data-flow analysis and consequently to get better results.…”

Section: Related Workmentioning

confidence: 99%

IccTA: Detecting Inter-Component Privacy Leaks in Android Apps

Bartel

Bissyandé³

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

405

360

View full text Add to dashboard Cite

Abstract-Shake Them All is a popular "Wallpaper" application exceeding millions of downloads on Google Play. At installation, this application is given permission to (1) access the Internet (for updating wallpapers) and (2) use the device microphone (to change background following noise changes). With these permissions, the application could silently record user conversations and upload them remotely. To give more confidence about how Shake Them All actually processes what it records, it is necessary to build a precise analysis tool that tracks the flow of any sensitive data from its source point to any sink, especially if those are in different components.Since Android applications may leak private data carelessly or maliciously, we propose IccTA, a static taint analyzer to detect privacy leaks among components in Android applications. IccTA goes beyond state-of-the-art approaches by supporting intercomponent detection. By propagating context information among components, IccTA improves the precision of the analysis. IccTA outperforms existing tools on two benchmarks for ICC-leak detectors: DroidBench and ICC-Bench. Moreover, our approach detects 534 ICC leaks in 108 apps from MalGenome and 2,395 ICC leaks in 337 apps in a set of 15,000 Google Play apps.

show abstract

Section: Related Workmentioning

confidence: 99%

IccTA: Detecting Inter-Component Privacy Leaks in Android Apps

Bartel

Bissyandé³

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

405

360

View full text Add to dashboard Cite

show abstract

“…• Linares-Vásquez et al [27] From this overview, the state-of-the-art suggests a significant energy impact of code smells. However, the available evidence is limited in terms of number of smells and representativeness of the tested applications.…”

Section: Related Workmentioning

confidence: 99%

Empirical Evaluation of the Energy Impact of Refactoring Code Smells

Verdecchia

Saez²,

Procaccianti

et al.

EPiC Series in Computing

View full text Add to dashboard Cite

Software energy efficiency has gained the increasing attention of the research community. How to improve it, however, still lacks evidence. Specifically, the impact of code smell refactoring on energy efficiency has been scarcely investigated. In the exploratory study here reported, we investigate the impact on performance and energy consumption of refactoring well-known code smells on Java software applications. In order to understand if software metrics can be used as indicators of the energy impact of refactoring, we also measured the variation caused by refactoring on a set of well-established software metrics. We conducted a controlled experiment using state-of-the-art power measurement equipment. Statistical hypothesis testing and effect size estimation were performed on the experimental results, which show that in one out of three applications, refactoring each smell significantly impacted power-and energy consumption. E.g., refactoring Feature Envy and Long Method smells led to a 49% energy efficiency improvement. No software metric, however, significantly correlated with execution time, power or energy consumption. In conclusion, refactoring code smells resulted to be a viable process to significantly improve software energy efficiency. The magnitude of the impact may depend on application properties, e.g. size or age. Further research is needed to understand the relationship between software metrics and energy efficiency.

show abstract

“…Service workers are standardized by W3C 3 since 2009. According to the standard, a service worker is a special case of web worker 4 , it is implemented in a dedicated JavaScript file and runs in a separate thread with respect to the main JavaScript thread. Intuitively, a service worker can be considered as a piece of JavaScript code running in parallel to the main page, providing persistent background processing, and interacting with the rest of the PWA in an event-driven fashion.…”

Section: A Progressive Web Appsmentioning

confidence: 99%

“…For example, Linares-Vásquez et al [4] aim at identifying whether some API calls consume more energy than others, and if sequences of API calls (patterns) repeat themselves frequently, causing anomalies in energy consumption. The study analyzed the execution traces of 55 Android applications, looking for the most energy-greedy Android API calls.…”

Section: Related Workmentioning

confidence: 99%

Assessing the Impact of Service Workers on the Energy Efficiency of Progressive Web Apps

Malavolta

Procaccianti

Noorland

et al. 2017

2017 IEEE/ACM 4th International Conference on Mobile Software Engineering and Systems (MOBILESoft)

View full text Add to dashboard Cite

Abstract-Context. Mobile web apps represent a large share of the Internet today. However, they still lag behind native apps in terms of user experience. Progressive Web Apps (PWAs) are a new technology introduced by Google that aims at bridging this gap, with a set of APIs known as service workers at its core. Goal. In this paper, we present an empirical study that evaluates the impact of service workers on the energy efficiency of PWAs, when operating in different network conditions on two different generations of mobile devices. Method. We designed an empirical experiment with two main factors: the use of service workers and the type of network available (2G or WiFi). We performed the experiment by running a total of 7 PWAs on two devices (an LG G2 and a Nexus 6P) that we evaluated as blocking factor. Our response variable is the energy consumption of the devices. Results. Our results show that service workers do not have a significant impact over the energy consumption of the two devices, regardless of the network conditions. Also, no interaction was detected between the two factors. However, some patterns in the data show different behaviors among PWAs. Conclusions. This paper represents a first empirical investigation on PWAs. Our results show that the PWA and service workers technology is promising in terms of energy efficiency.

show abstract

Mining energy-greedy API usage patterns in Android apps: an empirical study

Cited by 184 publications

References 34 publications

IccTA: Detecting Inter-Component Privacy Leaks in Android Apps

IccTA: Detecting Inter-Component Privacy Leaks in Android Apps

Empirical Evaluation of the Energy Impact of Refactoring Code Smells

Assessing the Impact of Service Workers on the Energy Efficiency of Progressive Web Apps

Contact Info

Product

Resources

About