SQLite snapshots & btsnoop

Two more binary formats that logcat.ai decodes and analyzes directly. Upload them as-is, no text export step.

SQLite snapshots

Upload a SQLite database file (for example a Gralloc, settings, or telephony database pulled from a device) and the platform decodes it and reads its tables.

Beyond standalone analysis, a SQLite snapshot is especially useful inside a multi-file upload, where it acts as a reference table that resolves opaque identifiers in the sibling logs. A fingerprint or device-registry database uploaded alongside a Wi-Fi or Bluetooth log lets the platform turn anonymous MAC addresses or IDs in those logs into named entities automatically. See Multi-file bundles.

btsnoop (Bluetooth HCI)

Upload a btsnoop capture (the Bluetooth HCI snoop log Android records, btsnoop_hci.log) and the platform decodes the HCI packets for analysis. Useful for pairing failures, connection drops, and profile-level Bluetooth issues.

Send the capture as its own upload. A bugreport archive also carries a small Bluetooth log, but that one is a short rolling buffer of recent radio activity rather than a full capture, so it is not analyzed as one. To get a full capture, turn on the Bluetooth HCI snoop log in Developer options, reproduce the problem, then pull the file and upload it here.

Example questions to ask

Ask from the Research tab once the file is analyzed. These target a btsnoop capture; a SQLite snapshot is usually a reference table read alongside its sibling logs. Reach for Quick Search when you already know what you’re after, Deep Research when you need the root cause.

Quick Search for fast, cited lookups:

  • “Which devices connected over Bluetooth?”
  • “Show me the HCI command errors.”
  • “Which Bluetooth profiles were used?”

Deep Research for multi-step root-cause investigations:

  • “Why did the Bluetooth connection keep dropping?”
  • “Trace the pairing failure back to its cause.”

See Quick Search and Deep Research for how the two modes differ.

Next