Privileged actions

[summer-son]

What are you trying to do?

Do I understand it correctly that in order for Privileged actions to work I need to add corresponding/missing permissions to Manifest XML (and build it)?

What have you tried?

No response

Version and platform

No response

[SysAdminDoc]

No — you don't need to touch the manifest or rebuild, and adding permissions there wouldn't help.

Actions like airplane mode, mobile data, screenshot, reboot, screen off and wake aren't gated by a permission OpenTasker can declare. Android reserves them for system or device-owner apps, so no uses-permission line grants them to a normal app. That's why they were reported as unsupported rather than "missing a permission".

The supported route is Shizuku, which runs a small service as the shell user (UID 2000) and lets an app ask it to perform exactly the operations it has allowlisted. OpenTasker now ships that transport, so those six actions work once Shizuku is running:

1. Install Shizuku and start it (wireless debugging on Android 11+, or adb from a computer; it needs restarting after a reboot). Setup: https://shizuku.rikka.app/guide/setup/
2. In OpenTasker, open Setup and grant the Shizuku permission on the Shizuku row.
3. Turn off the Shizuku kill switch on that same row — it defaults to on, so a process restart can never enable privileged behaviour before your preferences have loaded.

Two things worth knowing:

• OpenTasker only ever sends a fixed, checked-in argument list per action. Anything outside that allowlist is refused before dispatch, and an ordinary app-UID process is never used as a fallback.
• With Shizuku absent, stopped or revoked, those actions fail closed and say so rather than pretending to work.

The action editor now names the requirement and points at Setup, instead of only failing when the task runs — that gap is what made the manifest look like the answer.

[summer-son]

Thank you @SysAdminDoc for the answer!

But I'm currently able to run Airplane mode on/off (and choose which radios are switched by it) and lock screen (and perhaps others - need to check) by Tasker after I granted it WRITE_SECURE_SETTINGS via ADB and Accessibility permissions. The latter, AFAIK, has to be also mentioned in Android Manifest XML, so then the user can manually enable them in Accessibility Settings. Hence was my question...

Can I do so with OpenTasker?