android-runtime-flag-probe

Run temporary Android framework diagnostics via adb setprop and Settings changes.

7|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/himattm/skills --skill android-runtime-flag-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-runtime-flag-probe
Source: https://github.com/himattm/skills/tree/main/plugins/android/skills/android-runtime-flag-probe
Command: npx skills add https://github.com/himattm/skills --skill android-runtime-flag-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android framework diagnostics can be run temporarily without modifying app code.

Core Features & Use Cases

  • Enable verbose logging for selected framework tags via adb shell setprop log.tag.<Tag> VERBOSE.
  • Toggle visual and performance flags (e.g., debug.layout, debug.hwui.profile) to inspect rendering and frame timing.
  • Provide a safe reset workflow to restore defaults after investigation.

Quick Start

Connect your device and run a single targeted adb command to enable a diagnostic flag and observe immediate UI or log output.

Frequently Asked Questions about android-runtime-flag-probe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable verbose Android logging without modifying app code?

You can enable verbose Android logging without modifying app code by using ephemeral adb shell setprop log.tag.<Tag> VERBOSE commands to temporarily toggle diagnostic flags for UI rendering and performance investigations.

Can I inspect Android UI rendering and frame timing without changing app code?

Yes, you can inspect Android UI rendering and frame timing without changing app code by toggling visual and performance flags like debug.layout and debug.hwui.profile through ephemeral adb shell commands.

How do I restore default Android diagnostic settings after debugging?

To restore default Android diagnostic settings after debugging, run the provided safe reset workflow which reverses the ephemeral adb setprop and Settings changes made during your investigation.

Does enabling Android framework diagnostics via adb require app redeployment?

No, enabling Android framework diagnostics via adb does not require app redeployment. It uses temporary adb setprop and Settings changes to run diagnostics immediately on a connected device.

What is the best way to verify Android lifecycle behavior during development?

The best way to verify Android lifecycle behavior during development is using temporary adb setprop commands to enable framework diagnostics, allowing you to observe lifecycle events immediately without altering your application source.