1. Information about the paper


Metri, Grace, Weisong Shi, Monica Brockmeyer, and Abhishek Agrawal. “BatteryExtender: an adaptive user-guided tool for power management of mobile devices.” In Proceedings of the 2014 ACM International Joint Conference on Pervasive and Ubiquitous Computing, pp. 33-43. ACM, 2014.


The battery life of mobile devices is one of their most important resources. Much of the literature focuses on accurately profiling the power consumption of device components or enabling application developers to develop energy-efficient applications through fine-grained power profiling. However, there is a lack of tools to enable users to extend battery life on demand. What can users do if they need their device to last for a specific duration in order to perform a specific task? To this extent, we developed BatteryExtender, a user-guided power management tool that enables the reconfiguration of the device’s resources based on the workload requirement, similar to the principle of creating virtual machines in the cloud. It predicts the battery life savings based on the new configuration, in addition to predicting the impact of running applications on the battery life. Through our experimental analysis, BatteryExtender decreased the energy consumption between 10.03% and 20.21%, and in rare cases by up to 72.83%. The accuracy rate ranged between 92.37% and 99.72%.


2. My review of the paper

  1. Saving configuration.

Instead or in addition to resetting configuration every reboot, we should provide a way to save the configuration. Therefore, the user does not have to configure manually when doing repetitive/similar task. Such repetitive manual configuration would annoy both novice or advanced users.

  1. Compare to built in power saver.

Each platform or vendor (Microsoft and Dell in this case) usually has provided a power saver method. This paper should instead compare itself with built-in power saver. It’s just not fair to compare BatteryExtender with default platform setting. Does BatteryExtender offer significant improvement than built-in battery saver, which in many cases, have been designed by the vendor to be easily used by novice users? This remains a question to be answered. Furthermore, there are also online tutorials/tips on battery saving that can be googled and followed easily. These tips usually guide users to disable un-needed components with built-in platform setting. It should also compare itself to this approach.

  1. Notify when to charge if it is just not enough.

A novice user might just remember to extend battery life when it is too late. Then, in addition to extending battery life, we should provide an estimation about when the user should charge the device, when otherwise an important task would be interrupted. Because when the task is interrupted before completed and causes the novice user to lose work/data, the user might think that extending the battery life would be useless. Then if calculated that the task could not be done with current battery life, the user can make an informed decision to do the task after charging, safely.

  1. Finding that disabling “USB Root Device (xHCI)” contributes significant efficiency should be addressed by Microsoft to offer better platform.
  2. What if, during a download scenario, a video call comes in? Well, this would be the user’s decision.