Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Prevent system backup from clearing database lock state / Allow to auto-export settings #2719

Open
schklom opened this issue Nov 29, 2024 · 0 comments

Comments

@schklom
Copy link

schklom commented Nov 29, 2024

When backing up KP2A through the system (Seedvault), the database loaded gets cleared from memory and I need to input the full database password (i disabled biometric unlock).

The way I see it, there are 2 possible ways to avoid that inconvenience.

Option 1

Can this be prevented, e.g. (not sure if doable) by storing the memory state to a file in Android/data/... on backup, and restoring that on app launch if it exists?

Option 2

If option 1 is not good, I would like to export the app settings (name and locations of databases i.e. the list of databases shown on the app first page, TOTP Seed field name, Length of QuickUnlock key, etc...), ideally automatically on change to a user-picked directory like how Obtainium does.
This way, I could exclude KP2A from being backed up by the system (i.e. keep my database QuickUnlock-able after system backup), and be able to manually restore the app settings whenever I need to re/install the app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant