Some keys not working from Cherry cymotion master keyboard

[keiem]

Hello,

I have since a very long time a Cherry cymotion master (linux edition). It has a lot of extra keys and they all work in linux.
Since windows 11 the driver is to old to get the special keys working. So luckily I just discovered hid-remapper and now I can use my extra keys again in windows, except 4. The key presses are registered by hid-remapper because the blue led flashes, but the monitor feature in hid-remapper doesn't show a hex code. I have no idea why, because they work in linux so they are not broken.

Here is the full log I captured from these keys with evtest in linux (keypresses are the last lines) :

Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46a product 0x27 version 0x111
Input device name: "HID 046a:0027"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 1 (KEY_ESC)
Event code 28 (KEY_ENTER)
Event code 74 (KEY_KPMINUS)
Event code 78 (KEY_KPPLUS)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Event code 110 (KEY_INSERT)
Event code 111 (KEY_DELETE)
Event code 113 (KEY_MUTE)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 116 (KEY_POWER)
Event code 119 (KEY_PAUSE)
Event code 120 (KEY_SCALE)
Event code 128 (KEY_STOP)
Event code 130 (KEY_PROPS)
Event code 131 (KEY_UNDO)
Event code 133 (KEY_COPY)
Event code 134 (KEY_OPEN)
Event code 135 (KEY_PASTE)
Event code 136 (KEY_FIND)
Event code 137 (KEY_CUT)
Event code 138 (KEY_HELP)
Event code 139 (KEY_MENU)
Event code 140 (KEY_CALC)
Event code 142 (KEY_SLEEP)
Event code 143 (KEY_WAKEUP)
Event code 144 (KEY_FILE)
Event code 148 (KEY_PROG1)
Event code 149 (KEY_PROG2)
Event code 150 (KEY_WWW)
Event code 152 (KEY_SCREENLOCK)
Event code 155 (KEY_MAIL)
Event code 156 (KEY_BOOKMARKS)
Event code 158 (KEY_BACK)
Event code 159 (KEY_FORWARD)
Event code 161 (KEY_EJECTCD)
Event code 163 (KEY_NEXTSONG)
Event code 164 (KEY_PLAYPAUSE)
Event code 165 (KEY_PREVIOUSSONG)
Event code 166 (KEY_STOPCD)
Event code 167 (KEY_RECORD)
Event code 168 (KEY_REWIND)
Event code 169 (KEY_PHONE)
Event code 171 (KEY_CONFIG)
Event code 172 (KEY_HOMEPAGE)
Event code 173 (KEY_REFRESH)
Event code 174 (KEY_EXIT)
Event code 176 (KEY_EDIT)
Event code 177 (KEY_SCROLLUP)
Event code 178 (KEY_SCROLLDOWN)
Event code 181 (KEY_NEW)
Event code 182 (KEY_REDO)
Event code 202 (KEY_PROG3)
Event code 204 (KEY_DASHBOARD)
Event code 206 (KEY_CLOSE)
Event code 207 (KEY_PLAY)
Event code 208 (KEY_FASTFORWARD)
Event code 209 (KEY_BASSBOOST)
Event code 210 (KEY_PRINT)
Event code 212 (KEY_CAMERA)
Event code 216 (KEY_CHAT)
Event code 217 (KEY_SEARCH)
Event code 219 (KEY_FINANCE)
Event code 223 (KEY_CANCEL)
Event code 224 (KEY_BRIGHTNESSDOWN)
Event code 225 (KEY_BRIGHTNESSUP)
Event code 228 (KEY_KBDILLUMTOGGLE)
Event code 229 (KEY_KBDILLUMDOWN)
Event code 230 (KEY_KBDILLUMUP)
Event code 231 (KEY_SEND)
Event code 232 (KEY_REPLY)
Event code 233 (KEY_FORWARDMAIL)
Event code 234 (KEY_SAVE)
Event code 235 (KEY_DOCUMENTS)
Event code 240 (KEY_UNKNOWN)
Event code 241 (KEY_VIDEO_NEXT)
Event code 244 (KEY_BRIGHTNESS_ZERO)
Event code 256 (BTN_0)
Event code 353 (KEY_SELECT)
Event code 354 (KEY_GOTO)
Event code 358 (KEY_INFO)
Event code 362 (KEY_PROGRAM)
Event code 366 (KEY_PVR)
Event code 370 (KEY_SUBTITLE)
Event code 372 (KEY_ZOOM)
Event code 374 (KEY_KEYBOARD)
Event code 375 (KEY_SCREEN)
Event code 376 (KEY_PC)
Event code 377 (KEY_TV)
Event code 378 (KEY_TV2)
Event code 379 (KEY_VCR)
Event code 380 (KEY_VCR2)
Event code 381 (KEY_SAT)
Event code 383 (KEY_CD)
Event code 384 (KEY_TAPE)
Event code 386 (KEY_TUNER)
Event code 387 (KEY_PLAYER)
Event code 389 (KEY_DVD)
Event code 392 (KEY_AUDIO)
Event code 393 (KEY_VIDEO)
Event code 396 (KEY_MEMO)
Event code 397 (KEY_CALENDAR)
Event code 398 (KEY_RED)
Event code 399 (KEY_GREEN)
Event code 400 (KEY_YELLOW)
Event code 401 (KEY_BLUE)
Event code 402 (KEY_CHANNELUP)
Event code 403 (KEY_CHANNELDOWN)
Event code 405 (KEY_LAST)
Event code 407 (KEY_NEXT)
Event code 408 (KEY_RESTART)
Event code 409 (KEY_SLOW)
Event code 410 (KEY_SHUFFLE)
Event code 412 (KEY_PREVIOUS)
Event code 416 (KEY_VIDEOPHONE)
Event code 417 (KEY_GAMES)
Event code 418 (KEY_ZOOMIN)
Event code 419 (KEY_ZOOMOUT)
Event code 420 (KEY_ZOOMRESET)
Event code 421 (KEY_WORDPROCESSOR)
Event code 422 (KEY_EDITOR)
Event code 423 (KEY_SPREADSHEET)
Event code 424 (KEY_GRAPHICSEDITOR)
Event code 425 (KEY_PRESENTATION)
Event code 426 (KEY_DATABASE)
Event code 427 (KEY_NEWS)
Event code 428 (KEY_VOICEMAIL)
Event code 429 (KEY_ADDRESSBOOK)
Event code 430 (KEY_MESSENGER)
Event code 431 (KEY_DISPLAYTOGGLE)
Event code 432 (KEY_SPELLCHECK)
Event code 433 (KEY_LOGOFF)
Event code 439 (KEY_MEDIA_REPEAT)
Event code 442 (KEY_IMAGES)
Event code 576 (KEY_BUTTONCONFIG)
Event code 577 (KEY_TASKMANAGER)
Event code 578 (KEY_JOURNAL)
Event code 579 (KEY_CONTROLPANEL)
Event code 580 (KEY_APPSELECT)
Event code 581 (KEY_SCREENSAVER)
Event code 582 (KEY_VOICECOMMAND)
Event code 583 (KEY_ASSISTANT)
Event code 584 (KEY_KBD_LAYOUT_NEXT)
Event code 585 (KEY_EMOJI_PICKER)
Event code 586 (KEY_DICTATE)
Event code 587 (KEY_CAMERA_ACCESS_ENABLE)
Event code 588 (KEY_CAMERA_ACCESS_DISABLE)
Event code 589 (KEY_CAMERA_ACCESS_TOGGLE)
Event code 592 (KEY_BRIGHTNESS_MIN)
Event code 593 (KEY_BRIGHTNESS_MAX)
Event code 596 (?)
Event code 597 (?)
Event code 598 (?)
Event code 608 (KEY_KBDINPUTASSIST_PREV)
Event code 609 (KEY_KBDINPUTASSIST_NEXT)
Event code 610 (KEY_KBDINPUTASSIST_PREVGROUP)
Event code 611 (KEY_KBDINPUTASSIST_NEXTGROUP)
Event code 612 (KEY_KBDINPUTASSIST_ACCEPT)
Event code 613 (KEY_KBDINPUTASSIST_CANCEL)
Event type 2 (EV_REL)
Event code 6 (REL_HWHEEL)
Event code 12 (REL_HWHEEL_HI_RES)
Event type 3 (EV_ABS)
Event code 32 (ABS_VOLUME)
Value 0
Min 0
Max 1023
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1781115892.706028, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0279
Event: time 1781115892.706028, type 1 (EV_KEY), code 182 (KEY_REDO), value 1
Event: time 1781115892.706028, -------------- SYN_REPORT ------------
Event: time 1781115892.818007, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0279
Event: time 1781115892.818007, type 1 (EV_KEY), code 182 (KEY_REDO), value 0
Event: time 1781115892.818007, -------------- SYN_REPORT ------------
Event: time 1781115895.026123, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0303
Event: time 1781115895.026123, type 1 (EV_KEY), code 202 (KEY_PROG3), value 1
Event: time 1781115895.026123, -------------- SYN_REPORT ------------
Event: time 1781115895.114017, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0303
Event: time 1781115895.114017, type 1 (EV_KEY), code 202 (KEY_PROG3), value 0
Event: time 1781115895.114017, -------------- SYN_REPORT ------------
Event: time 1781115896.690077, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0302
Event: time 1781115896.690077, type 1 (EV_KEY), code 149 (KEY_PROG2), value 1
Event: time 1781115896.690077, -------------- SYN_REPORT ------------
Event: time 1781115896.753883, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0302
Event: time 1781115896.753883, type 1 (EV_KEY), code 149 (KEY_PROG2), value 0
Event: time 1781115896.753883, -------------- SYN_REPORT ------------
Event: time 1781115897.842099, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0301
Event: time 1781115897.842099, type 1 (EV_KEY), code 148 (KEY_PROG1), value 1
Event: time 1781115897.842099, -------------- SYN_REPORT ------------
Event: time 1781115897.922075, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0301
Event: time 1781115897.922075, type 1 (EV_KEY), code 148 (KEY_PROG1), value 0
Event: time 1781115897.922075, -------------- SYN_REPORT ------------

