The main report
A single large text file, usually named bugreport-*.txt, holding the dumpstate output — the bulk of the archive, and the file Indagium treats as the primary log candidate.
Guide / Android bug report
Open an Android bug report and find what broke.
A bug report bundles a whole device's worth of context into one .zip. This guide covers the whole trail for how to open an Android bugreport in Indagium: capture it, open the archive directly, pick the right entry, and read it as evidence instead of a wall of dumpstate text.
From archive to answer
Five steps from bugreport to root cause.
A bug report is only useful once someone has actually read it. The five steps below take you from a raw .zip on disk to a written finding, without a detour through a file manager or a text editor.
- 01
Capture the bug report
From a computer with USB debugging on, run
adb bugreport bugreport.zip. That single command pulls a full report over the connected cable and writes it straight to a.zipfile. On the device itself, enable Developer options and use Take bug report instead — useful when you don't have adb handy, or the person hitting the bug isn't the one who will read the log. Both paths end at the same kind of archive. - 02
Open the archive directly
Drop the
.zipor.7zon the Indagium window, or use the toolbar's Open dialog. It scans the archive for log candidates — logcat dumps, ANR traces — without you unpacking anything first, then shows a picker rather than dumping the raw archive listing on you. - 03
Choose what to load
Pick the entry that matters for this investigation. You can open several candidates at once, each in its own tab, so a suspect ANR trace and the main logcat dump don't have to compete for the same view. If the archive also holds a screen recording, attach it to the tab in the same step instead of hunting it down afterward.
- 04
Find crashes and ANRs
Crash, ANR, and native-crash detection has already run by the time the tab opens — stack traces are folded automatically, so you can jump to the Crashes category and select the fatal exception instead of scrolling a dumpstate file that can run to tens of thousands of lines. Custom issue rules can add your own categories on top of the built-in ones.
- 05
Export the record
Select the exception and its stack, add an annotation, then export it as Markdown or Jira markup from the Notes panel — ready to paste into a ticket. Export the filtered log itself to TXT or CSV from the log toolbar when the raw rows need to travel with the write-up too.
Know the archive
What's actually inside a bugreport zip.
A bug report is not one log file — it is a snapshot of the device's diagnostic state at the moment it was taken. Knowing the shape helps you find the useful part faster instead of scrolling the whole thing top to bottom.
The logcat buffers
Inside that file, the system, event, radio, and main logcat buffers appear one after another, alongside process and service dumps captured at the same moment.
ANR traces
When an app hung, its stack traces at the moment of the ANR are typically captured as their own section or file in the archive, separate from the main report.
Other files
Depending on the device and how the report was taken, expect extras alongside the main report — a screenshot is a common one, and a screen recording if one was running.
Questions
Reading a bug report, answered.
How do I capture an Android bug report?
Run adb bugreport bugreport.zip from a computer with USB debugging enabled, or use Developer options → Take bug report directly on the device. Both hand you a .zip to open.
What's inside a bugreport zip?
A large main text file (dumpstate output, including the logcat buffers) plus, depending on the device, separate files such as ANR traces and a screenshot alongside it.
Can Indagium open a bug report zip directly?
Yes — drop the .zip or .7z on the window and Indagium scans it for log candidates and offers a picker, no manual unzipping needed.
How do I find crashes and ANRs once it's open?
Crash, ANR, and native-crash detection runs automatically on the loaded entry, folding stack traces so you can jump straight to the Crashes category.
Keep going