Quick unlock no longer working since updated to Android 9
Samsung S8
Android 9
Same happened to me when I loaded a system backup from a phone running Android 8.1 onto my new Pixel 3a running Android 9.
Solved by going into Keepass2Android settings, disable fingerprint unlock, then re-enable fingerprint unlock.
Fixed. I had stopped Keepass using notifications but that is required for quick unlock to work.
Thanks for your suggestion. It didn't work for me but now I use fingerprint login which I never tried before
Quick unlock has not been working for me for quite some time. I always have to enter my long (20 character) password now. Not sure if this happened when my phone (T-Mobile Samsung Galaxy S9+) was updated to Android 9 or if it started after the April update to KeePass2Android. Since I don't use fingerprint unlock I didn't try the suggestion to disable/reenable fingerprint unlock. I do have notifications turned on for KeePass2Android.
I see this thread has been closed. Can it be reopened, or do I need to start a new thread?
@D000DM000R I'm pretty sure it's related to your system settings. Please make sure you see the "Enable QuickUnlock" checkbox when you open your database. If this is checked and you unlock the DB, what happens if you click the lock icon in KP2A's menu? Do you see the QuickUnlock notification?
Yes, I do see the QuickUnlock notification page.
If you click the notification, you should see the QuickUnlock screen where you can enter the last three digits (by default) of your password to unlock quickly. Is this working, too? If yes, what is NOT working?
Yes, that works fine.
The problem occurs when the app is inactive, automatically times out (app
timeout currently set to 5 minutes), and then locks the database. To unlock
the database after the database has auto-locked I need to use my full
master password rather than quick unlock.
On Sun, Aug 18, 2019 at 12:23 PM PhilippC notifications@github.com wrote:
If you click the notification, you should see the QuickUnlock screen where
you can enter the last three digits (by default) of your password to unlock
quickly. Is this working, too? If yes, what is NOT working?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PhilippC/keepass2android/issues/823?email_source=notifications&email_token=ADVPOYZWSXHPXCPPZOI4QTLQFGORXA5CNFSM4HMWBHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4RGMGY#issuecomment-522348059,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADVPOYZBI4D4O2DFYXYWUILQFGORXANCNFSM4HMWBHEQ
.
this very much sounds like it's a battery optimiztaion setting or something similar on your device, because QuickUnlock is enabled correctly, but Android kills the app while it's in background.
That will be the answer. I found this was the issue on my Samsung S8. Check power settings/battery/keypass app. Something like 'put to sleep when not in use'
Also I wasn't sure how/when quick unlock should be available so wasn't sure if it was working properly but understand now.
I did a bit of poking around and found that 'put to sleep when not in use'
was turned on for KeePass2Android (not sure how or why that option was
turned on). I've turned 'put to sleep when not in use' off and am testing
now.
On Mon, Aug 19, 2019 at 3:59 AM PhilippC notifications@github.com wrote:
this very much sounds like it's a battery optimiztaion setting or
something similar on your device, because QuickUnlock is enabled correctly,
but Android kills the app while it's in background.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PhilippC/keepass2android/issues/823?email_source=notifications&email_token=ADVPOY5IYT2LI5LUCY3WS6LQFJ4IFA5CNFSM4HMWBHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4SQK6I#issuecomment-522519929,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADVPOY4TWU5YCSJ2LRELXJTQFJ4IFANCNFSM4HMWBHEQ
.
tuning the option 'put to sleep when not in use' did fix the problem. Thanks for the help.
Most helpful comment
Same happened to me when I loaded a system backup from a phone running Android 8.1 onto my new Pixel 3a running Android 9.
Solved by going into Keepass2Android settings, disable fingerprint unlock, then re-enable fingerprint unlock.