Skip to main content
Introducing logcat.ai PlaygroundRead

Part of the logcat.ai Platform

From Baseband to Framework
in One Investigation

Not just a telecom log viewer. logcat.ai reconstructs the device-side modem stack end-to-end (chipset baseband, RIL, IMS, and Android telephony framework) and traces failures across the proprietary boundary in a single investigation.

Why Modem Stack Debugging Is Hard

Device-side connectivity crosses chipset baseband, RIL, IMS, framework, and audio HAL, and a single fault touches all of them

Protocol Complexity

NAS, RRC, SIP, RTP, GTP: hundreds of message types across multiple protocol layers, each with their own state machines and failure modes.

VoLTE/VoNR Call Setup Failures

A single VoLTE or VoNR call touches RRC connection setup, NAS attach, IMS registration, SIP INVITE, and RTP negotiation. Failure at any point kills the call.

Needle in a Haystack

Thousands of repetitive PHY/MAC entries, periodic measurement reports, and routine signaling: the actual issue is often buried in a sea of normal traffic.

Cross-Layer Correlation

When the modem reports a failure, is it a radio issue, a network reject, a SIM problem, or an Android framework bug? Connecting events across layers requires deep expertise.

Two Days of Manual Work, or Five Minutes

Traditional telecom debugging requires multiple specialized tools, manual timestamp correlation, and deep domain expertise. logcat.ai collapses the entire workflow into a single question.

The Manual Way
§ 01

Open QXDM / QCAT: Load DLF, filter NAS + RRC messages manually

§ 02

Open logcat separately: Search for IMS / telephony tags manually

§ 03

Open vendor thermal tool: Cross-reference kernel thermal zone timestamps

§ 04

Manual timestamp alignment: Correlate events across 3+ tools by eye

§ 05

Build the timeline: Paste findings into a spreadsheet or doc

§ 06

Write root cause report: Summarize findings for the team

Σ

~2 days, 3+ tools, senior engineer required

With logcat.ai
§ 01

Upload your logs: QCAT exports, logcat, dmesg, bugreport — all in one upload

§ 02

Ask your question: "Why did the VoLTE call drop at 14:32?"

§ 03

Get the full cross-layer root cause: Deep Research traces RRC, NAS, SIP, IMS, and kernel events automatically

Σ

~5 minutes, 1 platform, any engineer

Compare multiple log sets side-by-side with Delta to find regressions across firmware versions.

Built for Telecom Engineers

Purpose-built AI analysis tools that understand 4G LTE and 5G NR protocols

Deep Research

Multi-step AI investigation within a single log file. Ask questions like 'trace the attach failure through NAS messages' and the AI iteratively searches, analyzes, and builds a complete investigation.

Delta Cross-Layer Analysis

Upload multiple files (modem export, logcat, and dmesg) and Delta correlates events across all layers. See how a modem-layer event connects to the Android framework.

Learn more about Delta
Protocol-Aware Analysis

logcat.ai understands NAS message flows (EMM/ESM and 5GMM/5GSM), RRC state transitions, SIP dialog sequences, and their interdependencies across LTE and 5G NR, not just text pattern matching.

AI Root Cause Analysis

Pattern recognition across thousands of log lines identifies the root cause, not just the symptom. Trained on real-world telecom failure patterns.

Cross-Layer Correlation with Delta

See how Delta correlates events across modem logs, logcat radio, and kernel dmesg to find the real root cause

Delta Correlation Engine

Multi-file cross-layer analysis

Uploading
Modem Export
14:32:03 NAS: Attach Request sent
14:32:04 NAS: Auth Response OK
14:32:05 NAS: Attach Reject #19
14:32:06 NAS: Detach Request
Logcat Radio
14:32:03 RIL: requestSetup
14:32:04 RIL: setRadioPower ON
14:32:05 RIL: registration failed
14:32:06 RIL: dataCallListChanged
IMS SIP Trace
14:32:03 INVITE sip:+1555@ims.net
14:32:04 100 Trying → 183 Progress
14:32:05 503 Service Unavailable
14:32:06 BYE → session terminated

Upload multiple log files for comparison

Who Uses This

Built for device-side modem and connectivity teams

Modem Integration Engineers

Chipset and OEM engineers debugging NAS attach failures, handover issues, RRC connection problems, and modem firmware crashes across the proprietary boundary.

VoLTE/VoNR/IMS Engineers

Engineers working on VoLTE and VoNR call setup, IMS registration flows, SIP signaling, and voice quality across the IMS framework and chipset audio HAL.

Field Test Engineers

Drive test and field validation engineers analyzing coverage investigations, handover performance, and device-network interaction across regions.

What We Analyze

