Keepass2android: Suggestion: QuickUnlock timeout

[arden13]

I think it would be great if I could set a timeout feature for QuickUnlock. That way if I leave it open overnight or after 6 hours or whatever I have to input my master password to gain access.

I apologise if this is already a feature and I can't find it.

[Wh1rledPeas]

I just went through the entire app settings and can't find this either. I think it would be nice to have a setting such as this, so after a particular amount of time quick unlock expires and you have to reenter the master password.

The only setting that currently exist, that I can find any way, is the time out for the quick unlock itself. Which defines the amount of time the app remains unlocked before asking for the quick unlock password again.

[binarious]

I do have to enter my master password after some time (and would like to turn it off).

[NumbGnat]

@binarious Go to...

Settings -> Application -> Security -> Application Timeout

[arden13]

That doesn't solve the QuickUnlock issue. It just locks the database.

On Mon, Apr 9, 2018, 4:29 PM Todd Powers [e-mail] wrote:

@binarious https://github.com/binarious Go to...

Settings -> Application -> Security -> Application Timeout

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PhilippC/keepass2android/issues/310#issuecomment-379883765,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUDa8MleKxkr_VrH3uizcJ0dxzQaLtDtks5tm8SSgaJpZM4S3Zz3
.

[binarious]

FYI: I solved my problem by disabling Android's battery optimizations for keepass2android. The QuickUnlock now always works as expected. A setting for the timeout (and maybe the documentation to disable battery optimizations) is still a good suggestion.

But isn't this a dup of #53?

[NumbGnat]

@binarious You are correct. This is a duplicate of Issue #53, created by @Alan-Smith.

Regarding your particular issue, knowing Android the way I do, there are a number things that might affect how it shuts down. I personally don't allow battery optimization on many of my apps that I expect notifications from or that I expect to provide their automatic functionality from time to time in the background. Things like messenger apps, virus protection, etc.

I also make sure that the status bar icon remains for as long as the database is open. That is another thing that can affect weather Android shuts the app down or not.

I'm not sure if there's something keepass2android can do to detect weather it is currently included or excluded from battery optimization and warn the user, or if there's something in the applications manifest that it can indicate to the Android system weather battery optimization can adversely affect the application.

Either way... This seems like a discussion for a different issue all together. I would suggest that you create one if you think it's needed. Battery optimization has been discussed in a couple of other issues on the site. All of which have been closed.

[electrofloat]

Please everyone, don't hijack the issue. Read the OP and only reply if it is relevant.
Anything other should go into a separate issue.

[binarious]

I wasn't hijacking. I thought I was running into a predefined timeout I'd like to be able to configure. Turned out not to be the case. Anyways, @arden13, this issue can be closed as being a duplicate.

[PhilippC]

I agree this is a duplicate of #53