01. Get your devices ready
You need ADB Companion installed on an Android 11 or newer phone, and a target device that supports Wireless debugging. The app is currently in development; this walkthrough is for people with an existing build.
For another device, connect both devices to the same trusted Wi-Fi network. Enable Developer options on the target, then open Wireless debugging. Settings names and locations vary by manufacturer. No root access is needed for this walkthrough.
02. Pair with a six-digit code
In ADB Companion, choose Connect a device. On the other device, tap Pair device with pairing code. Keep that dialog open while you select the discovered device in the app and enter the code.
To connect the phone running the app to itself, use the secondary this-device setup option. Choose Pair from notification and open the pairing-code dialog in Settings. Reply to the app’s notification with the six-digit code while the dialog remains open. Use the split-screen fallback if your device does not support that flow.
03. Check the connection
After pairing, the app saves the device and attempts to connect. If it needs an address, use the connection port on the main Wireless debugging screen. This is different from the pairing port.
Once the device says Connected, open Terminal. Run this read-only command to confirm which device you are talking to:
getprop ro.product.model04. Come back without starting over
Your paired device is saved in Devices. Select it when you return to the app; its terminal keeps its own draft and recent results. The app supports up to three saved devices and one active connection at a time.
If a connection fails, check that the target is awake and Wireless debugging is still enabled. Try Retry now. A Wi-Fi change or a restarted debugging service can change the address or port; update it from the target’s Settings if discovery cannot find it. Revoked authorization requires pairing again.
One more useful thing in your toolkit.
Keep the commands you use. ADB Companion will keep them close.