software-android-runtime-debugging
Installation
SKILL.md
Native Android Runtime Debugging
Use this skill when the core problem is not app architecture or visual design, but runtime truth: did the current APK/AAB build, install, launch, and render on the intended emulator or device — and, once that's proven, why is it slow, freezing, or leaking memory?
This skill owns stale-build suspicion, emulator drift, malformed APKs, ADB failures, Gradle cache corruption, ProGuard/R8 stripping, Compose recomposition issues, ANR/jank/memory/startup performance triage, and the proof loop required before trusting screenshots, UI behavior, or downstream API/auth debugging.
Platform Currency (look up, do not assume)
Platform facts drift within months. Before citing any of these, check the live source:
- Current Android release and API level: developer.android.com/about/versions.
- Google Play target API requirement and deadlines: developer.android.com/google/play/requirements/target-sdk. Never hardcode the required level.
- 16 KB page-size support for apps that ship native (
.so) libraries: an app whose ELFLOADsegments are still 4 KB-aligned runs in a backcompat mode on 16 KB devices, so test on a 16 KB-page-size emulator image, not just the default. Check the current enforcement scope at developer.android.com/guide/practices/page-sizes. - AGP and Gradle minimums: a new AGP major version can raise the minimum Gradle version and change Kotlin plugin defaults. Check developer.android.com/build/releases/gradle-plugin-roadmap before assuming an older Gradle wrapper still works.
- Android Studio release name and version: developer.android.com/studio/releases. Google renames each yearly series.
- Perfetto, not Systrace, is the system- and app-tracing stack; Systrace is retired. See references/performance-triage.md.