Android Dumpstate Analysis: 3 System Diagnostics Worth Running
How to access the Android dumpstate log on Samsung, Pixel, and Motorola phones and use it to check battery health, rogue wakelocks, and disk write latency.
Android phones quietly log thousands of system events every day, and that data is accessible through a built-in diagnostic file called the dumpstate. On Samsung devices, a dial code pulls up the full log in minutes. On Pixel and Motorola phones, developer options offer the same. ZDNet senior editor Kerry Wan walked through three practical data points the log surfaces: battery degradation, apps that silently drain power overnight, and storage performance issues that slow read/write speeds.
What happened
| Detail | Value |
|---|---|
| Samsung dial code | *#9900# |
| Google/Motorola dial code | *#*#7262626#*#* |
| Battery replacement threshold (capacity) | Below 75% of original |
| Battery replacement threshold (cycles) | Over 500 charge cycles |
| High disk write latency flag | Write MS value over 200ms |
The dumpstate is a system-level log file that records every significant action your Android phone performs: charge cycles, app activity, background CPU usage, and storage read/write operations. It has always been there. Most users never look at it.
Kerry Wan at ZDNet published a practical guide on August 5, 2026 explaining how to pull the file and what to search for once you have it.
How do you access the dumpstate on Android?
The method varies slightly by manufacturer.
- Samsung: Open the Phone app, dial *#9900# to open the SysDump menu, tap “Run dumpstate/logcat,” and then “Copy to phone_storage.” If the code is blocked, disable Samsung’s Auto Blocker feature first.
- Google Pixel and Motorola: Dial *#*#7262626#*#* to trigger a bug report download. Alternatively, enable developer options, tap “Take bug report,” choose interactive or full, and save to Google Drive or local storage.
The resulting file is plain text. Search for specific terms within it to find the data points that matter.
3 diagnostics worth checking
1. Battery health and charge cycles
Search the log for dumpsys batterystats. This section contains a charge counter value and a design capacity figure. Divide the charge counter by the design capacity to get your current battery health as a percentage.
According to Wan, a battery below 75% capacity combined with more than 500 charge cycles is a reliable signal to replace the battery before spending money on a new phone. Many people upgrade hardware when a battery swap costing a fraction of the price would restore most of the performance.
2. Rogue wakelocks draining the battery overnight
A wakelock is a software instruction that prevents the phone’s CPU from entering a full sleep state. Legitimate apps use them briefly. Some apps, particularly those with aggressive background tasks or always-on location services, hold wakelocks for hours.
Search for statistics since last charge or dump of service wakelock to see which apps hold wakelocks and for how long. Compare those durations against your phone’s screen-off time, which is listed in your power settings. Wan found his Instagram app, specifically its location services, running for six to eight hours overnight. He resolved it by revoking location permissions for that app.
3. Disk write latency and log file buildup
Search for DUMP OF SERVICE diskstats and look at the Write MS value. Anything over 200ms indicates the phone’s internal storage is struggling under load, which can make the whole device feel sluggish even if the processor is fine.
Part of the cause can be the dumpstate logs themselves. Even when you do not request one manually, Android phones generate system reports periodically for tracking purposes. These files can accumulate to several gigabytes. On Samsung devices, you can delete them directly from the SysDump menu.
Why it matters
Most people troubleshoot slow phones by clearing the app cache or buying a new handset. The dumpstate gives you the specific reason performance has dropped, whether that is a degraded battery, one misbehaving app, or storage congestion.
For small businesses that rely on phones for customer calls, field work, or mobile payments, this kind of diagnostic takes under 30 minutes and can extend a device’s useful life by a year or more. That is worth knowing before approving a hardware refresh.
The same principle applies to anyone managing a fleet of devices. If a staff member’s phone is constantly dying or running hot, the wakelock data points directly at the culprit app rather than requiring a factory reset and hours of setup time.
Our take
This is a genuinely useful tutorial buried under a clickbait framing. The three diagnostics Wan highlights, battery health, wakelocks, and disk latency, are the same things IT support checks first. The fact that you can get this data from a dial code without root access or ADB is a practical win for anyone comfortable with a text search.
The 75% capacity and 500-cycle thresholds are reasonable rules of thumb, though the relationship between the two matters: a phone at 78% capacity after 600 cycles may still be worth replacing, while one at 74% after 200 cycles suggests a different problem. Use the numbers as a starting point, not a hard cutoff.
If you are running AI tools or automation workflows on mobile, background wakelock abuse is especially relevant. Apps that poll APIs or sync data continuously are exactly the kind of process that shows up as a six-hour overnight wakelock. Knowing which app to restrict is faster than guessing.
For a broader look at how we approach device and workflow performance for clients, see our client project case studies.
What to do about it
- Dial the appropriate code for your device and download the dumpstate log.
- Search for dumpsys batterystats and calculate your battery health percentage using the charge counter and design capacity values.
- Search for dump of service wakelock and compare app durations against your overnight screen-off time.
- Revoke background location or activity permissions for any app with suspiciously long real-time wakelock durations.
- Search for DUMP OF SERVICE diskstats, note the Write MS value, and delete old system logs from the SysDump menu if you are on Samsung.
Run this check every six months or any time your phone starts feeling slower than expected.
Frequently asked questions
What is a dumpstate on Android?
A dumpstate is a system diagnostic log that records thousands of actions your Android phone performs, including charge cycles, app activity, background CPU usage, and storage operations. It can be accessed without rooting the device.
How do I access the dumpstate on a Samsung phone?
Open the Phone app, dial *#9900# to open the SysDump menu, tap 'Run dumpstate/logcat,' and then tap 'Copy to phone_storage.' If the code is blocked, disable Samsung's Auto Blocker feature first.
When should I replace my Android phone battery?
A commonly cited threshold is when battery capacity drops below 75% of its original design capacity combined with more than 500 charge cycles. You can calculate this from the dumpsys batterystats section of the dumpstate log.
What is a wakelock and why does it drain my battery?
A wakelock is an instruction that prevents the phone's CPU from fully sleeping when the screen is off. Apps with aggressive background tasks or always-on location services can hold wakelocks for hours, draining the battery significantly overnight.