Embedded systems have to go through so many
revolutionary changes, with the recent appearance of open
operating systems and smart phones, new and innovative
applications are invented to manage and monitor the energy
consumptions [1]. Examples are from stock tickers to citywide
social games, these devices promise to give support for a
large spectrum of applications, many applications such as
video-on-demand, and mobile gaming, real-time locationbased
tracking applications and location-aware mobile social
applications are often characterized by heavy network
transmission. These features imply a heavy workload on the
mobile phone processors, the display in performing mobile
phone services and the wireless network, which in result
causes a significant energy cost.
Rapidly growing energy demands have not kept pace with
advances in battery technology. Most android devices use
rechargeable electrochemical batteries for example lithiumion
batteries, as their portable energy source. These fully
charged batteries can run on this charge for only a few hours.
For example, if the games and whatsapp are used all the time,
the android phone can work for only several hours before it
runs out of its energy, therefore the power consumption has
emerged as a key issue of the energy management of portables.
Some existing tools can analyze android applications energy
consumptions, however these tools don't address monitoring
energy consumptions from a developer's standpoint because
of which the power consumption has emerged as a key issue
of the energy management of portables [3].
To analyze the energy consumption of mobile applications
on the Android operating system, software system will be
designed to monitor energy of the system. It can let
developers profile android system applications with battery
information.
This paper is divided into five sections, where section I
give an introduction, objective and goals. Section II gives a
deep literature survey. Section III contains a detailed plan of
work. Detailed methodology is highlighted in section IV.
Finally in section V power saver implementer is
mentioned .In section VI Results and in VII conclusion and
future work are drawn.