android-adb-system-inspector

Inspect Android processes, services, memory, and battery from Termux via ADB wireless debugging.

1|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/IceHeartGitH/Hermes-Agent-Android-Termux --skill android-adb-system-inspector-iceheartgith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-adb-system-inspector
Source: https://github.com/IceHeartGitH/Hermes-Agent-Android-Termux/tree/main/custom-skills/android/android-adb-system-inspector
Command: npx skills add https://github.com/IceHeartGitH/Hermes-Agent-Android-Termux --skill android-adb-system-inspector-iceheartgith

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Plain Termux cannot access privileged Android system data because Android denies the android.permission.DUMP permission, so users cannot see background apps, running services, memory, or battery state without root. This Skill bridges that gap by using ADB wireless debugging from the same phone to expose system inspection data without rooting the device. ## Core Features & Use Cases - Wireless ADB Setup: Guides pairing and connecting to Android Wireless debugging from Termux, handling the separate pairing and connection ports. - System Inspection Commands: Reports background app process counts, unique app UIDs, package names, top processes, battery status, and memory summaries via adb shell and dumpsys. - Use Case: A user on a phone-only setup wants to know how many apps are running in the background and check battery health; after enabling Wireless debugging and pairing, they run the helper's summary command to get processes, meminfo, and battery data in one report. ## Quick Start Ask the assistant to check ADB status and inspect how many background apps are running on this Android phone using wireless debugging.

Frequently Asked Questions about android-adb-system-inspector

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

FAQPage Schema
How do I inspect running Android processes from Termux without root?▼

Enable Wireless debugging in Android Developer options, then pair and connect adb from Termux using the android-tools package. Once connected, adb shell ps -A and dumpsys commands return full system process data that plain Termux cannot access.

How to pair adb wireless debugging on the same Android phone?▼

Open Settings, Developer options, Wireless debugging, then tap Pair device with pairing code to see the IP, port, and code. Run adb pair with that target and code from Termux, then adb connect to the main Wireless debugging port shown on the previous screen.

Why does dumpsys activity fail with Permission Denial in Termux?▼

Plain Termux lacks the android.permission.DUMP permission, so Android blocks dumpsys activity calls. Running the same command through an authorized adb shell session bypasses this restriction without requiring root access.

What is the difference between the adb pairing port and connection port?▼

The pairing port appears in the Pair device with pairing code dialog and is used only for adb pair. The connection port is the main IP address and Port value on the Wireless debugging screen and is used for adb connect afterward.

Does adb wireless debugging survive a phone reboot?▼

No, pairing codes and ports are temporary and change after a reboot or when Wireless debugging is toggled off. You must re-enable Wireless debugging and repeat the pair and connect steps to restore access.

What are the limitations of non-root ADB system inspection?▼

It is not root, so it cannot modify system settings or access app private data. Process and package lists show system state only, and the user must manually enable Wireless debugging and read codes from Android settings.