[Feature Request] Start only after screen is locked (or lock screen although AlwaysOn is active)

[la-balisa]

Samsung s10e
LineageOS 17.1
Rooted
No GAPPS

Hi ! I'm trying this application, because i think it could help me to have a replacement for LED notification (which is missing on my phone).
For now, it seems to work fine, but there is one thing i noticed : i usually set my security settings to lock the screen like 30 seconds after it shuts down, so i can quickly light it on if necessary. But when AlwaysOn is active, this timer isn't taken into account. So if i turn on screen like 10 minutes later, i go straight to the launcher, without needing the PIN !
If i set security to lock instantly when screen goes off, AlwaysOn works fine, and PIN is needed ; but i don't really like this setting.

As an insight, "Always On AMOLED" (another AOD app on fdroid) offers a setting to wait for the lock screen before starting ; this very functionnality seems to work fine on my phone (although the whole app is functionning very poorly)

Also, native LineageOS "Always On" setting works fine with delayed lock ; but isn't configurable at all, although i would like to remove clock (which i can do with your app :-) )

Anyway, thanks for your work, and feel free to ask for more info or whatever !

[Goutte]

From https://stackoverflow.com/questions/16635221/android-get-lock-timeout-programmatically

lock_screen_lock_after_timeout and an internal clock are perhaps what's needed to know whether to lock or not

[RedSteel-1]

Thanks a lot for the awesome program! :-)

About the issue:
This is a bad security issue. :-(

After screen timeout (system setting), the stock always-on is activated and locking the screen happen, this is how it supposed to work.
However, when using "Always On", it gets activated after screen timeout (system setting) but the device is unlocked!

Many might think that then screen timeout happens and always on runs, the phone is automatically locked, which supposed to be the case, but is not the case with "Always On".

Thinking that the phone is locked while it is actually not locked is a security issue and a false sense of security.

So, really hope this can be fixed.

[RedSteel-1]

This issue should not be classified as a feature request, cause this is actually a bug (a security bug)

[RedSteel-1]

Been a long while,
Any updates on this so far?