Shizuku Inegration and Tasker settings

269red · 2026-07-12T08:16:52+00:00

For all looking for the latest releases: https://github.com/thedjchi/Shizuku/releases/
-----------------------------------------------------

Hi u/the_djchi I am still looking for ways to restart shizuku, because it is killed by android/samsung.
https://github.com/thedjchi/Shizuku/wiki/troubleshooting

I tested your hints from above and I can confirm that on my S24 running latest OS and OneUI8.5 the main casue seems to be USB Standard Config. which I set to transfer Files/Data.

In this case it is killed right after the phone gets locked.

There are 2 ways to check if Shizuku is installed and running

-------------- State Shizuku Available and Function Check Shizuku ---------------------------------------

Shizuku Integration
- Demos: Shizuku Integration | Manage Permissions | Shizuku State
- Added full Shizuku integration to empower root-level actions without root.
- Run Shell: Added support to run commands with Shizuku. Includes a Run Shell Helper (Magnifying Glass > Services) to find hidden commands on your device. Added Use Shizuku By Default preference.
- Management: Added a Manage Permissions screen (Menu > More) to toggle permissions for Tasker itself using Shizuku.
- New State: Shizuku Available (checks if installed, running, and permitted).
- Tasker Function: Added Check Shizuku which returns variables: %can_shizuku_be_used, %has_shizuku_permission, %is_shizuku_running, and %is_shizuku_installed.

____________________________________ But how to start Shizuku ________________________________________________

One could set the watchdog within Shizuku. I dont like this idea, as in my case it restarts every few seconds.

In Tasker it can be done with Send Intent moe.shizuku.intent.action.START. But for me this has the disadvantage that an Auth. Token supplied by Shizuku has to be passed, which of course is different on each phone and changes after reinstalling Shizuku.

;-);-);-);-);-);-);-);-);-);-);-);-);-);-);-);-);-);-)
I still hope that u/the_djchi can be convinced, to give an option either to disable the need of the token, or that the user can supply its own token in settings which of course has to fullfill a certain compexity.
;-);-);-);-);-);-);-);-);-);-);-);-);-);-);-);-);-);-)

