android-profiler

Use the official Perfetto helper scripts such as record_android_trace with categories like sched, gfx, and wm after enabling USB debugging. The skill's recording workflow handles pushing configs, starting tracing daemons, and pulling the trace file.

Load the trace into a trace_processor session, run a system-wide triage with metrics like android_cpu and android_surfaceflinger, then investigate candidate threads by following their state transitions and dependency chains to the root cause.

Run the java_heap_dump helper script with your app's package name to capture a snapshot of all Java objects. You can then query the heap graph and dominator tree in trace_processor to find retained objects and leak paths.

Yes, but instead of adding it to PATH you invoke it as python followed by the trace_processor script path. The first invocation downloads the correct prebuilt native binary for your platform and caches it.

Common causes include guessing column names instead of checking schema with LIMIT 0, joining on tid/pid instead of utid/upid, using LIKE instead of GLOB, or missing INCLUDE PERFETTO MODULE statements for stdlib tables.

Use a custom TraceConfig when you need to combine multiple data sources in one trace, such as ftrace with heap dumps, or need controls like ring buffers and periodic file writes that the specialized helper scripts do not expose.