Eliminate need for root access by implementing an IME soft keyboard

[pattontim]

Do we need root access?

If we cannot use custom mapping then this app will be only available to rooted users, because there is no way to report different input buttons to whole system without root. There are some unofficial workaround using Accessibility framework, but that will also be crippled Android 13 onward.

Do you think it would be possible to implement a keyboard IME in order to map inputs across the entire system by having users change their IME keyboard in settings? This could let us maybe send keystrokes and implement onscreen keyboard using the pads. I'm no android dev but on the surface it seems possible.

[pattontim]

This IME seems to be capable of sending most keys including ALT and CTRL or other keys. I suggest modify this to implement a soft keyboard service and have it listening for key commands sent by our Steam Controller to send mapped inputs to the system. Then we can have the keyboard always show but shrink it down to minimize size or place it off screen.

https://github.com/senzhk/ADBKeyBoard/

[daitj]

Does IME keyboard have possibility to send d-pad and joystick axis as well?I haven't checked that?

…

On September 30, 2022 11:42:15 PM GMT+03:00, pattontim ***@***.***> wrote: This IME seems to be able of sending most keys including ALT and CTRL or other keys. I suggest we use this to implement a soft keyboard service and have it listening for key commands sent by our Steam Controller to send mapped inputs to the system. -- Reply to this email directly or view it on GitHub: #1 (comment) You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[pattontim]

Does IME keyboard have possibility to send d-pad and joystick axis as well?I haven't checked that?
…
On September 30, 2022 11:42:15 PM GMT+03:00, pattontim @.> wrote: This IME seems to be able of sending most keys including ALT and CTRL or other keys. I suggest we use this to implement a soft keyboard service and have it listening for key commands sent by our Steam Controller to send mapped inputs to the system. -- Reply to this email directly or view it on GitHub: #1 (comment) You are receiving this because you are subscribed to this thread. Message ID: @.>

The AdbKeyboard above functions by sending KeyEvents. KeyEvent and MotionEvent both extend android.view.InputEvent. However to do this it uses an InputConnection which only has sendKeyEvent, so it seems we can't map axis inputs with the same method.

You may want to look into the game controller API for sending axis inputs.

[pattontim]

Barring that, going accessibility mode doesn't seem that bad. Moving forward it seems like Google will manually permit apps on the Android store as long as the app is accessibility focused. A case could be made for the use of a steam controller as an accessibility device. All things considered, I might plan on pursuing an implementation that implements accessibility. Because I want to be able to send Input events and motion inputs like https://stackoverflow.com/questions/7695258/moving-mouse-pointer-on-android-screen-programmatically