After adapting to the Bluetooth remote control, the confirmation key is invalid. I don’t know how to set it through the keymap editor plugin? Could you please provide a tutorial? Thank you.
Probably like this?
It still hasn’t been solved. It doesn’t work according to the operation, and some buttons are invalid. How to set the keymap editor plug-in?
Read again above tutorial.
And provide more info what exactly is not working.
I: Bus=0005 Vendor=000d Product=3838 Version=0110
N: Name="SKYWORTH_0170 Consumer Control"
P: Phys=10:2c:6b:fd:fa:0f
S: Sysfs=/devices/virtual/misc/uhid/0005:000D:3838.0005/input/input14
U: Uniq=28:31:7e:16:f3:10
H: Handlers=kbd event9
B: PROP=0
B: EV=1f
B: KEY=306ff 0 0 483ffff17aff32d bfd4444600000000 1 130ff38b17c000 677bfad9415fed 9ed68000004400 10000002
B: REL=1040
B: ABS=100000000
B: MSC=10
I: Bus=0005 Vendor=000d Product=3838 Version=0110
N: Name="SKYWORTH_0170 Keypad"
P: Phys=10:2c:6b:fd:fa:0f
S: Sysfs=/devices/virtual/misc/uhid/0005:000D:3838.0005/input/input15
U: Uniq=28:31:7e:16:f3:10
H: Handlers=sysrq kbd leds event10
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f
cat 10-ur01.hwdb
evdev:input:b0005v000d*
KEYBOARD_KEY_c0041=enter
The confirmation key is invalid
evdev:input:b0005v000dp3838*
You need to find the key value: Homatics Box R 4K Plus - #1651 by r4w
Hello, sorry, we still can’t solve the same problem.
You do need to make some steps alone. All the required informations was provided.
evdev:input:b0005v000dp3838*
I can’t use this either, I gave up
Did yiu even run evtest and got the key value? Seems not.
Hello, I’m not very good at using it yet. Additionally, when I connect to Bluetooth on Corelec system and return to Android system, I need to re match it to use the Bluetooth remote control on Android system. I’m not sure if it’s a bug.
Try and learn - no one can do it for you.
It’s not.
This device is grabbed by another process.
No events are available to evtest while the
other grab is active.
In most cases, this is caused by an X driver,
try VT-switching and re-run evtest again.
Run the following command to see processes with
an open fd on this device
“fuser -v /dev/input/event9”
CoreELEC:~ # fuser -v /dev/input/event9
fuser: invalid option – ‘v’
BusyBox v1.36.1 (2024-07-14 05:38:59 IDT) multi-call binary.
Usage: fuser [-msk46] [-SIGNAL] FILE or PORT/PROTO
Find processes which use FILEs or PORTs
-m Find processes which use same fs as FILEs
-4,-6 Search only IPv4/IPv6 space
-s Don't display PIDs
-k Kill found processes
-SIGNAL Signal to send (default: KILL)
Kodi needs to be stopped
systemctl stop kodi
Testing ... (interrupt to exit)
Event: time 1721043652.226062, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041
Event: time 1721043652.226062, type 1 (EV_KEY), code 353 (KEY_SELECT), value 1
Event: time 1721043652.226062, -------------- SYN_REPORT ------------
cat SKYWORTH.hwdb
evdev:input:b0005v000dp3838*
KEYBOARD_KEY_7003e=enter
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.