related.tex
1.59 KB
\section{Related Work}
\label{sec-related}
One of the main activities on these mobile devices is \textbf{content
consumption}. A large number of applications for mobile devices are
content-delivery applications such as browsers, e-book readers, video players,
audio players, and photo viewers. Surveys have shown that consuming mobile
content such as video, books, news, etc. is the most popular activity among
mobile device users~\cite{mobile-content1, mobile-content2}.
But high app usage will often translate to high energy consumption and lack of longevity
in battery life is reported to be the least satisfying aspect of smartphone ~\cite{battery-complaint1}.
Previous work on component-based power modelling~\cite{dong2011, zhang2010,
jung2012} has mapped energy consumption to system-components like cpu, wifi chip, screen etc.
On the other hand, efforts like Eprof~\cite{pathak2011,pathak2012}, AppScope~\cite{yoon} traces system calls and monitors kernel activities to answer how much energy is consumed in an application level.
There has also being an impressive body of work to provide accurate energy measurement techniques
like by using either external hardware~\cite{carroll,
cignetti} or device-provided, built-in mechanisms such as smart
battery interfaces and voltage information~\cite{mansdi, xunsdi}.
But there has been no work as per our knowledge about identifying how much energy is consumed in providing
utility to the user. There exists a gap in our understanding what part of energy consumption by an app is
necessary to provide useful content to the user and what part of it is lost in inefficiency.