djairjr
commented
2 months ago I've read this on Reddit, but I can undertand how to change this configuration in retroarch.cfg
ANDROID: In Android builds, add input_android_physical_keyboard configuration option and its corresponding menu entry to force a device to act as a physical keyboard. When running on Android, RetroArch considers most devices that emit dpad events as gamepads, even if they also emit other keyboard events; this is usually the right thing to do, but it has the side effect of not letting some actual keyboards (e.g.: Logitech K480) act as such inside RetroArch. This configuration option allows users to manually select a specific input device to act as a physical keyboard instead of a gamepad, which is handy when emulating computers as opposed to consoles.
input_android_physical_keyboard = "Logitech Unifying Device. Wireless PID:4024"
Is something like this?
zoltanvb
Description
My Logitech K400+ keyboard is detected by RetroArch for Android, but I can't trigger any menu options and with that, I can't configure the system. The mouse pointer pops up, I can move it using the touchpad, but I can't select any options. When I press a button, the following message appears: Logitech K400 Plus not configured using fallback
Expected behavior
When I click on any option in the menu, the option should be triggered.
Actual behavior
The mouse pointer appears, moves, but there is no response when I click. The arrow keys don't work either.
Steps to reproduce the bug
1.Plug the Keyboard
Bisect Results
Always
Version/Commit
1.17
Environment information