Stopped working after Android 14 update

[jimmyl-source]

Hi, MATVT always worked on my Chromecast until the android 14 update. The cursor is visible but I can't click.
I tried to reinstall MATVT but after that i can't allow accessibility enable button, it turns right back off.

[virresh]

Thanks for reporting, have heard this from a few other folks as well.

It looks like Android 14 has introduced some scanning feature to check for apps installed from Playstore.

I've heard the either of the following works for people:

• Disable the scanning feature in Android Settings / Applications / Security / Scan Apps with Play Protect before app installation
• install the app via adb (not by sideloading it from some file explorer app etc)

Can you try any / both of the above and report if it works for you?

[johnsy616]

same issue here. i have a sony tv, it works good until i updated the sony updates yesterday. now only moving the mouse is working, but i cannot click anything.

it's a sony tv, i cannot install app via adb or disable security scanning.

[virresh]

don't think there's anything I can do to help here. The app has relied on the ability to sideload and use adb permissions (especially wireless adb).

[se735]

I installed the app with adb install and the click still doesn't work

[virresh]

I installed the app with adb install and the click still doesn't work

@se735 did you try the things mentioned in first comment ?

[se735]

@virresh Yes, i tried disabling the play protect scan and i installed the apk with adb install instead of installing it from a file explorer

[aquirozc]

Dear @virresh , I regret to inform you that the reason the app ceased to function is not an install-time-only limitation that users can easily circumvent but rather a new series of limitations on the operating system's wireless debugging capabilities intended to restrict the use of ADB without explicit user interaction.

The TCP port 5555, which is hardcoded at line 131 here, is no longer used as the default wireless debugging port. Instead, a new port number is assigned each time the device reboots or connects to a different Wi-Fi network.

The randomly assigned port is exposed by the device itself via mDNS through the advertisement of the ADB service. However, the library being used has not yet been updated to support the new Android 11+ pairing protocol.

[virresh]

Thanks @aquirozc for the analysis!

This is very helpful. Now I know what to simulate and can test out a few alternatives. I hope there's some bonjour library that can be tweaked to this mdns pairing protocol.

[jimmyl-source]

@virresh Thank you for trying to fix the problem. Here's a video link how tvQuickActions Pro handles the android 14 update.
https://www.youtube.com/watch?v=qDoqwE-Dufo

[aquirozc]

After some examination using a bytecode analyzer, I determined that the app @jimmyl-source shared uses Surge1223's libadb.so as it backend. A usage example of the native library can be found here

[virresh]

Thanks!
Took a look at the binary, and it's nice.

Although before I use it in the app, I'd like to dig a bit more about what changes are in the binary.
Do you happen to know Surge1223 ?
Would prefer avoiding compilation of libadb myself if possible, but still keep it a possibility to peek at the binary source.

[virresh]

Also, the native binary discussion just made me realize there was someone trying to work around the random port problem with Java code (#24 (comment))

I don't think that worked out, but seems like we can have some partial solutions.

[BlueCloudCaddo]

Any progress ? Following.

[manucajas]

Hi, im sure by now, everyone knows that MATVT can be installed with SAI installer.
The problem is that the mouse won't select anything.
I hope is something that can be done.