Bluetooth keyboard connects and is visible as Linux input, but does not navigate muOS frontend UI on RG35XX H
I’m testing Bluetooth keyboard support on an Anbernic RG35XX H running the current muOS Jacaranda release line.
I’ve confirmed that Bluetooth keyboard connectivity itself is working, but the muOS frontend still does not respond to the keyboard for UI navigation.
What works
- Bluetooth controller initializes successfully
- bluetoothd and bluetoothctl work normally
- the keyboard pairs, trusts, and connects successfully
- the keyboard is visible to Linux as an input device
- the keyboard works in terminal contexts after connection
Tested keyboard:
- ProtoArc XK03
Evidence that the keyboard is connected as a real input device
From /proc/bus/input/devices:
I: Bus=0005 Vendor=04e8 Product=7021 Version=0800
N: Name="ProtoArc XK03"
P: Phys=68:8f:c9:32:34:3a
S: Sysfs=/devices/virtual/misc/uhid/0005:04E8:7021.0001/input/input3
U: Uniq=e2:f8:96:fd:7b:ae
H: Handlers=sysrq kbd leds event3
This shows the keyboard is arriving as a normal keyboard device on event3.
What does not work
- In the main muOS frontend UI, arrow keys / Enter / etc. do not navigate menus
- The keyboard appears to be ignored by the frontend even though Linux sees it and terminal apps can use it
Additional notes
- I can confirm keypresses are visible at the Linux/input level
- This does not appear to be a Bluetooth pairing issue
- This seems more like a muOS frontend input-handling limitation than a controller/BlueZ issue
Question
Is Bluetooth keyboard navigation of the muOS frontend currently expected to work on Jacaranda?
If yes:
- is there a required setting, input remap, or frontend config I’m missing?
If no:
- would this be considered a feature request or known limitation?
Comments
Post a Comment