Kapptivate logo

ktm adb

Connect Android Studio or the ADB CLI to remote phones via a secure tunnel, then enable, monitor, and disable device access per agent.

ADB — use remote phones as if they were plugged into your machine

Usage

ktm adb [flags]

Subcommands

connect

Open an ADB tunnel to a remote phone

disable

Turn off the ADB bridge on an agent (terminates active connections)

enable

Turn on the ADB bridge on an agent (no agent restart)

status

Show phones, their agent's ADB bridge state, and who is connected

Details

Connect Android Studio or the ADB CLI to phones hosted on remote agents.

How it works: each agent runs an "ADB bridge" that exposes its phones for remote debugging. The bridge ships OFF — turn it on per agent (instantly, no agent restart), connect, and turn it off when you are done:

ktm adb status → every phone: agent, bridge on/off, current holder ktm adb enable --agent <hostname> → turn the bridge on (reverts to the agent's config on restart) ktm adb connect [serial] → tunnel a phone to your local ADB server (offers to enable if off) ktm adb disable --agent <hostname> --confirm → turn the bridge off and free its phones

The tunnel is a secure TLS connection on port 443. The device registers with your local ADB server automatically, so it appears in Android Studio like a phone plugged into your computer.

Only one user can hold a given phone at a time; a second connection is refused naming the current holder until they disconnect. The phone is released the moment you disconnect. 'ktm adb enable|disable' are shortcuts for the generic runtime adapter control — see 'ktm agents adapters --help'.

Related

Global flags (--output, --debug, --host, …) apply to every command. See the command reference overview.

What's next?

All commands

Browse the full CLI reference.

Get started

Install the CLI and authenticate.

Last updated on