lirc problem
|
24th Jun, 2014, 03:25 AM
Post: #1
|
|||
|
|||
lirc problem
Using the latest Xbian distribution I have this strange problem.
Somehow only the left, right, up and down keys seem to work in XBMC. I have a lircd.conf completely configured with all useful keys like KEY_OK, KEY_PLAY, KEY_STOP, etc. When testing the configuration with the 'irw' command, every key returns as expected . So far no problem, but when using the remote with XBMC only the direction keys are functioning. All other keys fail. Do I have to map the keys somewhere else too? I have searched but cannot find anything useful. Any ideas? |
|||
24th Jun, 2014, 03:53 AM
Post: #2
|
|||
|
|||
RE: lirc problem
Can you restart XBMC and try again?
pilight - modular domotica solution
|
|||
25th Jun, 2014, 04:58 PM
Post: #3
|
|||
|
|||
RE: lirc problem | |||
28th Jun, 2014, 04:25 AM
Post: #4
|
|||
|
|||
RE: lirc problem
Lircmap.xml file in .xbmc/userdata might have changed since Frodo or remote.xml in .xbmc/userdata/keymaps (if in use).
If I remember correctly first file translates lirc events (the ones displayed by irw) from specific remote (you can have many remotes mapped in the file) into commands (or you could call them 'buttons') that the other file translates it further into xmbc actions. The second file might not be present then default is taken from system xbmc folder. |
|||
8th Sep, 2014, 02:29 AM
Post: #5
|
|||
|
|||
RE: lirc problem
Frank,
Did you ever figure out your problem? I have a similar issue. thanks Jeff |
|||
8th Sep, 2014, 06:00 AM
Post: #6
|
|||
|
|||
RE: lirc problem | |||
8th Sep, 2014, 07:36 AM
Post: #7
|
|||
|
|||
RE: lirc problem
Ok, I do have the exact same problem, and somehow managed to gather some intel. I'm using an old ASUS EEEBox remote. My lirc config works fine (irw show only one line for each remote keypress).
Let's say I press a "supported" key : left. xbmc.log shows the following lines : Code: 23:23:19 T:3039515168 DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0 Now let's press an "unsupported" key, in my case the prominent "Windows logo" key in the middle of the remote : Code: 23:24:47 T:3039515168 DEBUG: Keyboard: scancode: 0x11, sym: 0x0077, unicode: 0x0077, modifier: 0x0 Looks like not action is registered for this key. From that point, I managed to get another Lircmap.xml from the Internet, fit for my exact remote. Regarding my KEY_W, it says : Quote:<start>KEY_W</start> When I do put my own Lircmap.xml over the existing one, KEY_W starts working well (going one screen back in history), but the "supported" keys (directional, play/pause, ...) are duplicated. Just like they're defined in two places : my own Lircmap.xml, and someplace else (not the original Lircmap.xml, for I overwritten it). A little more information I just gathered. If I press CONTINUOUSLY my Windows Logo key, I got the following logs : Code: 23:33:52 T:3039515168 DEBUG: Keyboard: scancode: 0x11, sym: 0x0077, unicode: 0x0077, modifier: 0x0 What I'm wondering is where those "Keyboard" lines come from. If I were able to disable their source, I should be able to replace it with my own Lircmap.xml and everything would be fine. |
|||
« Next Oldest | Next Newest »
|