Remote Stopped Working after TV Software Update

I turned on ADB Debugging, sent the connect command from myServer, and accepted the token. Also checked the box to always allow this device to connect. The TV shows as a connected ADB device.

Even after a restart of the TV, still no IP control.

Did you leave the TV in developer mode? Did you leave ADB enabled? Did you send any ADB commands, other than verifying that you are connected?

cjisble wrote:

I turned on ADB Debugging, sent the connect command from myServer, and accepted the token. Also checked the box to always allow this device to connect. The TV shows as a connected ADB device.

Even after a restart of the TV, still no IP control.

Did you leave the TV in developer mode? Did you leave ADB enabled? Did you send any ADB commands, other than verifying that you are connected?

I did leave the TV in Developer mode with ADB Debugging enabled.  It had been on for at least the last year, I just cycled it off and back on.  I did power the TV on and off with ADB and it works well.  If this happens again, at least I'll have a backup control method.

I also updated MyServer and it did a reboot after installing the update. Not sure if that has anything to do with it.

Sony IP control stopped working again. The Android TV driver is still working, so I'll start using that and see if it's stable.

Note:  I was looking at Wireshark while sending Sony IP control commands with the errors seen below.  There were no packets sent out to Port 20060, only 5555, and the log immediately showed no connection.  After a reboot of MyServer, IP control is now working correctly.  I'll keep an eye on it to make sure it continues to work.  I'll leave the notes below for troubleshooting.

==========

The Android TV driver is no longer working for Power control, and I don't know the syntax to change inputs on the TV using the Test command from the Android TV driver.  

For the Sony IP control driver, here is the log:

17/10/2025 16:16:02.16 · DEBUG · Server.doCommand - AV|7~Power~On from dashboard-fx-9u4m
17/10/2025 16:16:02.16 · DEBUG · SonyTVs.doCommand - Cmd=[7~Power~On] Client=[dashboard-fx-9u4m]
17/10/2025 16:16:02.16 · DEBUG · SonyTVs.TX >>> - TheaterTV:*SCPOWR0000000000000001
17/10/2025 16:16:02.16 · ERROR · SonyTVs.SendCommand - Cannot send command to device TheaterTV - Device not connected
17/10/2025 16:16:02.16 · DEBUG · SonyTVs.TX >>> - TheaterTV:*SEPOWR################
17/10/2025 16:16:02.16 · ERROR · SonyTVs.SendCommand - Cannot send command to device TheaterTV - Device not connected

Port 20060 is open:allonis@AllonisMyServer6:~ $ sudo nmap -p 20060 192.168.2.54
Starting Nmap 7.93 (  nmap.org  ) at 2025-10-17 16:17 EDT
Nmap scan report for 192.168.2.54\
Host is up (0.00021s latency).
PORT STATE SERVICE
20060/tcp open unknown
MAC Address: 14:3F:A6:76:EB:E7 (Sony Home Entertainment&Sound Products)\
Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds

Android TV Driver:

17/10/2025 16:21:05.21 · DEBUG · Server.doCommand - AV|35~Power~On from dashboard-fx-9u4m
17/10/2025 16:21:05.21 · DEBUG · AndroidTV.doCommand - Cmd=[35~Power~On] Client=[dashboard-fx-9u4m]
17/10/2025 16:21:05.21 · DEBUG · AndroidTV.doCommand - Reconnect to 192.168.2.54:5555
17/10/2025 16:21:05.21 · ERROR · AndroidTV.doCommand - Error in MoveNext - Object reference not set to an instance of an object.
17/10/2025 16:21:14.21 · DEBUG · AndroidTV.CheckAdb - Checking for ADB running
17/10/2025 16:21:14.21 · DEBUG · AndroidTV.CheckAdb - List of devices attached 192.168.2.129:55055 device 192.168.2.132:5555 unauthorized 192.168.2.23:5555 device 192.168.2.54:5555 device
17/10/2025 16:21:17.21 · DEBUG · AndroidTV.TX: ATV_TheaterTV - dumpsys display| grep "mScreenState"
17/10/2025 16:21:17.21 · DEBUG · AndroidTV.RX - ATV_TheaterTV << mScreenState=OFF>>
17/10/2025 16:21:17.21 · DEBUG · AndroidTV.TX: ATV_TheaterTV - dumpsys activity activities | grep "mResumedActivity"
17/10/2025 16:21:17.21 · DEBUG · AndroidTV.RX - ATV_TheaterTV <<>>

My understanding of the problem is when the Sony AndroidTV OS TVs that when the screen saver kicks in it also closes the communication port 20060. So, the workaround was to enable ADB on the TV and via the AndroidTV myServer driver to issue a "Disable Sleep" command (note - this really just sends it a "don't go to sleep for 23 years" command since the OS really doesn't support "disable").

The errors are showing the port is closed  (SonyTVs.SendCommand - Cannot send command to device TheaterTV - Device not connected)and ADB isn't authorized (DEBUG · AndroidTV.CheckAdb - List of devices attached 192.168.2.129:55055 device 192.168.2.132:5555 unauthorized 192.168.2.23:5555 device 192.168.2.54:5555 device). So, myServer can't then communicate with it.