Features / Android bug reports

Open the bugreport, keep the context.

Bug reports collect more than one clue. Open an adb bugreport's .zip and .7z archives directly in Indagium, choose what to load, then work through the relevant log offline in the same investigation space — free, and without Android Studio.

Indagium annotating an Android log and preparing an export.
Choose the useful evidence before you write the explanation.

A report is a record

From archive to evidence.

A bugreport can be large and full of adjacent detail. Indagium keeps the opening step, the reading step, and the handoff step close together.

01

Open the archive directly

Open .zip and .7z Android bug reports without unpacking the archive first.

02

Choose what to load

Pick the report content that belongs in the active tab instead of losing the case in an extracted folder.

03

Investigate in place

Use filters, crash and ANR detection, thread maps, time deltas, and compare view to read the evidence.

04

Share the finding

Annotate selections with notes, images, and video frames, then export Markdown or Jira markup.

What you can open

Everything a bugreport carries.

A bugreport archive is more than one log; Indagium reads the formats inside it the same way it reads a standalone file, without unpacking anything by hand first.

01

Bugreport archives

Open the .zip or .7z produced by adb bugreport or a device's own bug report tool, and choose which section to load.

02

Logcat text

Read the logcat content inside the report in threadtime, time, brief, or bare format; unrecognised lines are tagged RAW.

03

DLT captures

Open any bundled .dlt captures or raw DLT streams as their own tab, decoded as framed records.

04

DLT Viewer exports

Open DLT Viewer text and CSV exports alongside the rest of the report, ready to filter with the same tools.

Why open it offline

The report stays on your machine.

A bugreport can contain sensitive device and app data. Indagium reads it locally as a desktop app, so nothing is uploaded unless you deliberately turn on the optional AI assistant.

A clear handoff

Keep the proof close to the claim.

The final record can include the filtered log, annotations, and the context another person needs to understand the issue without reopening the entire report, or the log viewer that produced it.

Explore log analyzer tools
Indagium synchronizing a screen recording with an Android log line.
Attach a screen recording to a log line when the visual symptom matters.

Questions

Android bug report viewer, answered.

Common questions about opening, choosing content from, and exporting from an Android bugreport in Indagium.

What bug report formats can Indagium open?

Android bug reports as .zip or .7z archives, opened directly — no manual unzip step.

Can I choose which part of the bug report to load?

Yes. Indagium lets you pick the report content that matters instead of loading everything into one tab.

Does opening a bugreport require adb or a connected device?

No — capture the bugreport once with adb bugreport, then open the resulting archive in Indagium; no device connection is needed to analyze it offline.

Can I export findings from a bug report?

Yes. Annotate selections with notes, images, and video frames, then export as Markdown or Jira markup, or export the filtered log as TXT or CSV.

Is DLT data inside a bug report supported?

Indagium opens DLT (.dlt) captures, raw DLT streams, and DLT Viewer text/CSV exports as their own tabs; support depends on what's included in the report.