FEAT: Keep App Open (FLAG_KEEP_SCREEN_ON)

[rtfmkiesel]

Thanks for your work, it is working really great.

What do you think about introducing a toggle in the settings that effectively "disables" the phone's lock screen, even without user interaction? While I'm not versed in Android development, I believe a video player can implement a similar feature using something like FLAG_KEEP_SCREEN_ON, which prevents the screen from locking even when the user isn't interacting with the device.

My use case is that I often need to take a few pictures and then wait a minute or two before taking more. During this waiting period, my phone locks. Although I can adjust the lock screen timeout, doing so before every photography session can be quite inconvenient.

Thanks

[Staacks]

That should be possible... Just to be clear about your use-case: Is the screen lock interferring with the intervalometer function (because that should have been fixed with the previous release) or is it just the invonvenience of having to unlock the phone and possibly missing the trigger moment you have been waiting for?

[rtfmkiesel]

No, I'm just using the regular shutter button. ty

[Staacks]

ok, I have put it on my todo list. Should not be difficult, but it may be a while until I get around to update this app again.

[rtfmkiesel]

I quickly did a PoC for this in the linked PR. I verified that this works on Android 16 and an A7C II.

This was done by AI, as I have no idea how to do stuff in Kotlin. If you do not want such code, I fully understand that. I just wanted the feature for an upcoming session. Merge it or close the PR and use it as a reference.

[Staacks]

Thanks, I don't mind AI code on principle, but I have never been entirely convinced by the results as it always shines through that the AI does not really "understand" what it is doing. In case of Android in particular it is a general non-AI problem that there are always seven ways to do things, of which three are outdated, two not applicable, one uses a restricted API and the final one only works fine on the latest two API levels. Of these the AI usually picks a random one it finds on stackoverflow :)

Anyway, it is still impressive that this can be implemented just with a few prompts and it makes clear that I do not have to spend a lot of time on this feature. From a quick glance at the code it looks clean (it always does), but the AI decided to keep track of the user setting in a Flow that is meant to keep track of granted user permissions (hence that flow is named "Permissions").

Will look at it when I find some time.