Upload plaintext modem-stack logs from any of these sources for AI-powered analysis

Modem Diagnostic Logs

Plaintext modem diagnostic logs from any vendor: Qualcomm QCAT exports, MediaTek MTKLogger output, Samsung Shannon modem logs, or any tool that produces decoded NAS, RRC, PHY, and MAC messages.

Logcat Radio Logs

Android logcat output focused on telephony: RIL messages, TelephonyManager events, IMS registration, and modem trace data.

Dmesg Kernel Logs

Linux kernel logs from the modem subsystem: driver initialization, firmware loading, crash traces, and hardware-level modem events.

IMS/VoLTE/VoNR Captures

Network packet captures containing SIP signaling, IMS registration flows, and VoLTE/VoNR call setup messages for voice-over-IP debugging.

How to Export Your Logs

Step-by-step guides for capturing the right logs for analysis

Qualcomm (QCAT)
  1. § 01Capture diagnostic logs using QXDM Professional
  2. § 02Open the captured log file in QCAT
  3. § 03Go to Tools → Convert log to TXT
  4. § 04Upload the exported .txt file to logcat.ai
MediaTek (MTKLogger)
  1. § 01Capture modem logs using MTKLogger (DebugLoggerUI on Android 10+). Access via *#*#3646633#*#*
  2. § 02Modem logs (mdlog) are in binary format. Decode using MediaTek ELT tool
  3. § 03Export decoded logs as plaintext
  4. § 04Upload the exported text file to logcat.ai
Samsung (Shannon/Exynos)
  1. § 01Capture CP logs via Samsung SysDump. Dial *#9900# and run CP-based log
  2. § 02Decode logs using ShannonDM (Exynos) or QXDM/QCAT (Snapdragon)
  3. § 03Export decoded logs as plaintext
  4. § 04Upload the exported text file to logcat.ai
Radio Logcat
  1. § 01Connect device via ADB
  2. § 02Run: adb logcat -b radio > radio.log
  3. § 03Upload the saved log file to logcat.ai
Σ
Plaintext required

All logs must be in plaintext format. Binary proprietary formats must first be exported to text using their respective vendor tools. We also accept Android logcat, kernel (dmesg) logs, and bugreports to assist with investigation. Note: vendor tool workflows may change across versions. Refer to your vendor's documentation for the latest steps.

Common questions

Frequently Asked Questions

Common questions about modem-stack log analysis

We support any plaintext log file: modem diagnostic exports from Qualcomm QCAT, MediaTek MTKLogger, Samsung CP logs, Android logcat (including radio buffer), dmesg/kernel logs, and pcap captures. The key requirement is that logs must be in human-readable text format.

For a Qualcomm baseband capture, no. Upload it as it came off the device and we decode it for you. For other vendors you will still need their tools to capture and export modem diagnostic logs as plaintext: MediaTek ELT, Samsung ShannonDM, and so on. Either way, logcat.ai itself requires no special tools or plugins. If you already have plaintext logs from logcat, dmesg, or other sources, you can upload those directly.

Some of them. Qualcomm baseband captures upload directly, as they came off the device, and are decoded for you with no conversion step and no vendor tool. Other proprietary binary formats (MediaTek MCL, Samsung, and the rest) still need exporting to plaintext with their own vendor tools first, and we work with any plaintext output regardless of which tool produced it. Recognition is by content, not by file extension, so a renamed capture still works.

Our AI understands NAS (EMM/ESM for LTE, 5GMM/5GSM for NR), RRC, SIP/IMS, MAC/PHY layer messages, and their interactions. It can trace issues across protocol layers and identify root causes. This is not an exhaustive list. The AI works with any plaintext protocol messages including GTP, RTP, PDCP, RLC, and others as long as they appear in your logs.

Deep Research performs multi-step AI investigations within your log file. It iteratively searches for relevant events, follows protocol flows across baseband and framework, and builds a comprehensive analysis, similar to how an expert engineer would manually trace through the logs, but in seconds.

Deep Research investigates a single log file in depth: it searches, analyzes, and follows protocol flows within one file. Delta is a multi-file comparison engine: you upload two or more log files (e.g., modem export + logcat radio + kernel log) and Delta correlates events across all of them. Use Deep Research when you have one file and a question. Use Delta when you need to connect events across multiple files, compare behavior between devices, or track down cross-layer issues.

Yes. Your logs are processed in isolated environments, encrypted at rest and in transit, and never shared between users. We understand modem and baseband logs may contain sensitive vendor and network details. See our privacy policy for full details.

Modem · NAS · RAN

Start Analyzing Your Modem Stack Logs

Upload your baseband exports, logcat radio output, or kernel traces and let logcat.ai do the heavy lifting across the device-side stack