+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Configuration (/forum-17.html)
+--- Thread: lirc problem (/thread-2365.html)
lirc problem - Frank Tamminga - 24th Jun, 2014 03:25 AM
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?
RE: lirc problem - CurlyMo - 24th Jun, 2014 03:53 AM
Can you restart XBMC and try again?
RE: lirc problem - Frank Tamminga - 25th Jun, 2014 04:58 PM
(24th Jun, 2014 03:53 AM)CurlyMo Wrote: Can you restart XBMC and try again?
Did that already, (and again since you asked) but it didn't work.
I still can only navigate my menu.
What do I do wrong?
BTW, I've had it all working using Frodo on OpenElec, so it has to be possible.
RE: lirc problem - Sim1 - 28th Jun, 2014 04:25 AM
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.
RE: lirc problem - Jeff_DML - 8th Sep, 2014 02:29 AM
Frank,
Did you ever figure out your problem? I have a similar issue.
thanks
Jeff
RE: lirc problem - Frank Tamminga - 8th Sep, 2014 06:00 AM
(8th Sep, 2014 02:29 AM)Jeff_DML Wrote: Frank,Unfortunately not. But after an unstable Xbian release I returned to OpenElec and was able to restore my IR capabilities.
Did you ever figure out your problem? I have a similar issue.
thanks
Jeff
No more bleeding edge for me
RE: lirc problem - olivierm - 8th Sep, 2014 07:36 AM
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
23:23:19 T:3039515168 DEBUG: OnKey: left (0xf082) pressed, action is Left
23:23:19 T:3039515168 DEBUG: LIRC: Update - NEW at 1482939:000000037ff07bdf 00 KEY_LEFT Asus_RC1974502_00 (KEY_LEFT)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
23:24:47 T:3039515168 DEBUG: OnKey: w (0xf057) pressed, action is
23:24:47 T:3039515168 DEBUG: LIRC: Update - NEW at 1570364:000000037ff07bf2 00 KEY_W Asus_RC1974502_00 (KEY_W)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
23:33:52 T:3039515168 DEBUG: OnKey: w (0xf057) pressed, screen saver/dpms woken up
23:33:52 T:3039515168 DEBUG: LIRC: Update - NEW at 2115510:000000037ff07bf2 00 KEY_W Asus_RC1974502_00 (KEY_W)
23:33:52 T:3039515168 DEBUG: Keyboard: scancode: 0x11, sym: 0x0077, unicode: 0x0077, modifier: 0x0
23:33:52 T:3039515168 DEBUG: OnKey: w (0xf057) pressed, action is
23:33:52 T:3039515168 DEBUG: Keyboard: scancode: 0x11, sym: 0x0077, unicode: 0x0077, modifier: 0x0
23:33:52 T:3039515168 DEBUG: OnKey: w (0xf057) pressed, action is
23:33:52 T:3039515168 DEBUG: Keyboard: scancode: 0x11, sym: 0x0077, unicode: 0x0077, modifier: 0x0
23:33:52 T:3039515168 DEBUG: OnKey: w (0xf057) pressed, action is
23:33:52 T:3039515168 DEBUG: Keyboard: scancode: 0x11, sym: 0x0077, unicode: 0x0077, modifier: 0x0
23:33:52 T:3039515168 DEBUG: OnKey: w (0xf057) pressed, action is
[and so on]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.