Device Connection and Pairing

Device Connection and Pairing

中文

Screen Remote supports three ADB access types: USB, TCP, and Wireless Debugging/mDNS.

When creating or editing a session, select a device type first:

• TCP: enter a host and port, for example 192.168.5.13 and 5555.
• USB: enter a USB serial, or select a scanned device.
• mDNS: enter a Wireless Debugging connect service, or select a nearby discovered device.

Do not enter usb:, tcp:, or mdns: prefixes manually. The connection layer creates the ADB transport serial.

USB connection

Use USB for first connection, unstable networks, lower latency, or initial Wireless Debugging setup.

1. Connect the target through USB or OTG.
2. Create or edit a session.
3. Select USB.
4. Enter the USB serial or select a USB device.
5. Connect.
6. Grant permission in the system dialog.

The USB serial identifies the session. Device selection fills it automatically. A successful connection can enter remote control or ADB-only management.

TCP connection

Use TCP when an ADB TCP endpoint is already reachable on the local network.

1. Select TCP.
2. Enter the host.
3. Enter the port, commonly 5555.
4. Save and connect.

IPv6 address and port normalization is supported, including relevant IPv6 and [IPv6]:port forms.

Wireless Debugging pairing

Use this for Android 11+ devices and TLS Wireless Debugging. The pairing-code method is recommended because it is generally more reliable for application-level Android flows.

1. Enable Wireless Debugging on the target.
2. Open “Pair device with pairing code.”
3. Enter the host, pairing port, and pairing code in Screen Remote.
4. Complete pairing.
5. Use the separate connection port for the actual connection.

mDNS connect services

After pairing, the target normally advertises an _adb-tls-connect._tcp service. For an mDNS session, enter the service name or select it from the nearby-device list.

• Discovery is continuous and does not require manual refresh.
• A connect service is a connection entry point; it does not enter a pairing code.
• Complete pairing first when the peer is not yet paired.

Connection states

• Remote control: ADB and the scrcpy video/control path are active.
• ADB connected: ADB is active, but remote video is not currently open.
• Connecting: a connection attempt is in progress.
• Disconnected: the session has no usable connection.

Common errors

• Unauthorized device: approve the ADB authorization prompt on the target.
• Unreachable port: check host, port, and network reachability.
• Paired but cannot connect: do not reuse the pairing port as the connection port.
• IPv6 error: enter a standard address and let the session normalize it.