Two of my Chromecasts for Google TV upgraded to Android TV OS 14 and ADBTuner can no longer make the ADB Connection. Anyone else get an upgrade and experience the same behavior?
1 Like
Wait, what? Did Google disable ADB? Are you able to connect to it via a regular ADB client (like adblink from Jocala)?
Edit: another idea occurred to me - maybe the developer flag got reset with the OS update, and you need to re-enable?
1 Like
From googling, it doesn't appear that ADB got disabled with this update.
When each device rebooted with the update, ADB Tuner could no longer establish the Android connection. I looked at both - developer options and ADB were still enabled on both. I turned off debugging, rebooted, turned back on, re-added the tuners, no luck. I turned off developer options, rebooted, re-enabled, re-added the tuners, no luck.
I'll try a regular client tomorrow. Need to wait out this freak-out moment.
I imagine you've already checked this, but just in case:
IP address change on the stick(s)?
IP address didn't change - I just checked again to be sure 
@bnhf - FYI
ADB over TCP/IP seems to be disabled by default in Android 14 on the CCwGTV 4k.
Opening an adb connection to the device via usb or wireless debugging (with the pairing code) and running adb tcpip 5555 will enable it again, but it doesn't persist after a reboot.
If you are using ADBTuner, ah4c, or similar. Do not upgrade.
I'm looking into some options.
The newer "wireless debugging" feature could be used, but it would require adding support for the dynamic port mapping and interactive pairing code process.
Unfortunately, wireless debugging is also disabled after each reboot so that's something else to figure out (it will need to be toggled back on, but not re-paired after each reboot).
Temporary fix if you have adb installed on your computer:
On the CCwGTV go to Settings -> System -> Developer Options and turn on Wireless Debugging. Then within that Wireless Debugging section, select "Pair device with pairing code."
Make note of the pairing code, IP address, and port.
From your computer run:
adb pair <ip address>:<port>
and then enter the pairing code when prompted.
If the connection is successful (command output would say Successfully paired to <ip address>:<port> and there will be a popup on the device itself confirming connection.
While connected run this command:
adb tcpip 5555
It should say restarting in TCP mode port: 5555 and from there ADBTuner/ah4c should work again until the Chromecast is rebooted.
3 Likes
@turtletank thank you so much for all you have done with this project. It's been amazing.
I have one CCwGTV 4k and 2 Onn $20 boxes. They are all still on 12 as of this morning.
I am pondering replacing the CC with another Onn box to avoid this issue as long as possible. I'd put my FireSticks back in, except I have really enjoyed being able to record from Peacock.
I noticed on Reddit that, "the hardware H.264 decoding support has been removed** rendering a user unable to use their HDHR on their CCwGTV..
Is this the same for FireTV? Anyone know? Thanks!
FireTV devices are nowhere near Android 14 ... New devices will be coming out with Android 14 but they usually do not upgrade older devices so I would not worry.
My devices are on Android 9 that I use for ADBTUNER.
Fire TV sticks are usually throw away devices.
No nd to be concerned.
Not only did Google kill ADB it also killed the ability to VIEW Cable Card DRM channels. So I am Glad that my FiresTicks are able to use XFINITY Stream and with ADBTUBER I can still Capture DRM Channels.
This discussion prompted me to check my ONN hardware to see what OS versions are running.
Regardless of which device model; UHD, 4K, or 4Kpro, The OS is currently Android TV 12.
Do any of you know if it is possible to prevent any automatic OS upgrades? It seems to me that these devices usually prompt me that an upgrade is available before downloading and installing. Perhaps, just ignoring the reminder is enough? 
+1 for FireTV devices as inputs for ah4c and ADBTuner. Even the most recent versions of FireOS (used on the FireStick 4K Max 2nd Gen), are based on Android 11 -- so they'll likely be available, and work well, for years to come.
There are a few consistent detractors on the forum for these devices, but I have found them to be excellent. One of the features that stands out for me, is the FireTV app which allows for remote control of FireSticks WITHOUT using ADB.
For anyone that's away from their home LAN for long periods of time, or manages an encoder in a remote location, the Fire TV app will run on a Mac Mini (or the like). Set up remote access to that Mac device, and even from far away you can both view the display, and send remote control commands to any FireStick on the same network. This works whether adb is functioning or not -- which can, on occasion, be very handy.
In addition, they've worked very well with PoE Ethernet adapters, which is another plus when you're not "on site". This makes hard reboots something that can be done through a managed PoE switch. Not something that needs to be done often, but when you need it, being able to do it remotely beats the heck out of talking an elderly parent through the process.
Thank you for enlightening me about Firesticks. I had no idea about these very desirable features. 
I have never been an Amazon Device or Mac guy. I may have to broaden my mind a bit... I learn so much through this amazing community. 
A total of 7 across 3 encoders. Two on a remote LinkPi, 4 on a "local" URayCoder, and one on a LinkPi for development. I live outside the US for half the year though, at which point they're all remote.
Not sure any other stick would have worked as well, remotely managed.
My ONN boxes are on ANdroid tv 12.
I highly doubt the devices will be updated becuase they are not powerful enough.
These $20.00 devices when warn out will be better off replaced.
I'm not too woried about the updates. The new equipment will eventually have the update but these cheap boxes are throw away type devices.
Enjoy them while they work.
Is there a known list of ways to keep Fire TV devices “active” on YouTube TV, for lack of a better term? I’ve done what I’ve picked up from the forum to keep my Fire devices from sleeping, even using a terminal-like ADB app a while back to send a “no sleep” command, if I recall, but my devices still seem to take longer (maybe 8-9 seconds instead of about 4) to tune to a channel if not used for several hours. I figure I’m probably missing something.
My setup was using the newest Firesticks and I loved it as the sticks are fast and support WiFi6.
I pulled them and replaced with Onn/CCwGTV so I could record Peacock. If it wasn't for Peacock I could put them back in and eBay the Google boxes.
Throwing out a wish list here- I would love to be able to set a channel flag in ADBtuner to either use a random tuner or to only use a specified tuner
Or be able to run multiple ADBtuner versions so my Firewticks would be used for Sling and my ONN boxes for Peacock. Then in Channels I could still have my 3 tuner limit set for Sling and use a 4th tuner for Peacock.
Guess it's off to the store today to get another ONN box.
This can be done already just specify a different port for ex 5592 is the default but you can set a second with 5593 ...