Home Page » News » Tutorials » How to Capture a Full Android Bug Report Using Developer Options and ADB

Capture a Full Android Bug Report with Developer Options and ADB

13 min read Learn step‑by‑step how to generate a complete Android bug report via Developer Options and ADB, extract the logs, and safely analyze them for troubleshooting. September 28, 2026 22:00

Why a Full Bug Report?

When an app crashes, a feature misbehaves, or you need to hand a device over to support, a bug report provides a snapshot of the system state. It bundles logcat output, stack traces, tombstones, and a copy of the current UI hierarchy. Developers and support engineers rely on this data to reproduce the issue and pinpoint the root cause.

Android offers two ways to generate a bug report: through the on‑screen Take bug report option in Developer Options, and via the command‑line tool adb bugreport. The latter is especially handy when you need the report on a PC for deeper analysis.

When to Use This Tutorial

You are experiencing a persistent crash or unexpected behavior and need detailed logs.
You want to share diagnostic data with a developer without installing extra apps.
You are a power user who prefers a command‑line workflow.

Before You Start

Gather the following items to avoid interruptions:

A Windows, macOS, or Linux PC with Android Platform‑Tools (ADB) installed.
A USB cable that supports data transfer (or a reliable Wi‑Fi ADB connection).
At least 30 % battery on the Android device.
Free internal storage (the bug report can be 150 MB – 300 MB depending on device activity).
Patience – generating a full bug report may take 1‑3 minutes.

Step 1 – Enable Developer Options and USB Debugging

Open Settings on the Android device.
Navigate to About phone → Software information (the exact path can vary by manufacturer).
Tap Build number seven times. You’ll see a toast confirming "You are now a developer!".
Return to the main Settings screen; a new entry Developer options appears.
Enter Developer options and toggle USB debugging on. Confirm the security prompt.

Why? USB debugging grants ADB the permission to communicate with the device and to pull system files needed for a complete bug report.

Step 2 – Connect the Device to Your PC

Plug the USB cable into the phone and the PC.
On the phone, you may see a dialog "Allow USB debugging?". Check Always allow from this computer and tap OK.
Open a terminal (Command Prompt, PowerShell, or macOS/Linux shell) and verify the connection:
```
adb devices
```
You should see the device’s serial number followed by device.

If the device shows as unauthorized, re‑accept the debugging prompt on the phone.

Step 3 – Choose the Bug Report Type

Android offers two report flavors:

Full bug report – captures everything (logcat, tombstones, system traces, UI hierarchy). Best for developers.
Interactive bug report – lets you add a short description before the capture starts. Useful for end‑user support.

For this tutorial we focus on the Full bug report because it contains the most data for analysis.

Step 4 – Initiate the Bug Report from the Device

Open Settings → Developer options.
Scroll down to the Bug report section.
Tap Take bug report. A dialog appears asking for the report type – choose Full report.
Tap Report. Android will display a progress spinner and a notification indicating that the bug report is being generated.

What you should see: After a short wait, a notification reads "Bug report saved" and offers a Share button.

Step 5 – Retrieve the Report via ADB (Preferred Method)

While you can tap the notification to share the zip file, pulling it with ADB guarantees the file lands in a known location and avoids accidental truncation.

Open a terminal on your PC.
Run the following command, replacing mybugreport.zip with a name of your choice:
```
adb bugreport mybugreport.zip
```
ADB will start the same internal capture process that the UI uses, then stream the resulting zip file to your current directory.
When the command returns to the prompt, the file mybugreport.zip is ready.

On Windows, you may need to use adb.exe and ensure the terminal’s working directory is writeable.

Step 6 – Extract and Explore the Contents

The bug report zip contains several files:

File	Purpose
`bugreport.txt`	Human‑readable concatenation of logcat, kernel logs, and system state.
`system_log.tar.gz`	Compressed logs from various system services.
`tombstones/`	Native crash dumps (core‑like files) for native code crashes.
`dumpstate/`	UI hierarchy snapshots (XML) and screenshots taken at the moment of capture.

Use any archive manager (7‑Zip, WinRAR, or the built‑in macOS Archive Utility) to extract the zip. Open bugreport.txt in a text editor and search for keywords like FATAL EXCEPTION, ANR, or the package name of the problematic app.

Step 7 – Analyze the Log for Common Issues

Below are three typical patterns you might encounter:

Java crashes – Look for lines starting with E/AndroidRuntime followed by a stack trace. The Caused by: clause often points to the offending class.
Native crashes (ABI mismatch, missing libraries) – Inspect the tombstones/ directory. Each file is named after the process ID and contains a backtrace from the native debugger.
ANR (Application Not Responding) – Search for ANR in entries. The report will include the UI thread state and any blocked resources.

If you need to share the report with a developer, compress the entire extracted folder (excluding any personal screenshots) and send it via a secure channel.

Step 8 – Clean Up Sensitive Data

Bug reports can contain personal information: usernames, URLs, location data, and even clipboard contents. Before uploading the zip to a public forum, either redact the sensitive sections in bugreport.txt or use a tool like sed to strip lines matching known patterns.

Alternative: Using ADB Over Wi‑Fi

If a USB cable is inconvenient, you can enable wireless ADB:

Connect the phone via USB once and run adb tcpip 5555.
Find the device’s IP address (Settings → About phone → Status → IP address).
On the PC, run adb connect device_ip:5555. You should see "connected to device_ip".
Proceed with adb bugreport as described in Step 5.

Wireless ADB is slower and less stable on congested networks; use a wired connection for the most reliable capture.

Troubleshooting Common Issues

Bug report generation hangs or never finishes
- Ensure the device has enough free storage (at least 200 MB). Delete unnecessary files or move media to a computer.
- Restart the device and try again; a fresh boot clears temporary buffers that can block the capture.
ADB reports "device offline"
- Re‑plug the USB cable, accept the debugging prompt again, or restart the ADB server with adb kill-server && adb start-server.
Permission denied when pulling the bug report
- On Android 12+, the bug report is saved under /data/local/tmp, which is only accessible to ADB with root or privileged debugging. Using the adb bugreport command bypasses this restriction because it streams the data directly.

Best Practices for Ongoing Diagnostics

Keep a short adb logcat -b all -v threadtime > recent.log buffer on hand for quick, lightweight captures.
When reporting a bug to a developer, include:
1. Device model and Android version.
2. Exact steps to reproduce the issue.
3. A reference to the relevant section of the bug report (e.g., "see line 342 in bugreport.txt for the stack trace").
Store bug reports in an encrypted folder (e.g., using VeraCrypt) if you keep them for later analysis.

Wrapping Up

Capturing a full Android bug report is a powerful, low‑overhead way to gather the exact data developers need to fix a problem. By following the steps above you can generate the report, retrieve it safely with ADB, extract the relevant logs, and share only the information that matters while protecting your privacy.

With this workflow in your toolbox, you’ll spend less time guessing and more time providing concrete evidence—making the troubleshooting loop faster for you and anyone you collaborate with.

User Comments (0)

Add Comment

No comments added yet.

Add Comment

Your Name: *

Comment Title: *

Your E-mail: * We'll never share your email with anyone else.

Your Comment: *

Comments will not be approved to be posted if they are SPAM, abusive, off-topic, use profanity, contain a personal attack, or promote hate of any kind.