8.95.1 on WeTek Play 1: Multimedia Keys not working

**Sepp** · December 30, 2018 at 12:21 AM

Hi,

I have a problem with not all buttons (on keyboard, remote control, ...) being properly recognized. Same setup/configuration/hardware worked for LE7 and LE8 flawlessly.

For what I've narrowed it down, it seems to be limited to the "multimedia keys".

All keys are properly recognized by the OS, as you can see for the examples of the "next" and the "red" key with two different input sources:

Code

XXXXX:~/.kodi/temp # libinput debug-events
-event0   DEVICE_ADDED     HBGIC Technology Co., Ltd. USB Keyboard Mouse seat0 default group1  cap:p left scroll-nat scroll-button
-event1   DEVICE_ADDED     HBGIC Technology Co., Ltd. USB Keyboard Mouse seat0 default group1  cap:kp scroll-nat
-event3   DEVICE_ADDED     key_input                         seat0 default group2  cap:k
-event2   DEVICE_ADDED     aml_keypad                        seat0 default group3  cap:kp left scroll-nat scroll-button
 event2   KEYBOARD_KEY      +3.94s    KEY_FASTFORWARD (208) pressed
 event2   KEYBOARD_KEY      +4.21s    KEY_FASTFORWARD (208) released
 event2   KEYBOARD_KEY      +4.83s    KEY_RED (398) pressed
 event2   KEYBOARD_KEY      +5.11s    KEY_RED (398) released
-event1   KEYBOARD_KEY      +8.80s    KEY_NEXTSONG (163) pressed
 event1   KEYBOARD_KEY      +8.81s    KEY_NEXTSONG (163) released
 event1   KEYBOARD_KEY     +10.37s    KEY_RED (398) pressed
 event1   KEYBOARD_KEY     +10.38s    KEY_RED (398) released

Display More

E.g., here you see the correctly recognized "next" button in the Kodi log:

Code

01:12:17.839 T:3001021296   DEBUG: CLibInputKeyboard::ProcessKey - using delay: 400ms repeat: 80ms
01:12:17.843 T:2639397744   DEBUG: Thread Timer start, auto delete: false
01:12:17.856 T:3011207088   DEBUG: Keyboard: scancode: 0xa3, sym: 0x00b0, unicode: 0x0000, modifier: 0x0
01:12:17.858 T:3011207088   DEBUG: HandleKey: next_track (0xf0ba) pressed, action is noop
01:12:18.110 T:2639397744   DEBUG: Thread Timer 2639397744 terminating
01:12:18.129 T:3011207088   DEBUG: Keyboard: scancode: 0xa3, sym: 0x00b0, unicode: 0x0000, modifier: 0x0

And here the non-functional "red" button in the Kodi log:

Code

01:14:37.301 T:3011207088   DEBUG: Keyboard: scancode: 0x00, sym: 0x0000, unicode: 0x0000, modifier: 0x0
01:14:37.301 T:3011207088   DEBUG: GetActionCode: Trying Hardy keycode for 0xf200
01:14:37.301 T:3011207088   DEBUG: Previous line repeats 2 times.
01:14:37.301 T:3011207088   DEBUG: HandleKey: long-0 (0x100f200, obc-16838913) pressed, action is
01:14:37.581 T:3011207088   DEBUG: Keyboard: scancode: 0x00, sym: 0x0000, unicode: 0x0000, modifier: 0x0

For testing purpose, I already did various tests with eventlircd stopped (stopping kodi, stopping eventlircd, starting kodi again): no change.

sadmad · January 7, 2019 at 7:36 AM

Maybe related: wetek play 1, 8.95.2 (same with 8.95.1), context menu is not recognised and the back button is mapped wrong.

hubsif · February 5, 2019 at 8:25 PM

I'm having the same issue since the CoreELEC update to 8.99, based on LE9. Everything has been working fine before, now multiple keys don't work anymore, like STOP and EPG, for my custom configured remote on a Amlogic S905 box. Getting the same non-functional error logs for those keys, though libinput shows that they're mapped just fine.

Sepp: Have you found a solution yet?

**Sepp** · February 6, 2019 at 11:32 PM

hubsif: No, not really. Whenever there is a non-mediakey alternative for the same function (i.e. a letter instead of a mediakey), I use that instead. Unfortunately, there is not always an alternative, e.g. for the color buttons. I'm really unhappy about that.