android: add launcher shortcuts to connect and disconnect the VPN#810
Open
brettjenkins wants to merge 1 commit into
Open
android: add launcher shortcuts to connect and disconnect the VPN#810brettjenkins wants to merge 1 commit into
brettjenkins wants to merge 1 commit into
Conversation
Add an AutomationActivity trampoline and two static launcher shortcuts (Connect, Disconnect) wired to the existing CONNECT_VPN / DISCONNECT_VPN intents. The actions can also be invoked from Samsung Modes and Routines or Tasker. The activity exists because starting an activity reliably wakes an app that the OS has force-stopped or deep-slept (e.g. Samsung battery management) and lets connect start the foreground VPN service, whereas the broadcast/Worker path is unreliable from that state. Exit-node automation is unchanged and remains available via the existing IPNReceiver USE_EXIT_NODE broadcast once the VPN is connected. Updates tailscale/tailscale#10831 Updates tailscale/tailscale#14148 Updates tailscale/tailscale#13623 Updates tailscale/tailscale#18847 Updates tailscale/tailscale#9531 Updates tailscale/tailscale#9497 Updates tailscale/tailscale#16415 Updates tailscale/tailscale#17855 Updates tailscale/tailscale#17738 Signed-off-by: Brett Jenkins <brett@brettjenkins.co.uk>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two static launcher shortcuts — Connect and Disconnect — backed by a transparent, no-UI
AutomationActivitytrampoline on the existingCONNECT_VPN/DISCONNECT_VPNintents. The actions can also be invoked from Samsung Modes & Routines and Tasker (Send Intent → Activity).Why an activity rather than the existing broadcast
I wrote the original
IPNReceiverbroadcast support, and it worked reliably when it landed. Over successive Android releases the background-execution and power-saving restrictions have tightened (Doze, app standby, and OEM battery managers like Samsung's deep sleep), and the broadcast path has become unreliable at waking an app that's been stopped or slept — it often can't start the foreground VPN service from that state.Starting an activity avoids this: it wakes the app and lets connect start the foreground VPN service. The existing broadcast actions are unchanged.
On-device validation
On a Galaxy S25 (SM-S948B, Android 16), with Tailscale put into deep sleep (hibernated + background-execution denied + restricted standby bucket + force-stopped) and triggered by real Tasker intents:
IPNReceiver: failed to connectAutomationActivity: connected — both screen-on and screen-offNotes for reviewers
IPNReceiver. This adds an activity entry point for the reliable foreground-wake path, not new capability.IPNReceiverUSE_EXIT_NODEbroadcast once connected.Related issues
Implements the launcher-shortcut / automation requests in tailscale/tailscale#9531, tailscale/tailscale#9497, tailscale/tailscale#16415, tailscale/tailscale#17855, and tailscale/tailscale#17738, and improves the broadcast-intent reliability reported in tailscale/tailscale#10831, tailscale/tailscale#14148, tailscale/tailscale#13623, and tailscale/tailscale#18847.