Android Debug Bridge on Chromecast wGTV 4K after Android 14 update

Configuration
, ,
1

It has been confirmed that USB debugging does not work on Chromecast wGTV 4K after Android 14 update. And apparently it is not a bug but a new security feature.
What are the options to continue using ADB on Home Assistant for CCwGTV?

2

You can still connect to it, just in a new and not so automatic-able solution.

You have to use the new pairing method, for which you have to initiate a connection from the Chromecast, which will give us a random port with a random pairing code, and as a candy on the top of it, you have to use the same WiFi network for both of the devices, which can kill the ethernet option.

Nice and happy!

3

Is the Home Assistant ADB integrationā€™s user interface updated to use the new pairing method? I still see the old interface.

4

Has anyone been able to connect since it was updated to android 14, I still get errors when i try and connectā€¦

5

Me too - searching for a solution (with description how to) I see mention of ā€˜new pairing methodā€™ in this thread, but have not found what that is or how toā€¦ any assistance or link to how to would be greatly appreciatedā€¦

6

Just got the Android 14 update :frowning:

Anyone managed to make adb work over ethernet?

7

I canā€™t get it to work at all, the pairing option in the Cast settings menu (under Wireless Debugging) provides the IP:PORT but I never get anything other than the ā€œFailed to connectā€ error.

Has anyone tried:

  1. Connecting via ADB over wireless from some other device, and
  2. Running ā€œadb tcpip 5555ā€ to open port 5555 for ADB?

I only have my work laptop here, so Iā€™m not sure how I can do this workout finding a personal device I can install the Android SDK ontoā€¦

8

Would it be fair to say that the ADB integration needs to be updated to support ADB over wireless, so it can accept a pin?

9

Hi everyone, --I think Iā€™ve got it working with a straight pair on port 5555 as usual, but thereā€™s a few steps and Iā€™ll need to see if it survives updates.ā€“

EDIT: no it didnā€™t survive a reboot, I thought it had but it hadnā€™tā€¦ I had to reload the ADB integration to see it had failed to reconnect. Perhaps the ADB server can be configured to reconnect and re-enable port 5555 on demandā€¦ though Iā€™m struggling to see how it can be automated as wireless debug is disabled on boot, and the port keeps changingā€¦

  1. I spun up an ADB docker, and then entered a bash session inside the container (though Iā€™m sure it would work from a device with the SDK installed)
  2. Went into developer settings inside the Cast menu, enabled wireless debug, then selected the option to pair with a code - this displays IP, port and pair code.
  3. In the docker session, I entered: adb pair ipaddress:port (as displayed on the cast display)
  4. I was then prompted for a pair code, which is also displayed on the cast display - entered that, and then got a response that the pairing was successful.
  5. Backed out of the pairing option within the Cast menu, where you can see the ADB port (different to the pairing port)
  6. Then in the docker session: adb connect :
  7. Then: adb tcpip 5555 (these commands had no response)
  8. Back in home assistant I added the ADB debug bridge on port 5555, same as before the updateā€¦ straight through as normal.
1 Like
10

Thanks for both trying and sharing - your skills beyond mine on this - hopefully someone will eventually figure it out as I would really like to get this up and working again

11

Iā€™m afraid we can no longer rely on ADB and its full set of control features. The decision to disable wireless debugging in Android 14 as an ā€œimprovementā€ was made years ago and will not be reversed. There is no workaround for Google Chrome devices that survive a reboot. You can only prevent the A14 update from taking place.

12

After digging around for a solution to this I have been able to get everything reconnected and have a solution to re-adding devices easily when the debug port changes if rebooted or wireless debug was disabled. The process is similar to what @MattP shared earlier.

Here are the steps that I used to get the wireless debugging enabled and connected again.

Prerequisite

As far as I know you will need to have a seperate Android debug bride (ADB) addon until the integrated version is updated to support android 14, if it is updated.
I found GitHub - Amateur-God/Hassio-Addons in another forum and it has been working well for me. Hereā€™s a link to the ADB Server documentation too.

Steps to setup a new connection

  1. Enable the developer options on the chromecast.
  2. In the developer options locate and enable wireless debugging.
  3. Select ā€œPair the device with pairing codeā€.
  4. Open the UI of your ADB server.
    • (The following steps are written assuming you are using the addon I shared and running it from the Home Assistant server).
  5. Run the following command to start the pairing process. Enter the IP address & pairing port as it appears on the chromecast.
    adb pair IP:Port
    • If you want to copy or past text or code to and from the ADB Server addon you will need to use the context menu (right-click).
  6. Provide the pairing code when prompted. You should receive a confirmation on screen.
  7. On the Chromecast exit the pairing screen to show the wireless debug sceen again.
  8. Run the following command to connect to the chromecast now that itā€™s paired.
    adb connect IP:Port
  9. You can verify that the device has connected successfully and display any other connected devices with the following code.
    adb devices -l
  10. Navigate to the Android Debug Bridge integration (<your-HA-address>/config/integrations/integration/androidtv) and add the chromecast with the information displayed on the wireless debug page.
    • Host: <Chromecast IP>
    • Port: <Wireless Debug Port>
    • ADB Server IP: 127.0.0.1

Reconnect/Recreate ADB connection.

  1. Double check that the Wireless Debug is enabled on your device.
  2. Open the ADB Web UI and enter the following command. You will receive a list of your connected devices as well as services on your network.
    adb devices -l
  3. Run the following command to get more information about the services.
    adb mdns services
  4. Locate the IP of your disconnected device in this list. The port listed is the debug port that has been regenerated.
  5. Run the following command to reconnect to the device.
    adb connect IP:Port
    • You can verify that the device has connected successfully and display any other connected devices with the following code again.
      adb devices -l
  6. Navigate to the Android Debug Bridge integration (<your-HA-address>/config/integrations/integration/androidtv) and delete the device.
    • Unfortunately, Iā€™m unaware of a way to reconfigure an existing device without deleting it.
  7. After the device has been deleted, use the ā€œAdd Deviceā€ process again.
    • Host: <Chromecast IP>
    • Port: <Wireless Debug Port>
    • ADB Server IP: 127.0.0.1
2 Likes