evtest doesn't seem to give hex codes.

[jfedor2]

Seems the device has a broken report descriptor that gets patched up by the Linux kernel:

https://github.com/torvalds/linux/blob/master/drivers/hid/hid-cherry.c

Might be fixable with custom usages. I'd start by dumping the descriptor and possibly some traffic involving the keys in question. Just keep in mind that depending on the tool you use you might get the patched descriptor on Linux.

[keiem]

This is the output for the descriptor:

❯ sudo hexdump -C /sys/class/hidraw/hidraw1/device/report_descriptor

00000000 05 0c 09 01 a1 01 85 01 19 00 2a ff 03 15 00 26 |..........*....&|
00000010 ff 03 95 01 75 10 81 00 c0 05 01 09 80 a1 01 85 |....u...........|
00000020 02 19 81 29 83 15 00 25 01 75 01 95 03 81 02 75 |...)...%.u.....u|
00000030 01 95 05 81 01 c0 06 00 ff 09 01 a1 01 85 03 09 |................|
00000040 00 15 00 26 ff 00 75 08 95 08 91 80 c0 |...&..u......|
0000004d

his is the output from hid-recorder altough I think this not really raw and the driver is involved:

❯ sudo hid-recorder
Available devices:
/dev/hidraw0: HID 046a:0027
/dev/hidraw1: HID 046a:0027
/dev/hidraw2: HID 046a:0027
Select the device event number [0-2]: 1

