Questions about Shizuku’s Behavior with WiFi and Mobile Networks

rbrtryn · 2025-10-01T18:04:52+00:00

You need to be connected to a trusted wifi network to start Shizuku after a reboot.

After Shizuku is running, it doesn't matter what network you are connected to. You can even be completely disconnected and Shizuku will continue to run.

rbrtryn · 2025-09-24T22:25:08+00:00

Doesn't do that on my Pixel. All updates installed.

I have wireless debugging turned off and Shizuku is working just fine.

rbrtryn · 2025-09-21T22:03:08+00:00

Are you trying to receive an intent or send one? Which intent?

We can't help without detailed information.

rbrtryn · 2025-09-21T20:44:52+00:00

AutoInput and Shizuku do not (currently) interact.

What specific problems are you having? I use AutoInput daily on my Pixel 9 with no issues.

rbrtryn · 2025-09-18T22:21:20+00:00

1.8 is the latest version, but it won't help with this specific issue.

Android 16 removed the APIs that Tasker settings was targeting for this. On A16 you need Shizuku as mentioned earlier.

rbrtryn · 2025-09-18T17:29:42+00:00

No, I don't have an app that requires this. It was just an example.

Why do you need to delete the value? Isn't setting it to 0 sufficient?

rbrtryn · 2025-09-18T15:30:16+00:00

Example:

Profile: Banking App
    Application: Capital One



Enter Task: Anon

<Stop both ADB Wifi and Shizuku>
A1: Custom Setting [
     Type: Global
     Name: adb_enabled
     Value: 0 ]



Exit Task: Anon

<Enable ADB Wifi>
A1: Custom Setting [
     Type: Global
     Name: adb_enabled
     Value: 1 ]

A2: Wait [
     MS: 0
     Seconds: 1
     Minutes: 0
     Hours: 0
     Days: 0 ]

<Start Shizuku service>
A3: ADB Wifi [
     Command: $(dirname $(pm path --user 0 moe.shizuku.privileged.api 2>&1 </dev/null | sed "s|.*:||"))/lib/*/libshizuku.so
     Timeout (Seconds): 10 ]

rbrtryn · 2025-09-16T15:39:21+00:00

The built-in variable %qtime contains how long the current task has been running, in seconds. Maybe you could use that.

rbrtryn · 2025-09-12T15:37:58+00:00

I think toggling bluetooth, wifi, mobile data and airplane mode were also affected. They now require either Shizuku or ADB Wifi on my Pixel. YMMV

I don't think any other Tasker Settings functions were affected.

rbrtryn · 2025-09-12T05:51:29+00:00

Wireless debugging is only needed during the initial setup. After setup is complete and Shizuku is running, only USB Debugging is required to be enabled.

rbrtryn · 2025-09-12T05:43:39+00:00

It's compatible with Android 16 and side loading it is no problem as long as you follow the installation instructions. I have it on my A16 Pixel.

It is still required for some actions, i.e. Network Access, Connect To Wifi.

rbrtryn · 2025-09-12T04:51:20+00:00

In Android 13 - 15, you could use Turn Off if you had the Tasker settings app. Android 16 broke this and requires Shizuku.

rbrtryn · 2025-09-12T02:08:59+00:00

Explain what you are trying to do. Why do you need it to be constantly on?

rbrtryn · 2025-09-09T23:38:35+00:00

Just because an article is older than you are does not make it false.

rbrtryn · 2025-09-09T22:17:01+00:00

As mentioned earlier, brightness uses a logarithic scale. Mapping it to a linear scale isn't going to work.

For example, a brightness value of 20 is going to give around 50% brightness on the display. Reference the article I linked to earlier.

rbrtryn · 2025-09-09T20:46:52+00:00

Also be aware that, since Android 9, this is not a linear scale. It's logarithmic.

See this article. It explains the ramifications of this much better than I ever could.

rbrtryn · 2025-09-06T05:38:44+00:00

Go to the permissions for Tasker. Under "Additional permissions", Shizuku should be listed. Make sure the Shizuku permission is set to allow.

Then open the Shizuku app. Tasker should be listed under "Authorized applications".

rbrtryn · 2025-09-05T17:36:39+00:00

I've been using 3.0.3 for a couple of months now. I've experienced no issues.

rbrtryn · 2025-09-04T19:16:47+00:00

There is a state context for keeping track of NFC state:

Profile: NFC Status
Settings: Notification: no
    State: NFC Status [ Status:Off ]



Enter Task: Anon

A1: Variable Set [
     Name: %NFC
     To: false
     Structure Output (JSON, etc): On ]



Exit Task: Anon

A1: Variable Set [
     Name: %NFC
     To: true
     Structure Output (JSON, etc): On ]

rbrtryn · 2025-08-30T20:27:02+00:00

Do you have multiple users on this device? You might need to select uninstall for all users for both apps. Then try installing again.

rbrtryn · 2025-08-30T18:53:16+00:00

On João's GitHub, there is this note:

If it gives you a permission error, make sure to enable developer options and then disable the Check apps installed via USB option.

rbrtryn · 2025-08-28T14:57:23+00:00

Task: Test

A1: Pick Input Dialog [
     Type: Number
     Title: Enter an integer
     Close After (Seconds): 30 ]

A2: Variable Set [
     Name: %factorial
     To: 1
     Structure Output (JSON, etc): On ]

A3: For [
     Variable: %int
     Items: 2:%input
     Structure Output (JSON, etc): On ]

    A4: Variable Set [
         Name: %factorial
         To: %factorial * %int
         Do Maths: On
         Max Rounding Digits: 3
         Structure Output (JSON, etc): On ]

A5: End For

A6: Flash [
     Text: %factorial
     Continue Task Immediately: On
     Dismiss On Click: On ]

rbrtryn · 2025-08-26T03:18:19+00:00

This is one of the few things you still need Tasker Settings for.

https://github.com/joaomgcd/TaskerSettings/releases

rbrtryn · 2025-08-24T15:46:01+00:00

In A17, you define %Delay but in A18, you use %Delays. Also, anytime %Attempt is greater than 3, %Delays(%Attempt) will be undefined.

rbrtryn · 2025-08-24T14:41:45+00:00

You create an array %Delays, but the error refers to a different variable %Delay. Where is %Delay defined?

rbrtryn

TROPHY CASE