You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Enrol Android phones reached over the network (adb connect host:port) #1250
We have a rack of Android phones wired by Ethernet, with adb over TCP on (adb connect <ip>:5555). The phones' USB ports are taken by their network adapters, so none of them has a USB path to a worker. In 0.5.0, simlock device add --platform android <ip>:5555 refuses each one: "only USB-connected devices can be enrolled" (reason network-only). That's by design since #441 ("The transport decides; the serial's shape never does"), but it leaves a whole phone farm outside the pool unless every phone is re-cabled to one host by USB.
Who runs into this
Anyone with a farm or rack of real Android phones reached over the network: wired or Wi-Fi adb, older phones with adb tcpip, or Android 11+ wireless debugging. For us, it's coding agents that need real Samsung phones (their own OEM quirks, which emulators don't have) and lease them through the gateway the same way they lease emulators.
What you would like to happen
An opt-in for enrolling network adb transports on a worker, for example a worker config key, or device add --network, with the worker reconnecting (or reporting not-present) when the transport drops. The caveats you'd know better than us: the worker doesn't own the transport, adb's server restarts drop network devices, and Android 11+ pairing.
Anything else
Our workaround on 0.5.0 (one Linux worker, 17 Galaxy S9+ on Android 10): a one-line patch that counts an IPv4:port serial as attached in the Android driver's parseDevices (dist/drivers/android/physical-handler.js), plus a timer on the worker that runs adb connect for each phone and simlock device add for any that aren't enrolled. With it, all 17 enrol and a phone leases through the gateway (lease --platform android --physical). We'd rather drop the patch.
Activity
V3RON commentedon Nov 16, 2026
Being specified in #1589. This issue stays open until that feature ships.
Written by an agent.