HID 046a:0027
0x05, 0x0c, // Usage Page (Consumer Devices) 0
0x09, 0x01, // Usage (Consumer Control) 2
0xa1, 0x01, // Collection (Application) 4
0x85, 0x01, // Report ID (1) 6
0x19, 0x00, // Usage Minimum (0) 8
0x2a, 0xff, 0x03, // Usage Maximum (1023) 10
0x15, 0x00, // Logical Minimum (0) 13
0x26, 0xff, 0x03, // Logical Maximum (1023) 15
0x95, 0x01, // Report Count (1) 18
0x75, 0x10, // Report Size (16) 20
0x81, 0x00, // Input (Data,Arr,Abs) 22
0xc0, // End Collection 24
0x05, 0x01, // Usage Page (Generic Desktop) 25
0x09, 0x80, // Usage (System Control) 27
0xa1, 0x01, // Collection (Application) 29
0x85, 0x02, // Report ID (2) 31
0x19, 0x81, // Usage Minimum (129) 33
0x29, 0x83, // Usage Maximum (131) 35
0x15, 0x00, // Logical Minimum (0) 37
0x25, 0x01, // Logical Maximum (1) 39
0x75, 0x01, // Report Size (1) 41
0x95, 0x03, // Report Count (3) 43
0x81, 0x02, // Input (Data,Var,Abs) 45
0x75, 0x01, // Report Size (1) 47
0x95, 0x05, // Report Count (5) 49
0x81, 0x01, // Input (Cnst,Arr,Abs) 51
0xc0, // End Collection 53
0x06, 0x00, 0xff, // Usage Page (Vendor Defined Page 1) 54
0x09, 0x01, // Usage (Vendor Usage 1) 57
0xa1, 0x01, // Collection (Application) 59
0x85, 0x03, // Report ID (3) 61
0x09, 0x00, // Usage (Undefined) 63
0x15, 0x00, // Logical Minimum (0) 65
0x26, 0xff, 0x00, // Logical Maximum (255) 67
0x75, 0x08, // Report Size (8) 70
0x95, 0x08, // Report Count (8) 72
0x91, 0x80, // Output (Data,Arr,Abs,Vol) 74
0xc0, // End Collection 76

