Yes but without Shizuku, the app won’t run at all on your phone. Unless you have an alternative solution/suggestion, that’s the trade off for certain Android 11 devices.
I can either support those devices with this trade off or not support them at all if adb is not practical.
Is there a way to see what shizuku uses maybe just an adb command that could fix it? Its worth the trade off.
Unless you are rooted, we need adb to start Shizuku when you reboot, and we need Shizuku to perform the gesture.
From Android 11 and up, you don’t need adb to start Shizuku.
See over here where I explain how to do it.
@anonymousfliphones have you tried this?
WIRELESS DEBBUGING IS ADB JUST OVER WIFI INSTEAD OF USB
So then over there even with wireless debugging you still have to restart it every time you reboot your phone so its easier but if you do not have access to wifi or network like the average user it is not possible to do and telling the basic user that “in order to start the mouse you have to activate this app every time you restart your phone in this manner” wont work because its to complicated for people who know nothing about there things it doesn’t really work out
It works for me to start Shizuku that way.
Do you have to restart it every time you reboot your phone?
yes
Exactly my point not practical for the average user
What are you suggesting then? We have already said that this is the tradeoff to get cursors to work on some Android 11 devices.
I wonder if its possible to make an accessibility app that would startup Shizuku by itself via wireless debugging, and create a WiFi network so the phone can connect to itself.
There might be a adb command to do what shizuku does because usually if an app could do something adb could also
Right, but you can’t run adb commands from an unrooted device without Shizuku…
The point is to be able to start Shizuku without a computer.
And you say that my mehalech isn’t practical.
So I’m wondering if it would be possible to automate my approach using accessibility services.
What do u mean you can not run adb commands with out shizuku? That is false
That would be great but if we could take out the whole shizuku and just figure out what shizuku takes a hold of to work and just use that adb command once instead that would be even better
That’s not how it works. Shizuku is used for every click and gesture.
I also don’t even know how many users have this Android 11 issue to make the implementation, overhead, and headache worth it, in addition to the question of how many users are willing to use adb and Shizuku.
How does shizuku work
No app on an unrooted rom can execute adb commands.
Android doesn’t let that.
The whole point of adb is to give devs access to parts of the system that Google don’t want apps to be able to access, for obvious security reasons (or at least obvious to everyone besides for Microsoft).
What Shizuku does (on unrooted devices) is have adb run a shell script that somehow gives Shizuku access to adb, until reboot.
Since the only way to be able to tap on a screen on non touch Android 11’s seems to be through an adb API, there’s no way to cut Shizuku.
Cutting out Shizuku would just mean having to build our own Shizuku-like framework to access adb, which would have the same restrictions.
Oh i thought you meant that you cant execute any commands without shizuku
An Android app can’t.
From adb itself you can.