How to Measure Battery Life & Power Draw on a Handheld PC

This guide shows you how to measure the actual battery life and real-time power draw of a handheld gaming PC (like a Steam Deck, ROG Ally, or Lenovo Legion Go). You’ll learn what tools to use, how to run a controlled test, and how to read the results so you can compare performance settings or decide if your battery is degrading.

What You’ll Need

Your handheld gaming PC fully charged (to 100%)
A stopwatch or timer (phone app works)
A game or benchmark that you’ll run identically each time
Built-in performance overlay (most handhelds have one) OR a third-party tool like MSI Afterburner + RTSS (for Windows devices)
Notepad or spreadsheet to record results
Charger (for after the test)

Step-by-Step

Set a consistent test scenario. Choose a game and a specific scene (e.g., a particular level or a benchmark run). The more repeatable, the better. If you want to measure idle draw, just leave it on the home screen.
Set your power profile. Decide on a TDP (Thermal Design Power) limit—like 15W, 25W, or 30W—and set it in the handheld’s quick settings menu. Also set screen brightness to a fixed level (e.g., 50%) and disable any frame rate caps if you want to see raw draw, or enable them if you want to test typical usage.
Enable the performance overlay. On Steam Deck, press the QAM button (…) and go to Performance → Advanced View. On Windows handhelds, open the built-in overlay (usually via a button on the controller) or launch MSI Afterburner and enable the on-screen display for power, FPS, and temperatures.
Fully charge the device. Plug it in until it hits 100%. Unplug it and note the time.
Start the test. Launch your chosen game or benchmark and play for a set period—say 30 minutes. Alternatively, you can run until the battery dies, but that takes longer.
Record power draw. During the test, note the average power draw (in watts) shown in the overlay. Write it down every 5 minutes or just take the average at the end.
Record battery percentage. At the end of your test period, note the battery percentage remaining.
Calculate battery life. Use the formula: (Battery capacity in Wh) / (Average power draw in W) = estimated hours. For example, if your battery is 40Wh and average draw is 15W, you get ~2.67 hours. But to get a real-world number, use the percentage drop: (Time elapsed) / (Percentage drop) × 100 = total battery life. E.g., 30 min / 20% drop = 1.5 min per 1% → 150 minutes total.
Repeat for different settings. If you’re comparing TDP levels or brightness, repeat the test with the same game and scene, changing only the variable you’re testing.

Common Mistakes

Not fixing the scene. If you run a different part of the game, power draw will vary wildly. Use the same level or benchmark every time.
Ignoring screen brightness. The display can draw 5-10W alone. Keep it constant.
Forgetting to disable charging. If you leave the charger plugged in, you’re not measuring battery life.
Using the wrong battery capacity. Check your device’s spec sheet—some handhelds have 40Wh, others 50Wh. Use the actual number.
Not accounting for background processes. Windows updates or cloud sync can spike power draw. Close unnecessary apps before testing.

Tips

For more accurate power draw, use a USB-C power meter (like a USB-C watt meter) between the charger and the device. This measures total system draw, including the screen and speakers.
Run the test for at least 30 minutes to average out spikes.
If you’re only interested in battery life, you can just run the game until the battery hits 10% and note the time.
Use a consistent frame rate cap (e.g., 30 FPS) to reduce power fluctuations.
Record ambient temperature—heat can affect battery performance slightly.

Troubleshooting

Overlay not showing power draw: On Windows, MSI Afterburner may need to be configured to show “GPU power” and “CPU power” separately. On Steam Deck, make sure you’re in the “Advanced View” of the performance overlay.
Battery percentage drops unpredictably: If the device is still indexing or updating, power draw will spike. Wait until background tasks finish before testing.
Device shuts down before reaching 0%: Some handhelds have a safety cutoff at 5% or 10%. That’s normal—your usable battery life is slightly less than the full capacity.
Results vary between runs: Even with the same settings, power draw can vary due to temperature, Wi-Fi, or game updates. Run the test twice and take the average.

Frequently Asked Questions

How do I check my handheld’s battery capacity in Wh?

Look up the spec sheet from the manufacturer. For example, the Steam Deck LCD has a 40Wh battery, the OLED model has 50Wh, and the ROG Ally has 40Wh. You can also use software like HWiNFO on Windows to read the battery’s design capacity.

What is a good average power draw for a handheld?

It depends on the game. Light indie games might draw 10-15W, while AAA titles can draw 25-30W or more. Lower TDP settings reduce draw but also lower performance.

Can I measure battery life without a game?

Yes, you can measure idle draw by just leaving the device on the home screen. That gives you the minimum power draw, but actual gaming will be much higher.

Does screen brightness affect battery life significantly?

Yes, the screen can be one of the biggest power consumers. Reducing brightness from 100% to 50% can extend battery life by 20-30% on some devices.

Is it better to measure power draw with a wall meter or software?

Software gives you the power draw of the APU (CPU+GPU) and sometimes the whole system, but it may not include the screen. A USB-C wall meter measures total power coming from the charger, which is more accurate for overall consumption, but it only works while charging.

How often should I run a battery test?

If you’re just curious, once is enough. If you suspect battery degradation, run a test every few months and compare the results. A significant drop in capacity (e.g., 20% reduction) might indicate the battery needs servicing.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →