ADB Nexus: Wireless ADB Shell

ADB normally needs a computer. ADB Nexus does not. Pair over wireless ADB or plug in with USB OTG, then open an ADB shell, move files, install APKs and read logcat, straight from the phone in your hand.

Use ADB Nexus without connecting another device to check your host phone. The live dashboard and scrollable Device Info tabs cover memory, CPU, storage, battery, Android system details, display, network, connectivity, camera capabilities, thermal readings, sensors, installed apps and hardware tests.

Connect an authorized Android target through Wireless debugging, legacy ADB over TCP, or compatible USB OTG hardware. Remote tools appear only after Android's normal pairing or RSA authorization is complete.

Key features

• Live device dashboard with animated memory history and per-core CPU status
• Detailed Android device info, battery, display, network, sensor and thermal views
• Wireless debugging pairing and connection tools for supported Android devices
• USB OTG ADB support on compatible phones, adapters, cables and targets
• ADB shell terminal with command history, tabs, output status and Safe Mode
• File manager for authorized upload, download, preview and storage tasks
• App manager with icons, package details, permissions, components and target controls
• APK installation and export for devices you are allowed to manage
• Process inspection, system properties, logcat and diagnostic reports
• Remote screenshots, delayed or loop capture, and supported screen recording
• Network discovery, Wi-Fi analysis, data usage, app analysis and device widgets
• Host-phone tools that remain useful when no ADB target is connected
• Contextual help, permission guidance, privacy choices and export tools

Two device contexts, one interface

Host phone mode shows information and tools for the Android device running ADB Nexus. When a remote ADB session is active, the same interface switches to data and supported controls for the connected target. Remote-only actions are hidden or clearly identified until a live session supports them.

ADB Nexus respects Android security

ADB Nexus does not bypass Wireless debugging pairing, USB RSA authorization, lock screens, encryption, SELinux, file permissions, app debuggability or root policy. Some values and actions may be unavailable because of the Android version, device manufacturer, network isolation, USB hardware or target configuration. Root-only commands still require a target that is already rooted and authorized.

Privacy by design

ADB commands and output, pairing codes, target addresses and serials, package names, file names, paths, file contents, Wi-Fi scan results and target-device data are processed locally by ADB Nexus. Optional Firebase analytics, crash reporting, performance diagnostics and installation registration have separate controls. Advertising data is handled according to Google consent choices and the ADB Nexus privacy policy.

Use ADB Nexus only with devices and networks you own or have permission to administer.

Recent changes:
Wireless debugging gets a new port every time you toggle it or restart your phone. ADB Nexus used to keep showing the old connection as live, then fail every command with an error that blamed your settings. It now spots a dead port on the first attempt and reconnects instead.

Setting up call recording with Astra Recorder retries once by itself if the connection drops mid-setup, and tells you in plain words what went wrong instead of showing an internal message.