Capture a Full Bug Report on Android Using Developer Options

Before you start

Gather a few minutes of uninterrupted time, a USB cable (or Wi‑Fi ADB if you prefer), and a computer with adb installed. While the bug‑report feature works entirely on the device, having adb makes it easier to pull the generated zip file for deeper analysis.

Important: The bug report contains a snapshot of system logs, memory info, and potentially personal data such as app usage timestamps. Treat the file as sensitive and store it securely.

1. Enable Developer Options on your Android device

Most Android phones hide Developer Options by default. Follow these steps to reveal them:

If your device runs Android 12 or newer, the path may be Settings > System > Advanced > Developer options. The wording can differ slightly on Samsung ("Developer options" under Settings > About phone > Software information), but the tap‑seven‑times rule stays the same.

2. Turn on the bug‑report feature

Within Developer Options, locate the toggle named Take bug report or Bug report. The exact label varies:

• Pixel / AOSP: Take bug report
• Samsung: Bug report (under Developer options)
• OnePlus: Bug report

Set it to Enabled. Some OEMs also let you choose the bug‑report type – Full or Interactive. Choose Full for the most comprehensive data set.

3. Capture the bug report

Now you’re ready to generate the log bundle. There are two ways: via the UI or via adb. The UI method works on any device, while the adb method is handy when you want to script multiple captures.

3.1 UI method (no computer needed)

After saving, you’ll have a file named something like bugreport_2024-10-10_14-23-01.zip.

3.2 ADB method (optional but powerful)

If you have a computer ready, connect the device via USB (or enable adb over Wi‑Fi) and run:

adb bugreport bugreport_$(date +%F_%T).zip

The command triggers the same full bug‑report process and automatically pulls the resulting zip to the current directory on your computer. This eliminates the need to locate the file on the phone later.

4. Retrieve and explore the bug report

The zip contains several useful artifacts:

• bugreport.txt – a human‑readable summary of logs, stack traces, and system state.
• system.log – raw logcat output from the time capture started.
• event.log – event‑based logs (useful for input events).
• dumpstate.txt – a snapshot of the Android system services.
• Various .png screenshots taken automatically (if the bug report includes UI state).

To view bugreport.txt, simply open it with any text editor. For deeper analysis, you can feed system.log into logcat filters or upload the zip to Badger (an open‑source bug‑report viewer).

5. Common troubleshooting scenarios

5.1 The bug‑report shortcut never appears

• Check: Ensure Take bug report is enabled in Developer Options.
• Device‑specific quirk: Some OEM skins hide the shortcut until you pull the notification shade twice.
• Work‑around: Use the adb bugreport command instead.

5.2 Capture stalls at “Preparing bug report…”

• Reason: Low storage can prevent the system from writing the zip file.
• Fix: Free at least 200 MB of space, then retry.

5.3 The generated zip is empty or missing expected logs

• Cause: Some manufacturers restrict log access for privacy.
• Solution: Enable USB debugging (also in Developer Options) and use the adb bugreport method, which forces a more complete dump.

6. Safety and privacy considerations

Because a bug report can contain personal identifiers, treat it like a forensic dump:

• Store it on an encrypted drive.
• Do not share it publicly unless you have removed sensitive sections (you can edit bugreport.txt).
• If you are sending the report to a support team, use the device‑manufacturer’s official channel.

Disabling the feature after you’re done is a good habit. Return to Developer options and toggle Take bug report off.

7. When to use a full bug report

A full bug report is most useful when you encounter:

• Unexplained crashes that don’t produce a visible error dialog.
• Intermittent performance hiccups where you need a timeline of system events.
• Connectivity issues that may involve low‑level drivers (Wi‑Fi, Bluetooth, cellular).

For simple app‑level problems, a filtered logcat capture (via adb logcat) may be sufficient, but the full bug report saves you from hunting down missing logs later.

8. Quick recap

1. Enable Developer Options by tapping the Build number seven times.
2. Turn on Take bug report (choose Full).
3. Trigger the report via the notification shortcut or adb bugreport.
4. Save the resulting .zip and extract the logs you need.
5. Secure the file and disable the bug‑report toggle when finished.

With these steps you can capture a comprehensive snapshot of your Android device’s state, making it far easier to diagnose elusive bugs or share reproducible data with developers.