How to Inspect Bugreport Generation and Diagnostic Sessions on Android Using ADB dumpsys bugreport

In Android platform diagnostics, generating system bug reports is the authoritative method for capturing system logs, kernel dmesg ring buffers, thread stack dumps, memory snapshots, and battery telemetry into a consolidated diagnostic archive. Historically initiated exclusively via the monolithic bugreport shell binary, modern Android versions orchestrate diagnostic collection through BugreportManagerService. This privileged framework service manages active dumpstate processes, enforces calling application security permissions, tracks percentage completion progress, and coordinates file descriptor sharing for telemetry export. Using the Android Debug Bridge (ADB) to execute dumpsys bugreport, platform engineers, QA automation specialists, and enterprise fleet administrators can monitor in-progress report sessions, diagnose capture timeouts, and inspect framework dumpstate listeners.

Architecture of the Android BugreportManager Subsystem

The Android bug report architecture resides within com.android.server.os.BugreportManagerService, which acts as a secure IPC wrapper around the native dumpstate executable. When an application, system UI handler, or ADB command initiates a report, the service coordinates several critical components:

• Native dumpstate Daemon: Spawns under root/system privileges to query hardware subsystems, dump system services via dumpsys, pull tombstone crash logs, and serialize output into compressed zip packages.
• Bugreport Callback Listener: An asynchronous IPC interface (IDumpstateListener) providing real-time progress callbacks (from 0% to 100%) and error status notifications back to the requesting client.
• Mode Enforcers: Governs whether a capture operates in FULL mode (standard comprehensive capture), INTERACTIVE mode (user-initiated with system UI notifications), WIFI mode (specialized radio/telecom logging), or TELEPHONY mode.
• Caller Security Verification: Enforces the privileged android.permission.DUMP and android.permission.BUGREPORT permissions, ensuring third-party applications cannot siphon sensitive user or system telemetry without explicit user authorization.

Extracting Bugreport Subsystem Diagnostics via ADB

To inspect the status of the BugreportManager service on an active device or emulator, execute dumpsys bugreport from an ADB shell session:

# Extract complete BugreportManagerService diagnostic telemetry
adb shell dumpsys bugreport

# Filter for active sessions and listener registrations
adb shell dumpsys bugreport | grep -E "Active|Session|Caller|Progress"

When no diagnostic collection is currently taking place, the dump reports an idle state (No active bugreport sessions) while confirming that the listener dispatch thread is alive and listening on system binder sockets.

Monitoring Active Bug Report Progress and Caller Details

Because full system bug reports can take between one and four minutes to assemble across complex device environments, inspecting dumpsys bugreport during capture provides real-time visibility into the operation:

# Trigger an asynchronous interactive bug report via ADB
adb bugreport ./bugreport_output.zip &

# Monitor the active dumpstate session in another terminal
adb shell dumpsys bugreport

Review the active session parameters revealed in the output:

• mCallingUid and mCallingPackage: Identifies the user ID and process name that triggered the collection (e.g., com.android.shell when invoked via ADB, or com.android.systemui when triggered via Developer Options).
• mProgress: Displays the current percentage completion reported by the native dumpstate engine as it cycles through system service audits, kernel buffers, and tombstone captures.
• mMode: Confirms the operational scope (e.g., BUGREPORT_MODE_FULL or BUGREPORT_MODE_INTERACTIVE).
• mOutFile: Details the target file descriptor and destination path where the compressed diagnostic archive is being assembled.

Diagnosing Capture Timeouts and Daemon Deadlocks

If a bug report capture freezes or fails to complete, the diagnostic dump highlights underlying service blockages:

• Service Hangs During dumpstate: When dumpstate queries individual services using dumpsys, a hung service (such as an unresponsive sensor HAL or audio routing pipeline) can block the dumping thread. Look at the last logged progress checkpoint to identify which subsystem stalled the collection.
• Storage Exhaustion: Bug reports require several hundred megabytes of temporary workspace inside /data/user_de/0/com.android.shell/files/bugreports/. If device storage is nearly exhausted, the service aborts with an I/O error token.
• Consent Timeouts: On user-facing builds, the system UI displays an interactive dialog requesting consent before sharing the report. If the prompt is ignored, the session expires after a predetermined timeout window.

Programmatic Bug Report Verification for Automation Pipelines

For automated continuous integration (CI) and fleet test benches, polling dumpsys bugreport allows test runners to detect when an asynchronous capture completes before pulling artifacts:

# Shell script loop to verify bugreport completion
while adb shell dumpsys bugreport | grep -q "Active session"; do
    echo "Bugreport is currently generating..."
    sleep 5
done
echo "Bugreport generation finished."

Inspecting the bugreport subsystem via ADB provides transparency into platform diagnostics, streamlines QA reporting pipelines, and ensures robust diagnostic artifact collection across Android enterprise environments.