Measuring & Reducing Android App Power Consumption: Tools & Techniques

Fundamentals of Power Consumption

Power (P) is calculated as current (I) multiplied by voltage (U):

P = I × U

. Energy (E) equals power times time:

E = P × T = I × U × T

. Energy consumption (E) is measured in joules (J), while power consumption (P) is measured in watts (W). In mobile devices, current is expressed in milliamps (mA) to represent power, and battery capacity is expressed in milliamp‑hours (mAh) to represent energy.

Because the discharge voltage of a phone is typically constant (about 3.7 V), voltage can be omitted from the formulas, allowing mA to indicate power usage and mAh to indicate total energy used.

Components of Power Consumption

Android’s developer documentation splits battery usage information into two parts: battery usage statistics and a power‑profile configuration file. The BatteryStats service tracks component state durations (e.g., Wi‑Fi, Bluetooth, GPS, screen, CPU) and estimates each component’s energy use based on timing data.

Thus, an app’s total power draw can be expressed as the sum of the power consumed by the device’s hardware components. Major contributors include the CPU, display, Wi‑Fi, cellular data, GPS, and audio/video calls.

The power‑profile file (

/frameworks/base/core/res/res/xml/power_profile.xml

) provided by device manufacturers defines the current draw for each component. Developers can extract this file by decompiling

framework-res.apk

and locating

power_profile.xml

in the

/res/xml/

directory.

Power Measurement Methods

PowerMonitor (external power source) : High‑frequency, high‑precision current sampling; most accurate but requires device disassembly.

dumpsys batterystats : Provides detailed per‑app power data; output can be hard to read.

System power ranking : Simple visual ranking of apps; lacks detailed metrics.

Battery Historian : Google’s official tool that visualizes BatteryStats data; works on Android 5.0+.

1. PowerMonitor

PowerMonitor captures current at high frequency using an external power supply, making it suitable for precise analysis of background and screen‑off states, though it requires hardware setup and device teardown.

2. dumpsys batterystats

Export battery statistics with:

<code>adb shell dumpsys batterystats > battery.txt</code>

Reset the collected data using:

<code>adb shell dumpsys batterystats --reset</code>

BatteryStatsService aggregates usage per UID, allowing developers to monitor resource consumption of individual apps.

3. System Power Ranking

Device manufacturers often provide built‑in power ranking screens (e.g., Huawei) that break down hardware and software power usage per app.

4. Battery Historian

Battery Historian visualizes BatteryStats data in a web UI. Install it via Docker or source code, or use the hosted version at https://bathist.ef.lc/ .

Typical workflow:

Connect the device via ADB.

Reset battery stats:

<code>adb shell dumpsys batterystats --reset</code>

Run the test scenario.

Collect a bug report (Android 7.0+):

<code>adb bugreport bugreport.zip</code>

or (Android 6.0‑):

<code>adb bugreport bugreport.txt</code>

Open Battery Historian in a browser, load the bug report, and submit to generate visual charts.

Understanding the Chart Markers

Marker 1: Add additional metrics from the dropdown.

Marker 2: Hover to see detailed information for each metric.

Marker 3: Hover over an entry to view its specific power consumption over time.

Marker 4: System Stats group shows overall device data (e.g., screen brightness).

Marker 5: App Stats group displays detailed per‑app information.

Battery Historian also provides per‑app visualizations such as estimated power use, network activity, wake‑locks, services, process info, and sensor usage.

By analyzing these data, developers can identify high‑consumption components and apply targeted optimizations to reduce overall power usage.