Problems detected by GreenDroid
In our controllled experiments,
GreenDroid detected 14 real energy problems. We list the details of
these problems (including some direct URL links) such that interested
researchers can investigate them for further research or replicate our
study.
1. Existing problems
GreenDroid detected 12 energy problems that were confirmed before our
experiments. These problems are:
These problems are known to cause huge energy waste and
great inconvenience for users. Below are two user reviews for Zmanim
and Geohash Droid, respectively.
2. New problems
GreenDroid also detected two new energy problems that were previously
unknown. We then submitted bug reports to developers and the two bugs
have been confirmed by developers.
Below are two comments from developers for Omnidroid issue 179 and
GPSLogger issue 7, respectively.
Omnidroid: "Completely
true, and your suggestion is a great idea and you're correct omnidroid
does suck up way more energy than necessary as a result. I'd be
happy to accept a patch in this regard."
GPSLogger: "
Why
would someone keep polling GPS if the location data are continuously
discarded? GPS is an energy hog! The current design is far from
perfect."
We also created a patch for GPSLogger to optimize its energy
consumption. We did some field testing of our patch and the result
suggested that there is around 20% energy saving. Although this saving
is not too
much, considering users typically concurrently run multiple
applications on their smartphone, it is still meaningful if the energy
consumption for each application can be reduced by 20%. This patch was
later integrated into GPSLogger and a new version can be downloaded
here.