PhilippC / PhilippC/keepass2android
[BUG] USB Keyboard Plug-In keeps getting removed on every reboot
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
I am using the USB Keyboard plug-in. It works fine on my S21+ (I have automatic keyboard setup automation / automated usb gadget tool on boot, thanks to magisk, root, llamalabs automate).
Every time I boot my phone, I go to K2A, settings, plugins.. and the list is empty.
I then install the USB Keyboard plug-in, and it's there in settings/plugins, available until next boot. It works fine / text is typed over USB.
I see that the keepass2android data directory does contain KP2A.Plugin.th.in.whs.k2ausbkbd.xml with:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<string name="requestToken">f9447784-4bee-42b6-b58f-e684543ea6c7</string>
<string name="scopes">["keepass2android.SCOPE_CURRENT_ENTRY"]</string>
<string name="accessToken">M79Fd*......*QS</string>
</map>
I did have to flash a bluetooth patch and vaultkeeper patch to prevent bluetooth pairings from dissapearing. My bluetooth pairings now are fine after a reboot, but the plugin in k2a dissapears. Could this be related?
Describe what you expected to happen:
I expect the plugins to stay after a reboot
What version of Keepass2Android are you using?
1.10-pre
Which version of Android are you on?
14
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
Reproduce the reboot behavior on Android 14 with the USB Keyboard plug-in and inspect the Keepass2Android data directory, including KP2A.Plugin.th.in.whs.k2ausbkbd.xml. Trace how the plug-in is discovered and retained across boot; done means the installed plug-in remains listed and usable after reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100