Now that Shizuku (v13.6.0) can automatically enable itself on boot without root, some people with unrooted devices may prefer this over the...
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/mylastacntwascursed on 2025-06-03 00:45:26+00:00.

Now that Shizuku (v13.6.0) can automatically enable itself on boot without root, some people with unrooted devices may prefer this over the somewhat more cumbersome setup required to automatically enable Tasker’s own ADB Wifi on boot.

I’ve seen people here recommend using Termux or ShizuTools as an intermediate between Shizuku and Tasker, but this is wholly unnecessary. Tasker can utilize Shizuku directly!

Setup

  • In Shizuku, tap Use Shizuku in terminal apps > Export files
  • In the exported file rish, replace RISH_APPLICATION_ID="PKG" with RISH_APPLICATION_ID="net.dinglisch.android.taskerm"
  • In Tasker, go to Menu > More > Run An Action > File > Copy File
    • In From use the magnifier icon to select the file rish
    • In To put /data/data/net.dinglisch.android.taskerm/
    • Tap the back arrow in the top-left corner
    • (nothing happens, there’s no feedback)
  • Repeat the previous step for the file rish_shizuku.dex
  • Optional: to verify that the files made it to the other side, use Menu > More > Run An Action > Input > Pick Input Dialog > File, in Default Input put /data/data/net.dinglisch.android.taskerm/ and tap the back arrow in the top-left corner; a file browser with the contents of the directory is now shown
  • Create a global variable named %AdbShell with value sh /data/data/net.dinglisch.android.taskerm/rish -c

Use

  • In a Run Shell action, use %AdbShell 'your adb shell command', e.g. %AdbShell 'pm suspend com.instagram.android'

The first time you do this, Android will ask “Allow Tasker to access Shizuku?” After allowing this, Tasker will show up in the list of authorized applications in Shizuku.

Caveats

  • On my device, where commands execute instantaneously using ADB Wifi, using Shizuku adds a one second delay
  • When ADB Wifi is activated Tasker utilizes it internally for some actions that otherwise don’t work; this benefit is lost when using Shizuku instead
  • When rish and/or rish_shizuku.dex are updated in future releases of Shizuku, one might need to export those new versions to /data/data/net.dinglisch.android.taskerm/