I'm using libreelec which is linux based.
It seems that this remote is constantly "pinging" the receiver. If carried away from HTPC it flashes red-green.
The receiver was plugged in the back of my HTPC and there is a lot of cables, close to the speaker and other obstacles. Two days ago i plugged it in the front usb and so far so good.
This is the test i made: carried the remote to the kitchen, pressed volume up and volume on the HTPC in the living room went to 100%. If carried even further, at one point remote loses connection and starts flashing red-green.
It really could be that this receiver unit has weaker signal than my old MX3-M.
Besides the problem with the receiver, remote works ok, colored keys can be mapped which is an improvement over MX3, dedicated <back> and <enter> keys are fine, but the key with overlapping rectangles is not even registering in linux.
The device registers in linux like this:
Code:
lsusb
Bus 004 Device 002: ID 1d57:ad03 Xenta
dmesg
[136783.335993] input: FREEWAY TECHNOLOGY as /devices/pci0000:00/0000:00:13.0/usb5/5-3/5-3:1.2/0003:1D57:AD03.0003/input/input19
[136783.390060] hid-generic 0003:1D57:AD03.0003: input,hiddev0,hidraw0: USB HID v1.01 Keyboard [FREEWAY TECHNOLOGY] on usb-0000:00:13.0-3/input2
[136783.393264] input: FREEWAY TECHNOLOGY as /devices/pci0000:00/0000:00:13.0/usb5/5-3/5-3:1.3/0003:1D57:AD03.0004/input/input20
[136783.393740] hid-generic 0003:1D57:AD03.0004: input,hidraw1: USB HID v1.01 Mouse [FREEWAY TECHNOLOGY] on usb-0000:00:13.0-3/input3
Following is the output from evtest.
Normal response, on keydown evtest registers "value 1" and on key release "value 1":
Code:
Event: time 1475086924.355701, -------------- SYN_REPORT ------------
Event: time 1475086935.675610, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1475086935.675610, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1475086935.675610, -------------- SYN_REPORT ------------
Event: time 1475086935.875520, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1475086935.875520, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
Event: time 1475086935.875520, -------------- SYN_REPORT ------------
When the repeating event occurs, there is no "value 1" but instead evetest registers "value 2" indefinitely:
Code:
Event: time 1475086989.163544, -------------- SYN_REPORT ------------
Event: time 1475086991.115757, type 4 (EV_MSC), code 4 (MSC_SCAN), value c018a
Event: time 1475086991.115757, type 1 (EV_KEY), code 155 (KEY_MAIL), value 1
Event: time 1475086991.115757, -------------- SYN_REPORT ------------
Event: time 1475086992.117440, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.117440, -------------- SYN_REPORT ------------
Event: time 1475086992.150754, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.150754, -------------- SYN_REPORT ------------
Event: time 1475086992.183881, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.183881, -------------- SYN_REPORT ------------
Event: time 1475086992.220568, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.220568, -------------- SYN_REPORT ------------
Event: time 1475086992.253986, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.253986, -------------- SYN_REPORT ------------
Event: time 1475086992.287260, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.287260, -------------- SYN_REPORT ------------
Event: time 1475086992.320602, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.320602, -------------- SYN_REPORT ------------
Event: time 1475086992.353892, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.353892, -------------- SYN_REPORT ------------
Event: time 1475086992.387221, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
...