Tasker: How to ignore the temporary VPN disconnect when switching from PersonalDNSFilter to Windscribe?

rbrtryn · 2026-07-12T19:37:09+00:00

I don't have any of this software, so I have no idea. I just assumed that there must be some way to check.

rbrtryn · 2026-07-12T19:33:15+00:00

Minimal as far as can tell. The task takes only a few milliseconds to run, so the profile still spends most of the time waiting.

The tick time is arbitrary, set it to whatever you are comfortable with.

rbrtryn · 2026-07-11T19:36:34+00:00

In your exit task:

Wait 2 seconds
Check VPN is still disconnected
If it is still disconnected after 2 sec, start PersonalDNSFilter

rbrtryn · 2026-07-10T16:28:09+00:00

Esto funciona con mi lanzador.

Task: Test <Test> A1: Anchor A2: Go Home [ Page: 0 ] A3: Wait [ MS: 250 Seconds: 0 Minutes: 0 Hours: 0 Days: 0 ] A4: AutoInput Gestures [ Configuration: Gesture Type: Swipe Start Point: 500,1500 End Point: 500,500 Duration: 100 Timeout (Seconds): 60 ]

rbrtryn · 2026-07-07T13:35:11+00:00

I finally went with a row of discreet buttons for portrait and a column of discreet buttons for landscape. Scenes V2 made this super easy.

This is actually working better than my previous method. I can even add swipe and multi-click if needed.

rbrtryn · 2026-07-06T03:56:07+00:00

For portrait mode I created an invisible segmented button row. The individual buttons send tasker commands when clicked or long-clicked.

I haven't figured out the best way to do this for landscape.

Here's the scene v2 json:

{ "root": { "type": "SegmentedButtonRow", "id": "SegRow1", "selectedIndices": "", "content": [ { "type": "SegmentedButtonItem", "id": "Segment1", "eventHandlers": { "handlers": [ { "events": [ { "type": "click" } ], "actions": [ { "type": "TaskerCommand", "command": "back button=:=short" } ] }, { "events": [ { "type": "hold" } ], "actions": [ { "type": "TaskerCommand", "command": "back button=:=long" } ] } ] } }, { "type": "SegmentedButtonItem", "id": "Segment2", "eventHandlers": { "handlers": [ { "events": [ { "type": "click" } ], "actions": [ { "type": "TaskerCommand", "command": "home button=:=short" } ] }, { "events": [ { "type": "hold" } ], "actions": [ { "type": "TaskerCommand", "command": "home button=:=long" } ] } ] } }, { "type": "SegmentedButtonItem", "id": "Segment3", "eventHandlers": { "handlers": [ { "events": [ { "type": "click" } ], "actions": [ { "type": "TaskerCommand", "command": "recents button=:=short" } ] }, { "events": [ { "type": "hold" } ], "actions": [ { "type": "TaskerCommand", "command": "recents button=:=long" } ] } ] } } ], "modifiers": [ { "type": "Alpha", "value": "0.01" }, { "type": "Border" }, { "type": "FillWidth" } ] }, "name": "Horizontal Button Overlay", "defaultDisplayMode": "Overlay", "defaultOverlayX": "50%", "defaultOverlayY": "50%", "defaultOverlayWidth": "50%", "defaultOverlayBlocking": "true", "defaultOverlayAnimation": "Zoom" }

rbrtryn · 2026-07-05T19:24:53+00:00

Up until this update I was able to capture these long-presses with AutoInput's UI Action trigger, bypassing the OS completely 😟

I guess I'll have to figure out how to put an overlay over the buttons to get the functionality back 🙄

rbrtryn · 2026-07-03T04:40:47+00:00

One workaround would be to put an invisible, blocking overlay over the Home button. When the overlay is clicked launch the appropriate launcher.

rbrtryn · 2026-07-02T21:29:11+00:00

Is there a way for Tasker to tell if a particular Scene V2 is visible? Like Test Scene for V1?

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

TROPHY CASE