R: 77 05 0c 09 01 a1 01 85 01 19 00 2a ff 03 15 00 26 ff 03 95 01 75 10 81 00 c0 05 01 09 80 a1 01 85 02 19 81 29 83 15 00 25 01 75 01 95 03 81 02 75 01 95 05 81 01 c0 06 00 ff 09 01 a1 01 85 03 09 00 15 00 26 ff 00 75 08 95 08 91 80 c0
N: HID 046a:0027
I: 3 046a 0027
ReportID: 1 /Consumer Devices ['AC Redo/Repeat']
E: 000000.000000 3 01 79 02
ReportID: 1 /Consumer Devices ['0xc0000']
E: 000000.143963 3 01 00 00
ReportID: 1 /Consumer Devices ['0xc0303']
E: 000002.655910 3 01 03 03
ReportID: 1 /Consumer Devices ['0xc0000']
E: 000002.783908 3 01 00 00
ReportID: 1 /Consumer Devices ['0xc0302']
E: 000005.407777 3 01 02 03
ReportID: 1 /Consumer Devices ['0xc0000']
E: 000005.543834 3 01 00 00
ReportID: 1 /Consumer Devices ['0xc0301']
E: 000007.999738 3 01 01 03
ReportID: 1 /Consumer Devices ['0xc0000']
E: 000008.159728 3 01 00 00

I also have a output from hexdump, but the results always vary when I press a key. In the below I pressed the buttons one after another:

❯ sudo hexdump -C /dev/hidraw1
00000000 01 79 02 01 00 00 01 79 02 01 00 00 01 79 02 01 |.y.....y.....y..|
00000010 00 00 01 03 03 01 00 00 01 03 03 01 00 00 01 03 |................|
00000020 03 01 00 00 01 02 03 01 00 00 01 02 03 01 00 00 |................|
00000030 01 01 03 01 00 00 01 01 03 01 00 00 01 01 03 01 |................|

Tell me if this is valuable or do I have to find another method.

[jfedor2]

As mentioned these are the patched descriptors, but we can guess what the real one is based on this and the kernel source.

Unfortunately because this is an array input we can't fix it with configuration (custom usages), you'd need some special handling in the firmware.