View Single Post
Old Yesterday, 11:38 PM   #73
lumping-sugar66
Zealot
lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.
 
lumping-sugar66's Avatar
 
Posts: 146
Karma: 87635
Join Date: Oct 2023
Location: Ontario, Canada
Device: Kobo Aura Edition 2, Kobo Clara 2E, Kobo Libra 2
New Diagnostic Tools

Pushed an update with additional diagnostic tools to help troubleshoot more Bluetooth controllers and help identify the events generated by them.

After connecting your Bluetooth device, navigate to Diagnostics > Debug Tools. The following tools are now available:

List all input devices
Displays all input devices on your Kobo along with their names. This identifies which /dev/input/eventX your controller is assigned to.

Test specific device
Allows you to select and test any input device directly. Useful if your controller is mapped to a different event device than the default.

Live capture (15 sec)
Hooks into KOReader's input system and captures all key events for 15 seconds. Press buttons on your controller during the capture window to see which key codes are being generated.

Output includes:
- Key codes received by KOReader
- Human-readable names for known keys
- Summary of unique codes detected

Code:
=== KEY CODES DETECTED ===

  Code 109 = PAGEDOWN
  Code 104 = PAGEUP
  Code 115 (unknown - add to event_map!)

=== ALL PRESS EVENTS ===
  [14:32:15] Code 109 (PAGEDOWN)
  [14:32:16] Code 104 (PAGEUP)
If you are experiencing difficulties ensuring the device is sending the correct event codes after your button presses, or want to ensure the event listeners are created at the right places, you can use these new diagnostics tools.
Attached Thumbnails
Click image for larger version

Name:	IMG_7545.JPG
Views:	4
Size:	130.6 KB
ID:	219916   Click image for larger version

Name:	IMG_7546.JPG
Views:	4
Size:	145.0 KB
ID:	219917   Click image for larger version

Name:	IMG_7547.jpg
Views:	3
Size:	130.5 KB
ID:	219918  
lumping-sugar66 is offline   Reply With Quote