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.
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.