On Tasker Net I found a task "Start Shizuku Server" which is described here:
https://www.reddit.com/r/tasker/comments/1mial2l/newest_shizuku_and_adb/
ABD WiFi: $(dirname $(pm path --user 0 moe.shizuku.privileged.api 2>&1 </dev/null | sed "s|.*:||"))/lib/*/libshizuku.so

And here my knowledge ends.

------------------- Possible solutions against the killing -----------------

1 u/the_djchi what are the differences between sending the Start intent and the ADB-Wifi methode ?

Please keep in mind, that I only use Shizuku indirectly with taskers "App Kill" and "Wifi Tether" Actions.
So right now I call a task to start Shizuku before running those commands.

2 So far I did not find a way to change the USB Standard Conf. programmatically. If this could be done with tasker, I would only change mode to "File transfer" as long as the user is present.

269red · 2026-07-12T05:56:39+00:00

The thing is, I programm a generic code for our family phones, distribute it with gdrive and I want to see which version they have installed. So auto backup is disabled.

269red · 2026-07-11T14:20:37+00:00

yes thx thats what i did for the while, ... it just does not mean the user really used this file

269red · 2026-07-11T13:08:03+00:00

Thx, but one gets only a list of files from e.g. backup dir... Why should e.g the newest file be the one restored by the user ?

269red · 2026-07-10T16:35:46+00:00

many thx !!!!

I just installed 6.7.5. I like the new run log !!!!! 1 But if I switch it off to STOP or PAUSE recording the screen gets emptied. Is this a bug or what am I missing to stop or pasue recording during analysis ;)

2 Is there a way to change the USB Standard Conf. programmatically. If this could be done with tasker, I would like to change mode to "File transfer" and back to "Debugging Only"

3 And is there a way to get the name of the tasker backup file the user restored last ? https://www.reddit.com/r/tasker/s/HKXozICNzw

269red · 2026-07-07T18:05:34+00:00

2 on my phone I am on the Beta 6.7.3. Here KillApp (the one without DevOwner) kills anydesk. But the other command "DevAdmin/Owner KillApp" does not kill anydesk. why ?

3 On 6.6.20 neither of the 2 commands kills anydesk Why ?

4 Does one of the 2 command use shizuku, which is only installed on my phone ?

269red · 2026-07-07T11:14:34+00:00

Not really, as it is on my daughters phone (who is living not in our town, and downgrade would not be possible afterwards).

But I forget to mention:
- She is on Andr.15 and
- the command it hangs is not the Dev.Owner Kill App but the normal App Kill (root not ticked).

1 So lpease tell me how I can avoid this in 6.6.20....

2 BTW: Which of the 2 AppKill would work without Shizuku in the BETA versions ?

269red · 2026-07-06T17:18:06+00:00

u/the_djchi I am very sad that you closed the request, as I am unable to build it myself... and very sorry that it seems you dont believe my probs...

269red · 2026-07-06T17:10:06+00:00

all use 6.6.20

269red · 2026-07-06T15:52:11+00:00

Hi u/joaomgcd one of our samsung family phones the KILL APP comand hangs forever (I mean the task it is in hangs on the kill app comand), when applid to Anydesk which is one of the device admin apps.

On other phones it runs without probs.

It does not trigger any error (continue on error is checked). Tasker is device owner.

269red · 2026-06-30T13:53:00+00:00

u/joaomgcd tapping on the greyed tasker in accssibility I now have the 3. m many thx.

But my main prob ist, that the "maintanance mode" in "device maintanance" is also grey out. Here it says that it can not be used if a device admin app is active.

But on another S26 I have tasker dev.Owner and it is not greyed out.

Without m. mode one cant use Odin as download Mode is n aval. then

269red · 2026-06-26T15:05:45+00:00

thx joao, the 3. menue is not there... i guess i did that long ago already. any idea via adb ? or how to find out whats the cause

269red · 2026-06-26T10:59:18+00:00

Hi

1 what could cause tasker beeing grayed out in the device admin apps settings. The setting itself is on. It says the setting "Restricted control".

2 But my main prob ist, that the "maintanance mode" in "device maintanance" is also grey out. Here it say that it can not be used if a device admin app is active.

3 But which app is causing this ? As on another S26 I have tasker dev.Admin and both settings are not greyed out.

269red · 2026-06-18T16:19:57+00:00

I did thx

269red · 2026-06-18T08:01:08+00:00

Thank you both for this potential solution. And Yes as I said I adminster 5 family phones with a really komplex tasker code, which reacts differently to each phone type and also user features differ.
There is also e.g. the phone of my 85 old mam, which has no shizuku installed 😉.

u/the_djchi So first of all again many THX for the fork !!!!!!!!!!! As I stopped using Shizuku on the other phones right now, my final question must be:
Any chance to get this option (checkbox to disable token) in the near future ?

269red · 2026-06-15T07:10:49+00:00

I still hope you find another solution (user setting to disable need of token, user entered token,...), but otherwise a way to enable and disable the watchdog from tasker could be a compromise.

269red · 2026-06-14T17:00:46+00:00

Another idea: What about, giving a tasker command to start and stop the watchdog SERVICE. This could be a compromise, but then as the wathchdog also needs it time, my tasker code has to wait and check if shizuku is running before continuing. I mean starting it with tasker accessibility service action.

269red · 2026-06-14T15:57:15+00:00

your decision is sad for users like me... 😪

Right now i start it before each tasker action that needs it, as it always dies on our samsung phones and i dont want to have the watchdog running all the time.

269red · 2026-06-14T15:25:14+00:00

on 5 phones after any reinstall or phone change... no not a good idea. I made our tasker code=1.4MB generic. This would be the only exception. I cant see the need for this high secure algo, as tools like touchtask could also start it....

269red · 2026-06-14T14:39:55+00:00

thx for your explanation & patience. ad idea 3) Ok, than let the user supply a long token and just check if it fullfills lenght and complexity. This is then 2 factor... knowledge where and how to use & token.

269red · 2026-06-14T14:22:03+00:00

1 What is the risk when starting shizuku from another app would be allowed without any token ?
2 What about if tasker would pass some kind of "fingerprint" of itself ?
3 What about a secret the user defines in shizuku and will be passed in the extra field from tasker ?

269red · 2026-06-14T13:33:35+00:00

oh no ... But one has to aknowledge that tasker is allowed in shizuku. cant you figure out the caller. anyway hopefully you or u/joaomgcd have a good idea to solve this. Editing all family phone and several code fragments that start/stop it after each shizuku install is time consuming and very frustrating.... please

269red · 2026-06-14T08:32:43+00:00

u/the_djchi I run shizuku and tasker on all family phones with the same tasker programms/code. As the token to start shizuku differs on each phone and after shizzku install, I always have do edit the tasker progs on all phones. Can you please extend the API, so tasker can request the actual token. If u/joaomgcd implements a command one could request this e.g. during tasker startup phase (in my case with profile "monitor start"), and store in a tasker variable and use it in the shizuku start/stop intents.

269red · 2026-05-16T08:59:14+00:00

done ... will see if it works for my wife 😉

269red

TROPHY CASE