The Log Analysis Studio

Android logcat analysis, from noise to evidence.

Every incident has a story.

Indagium is a free, offline Android log viewer and logcat analyzer for investigating adb logcat files, bugreports, and DLT captures — from the first strange line to a clear, shareable explanation.

Get Indagium Read the analysis guide

macOS · Windows · Linux

EXHIBIT 01 · THE ACTIVE LOG

Indagium showing an Android log, a crash trace, annotations, and an AI investigation. — A dedicated place to retain the context around the line that matters.

Exhibit 01 / Live device capture

Record logcat and screen video together. Keep the timing.

Connect an Android device by USB or wireless debugging, investigate the live log as you reproduce an issue, and save a ZIP snapshot with its video and synchronization data.

USB / WIRELESS / SYNCHRONIZED ZIP

Start with the event, finish with evidence.

Filter and annotate while capture runs. Save a snapshot without stopping, then reopen the ZIP to move between log rows and the recorded screen together.

See Android logcat capture setup and workflow

01 / Read the evidence

A log viewer and log analyzer in one. Indagium helps it speak.

Work through the real sequence of events without flattening it into an endless stream of text. Filter, compare, fold recurring behavior, connect source and video, and leave an explanation the next person can follow.

Read the log

Open logcat .txt/.log files, Android bugreports, large traces, and supported DLT captures in a calm, native workspace — no Android Studio required.

Connect the clues

Follow the timing, repetition, thread activity, source, and video around an incident.

Explain the finding

Annotate the proof and export a record that is useful outside the app.

Collected evidence

Find the moment your logcat changed.

EXHIBIT A / REMOVE THE NOISE

Filter for the signal.

Combine level, tag, package, message, PID, and TID rules without changing the original log.

See log analysis features

EXHIBIT B / RECURRING PATTERN

Fold repetition into meaning.

Collapse recurring behavior, surface crashes, and see the structure inside a busy trace.

Explore the viewer

EXHIBIT C / THE RECORD

Leave a defensible record.

Add notes and context, then export evidence others can understand without reopening the whole log.

Work with bug reports

A connected investigation

One workspace. The full record.

12:01Symptom
The app enters the foreground.
12:01Pattern
A request begins repeating.
12:01Root cause
A blocking delay stands out.
12:02Report
The proof is annotated and shared.

Exhibit D / Assisted investigation

Ask better questions of the evidence.

Bring your preferred local or hosted AI provider into the active log, or connect any MCP client to Indagium’s own local MCP server. The assistant can investigate using Indagium’s tools, while every file-changing action stays under your control.

Explore the AI assistant and MCP server

Exhibit E / Corroborating evidence

Connect what happened to what you saw.

Attach a screen recording to a log line and move through them together. When a visual symptom needs an exact timestamp, the evidence remains in one place.

Explore video sync

Case closed?

Spend less time reading noise.

Start with the evidence. Finish with an explanation.

Download Indagium