Android Battery Power Consumption Testing Guide

Battery life is a critical concern for mobile users, and poorly designed apps can become uninstall targets due to excessive power consumption; therefore testers should perform targeted power‑usage testing.

1. Using a hardware power meter

Instruments such as the Agilent N6705B can provide precise current measurements. The method requires removing the phone battery, inserting the meter between the device and external power, and reading the current flow.

Advantages : accurate current data. Disadvantages : requires hardware investment, phone disassembly, and only yields overall device current without per‑app breakdown.

2. Analyzing power consumption with Battery Historian

Battery Historian, released by Google, visualizes battery‑related events from bugreport files for Android 5.0+ devices, allowing developers to see system‑level and app‑level power events on a timeline.

Two versions exist: Historian 1.0 (Python‑generated HTML) and the newer Historian 2.0 with clearer reports and faster execution.

Installation : Use the 2.0 version; detailed steps are widely available online.

Usage steps :

1. Restart ADB to avoid conflicts: adb kill-server then adb start-server .

2. Enable full wake‑history and reset stats:

adb shell dumpsys batterystats --enable full-wake-history

adb shell dumpsys batterystats --reset

3. Perform the test scenarios.

4. Disconnect the USB cable, then export the bugreport: adb bugreport > bugreport.txt .

5. Open Battery Historian (e.g., localhost:9999 ) and import the bugreport.

The resulting charts display parameters such as battery_level , plugged , Screen , Top (foreground app), wake_lock , running , Gps , phone_in_call , Sync , Job , data_conn , Status , phone_signal_strength , Health , and Plug . Each provides insight into how different system components and app behaviors affect power usage.

Pros : intuitive visual results with detailed consumption data. Cons : not compatible with Android versions below 5.0.

Data validity tips :

• Horizontal comparison : first measure hardware‑only consumption, then measure combined hardware‑software consumption; compare the two to isolate app‑level usage.

• Vertical comparison : run the same test on two identical phones, one with the app installed and one without; compare the total consumption to estimate the app’s impact.

Be aware of network‑related variations and device‑to‑device hardware differences; using the same phone model and batch reduces error.