android-trace-sections

Use Perfetto-based trace sections to instrument Android apps by wrapping suspect code blocks with Trace.beginSection or AGENT_TRACE labels. This provides per-thread visibility and frame-boundary correlation to quantify timing during jank analysis and cold-start optimization.

Mapping execution timing to frame budgets requires applying Perfetto trace sections in hot paths to diagnose slow startup and thread contention. Capturing traces on-device or host provides the precise timing and thread context needed for the performance investigation.

Using Perfetto trace sections for Android profiling requires androidx.tracing or android.os.Trace with appropriate minSdk support. You must also integrate with trace-capture and analysis tools to complete the end-to-end performance workflow.

Analyze Perfetto traces by running trace_processor queries to identify main-thread usage and frame correlation. This provides per-thread visibility and precise timing to answer what happened when during performance investigations.

Use trace sections instead of logging when Android performance analysis requires precise timing and thread context beyond logs. Trace sections provide per-thread visibility and frame-boundary correlation necessary for jank analysis and cold-start optimization.