himattm

Use to find stuck coroutines, leaked jobs, and suspended awaits with no resumer — the concurrency bugs that don't crash but cause hangs…

Use to flush out intermittent crashes and ANRs ("it crashes sometimes," "fails on slow devices," "happens after rotation a few times") by…

Use to extract concrete numbers and slice-level evidence from a `.perfetto-trace` captured by `android-perfetto-capture`.

Use to capture Perfetto system traces from a connected Android device — the input for any timing, threading, jank, or "is this on the main…

Use when you need empirical proof a code path actually executed — branch entries, callback fires, coroutine continuations, suspect early…

Use INSTEAD of git bisect when investigating a regression between two refs (releases, branches, "it worked yesterday") — especially when…

Use BEFORE fixing any non-trivial bug. Write a test that fails because of the bug, watch it fail, then fix the bug until the test passes…

Use to flip framework-level diagnostics without code changes — verbose framework logging (`log.tag.<Tag> VERBOSE`), view-bounds overlay…

Use to prove (or disprove) that a state actually changed between two points — "did the dialog dismiss?", "did this navigation actually…

Use to surface invisible main-thread I/O, leaked closeables, leaked activities, and other policy violations that don't crash but cause…

Use to answer questions logging can't — "did this run, on what thread, for how long, in what overlap with frame boundaries?" Wrap suspect…

Use when the user wants to scaffold, bootstrap, or create a new Android project from scratch.