You are not logged in.
Pages: 1
I recently acquired a Gamepad (dancepad to be more precise). However, when using it the same button alternates between being read as JOY_BTN_X and [Keyboard Key Y] For example JOY_BTN_1 and ENTER.
After having spend some time trying to figure out where the problem lies I decided to ask this Forum. The information I have currently gathered regarding this is as follows:
lsusb gives the following output for the gamepad:
Bus 001 Device 005: ID 0079:0011 DragonRise Inc. Gamepad When comparing the output of both xev and evtest to make sure I wasn't imagining things I noticed that they had a different output from eachother, where xev registered the same stroke as a keyboard button, whilst evtest saw it as a joystick button.
xev
KeyPress event, serial 41, synthetic NO, window 0x7a00001,
root 0x6c9, subw 0x0, time 6500798, (164,-14), root:(164,888),
state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES,
XLookupString gives 1 bytes: (0d) ""
XmbLookupString gives 1 bytes: (0d) ""
XFilterEvent returns: False
KeyRelease event, serial 41, synthetic NO, window 0x7a00001,
root 0x6c9, subw 0x0, time 6500862, (164,-14), root:(164,888),
state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES,
XLookupString gives 1 bytes: (0d) ""
XFilterEvent returns: False
KeyPress event, serial 41, synthetic NO, window 0x7a00001,
root 0x6c9, subw 0x0, time 6501958, (164,-14), root:(164,888),
state 0x10, keycode 117 (keysym 0xff56, Next), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 41, synthetic NO, window 0x7a00001,
root 0x6c9, subw 0x0, time 6501982, (164,-14), root:(164,888),
state 0x10, keycode 117 (keysym 0xff56, Next), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: Falseevtest
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x79 product 0x11 version 0x110
Input device name: "USB Gamepad "
Event: time 1553604553.415448, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1553604553.415448, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 1
Event: time 1553604553.415448, -------------- SYN_REPORT ------------
Event: time 1553604553.543453, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1553604553.543453, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 0
Event: time 1553604553.543453, -------------- SYN_REPORT ------------
Event: time 1553604554.463494, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1553604554.463494, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 1553604554.463494, -------------- SYN_REPORT ------------
Event: time 1553604554.551502, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1553604554.551502, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 1553604554.551502, -------------- SYN_REPORT ------------Additionally, when plugging it in, dmesg gives the following output:
[16353.810139] usb 1-6: new low-speed USB device number 5 using xhci_hcd
[16354.060416] usb 1-6: New USB device found, idVendor=0079, idProduct=0011, bcdDevice= 1.06
[16354.060420] usb 1-6: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[16354.060423] usb 1-6: Product: USB Gamepad
[16354.093503] input: USB Gamepad as /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-6/1-6:1.0/0003:0079:0011.0007/input/input25
[16354.093602] dragonrise 0003:0079:0011.0007: input,hidraw6: USB HID v1.10 Joystick [USB Gamepad ] on usb-0000:01:00.0-6/input0
[16355.242036] input: Microsoft X-Box 360 pad as /devices/virtual/input/input26Now, if someone has an idea on how to proceed further, that would be great; As you can imagine, having a combination of ALT, CTL, PGUP, PGDWN, ENTER and SPACE be pressed whilst using this thing is a bit inconvenient.
I can imagine I am missing something obvious or haven't provided near enough information, so please point that out if needed.
Last edited by Zephyros (2019-03-26 22:58:56)
Offline
Pages: 1