[Bug] Bluetooth Input Devices (HID) paired but not registering events (No getevent output) S10

[Ditroit]

Device: Samsung Galaxy S10 (Exynos 9820) ROM Version: ExtremeROM Nexus v2.6.0 & v2.6.1 (Android 15 Port) Issue: Bluetooth keyboards and mice pair successfully with the device and show as "Connected", but they do not register any input. No keystrokes are detected, and the mouse cursor does not appear.

There is noticeable system stuttering/lag when attempting to use the connected Bluetooth input device, suggesting a conflict or interrupt issue in the BT stack.

Troubleshooting Steps Taken:

Tested the Bluetooth keyboard on other devices (working correctly).

Connected to S10 on ExtremeROM: Pairing is successful.

Tested External Keyboard Helper: No scan codes received.

Root Debugging: Ran su -> getevent -l in terminal.

Result: Absolutely NO events are generated/printed in the terminal when pressing keys on the BT keyboard.

Conclusion: It seems the Kernel or the Bluetooth stack in this A15 port lacks support for Legacy HID devices or there is a regression in the input drivers. The system receives the connection but fails to translate the HID protocol into input events.

[Ditroit]

Subject: Update on v2.6.1 & Debugging findings (Mouse works, Keyboard doesn't)

Hi again, just wanted to add crucial debugging info after clean flashing v2.6.1:

Partial HID Functionality: I discovered that a Bluetooth Mouse works perfectly (cursor moves, clicks register). The issue is strictly isolated to the Bluetooth Keyboard input.

System Recognition (Handshake OK):

The system successfully pairs.

In Settings > General Management > Physical Keyboard, the device is correctly identified by name ("S5900M").

I even receive the toast notification: "Keyboard layout set to Spanish".

The Bottleneck: despite the OS recognizing the device and assigning a layout, getevent -l remains completely silent when pressing keys.

Mouse: Generates events in getevent.

Keyboard: Zero events generated.

Conclusion: It seems the kernel/stack is successfully establishing the HID connection (hence the name appearing in settings), but fails to interpret the specific input descriptors for this keyboard (possibly missing Legacy HID support or a specific keylayout mapping issue in this Android 15 port).

Hope this helps narrow down the fix for v3.0! Thanks for the hard work.