Diagnosing Android Battery Drain with ADB Battery Historian

Why a Battery Historian Is Useful

Android devices report a wealth of power‑related data, but the raw logs are difficult to read. Battery Historian is a Google‑provided web tool that visualises those logs, letting you see exactly which apps, services, or hardware components are consuming power and when.

What You’ll Need

• A Windows, macOS, or Linux computer with adb installed.
• A USB cable that can transfer data (not just charge).
• Root access is not required; the method works on any stock Android device with developer options enabled.
• Internet connection to download Battery Historian (a small Java JAR file).

Step 1 – Install the Android Debug Bridge (ADB)

1. Download the Android platform‑tools package for your OS.
2. Extract the ZIP file to a location you can remember (e.g., C:\adb on Windows or ~/adb on macOS/Linux).
3. Add the folder to your system PATH so you can run adb from any terminal.
4. Open a terminal (Command Prompt, PowerShell, Terminal) and verify the installation with:

   adb version

   You should see something like Android Debug Bridge version 1.0.41.

Step 2 – Enable Developer Options and USB Debugging on Your Phone

1. Open Settings → About phone.
2. Tap Build number seven times. You’ll see a toast confirming that developer mode is active.
3. Return to the main Settings screen and open System → Advanced → Developer options (the path may vary by OEM).
4. Toggle USB debugging on. Confirm any prompts that appear.
5. Connect your phone to the computer via the USB cable. When prompted on the device, allow the computer’s RSA key.

Step 3 – Capture a Battery Stats Dump

Battery Historian works with a log file generated by the dumpsys batteryinfo command. Follow these steps to collect a useful sample:

1. Open a terminal and confirm the device is recognized:

   adb devices

   You should see your device’s serial number listed.
2. Reset any previous battery stats to start with a clean slate (optional but recommended):

   adb shell dumpsys batterystats --reset

3. Use your phone normally for the period you want to analyse – typical scenarios are:
   • After a full charge, let the phone sit idle for a few hours.
   • During a heavy usage session (gaming, streaming, navigation).
   Tip: Keep the screen on at a moderate brightness so the log captures real usage.
4. When you’re ready, pull the battery stats file:

   adb shell dumpsys batterystats > batterystats.txt

   This creates a plain‑text file on your computer.

Step 4 – Download and Run Battery Historian

1. Download the latest battery-historian.jar from the official GitHub releases page. The file is typically under the name battery-historian-version.jar.
2. Open a terminal in the folder containing both battery-historian.jar and batterystats.txt.
3. Start the Historian server with:

   java -jar battery-historian.jar

   By default it binds to http://localhost:9999.
4. Open a web browser and navigate to that address. You’ll see the Battery Historian UI.
5. Click the Choose File button, select batterystats.txt, and press Upload. The tool will render a timeline view.

Step 5 – Interpreting the Timeline

Battery Historian presents several layers of information. Here’s how to read the most important sections:

• Power‑use bars (green, orange, red) – Show the relative contribution of each component. Green usually indicates low‑power background activity; orange/red highlight heavy consumers.
• App activity – Each installed app appears as a separate row. Look for long orange bars or frequent spikes.
• Wake‑locks – Represented by horizontal lines. A wake‑lock that stays active for minutes can drain the battery even if the screen is off.
• Network usage – Data‑transfer events are shown as small vertical ticks. Heavy network usage while the screen is off often points to background sync problems.
• Screen state – The topmost bar indicates when the display was on (bright) or off (dim). Correlate spikes with screen‑on periods to see if the drain is caused by UI rendering or background work.

Hover over any bar to see a tooltip with exact timestamps, duration, and the component’s name.

Step 6 – Identify Culprits and Take Action

1. App with long orange bars: Open Settings → Apps → [App] → Battery and use the Battery usage breakdown to restrict background activity or force stop the app.
2. Persistent wake‑lock: The offending package is usually displayed in the tooltip. Search online for that app’s known wake‑lock issues, or disable the feature in the app’s settings.
3. Excessive network traffic while screen is off: Consider disabling background data for the app (Settings → Apps → [App] → Data usage → Background data). If it’s a system service, check for OS updates that may contain bug fixes.
4. System services (e.g., GPS, Bluetooth) staying active: Toggle the corresponding radios off when not needed. You can also use adb shell dumpsys bluetooth or adb shell dumpsys location to verify their state.

Step 7 – Verify the Fix

After making adjustments, repeat Steps 3‑5 to capture a new battery log. Compare the new timeline with the original one; the problematic bars should be reduced or disappear entirely. Consistently lower overall power‑use percentages indicate a successful optimisation.

Additional Tips & Common Pitfalls

• Don’t forget to re‑enable USB debugging after a factory reset – the setting is cleared.
• Battery Historian requires Java 8 or newer. If you see an error about “Unsupported major.minor version”, update your Java runtime.
• Large logs can be unwieldy. If the upload hangs, limit the capture period (e.g., 30 minutes) or split the log using adb shell dumpsys batterystats --reset between captures.
• Some OEM skins hide certain power‑use details. In those cases, the visualisation may show generic “kernel” entries. The best workaround is to use a stock Android ROM or a custom ROM that provides full battery stats.
• Battery health deteriorates over time. Even after fixing software‑related drains, an aging battery may still show rapid discharge. Consider a replacement if the problem persists.

Conclusion

Battery Historian, combined with ADB, gives you a transparent view of what’s really eating your Android device’s juice. By following this guide you can capture accurate battery data, visualise it, pinpoint misbehaving apps or services, and apply concrete fixes. Regularly checking the battery log after major app installations or OS updates helps you stay ahead of hidden drains and keep your device lasting longer between charges.