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.

macOS · Windows · Linux

EXHIBIT 01 · THE ACTIVE LOG

Indagium showing grouped USB device events, log filters, and evidence notes.
A dedicated place to retain the context around the line that matters.
Filter USB polling, expand recurring attach/detach events, and keep the evidence. · 44 sec

Exhibit 01 / Live device capture

Record logcat and screen video together. Continue after a reboot.

Connect an Android device by USB or wireless debugging, investigate the live log as you reproduce an issue, and save a ZIP snapshot by default or choose Indagium Compact (.ind) for a smaller archive opened in Indagium. If the device restarts or temporarily disconnects, the same capture waits for it and preserves the outage interval.

USB / WIRELESS / REBOOTS / SYNCHRONIZED ARCHIVE

Start with the event, finish with evidence.

Filter and annotate while capture runs. Save a snapshot without stopping, then reopen the archive to move between log rows and the recorded screen together. ZIP is the default; Indagium Compact (.ind) is an optional smaller archive for opening in Indagium. During a reboot, Indagium waits for the original authorized device and marks the time it was unavailable.

See how capture recovers through a reboot

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.

01

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.

02

Connect the clues

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

03

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

EXHIBIT D / INTERACTION DIAGRAM

Turn rows into interactions.

Build an editable sequence diagram from selected log rows or the filtered view, then review each message beside its source evidence. Unsupported targets stay visible for review.

Explore sequence diagram generation

A connected investigation

One workspace. The full record.

  1. 12:01Symptom

    The app enters the foreground.

  2. 12:01Pattern

    A request begins repeating.

  3. 12:01Root cause

    A blocking delay stands out.

  4. 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

AI test suites / Android workflows

Turn a recorded workflow into an editable Android test.

Record device actions, review the steps, then choose an AI agent to run a case on a connected device or emulator with log and screen evidence.

See how recording and AI test runs work

Case closed?

Spend less time reading noise.

Start with the evidence. Finish with an explanation.

Download Indagium