perfetto-trace-analysis

Android UI jank root cause analysis uses Perfetto trace files to identify latency, memory pressure, or rendering issues. The Skill applies an evidence-first workflow to iteratively form hypotheses, collect metrics, and drill down to verified causes across app and system activity.

SQL queries debug Android performance in Perfetto traces by validating schemas, ensuring idempotency, and applying overlap-safe time filtering. The Skill reads the SQL reference and follows its Execution Protocol to connect symptoms to thread and process states.

Diagnosing memory pressure and latency in Android apps requires analyzing Perfetto trace data across CPU, Graphics, I/O, IPC, Memory, and Power domains. The Skill applies expert-vetted techniques and domain-aware investigation to isolate package-specific performance problems.

Perfetto trace analysis connects UI jank symptoms to thread states through a chain-of-evidence scratchpad and schema-validated SQL queries. It requires overlap-correct time filtering to accurately map dependencies between process states and performance bottlenecks.

Investigating Android app slowness with Perfetto requires a Perfetto trace file containing app and system activity data. The Skill analyzes this trace input to answer broad questions about app performance or perform targeted, package-specific diagnoses.

Perfetto SQL queries return incorrect data during trace analysis when they lack schema validation or overlap-safe time filtering. The Skill enforces strict compliance with the SQL reference Execution Protocol to ensure correct schemas, modules, and idempotency in query results.