Shizuku implementation

[FrameXX]

Have you ever heard of app called Shizuku?

In simple terms and as far as I understand it is aimed to provide privilegied access and permission to apps like MacroDroid or similiar and remove the need of manual ADB hacking for every app. There are more andvantages of using Shizuku. More can be read here:

Introduction | Shizuku

Let your app use system APIs directly

shizuku.rikka.app

On Android 11 onwards you no longer need computer to start ADB/debugging. You can start it directly from the device. With Shizuku you can start a wireless debugging and only thing you need is Wi-Fi connection. This makes it much more convenient to start Shizuku after every restart and clean app UI and guidiance makes it easy for the user.
MacroDroid could of course firstly use Shizuku to grant itself the permissions it needs, but also could probably use Shizuku running server to access some more Android functions I am unaware of.

Although I doubt you would plan such a implementation in near feature I wanted to make you aware of such an option. I think Shizuku is a nice and functional project (even though not much apps implemented shizuku, but there are some) providing a better user experience when trying to provide privilegied access for user apps.

Shizuku/README.md at master · RikkaApps/Shizuku

Using system APIs directly with adb/root privileges from normal apps through a Java process started with app_process. - RikkaApps/Shizuku

github.com

 

[Dimlos]

I actually used an app called Hail that supports Shizuku and thought it was interesting.
However, it is a bit troublesome on non-root devices because it is not possible to set Shizuku to start automatically after rebooting.

 

[Snurre]

Could'nt you just make MD start Shizuku with boot trigger?

 

[Dimlos]

This may be difficult because simply launching the application does not launch the Shizuku service.

 

[FrameXX]

Well. The main point here is that MacroDroid only needs to access Shizuku once to grant itself the needed permissions, so it's like an extra option how to grant MacroDroid prvilegied permission, without any PC or other external device. The ability to run shell is just a cherry on top.

 

[Dimlos]

At this time, MacroDroid does not support Shizuku, so it does not appear on the list.
As for rebooting, we can't do anything without the Shizuku service running, can we?

However, I think it is attractive to be able to grant root access as well as ADB hack.

 

[Dimlos]

Could'nt you just make MD start Shizuku with boot trigger?

I just installed it yesterday, so I'm sure there are parts I don't understand well.
It's free, so let's install it and deepen each other's knowledge.

 

[e.t.l]

Could'nt you just make MD start Shizuku with boot trigger?

There's currently a flow (macro) in the device automation app Automate that does this

Start shizuku ⋅ Community ⋅ Automate for Android

My plan is to try to port it to Macrodroid, but it looks nontrivial, at least with my level of coding knowledge. Would appreciate any assistance anyone can provide!

 

[Dimlos]

@e.t.l
MacroDroid itself cannot execute adb commands with wireless debugging, so use Termux or LADB.
Just run adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.

 

[e.t.l]

@e.t.l
MacroDroid itself cannot execute adb commands with wireless debugging, so use Termux or LADB.
Just run adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.

I'm aware of that. But if the solution to every issue was "just do it manually" then none of us would have installed Macrodroid

MD can run adb commands via plug-ins. I'm currently trying to find which one is the most reliable.

 

[Dimlos]

@e.t.l
ADB Shell [Tasker Plugin] is not an option because it cannot be used immediately after reboot.
LADB is unstable in some areas, so if stability is important to you, I think Termux is the way to go.

I am interested to know which method you use and how you set up your macros and scripts.

 

[e.t.l]

I thought the Termux:Tasker plugin would work well, but I'm having difficulty with it. I think I'm not configuring it right. Would appreciate any help or examples of working configurations for the plugin

 

[Dimlos]

@e.t.l
Unlike MacroDroid, Termux and Termux:Tasker are more challenging because they cannot be operated via GUI.

Here is a link to a thread that explains Termux, which may be helpful.

Wifi ADB debug mode lost on restart?

oh that was it , sorry, i just search only the digits .-) thanks so much @MacroDroidDev I wish we could search just the numbers

www.macrodroidforum.com

 

[yeedatoy]

Dhizuku runs like shizuku but as a device manager so it starts on boot. Hail supports it. Regarding Shizuku running on boot you can use Automate. There is an automation that starts wireless debugging and shizuku on boot so apps such as rootless jamesDSP will always run

 

[yeedatoy]

Start shizuku ⋅ Community ⋅ Automate for Android

There's the automation link and here's a screenshot of dhizuku.

GitHub - iamr0s/Dhizuku: A Android Application for share DeviceOwner

A Android Application for share DeviceOwner. Contribute to iamr0s/Dhizuku development by creating an account on GitHub.

github.com

 

[e.t.l]

@Dimlos so far I have paired Tasker via ADB wireless and can launch adb (and therefore start.sh) from MD using the Tasker:Termux app. MD is also capable of enabling Wireless Debug (assuming the device is connected to an Allowed network). I'm stuck right now because for some reason, Termux does not connect automatically to ADB. Every time I launch Termux, I have to run adb connect [localhost_IP]:[port], and that's a problem because the port number is randomized every time Wireless Debug is toggled. Other apps like ADB seem to remember the connection and do not need to reconnect with the port number each time it's launched (or at least, they're able to query the port number programmatically), but I don't know HOW they do that.

 

[e.t.l]

Dhizuku runs like shizuku but as a device manager so it starts on boot.

Seems interesting. What does it actually DO, though? It's a little unclear from the repo. Does it do all of Shizuku's functions, AND act as device owner? What added benefit is there to be able to letting other apps act as device owner? What is a use case for this?

 

[Endercraft]

Other apps like ADB seem to remember the connection and do not need to reconnect with the port number each time it's launched (or at least, they're able to query the port number programmatically), but I don't know HOW they do that.

Either they use Logcat to get the port of they run adb tcpip (port, probably 5555) which lets you connect to adb using the same port even if you're disconnected from network.

 

[e.t.l]

Either they use Logcat to get the port of they run adb tcpip

Oh yeah it's probably tcpip. I tried that and adb connect [localhost_IP]:5555 returned "device already connected", but when I ran adb devices it showed the localhost... as "Offline". So now I'm stuck here - can't figure out how to make the phone appear online to Termux even after it's connected :/

 

[Dimlos]

I think that there is nothing difficult, but it is recognized normally.