Closed lysin closed 9 years ago
ping @sraue the master of remotes :)
just in case, @lysin coold you please post the result of
dmesg | pastebinit
lsusb | pastebinit
thanks
i ordered such remote and should get this the next days, if we cant solve for beta2 then i try to solve this for beta3
I had to revert it back to stable version as it was unusable for me.
I'm going to try and run it from a USB and post the results later.
Cheers
That's the pain of a beta ... backup highly suggested. Thanks for reporting, but take meassures before replacing your stable media center in the living room.
2015-05-18 20:55 GMT+02:00 lysin notifications@github.com:
I had to revert it back to stable version as it was unusable for me.
I'm going to try and run it from a USB and post the results later.
Cheers
Reply to this email directly or view it on GitHub https://github.com/OpenELEC/OpenELEC.tv/issues/4157#issuecomment-103175030 .
Key-ID: 0x1A995A9B
keyserver: pgp.mit.edu
Fingerprint: 4606 DA19 EC2E 9A0B 0157 C81B DA07 CF63 1A99 5A9B
For what it's worth I have this remote (VRC-1100) and haven't had any problems with the 6.0 Beta or other custom builds from master - the remote works fine with a RPi2 and Revo3700 (Nvidia_Legacy).
rpi22:~ # lsusb
Bus 001 Device 004: ID 05a4:9881 Ortek Technology, Inc. IR receiver [VRC-1100 Vista MCE Remote Control]
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
@fritsch I did backup my system, I only had to downgrade to previous stable version. Everything is looking fine so far ;)
I will try and replicate the issue as soon as I get home.
Here you go:
dmesg http://sprunge.us/GIKN
lsusb http://sprunge.us/XZJH
If I kill "eventlircd" as suggested by someone at openelec forum, some more buttons start to work (like enter, back, FF, RW, and some shortcuts. Not fully functional tough.
Hope the info is helpful. If you need anything else, feel free to ask.
I'm having the same issue. My remote is a:
I: Bus=0003 Vendor=1241 Product=e000 Version=0110
N: Name="HOLTEK PC receiver "
P: Phys=usb-0000:00:1d.0-1.2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:1241:E000.0001/input/input7
U: Uniq=
H: Handlers=sysrq kbd event4
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f
I: Bus=0003 Vendor=1241 Product=e000 Version=0110
N: Name="HOLTEK PC receiver "
P: Phys=usb-0000:00:1d.0-1.2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:1241:E000.0002/input/input8
U: Uniq=
H: Handlers=kbd mouse0 event5
B: PROP=0
B: EV=1f
B: KEY=3007f 0 0 4c3ffff17aff32d bf54444600000000 1f0001 120c130b17c000 267bfad951dfed 9e168000004400 10000002
B: REL=143
B: ABS=7f0100000000
B: MSC=10
which is clearly not a remote at all, but pretending to be a keyboard and mouse.
Worked fine with my Harmony 300 before the upgrade. The only buttons that worked for me after the upgrade were the four arrows.
Happy to provide any other details that might help.
which is clearly not a remote at all, but pretending to be a keyboard and mouse.
That's how the VRC-1100 rolls...
This is the output from cat /proc/bus/input/devices
for 05a4:9881
, my "Ortek Technology, Inc. IR receiver [VRC-1100 Vista MCE Remote Control]" according to lsusb
:
I: Bus=0003 Vendor=05a4 Product=9881 Version=0110
N: Name="HID 05a4:9881"
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/0003:05A4:9881.0001/input/input5
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=e080ffdf01cfffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=05a4 Product=9881 Version=0110
N: Name="HID 05a4:9881"
P: Phys=usb-0000:00:1d.0-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.1/0003:05A4:9881.0002/input/input6
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=17
B: KEY=1f0000 1000002020000 3878d801d001 1e000000000000 0
B: REL=103
B: MSC=10
I: Bus=0003 Vendor=05a4 Product=9881 Version=0110
N: Name="eventlircd"
P: Phys=/dev/input/event3
S: Sysfs=/devices/virtual/input/input11
U: Uniq=
H: Handlers=mouse1 event6
B: PROP=0
B: EV=7
B: KEY=10000 0 0 0 0
B: REL=3
So one keyboard, one mouse... and then a virtual device, eventlircd
.
The VRC-1100 is fully functional with OE 6 Beta on a Revo 3700, so maybe the lack of eventlircd
on your systems is the key?
@sraue
Any news regarding this issue? Did you managed to pinpoint the origin of the problems with this remote?
Cheers
It seems it's a personal problem for now. As it works for all the others :-)
Edit: For completeness I use this remote together with my cubox i4 - all fine.
To my knowledge @sraue has bought this remote already and it was working for him, too. All with issues, please provide
dmesg | pastebinit (after boot) lsusb | pastebinit
and so on, as requested earlier.
Edit: Then unplug; wait; replug; wait and provide the same output again.
2015-05-28 15:32 GMT+02:00 lysin notifications@github.com:
Maybe it has something with a specific build or the kernel and hardware.
It's not working for a lot of pople. You can see here http://openelec.tv/forum/120-news-announcements/76763-beta-openelec-6-0-beta-1-released#139434, here http://openelec.tv/forum/120-news-announcements/76763-beta-openelec-6-0-beta-1-released?start=15#139469, here http://openelec.tv/forum/120-news-announcements/76763-beta-openelec-6-0-beta-1-released?start=45#139738 and here http://openelec.tv/forum/110-update-openelec/76910-remote-broken-after-5-95-1-upgrade#140181 .
I'm running x64 Generic build on a i3-3225.
Cheers
— Reply to this email directly or view it on GitHub https://github.com/OpenELEC/OpenELEC.tv/issues/4157#issuecomment-106310891 .
Key-ID: 0x1A995A9B
keyserver: pgp.mit.edu
Fingerprint: 4606 DA19 EC2E 9A0B 0157 C81B DA07 CF63 1A99 5A9B
same device, same problem. after wakeup some buttons don't give any feedback
non working remote: dmesg - http://sprunge.us/TiAC lsusb - http://sprunge.us/IhDe cat devices - http://sprunge.us/FFJP kodi log (backspace on remote) - http://sprunge.us/VaYa ls -l /dev/input/by-id - http://sprunge.us/WbhK
lrwxrwxrwx 1 root root 9 May 28 20:45 usb-05a4_9881-event-kbd -> ../event4 lrwxrwxrwx 1 root root 9 May 28 20:45 usb-05a4_9881-if01-event-mouse -> ../event5 lrwxrwxrwx 1 root root 9 May 28 20:45 usb-05a4_9881-if01-mouse -> ../mouse1
irw (only KEY_LEFT cause action in kodi) - http://sprunge.us/YYTN -- irw is receiving everything correct from the remote
working remote: ls -l /dev/input/by-id - http://sprunge.us/jALG
lrwxrwxrwx 1 root root 9 May 31 18:06 usb-05a4_9881-event-kbd -> ../event2 lrwxrwxrwx 1 root root 9 May 31 18:06 usb-05a4_9881-if01-event-mouse -> ../event3 lrwxrwxrwx 1 root root 9 May 31 18:06 usb-05a4_9881-if01-mouse -> ../mouse0
After wakeup is a completely different beast. Let's wait for @sraue.
Here is my data...
I'll happily load an official 5.95.1 to test if it might help.
Working 5.0.2 system after running for a while: dmesg - http://sprunge.us/CNdi lsusb - http://sprunge.us/daaG
and after remove/replace IR receiver: dmesg - http://sprunge.us/SCRd lsusb - http://sprunge.us/QNCR
Now same machine loaded with 5.95.1 after boot: dmesg - http://sprunge.us/TJVI lsusb - http://sprunge.us/FJjV
and after remove/replace IR receiver: dmesg - http://sprunge.us/bLdG lsusb - http://sprunge.us/XWWi
@not4smurf When does it stop working for you?
Before
[ 6.468704] input: HOLTEK PC receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:1241:E000.0001/input/input6
[ 6.517322] usb 1-1.6: new full-speed USB device number 4 using ehci-pci
[ 6.521007] hid-generic 0003:1241:E000.0001: input,hidraw0: USB HID v1.10 Keyboard [HOLTEK PC receiver ] on usb-0000:00:1d.0-1.2/input0
[ 6.549638] input: HOLTEK PC receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:1241:E000.0002/input/input7
[ 6.601297] hid-generic 0003:1241:E000.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [HOLTEK PC receiver ] on usb-0000:00:1d.0-1.2/input1
After:
[ 193.905212] input: HOLTEK PC receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:1241:E000.0003/input/input14
[ 193.957552] hid-generic 0003:1241:E000.0003: input,hidraw0: USB HID v1.10 Keyboard [HOLTEK PC receiver ] on usb-0000:00:1d.0-1.2/input0
[ 193.986367] input: HOLTEK PC receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:1241:E000.0004/input/input15
[ 194.038088] hid-generic 0003:1241:E000.0004: input,hiddev0,hidraw1: USB HID v1.10 Mouse [HOLTEK PC receiver ] on usb-0000:00:1d.0-1.2/input1
[ 194.211789] input: eventlircd as /devices/virtual/input/input16
It needs some udev rule as the input name changes ... @sraue ^^ this true?
so @not4smurf it stops working after replugging it?
It does not work for me with 5.95.1 at all. Well, just the 4 arrow buttons work - nothing else.
I just did the unplug/replug because you asked for it...
did you enable "Remote control sends keyboard presses" in kodi input settings ?
EDIT: meh, this option is now gone in isengard. whatever. pls ignore
did you enable "Remote control sends keyboard presses" in kodi input settings ?
I don't have that option under Input Devices, just the options to enable mouse/touchscreen and joystick/gamepad. I assume that means Kodi does not think I have a remote, which makes sense as my "remote" is effectively a keyboard..
The keys OK, start and enter produce the same irw event KEY_ENTER. the keys yellow and Live produce KEY_T the keys blue and DVD produce KEY_M
key description http://forum.kodi.tv/showthread.php?tid=220677&pid=1949375#pid1949375
Is this behavior expected?
@polojoe Yes, this is normal behaviour for this remote. It always worked like that.
Cheers
I've just updated to 5.95.2 and my remote behavior is exactly the same - that is, the four arrow buttons work, but nothing else.
New dmesg: http://sprunge.us/SeDH New lsusb: http://sprunge.us/hFfI New /proc/bus/input/devices: http://sprunge.us/dbNW
Happy to run any tests etc. that may help.
Are you testing without any custom remote.xml/keyboard.xml etc.?
Are you testing without any custom remote.xml/keyboard.xml etc.?
Correct. This remote has always just worked for me.
And, this is the Official build - I was on the DA build.
Also, just ran irw /run/lirc/lircd
and pressed a few buttons - it seems to be producing the expected codes.
Can you upload a full debug log? Press a few of the working/non-working buttons so we see how they're handled. You should be able to run irw at the same time, the output of which might also be useful (annotate the irw log with the actual buttons you're pressing).
Sure - here is my irw
output:
kodi:~ # irw /run/lirc/lircd
69 0 KEY_LEFT devinput
69 0 KEY_LEFT_UP devinput
6a 0 KEY_RIGHT devinput
6a 0 KEY_RIGHT_UP devinput
1c 0 KEY_ENTER devinput
1c 0 KEY_ENTER_UP devinput
e 0 KEY_BACKSPACE devinput
e 0 KEY_BACKSPACE_UP devinput
I forgot to start irw
so the output above is missing a LEFT and RIGHT that will be in the debug log.
I rebooted in debug mode, pressed the above keys then connected using Kore and turned off Debug.
Kodi seems to have KEY_ENTER mapped to "Fullscreen" and KEY_BACKSPACE mapped to noop...
11:16:47 T:139811993855872 DEBUG: LIRC: Update - NEW at 114907:1c 0 KEY_ENTER devinput (KEY_ENTER)
11:16:47 T:139811993855872 DEBUG: OnKey: 22 (0x16) pressed, action is FullScreen
11:16:48 T:139811993855872 DEBUG: LIRC: Update - NEW at 115284:1c 0 KEY_ENTER_UP devinput (KEY_ENTER_UP)
11:16:50 T:139811993855872 DEBUG: LIRC: Update - NEW at 117886:e 0 KEY_BACKSPACE devinput (KEY_BACKSPACE)
11:16:51 T:139811993855872 DEBUG: LIRC: Update - NEW at 118250:e 0 KEY_BACKSPACE_UP devinput (KEY_BACKSPACE_UP)
Here is the full debug log: http://sprunge.us/iYBc
Which buttons do KEY_ENTER
and KEY_BACKSPACE
correspond to on your remote, as I'm not able to reproduce your irw
output (perhaps not surprising, as my system works, or I'm simply pressing the wrong buttons!)
You said previously:
Worked fine with my Harmony 300 before the upgrade
Might it be worth testing with your real Hama VRC-1100, rather than the Harmony?
On my system (real Hama VRC-1100, RPi2, no custom remote.xml etc.), this is my irw
output for LEFT
, RIGHT
, OK
and <--
buttons (the last one being the left-pointing arrow button below the STOP button):
69 0 KEY_LEFT devinput
69 0 KEY_LEFT_UP devinput
6a 0 KEY_RIGHT devinput
6a 0 KEY_RIGHT_UP devinput
160 0 KEY_OK devinput
160 0 KEY_OK_UP devinput
ae 0 KEY_EXIT devinput
ae 0 KEY_EXIT_UP devinput
And now these same buttons in Kodi:
03:13:18 10016.387695 T:1967968256 DEBUG: LIRC: Update - NEW at 656854:69 0 KEY_LEFT devinput (KEY_LEFT)
03:13:18 10016.498047 T:1967968256 DEBUG: LIRC: Update - NEW at 656964:69 0 KEY_LEFT_UP devinput (KEY_LEFT_UP)
03:13:19 10017.639648 T:1967968256 DEBUG: LIRC: Update - NEW at 658105:6a 0 KEY_RIGHT devinput (KEY_RIGHT)
03:13:19 10017.797852 T:1967968256 DEBUG: LIRC: Update - NEW at 658264:6a 0 KEY_RIGHT_UP devinput (KEY_RIGHT_UP)
03:13:21 10019.907227 T:1967968256 DEBUG: LIRC: Update - NEW at 660373:160 0 KEY_OK devinput (KEY_OK)
03:13:23 10021.068359 T:1967968256 DEBUG: LIRC: Update - NEW at 661535:160 0 KEY_OK_UP devinput (KEY_OK_UP)
03:13:23 10021.764648 T:1967968256 DEBUG: LIRC: Update - NEW at 662231:ae 0 KEY_EXIT devinput (KEY_EXIT)
03:13:24 10022.098633 T:1967968256 DEBUG: LIRC: Update - NEW at 662564:ae 0 KEY_EXIT_UP devinput (KEY_EXIT_UP)
I'm assuming the KEY_ENTER
and KEY_BACKSPACE
codes might be the result of your OK
and <---
buttons, but you're not getting the correct codes for these buttons, so it looks like irw
(or eventlircd
?) is screwed up somehow, and it's not the mapping in Kodi that is the problem (as Kodi is simply being fed the wrong codes).
Have you tried a completely "clean" system - it might be worth (temporarily) renaming the .config
, .cache
and .kodi
directories then rebooting, or alternatively a totally fresh installation, and seeing if the irw
behaviour is still the same.
Thanks for all this!
I don't have a "real" Hama VRC-1100, I have a "HOLTEK PC receiver" - this is a cheap generic MCE look alike from eBay. I jumped in this thread because mine was behaving the same way as the original issue. The very first thing I said was "My remote is a..."
Anyway - I no longer have the original remote. I programmed the Harmony to send the same signals by teaching it every key press.
You are correct - my KEY_ENTER
and KEY_BACKSPACE
are from OK
and <--
.
Reading through this again got me thinking... my HTPC is actually and old laptop so I thought I would see what key codes the builtin keyboard keys would generate. irw
did not record anything. This is probably obvious to anyone who knows a bit more about this than me... Now, remembering that my remote is not a real remote (it's a strangely shaped USB keyboard) I tried kodi:~ # systemctl stop eventlircd
- and now everything works!
Is there some way that OpenELEC/Kodi should recognise that a remote is actually a keyboard and not use eventlircd?
Edit - I did also try the clean install by renaming out those 3 directories. That did nothing other than confuse me for a minute or two because my box no longer had the hostname I had set for it and I couldn't get to it :-)
@lysin in oe 5.0.8 the keys produced different events, this changed with oe 6 beta builds
Same issue, VRC-1100 and Nvidia Legacy 5.95.1/5.95.2. Some keys work but others don't.
dmesg http://sprunge.us/UgiQ lsusb http://sprunge.us/Lieg
https://www.dropbox.com/s/7t0p9g26yerlc54/log-2015-06-17-09.36.23.zip?dl=0
Hi all, i have same problem with my LOGITECH HARMONY TOUCH i have 2 intel nuc (DN2820FYKH internal IR, and DCCP847DYE with external speedlink IR Receveir) and it does not work in beta 1 and beta 2 (OK, INFO, BACK... dont work) just move key work.
psh. +1's dont help.
@polojoe You're right. I'm sorry, I misunderstood your question.
Same issue here, since beta 1 some keys don't work. Zotac AD06, with "PHILIPS MCE USB IR Receiver- Spinel plus".
dmesg: http://sprunge.us/OaCb lsusb: http://sprunge.us/NEXS
I have a MCE Remote clone with USB dongle which previously worked in Windows and Openelec until V5.95.1. I reverted to V5 but when 5.95.2 arrived I installed on spare computer to see if the problem was cured but it is still there.
The main missing keys are "OK" and "Back" but I think "FF" and "FB". The arrow keys and "Stop" work as do "Play" and "Pause". I don't use many other keys but "OK" and "Back" are essential!! I am using the Legacy Nvidia version.
Chris
Hello ! Same issue with my Zotac box and "PHILIPS MCE USB IR Receiver- Spinel plus". Beta2 didn't solve the problem. dmesg : http://sprunge.us/DRXd lusb : http://sprunge.us/cHjM
irw command give me the expected result :
irw /run/lirc/lircd
69 0 KEY_LEFT devinput
69 0 KEY_LEFT_UP devinput
6a 0 KEY_RIGHT devinput
6a 0 KEY_RIGHT_UP devinput
1c 0 KEY_ENTER devinput
1c 0 KEY_ENTER_UP devinput
9e 0 KEY_BACK devinput
9e 0 KEY_BACK_UP devinput
I: Bus=0003 Vendor=0471 Product=20cc Version=0100
N: Name="PHILIPS MCE USB IR Receiver- Spinel plus"
P: Phys=usb-0000:00:12.0-3/input0
S: Sysfs=/devices/pci0000:00/0000:00:12.0/usb5/5-3/5-3:1.0/0003:0471:20CC.0001/input/input6
U: Uniq=
H: Handlers=sysrq kbd event3
B: PROP=0
B: EV=120013
B: KEY=fc2b0 10240000000000 0 400158000 8001f84000c004 e0beffdf01cfffff fffffffffffffffe
B: MSC=10
B: LED=1f
I: Bus=0019 Vendor=1283 Product=0000 Version=0000
N: Name="ITE8713 CIR transceiver"
P: Phys=
S: Sysfs=/devices/virtual/rc/rc0/input7
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=100013
B: KEY=fff 0 200108fc32e 2b7605100000000 0 700158000 419200004001 9e968000000000 10004000
B: MSC=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="MCE IR Keyboard/Mouse (ite-cir)"
P: Phys=/input0
S: Sysfs=/devices/virtual/input/input10
U: Uniq=
H: Handlers=sysrq kbd mouse0 event6
B: PROP=0
B: EV=100017
B: KEY=30000 7 ff87207ac14057ff febeffdfffefffff fffffffffffffffe
B: REL=3
B: MSC=10
My remote was working fine for years...
Any news on this subject? Kodi 15 release is almost here and I really need this remote to work.
Thanks to all
I just upgraded to 5.95.3 and no change for me.
My work-around (since someone thought it would be a good idea to cripple systemctl...) is:
ln -s /dev/null /storage/.config/system.d/eventlircd.service
I can report that 5.95.3 changes nothing for me too. I can also report that the ln -s workaround improves the situation on my zotac box. Not all keys are back though..
Same problem here! it's so hard to get the remote? in a HTPC?
OpenELEC (official) Version: 5.0.8 : Ful log http://sprunge.us/ENLK IRW :
OpenELEC (official) Version: 5.0.8 OpenELEC:~ # irw 71 0 KEY_MUTE devinput 71 0 KEY_MUTE_UP devinput 71 0 KEY_MUTE devinput 71 0 KEY_MUTE_UP devinput a8 0 KEY_REWIND devinput a8 0 KEY_REWIND_UP devinput cf 0 KEY_PLAY devinput cf 0 KEY_PLAY_UP devinput d0 0 KEY_FASTFORWARD devinput d0 0 KEY_FASTFORWARD_UP devinput 19c 0 KEY_PREVIOUS devinput 19c 0 KEY_PREVIOUS_UP devinput 80 0 KEY_STOP devinput 80 0 KEY_STOP_UP devinput 197 0 KEY_NEXT devinput 197 0 KEY_NEXT_UP devinput 73 0 KEY_VOLUMEUP devinput 73 0 KEY_VOLUMEUP_UP devinput 72 0 KEY_VOLUMEDOWN devinput 72 0 KEY_VOLUMEDOWN_UP devinput 69 0 KEY_LEFT devinput 69 0 KEY_LEFT_UP devinput 67 0 KEY_UP devinput 67 0 KEY_UP_UP devinput 6a 0 KEY_RIGHT devinput 6a 0 KEY_RIGHT_UP devinput 6c 0 KEY_DOWN devinput 6c 0 KEY_DOWN_UP devinput 160 0 KEY_OK devinput 160 0 KEY_OK_UP devinput 6f 0 KEY_DELETE devinput 6f 0 KEY_DELETE_UP devinput ae 0 KEY_EXIT devinput ae 0 KEY_EXIT_UP devinput d4 0 KEY_CAMERA devinput d4 0 KEY_CAMERA_UP devinput 174 0 KEY_ZOOM devinput 174 0 KEY_ZOOM_UP devinput e2 0 KEY_MEDIA devinput e2 0 KEY_MEDIA_UP devinput 16d 0 KEY_EPG devinput 16d 0 KEY_EPG_UP devinput 189 0 KEY_VIDEO devinput 189 0 KEY_VIDEO_UP devinput 185 0 KEY_DVD devinput 185 0 KEY_DVD_UP devinput 188 0 KEY_AUDIO devinput 188 0 KEY_AUDIO_UP devinput
OpenELEC (official) Version: 5.95.3 : Full log http://sprunge.us/QFgb IRW :
OpenELEC (official) Version: 5.95.3 OpenELEC:~ # irw 1c 0 KEY_ENTER devinput 1c 0 KEY_ENTER_UP devinput 71 0 KEY_MUTE devinput 71 0 KEY_MUTE_UP devinput a8 0 KEY_REWIND devinput a8 0 KEY_REWIND_UP devinput a4 0 KEY_PLAYPAUSE devinput a4 0 KEY_PLAYPAUSE_UP devinput d0 0 KEY_FASTFORWARD devinput d0 0 KEY_FASTFORWARD_UP devinput a5 0 KEY_PREVIOUSSONG devinput a5 0 KEY_PREVIOUSSONG_UP devinput a6 0 KEY_STOPCD devinput a6 0 KEY_STOPCD_UP devinput a3 0 KEY_NEXTSONG devinput a3 0 KEY_NEXTSONG_UP devinput 73 0 KEY_VOLUMEUP devinput 73 0 KEY_VOLUMEUP_UP devinput 72 0 KEY_VOLUMEDOWN devinput 72 0 KEY_VOLUMEDOWN_UP devinput 69 0 KEY_LEFT devinput 69 0 KEY_LEFT_UP devinput 67 0 KEY_UP devinput 67 0 KEY_UP_UP devinput 6a 0 KEY_RIGHT devinput 6a 0 KEY_RIGHT_UP devinput 6c 0 KEY_DOWN devinput 6c 0 KEY_DOWN_UP devinput 1c 0 KEY_ENTER devinput 1c 0 KEY_ENTER_UP devinput 66 0 KEY_HOME devinput 66 0 KEY_HOME_UP devinput 9e 0 KEY_BACK devinput 9e 0 KEY_BACK_UP devinput d4 0 KEY_CAMERA devinput d4 0 KEY_CAMERA_UP devinput 174 0 KEY_ZOOM devinput 174 0 KEY_ZOOM_UP devinput e2 0 KEY_MEDIA devinput e2 0 KEY_MEDIA_UP devinput 16d 0 KEY_EPG devinput 16d 0 KEY_EPG_UP devinput 189 0 KEY_VIDEO devinput 189 0 KEY_VIDEO_UP devinput 185 0 KEY_DVD devinput 185 0 KEY_DVD_UP devinput 187 0 KEY_MP3 devinput 187 0 KEY_MP3_UP devinput
[ 1.461560] input: PHILIPS MCE USB IR Receiver- Spinel plusf0r ASUS as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.5/6-1.5:1.0/0003:0471:206C.0001/input/input6
If i type : ln -s /dev/null /storage/.config/system.d/eventlircd.service all working great!
Is someone working on this issue? Is this considered a release blocker? Do developers know now what is the underlying bug? Is there anything else we tester could do in order to help?
The silence on this side of the fence is deafening..
@lysin I suggest the title be changed to "MCE remotes not working" because this affects a range of MCE remotes, not just VRC-1100.
thank you not4surf !! this did the trick
ln -s /dev/null /storage/.config/system.d/eventlircd.service
thank you very much work fine for me : ln -s /dev/null /storage/.config/system.d/eventlircd.service :+1:
@tergo Done!
I'll give it a go later on when openelec 6 stable is released. Hope a fix is ready for it then...
@zosky While it makes things better, for me the layout isn't exactly the same as before (like context menu). Is that different in your case?
In my case the most relevant key that does not work as before is the "windows" button. I don't know the precise name. DOuble checking each key will take more time than I have available right now.
@kenzodeluxe its not perfect, but its workable now. with lircd disabled the hama is treated like it was before (as a keyboard/mouse) ... just need to change some of the defaults
for right click / left click ... i like info and context ...
cp /usr/share/kodi/system/keymaps/mouse.xml /storage/.kodi/userdata/keymaps/mouse.xml
nano /storage/.kodi/userdata/keymaps/mouse.xml
i changed <leftclick>
leftclick</leftclick>
to <leftclick>
contextmenu</leftclick>
... and rightclick to info
@zuzzurro 'windows key' is not one i use. im guessing its the same as a win-key on a keyboard ? you'll need to copy over the default keyboard.xml (like i did the mouse.xml) and figure out what to edit.
EDIT: i decided to make my windowsKey "Show only watched, unwatched or all videos"
<leftwindows>SendClick(10)</leftwindows>
Only a couple buttons are working.
IRW test output:
Output from "cat /proc/bus/input/devices" :