Skip to content

Stopped working after Android 14 update #104

Open

Description

@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.

Activity

  1. virresh commented on Aug 5, 2025

    @virresh
    Owner

    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?

  2. johnsy616 commented on Aug 16, 2025

    @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.

  3. virresh commented on Aug 23, 2025

    @virresh
    Owner

    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).

  4. se735 commented on Aug 25, 2025

    @se735

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

  5. virresh commented on Aug 25, 2025

    @virresh
    Owner

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

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

  6. se735 commented on Aug 25, 2025

    @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

  7. aquirozc commented on Aug 26, 2025

    @aquirozc
    Contributor

    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.

  8. virresh commented on Aug 26, 2025

    @virresh
    Owner

    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.

  9. jimmyl-source commented on Sep 5, 2025

    @jimmyl-source
    Author

    @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

  10. aquirozc commented on Sep 5, 2025

    @aquirozc
    Contributor

    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

  11. virresh commented on Sep 7, 2025

    @virresh
    Owner

    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.

  12. virresh commented on Sep 7, 2025

    @virresh
    Owner

    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.

  13. BlueCloudCaddo commented on Nov 6, 2025

    @BlueCloudCaddo

    Any progress ? Following.

  14. manucajas commented on Mar 8, 2026

    @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.

  15. Picton21 commented on Aug 28, 2026

    @Picton21

    Thank you for your continued work on this. Hopefully, something will come to light, allowing this to work once again on Onn.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions