Will your app work with an Ethernet Connection?

[gregeeh]

Hi,

Will your app make port 5555 the default when using Ethernet and not a WiFi connection? As in Android 14 WiFi debugging cannot be enabled when you have an Ethernet connection, at least that's the case on my Sony Bravia 8 TV.

This stops apps like Launcher Manger and tvQuickActions from working when using Ethernet.

TIA

[yudin-s]

The Wi-Fi/Ethernet part should only matter during setup. Once legacy ADB is listening on :5555, adb connect <tv-ethernet-ip>:5555 is just TCP on the LAN.

The catch is the first-time bootstrap. Auto ADB uses Android's wireless debugging/pairing path to grant itself enough access to enable legacy ADB later. If Android TV disables Wireless debugging completely while Ethernet is active, Auto ADB may not be able to do the initial pairing/setup in that state.

I would test it like this:

1. Temporarily connect the Bravia to Wi-Fi, complete Auto ADB pairing, and press [ENABLE LEGACY ADB] until the app shows legacy ADB connected/running.
2. Switch the TV back to Ethernet and reboot.
3. From another machine on the same network, run adb connect <ethernet-ip>:5555.

If step 3 works, Launcher Manager/tvQuickActions should be able to use the Ethernet address too. If legacy ADB disappears after switching to Ethernet, then the limitation is likely Android/Sony blocking the bootstrap path rather than port 5555 being Wi-Fi-only.

That result would be useful for other Bravia owners trying the same Ethernet setup.

[gregeeh]

Thanks for the detailed reply. I will try your suggestions tomorrow and let you know the results.

Greg

[gregeeh]

Hi,

Tried your suggestion with no luck. If connection via WiFi rebooting ADB defaults to port 5555 with WiFi Debugging Disabled. If you are connected via WiFi and change to Ethernet by just plugging it in you can still connect via port 5555 on the LAN. Reboot and your app shows ADB is not running.

I've run out of ideas unless you can think of something else.

[nozza87]

Hi,

Tried your suggestion with no luck. If connection via WiFi rebooting ADB defaults to port 5555 with WiFi Debugging Disabled. If you are connected via WiFi and change to Ethernet by just plugging it in you can still connect via port 5555 on the LAN. Reboot and your app shows ADB is not running.

I've run out of ideas unless you can think of something else.

I don't have a Sony TV to test on but I am trying to get my hands on an equivalent Android device as I have a few ideas for a workaround.
I don't have an ETA but will try to update here once I do.

[yudin-s]

That result narrows it down quite a bit: the TCP side works over Ethernet while Android is already up, but Auto ADB/legacy ADB is not surviving the reboot when Ethernet is the active network.

At that point I would not keep looking for a different adb connect syntax. I would check whether the TV ever opens port 5555 after the Ethernet reboot:

adb kill-server
adb start-server
adb connect <ethernet-ip>:5555

and, if you have nc or telnet available:

nc -vz <ethernet-ip> 5555

If port 5555 is closed after reboot, then the missing piece is on the TV side: Sony/Android is probably not re-enabling legacy ADB at boot for the Ethernet network state. In that case the remaining options are basically:

• keep the TV on Wi-Fi for the Auto ADB bootstrap/startup path;
• switch to Ethernet only after legacy ADB is already running;
• see whether the Auto ADB app can be changed to re-run its enable/start logic after boot and after network change, if Android allows it;
• ask the app maintainer whether Auto ADB currently listens for boot/network-change events or only enables legacy ADB from the button/manual flow.

The useful finding is that Ethernet itself is not blocking ADB: rebooting while on Ethernet is what drops the service.

[Jacek63]

Is there any way to also automate turning on wifi briefly for this if Wi-Fi is off (I usually keep wifi off), enabling wireless adb, moving to 5555, and then disabling wifi again if it was off? That will be great solution if possible.