TabQA logoTabQA

Android QA tool

How to collect logcat for a reproducible Android bug report

A log snippet is rarely enough. A useful report aligns time, device context, repro steps, visuals, and the relevant error window.

The traditional ADB workflow

If Android Platform Tools are already installed, use this sequence to capture the relevant log window.

Confirm the deviceadb devices
Clear stale logsadb logcat -c
Start writing a fileadb logcat -v threadtime > bug-logcat.txt
Find the foreground appadb shell dumpsys window | grep mCurrentFocus
Generate a full system reportadb bugreport bugreport.zip
Full logcat and bugreport archives can contain information from other apps, account identifiers, or device context. Filter and redact before sharing.

What a useful bug report contains

  1. A specific title and timestamp
  2. Phone model, Android version, and target package
  3. The shortest reproducible steps
  4. Expected and actual results
  5. Video or screenshots around the issue
  6. Warnings, errors, crashes, or ANRs from the same time window

Do not want to configure ADB? Put the workflow into one TabQA capture

TabQA connects over Chrome WebUSB, records video, screenshots, and logcat while you reproduce the issue, then filters around the target app and failure context.

Add to ChromeRead the TabQA docs