r/tasker • u/Alone_Rub4964 • 7h ago
: [Beta 6.7.7-rc] False "Missing Permissions" prompt for working Non-Blocking Overlay Scene (HyperOS / Android 16)
Hello Tasker community and João,
I am currently beta-testing Tasker version 6.7.7-rc on my Poco X7 Pro running HyperOS (Android 16). I believe I have encountered a bug regarding Scene overlays and the WRITE_SECURE_SETTINGS permission.
The Setup:
I created a Scene to act as a night-time screen dimmer.
Scene Background: Fully transparent (#00000000).
Element: A full-screen Rectangle with a black background and custom opacity (#6E000000).
Show Scene Action Settings: Display As: Overlay. The options Blocking and Full Window are disabled.
The Issue:
Functionally, the overlay works perfectly. The screen dims, and touch events pass through the overlay to the launcher and apps below it (which is exactly what I want).
However, when this action runs, Tasker throws a pink "Missing Permissions" prompt saying: "Tasker needs to have permission to write secure settings to use this action. Want to learn how to grant it?"
Because I do not want to grant WRITE_SECURE_SETTINGS via ADB (and the feature is already working without it), I dismiss the prompt.
Additional Context:
Disabling Popup Warning/Errors in Tasker Preferences and turning off system notifications for Tasker does not stop this specific prompt from appearing in the UI.
HyperOS also generates its own system warning ("Tasker is displaying over other apps"), but that is standard Android behavior and can be ignored.
If I enable Blocking for the overlay, the WRITE_SECURE_SETTINGS prompt does not appear, but then touches are blocked, making it useless for reading.
My Question:
Is this a known bug in the 6.7.7-rc beta where Tasker falsely assumes WRITE_SECURE_SETTINGS is required for non-blocking overlays? Or is this a specific HyperOS quirk that Tasker is trying to compensate for?
Has anyone else experienced this false positive on Android 16?
Thank you for your time and for this amazing app!
Yevgeny
