PhilippC / PhilippC/keepass2android
[QUESTION] Why do I always need the full password on my new phone? On the old one QuickUnlock worked
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
What version of Keepass2Android are you using?
1.11-r0 (on both phones)
On my previous phone, Motorola Edge 30 pro with Android 14, I could use QuickUnlock unless I quit Keepass2Android. I now have another phone, a Motorola Edge 50 pro, also Android 14, very often I need to type the full password. I've gone through the settings side by side, but they seem equal. Why do the two behave so differently? I like the QuickUnlock...
I haven't investigated if there is a time after which the full path is needed. It works if I go back to the app after a short while, but I get the feeling that if it takes more than an hour or so, then it wants the full password. But I haven't methodically checked this, so I may be well off here...
Any idea?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Reproduce the QuickUnlock behavior on the Motorola Edge 30 Pro and Edge 50 Pro with Android 14, comparing short and roughly hour-long gaps between app use. Done means identifying why the devices differ or documenting a confirmed cause and expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100