Finding · Android TV · ADB · Home automation
onn 4K Pro: USB debugging keeps ADB on port 5555 over Ethernet, across reboots
Wireless debugging switches off whenever an Android TV box isn't on Wi-Fi, which is why network ADB seems not to survive Ethernet. On the onn 4K Pro, turning on USB debugging keeps ADB listening on port 5555 on every network, including after a reboot on Ethernet alone. No root and no helper app.
Ryan McMillan · Found Oct 17, 2026 · Published Oct 18, 2026
Affected
- Device
- onn 4K Pro Streaming Device (two boxes)
- OS
- Google TV, Android 14 (build URO3.260203.035.A1, patch 2026-06-01)
- Setting
- Developer options → USB debugging on; Wireless debugging can stay off
- Root
- Not required
01
What happens
On current Android, network ADB normally means Wireless debugging: a pairing code, a random port, and Android turns it off whenever the device isn't on Wi-Fi. Plug an Android TV box into Ethernet and network ADB goes away; reboot it and the port changes. That breaks Home Assistant's Android TV integration, ADBTuner and anything else that expects <box-ip>:5555. The usual fixes need root (persist.adb.tcp.port) or a helper app that turns Wireless debugging back on at every boot.
The onn 4K Pro's firmware sets service.adb.tcp.port to 5555 at every boot. That property only matters while the ADB daemon is running, and USB debugging keeps the daemon running whether or not the box is on Wi-Fi. With USB debugging on, the box listens on TCP 5555 from boot, on Ethernet as well as Wi-Fi. Nothing has to be plugged into the USB port.
02
Evidence
Tested in three stages on one 4K Pro on October 17, 2026, then confirmed on a second:
- On Wi-Fi, no reboot: USB debugging on, Wireless debugging off. The ADB daemon kept running and port 5555 stayed open.
- Reboot on Wi-Fi: port 5555 open about 25 seconds after the reboot, with nothing else installed to help.
- Reboot on Ethernet only, Wi-Fi disconnected: port 5555 open on the Ethernet address about 33 seconds after the reboot.
- Second box, on Ethernet: back on 5555 about 34 seconds after a reboot.
$ adb shell getprop service.adb.tcp.port
5555
$ adb shell getprop persist.adb.tcp.port
$ adb shell settings get global adb_enabled
1
$ adb shell settings get global adb_wifi_enabled
003
Reproduce
- 01Unlock Developer options: Settings → System → About, then press OK on Android TV OS build seven times.
- 02Turn on Developer options → USB debugging. I set it over an existing ADB session with
adb shell settings put global adb_enabled 1, which is the setting the toggle writes. - 03Check the firmware preset:
adb shell getprop service.adb.tcp.portshould print5555. - 04Move the box to Ethernet, reboot it, then run
adb connect <box-ip>:5555. Approve the computer once at the TV with Always allow from this computer.
04
Fix and cautions
This is plain, unencrypted ADB on port 5555. The only protection is the approval prompt, and an approved computer has full control of the box. Keep the box on a network you control, and firewall port 5555 to the machines that need it.
Android also revokes ADB approvals that go unused for seven days. If a computer only connects occasionally, adb shell settings put global adb_allowed_connection_time 0 stops the expiry, at the cost of approvals lasting until you revoke them.
05
Not tested
- Tested on two onn 4K Pro boxes on one firmware build. A firmware update could remove the preset.
- The non-Pro onn 4K Streaming Box (build URO4.260304.011.B1) also presets
service.adb.tcp.portto5555, but I haven't tested USB debugging on it. - On other devices, check
getprop service.adb.tcp.portfirst. If it's empty, this won't work without root.
06
Prior work checked
- Home Assistant core issue #148359Android 14 broke ADB on port 5555 after reboots for the Android TV integration.
- Channels community: ADBTuner threadonn owners report losing ADB over Ethernet after reboots; one 4K Pro owner says it works, without an explanation.
- XDA: How to make adb listen to tcpip 5555 after rebootSolutions rely on root or persist.adb.tcp.port.
- adb-auto-enableA helper app that turns Wireless debugging back on and switches it to 5555 at boot. Its README requires a Wi-Fi connection.
Know of earlier write-ups? Tell me and I'll credit them here.
Updates
- Oct 18, 2026Published.