Support Inputstick

[github-k8n]

Keepass2Android supports plugins, one of which allows the use of Inputstick http://www.inputstick.com/
https://github.com/inputstick/KP2APlugin

A feature request would be to natively support Inputstick to type username/password/URL etc.
https://github.com/inputstick
https://github.com/inputstick/InputStickAPI-Android

[J-Jamet]

Linked to #259 #80

[schlomie]

A modest proposal, or as a stopgap...

You wouldn't necessarily need to integrate InputStick's API, at least not right away.

This came up in F-Droid not so long ago:
https://github.com/TheLastProject/ShareToInputStick
https://f-droid.org/en/packages/me.hackerchick.sharetoinputstick/

It acts as a share target, and then sends whatever arbitrary text you share with it to your InputStick. You would just need some kind of mechanism to select whichever field (username, password, email, attribute) you wanted to share; have it bring up the "Share With..." dialog, tap on "Share To InputStick" and you're done.

That said, I'm not much of an Android developer and I don't really know what all is involved with Android's Share With API - if there are any security concerns, so on and so forth.

Just throwing this out there as an idea.

[super9mega]

I just got an input stick and would love this to be implemented (I know its not as helpful as something like actual code but I wanted to show support). I work as IT and this would help out and make my day to day operations so much faster, currently the way to do it is to copy then use "usb Remote" in order to paste it, and it just adds alot of delay I could be using to fix the issues themselves. if you need any help I'm here and can test versions with this in it as well.

[Maingron]

Yeah, I need to send my credentials to Inputstick on a daily basis.
Unfortunately, without such integration, I have to stick to Keepass2Android for now

[wschlich]

I'd also love to have native InputStick support directly integrated in KeePassDX! <3

A modest proposal, or as a stopgap...

You wouldn't necessarily need to integrate InputStick's API, at least not right away.

This came up in F-Droid not so long ago: https://github.com/TheLastProject/ShareToInputStick https://f-droid.org/en/packages/me.hackerchick.sharetoinputstick/

It acts as a share target, and then sends whatever arbitrary text you share with it to your InputStick. You would just need some kind of mechanism to select whichever field (username, password, email, attribute) you wanted to share; have it bring up the "Share With..." dialog, tap on "Share To InputStick" and you're done.

ShareToInputStick itself works kinda well for me, but many times, connecting to an InputStick fails for the first time, so you have to re-select/tap the same device in ShareToInputStick at least twice (update: issue now reported). The KP2A InputStick plugin works a lot better for me in this regard (update: but also has a minor issue).

When considering to support ShareToInputStick (would be okay for a temporary workaround IMHO), please use the sharing intent text/x-keystrokes which was added to ShareToInputStick on my request a while ago. The benefit is that you can select to always use the ShareToInputStick app for this intent type, saving an extra step compared to using the text/plain intent type.

[wschlich]

@J-Jamet I see you have moved this issue over to your TODO list for KPDX5 at the end of last year. Thank you for considering it! How likely is it that you'll be actually implementing InputStick support for KPDX5, taking into account that this issue is open for over 6 years now and thus likely a low priority for you?
Also, do you have a rough estimate on when you plan to work on KPDX5?
I suppose that it will likely take quite a long time (several months or even longer) until we could expect this feature to be available in KPDX(5). Maybe you could consider implementing the ShareToInputStick workaround at first (see my previous posting).
Thanks and please keep up the great work with KPDX! 🙏

[J-Jamet]

Indeed, it wasn't a high priority, even though it might be a good addition, as it requires additional hardware. I don't have any estimates; the features are created as we go along. I'd like to set it up for personal use as well, but I don't even have the hardware. I'd like to explore the possibility of direct use from a modified ROM.
KeePassDX version 5 will be a refactoring of the code, so this will be an opportunity.