When I upgraded to Helix, the web-browser button on my VRC-1100 remote stopped working (I had set it to be XBMC home). I suspected the remote.xml and Lircmap.xml were overwritten upon upgrade.
Currently this is what happens when I use the button:
Code:
~$ tail -f ~/.kodi/temp/kodi.log
11:34:25 T:1398372087510 DEBUG: LIRC: Update - NEW at 164665:ac 0 KEY_HOMEPAGE /dev/input/event5 (KEY_HOMEPAGE)
and
Code:
~$ irw
ac 0 KEY_HOMEPAGE /dev/input/event5
Among other things, I tried adding this in /home/devuseraccount/xbmc/system/Lircmap.xml:
Code:
<remote device="devinput">
<obc6>KEY_HOMEPAGE</obc6>
</remote>
and this in ~/.kodi/userdata/keymaps/remote.xml:
Code:
<universalremote>
<obc6>XBMC.ActivateWindow(Home)</obc6>
</universalremote>
But it doesn't work. Any suggestions?
just map <KEY_HOMEPAGE> in remote.xml?
you cannot map LIRC keys in remote.xml wsnipex.
the remote.xml format is wrong. you need to map the key in a context, e.g. under <global>
Thanks. I think you mean like this? XBMC still doesn't respond.
~/.kodi/userdata/keymaps/remote.xml
Code:
<keymap>
<global>
<universalremote>
<obc6>XBMC.ActivateWindow(Home)</obc6>
</universalremote>
<remote>
<play>PlayPause</play>
<pause>Pause</pause>
<stop>Stop</stop>
<forward>FastForward</forward>
<reverse>Rewind</reverse>
<left>Left</left>
<right>Right</right>
<up>Up</up>
<down>Down</down>
<select>Select</select>
<enter>FullScreen</enter>
<pageplus>PageUp</pageplus>
<pageminus>PageDown</pageminus>
<back>Back</back>
<menu>PreviousMenu</menu>
<contentsmenu>PreviousMenu</contentsmenu>
<rootmenu>PreviousMenu</rootmenu>
<title>ContextMenu</title>
<info>Info</info>
<skipplus>SkipNext</skipplus>
<skipminus>SkipPrevious</skipminus>
<display>FullScreen</display>
<start>PreviousMenu</start>
<record>Record</record>
<eject>EjectTray()</eject>
<volumeplus>VolumeUp</volumeplus>
<volumeminus>VolumeDown</volumeminus>
<mute>Mute</mute>
<power>ShutDown()</power>
<myvideo>ActivateWindow(MyVideos)</myvideo>
<mymusic>ActivateWindow(MyMusic)</mymusic>
<mypictures>ActivateWindow(MyPictures)</mypictures>
<mytv>ActivateWindow(TVChannels)</mytv>
<guide>ActivateWindow(TVGuide)</guide>
<livetv>ActivateWindow(TVChannels)</livetv>
<liveradio>ActivateWindow(RadioChannels)</liveradio>
<recordedtv>ActivateWindow(TVRecordings)</recordedtv>
<epgsearch>ActivateWindow(TVSearch)</epgsearch>
<red>ActivateWindow(TVChannels)</red>
<green>ActivateWindow(MyVideos)</green>
<yellow>ActivateWindow(MyMusic)</yellow>
<blue>ActivateWindow(MyPictures)</blue>
<zero>Number0</zero>
<one>Number1</one>
<two>JumpSMS2</two>
<three>JumpSMS3</three>
<four>JumpSMS4</four>
<five>JumpSMS5</five>
<six>JumpSMS6</six>
<seven>JumpSMS7</seven>
<eight>JumpSMS8</eight>
<nine>JumpSMS9</nine>
<print>Screenshot</print>
</remote>
</global>
<Home>
<remote>
<info>ActivateWindow(SystemInfo)</info>
<clear>ActivateWindow(Weather)</clear>
<hash>ActivateWindow(Settings)</hash>
</remote>
</Home>
.
.
.
much more unchanged by me...
.
.
.
<Addon>
<remote>
<red>Red</red>
<green>Green</green>
<yellow>Yellow</yellow>
<blue>Blue</blue>
</remote>
</Addon>
</keymap>
This seems immune from even the slightest hint of working. Some other users resolved it using /home/devuseraccount/xbmc/system/keymaps/appcommand.xml like this:
Code:
<keymap>
<global>
<appcommand>
<browser_home>ActivateWindow(Home)</browser_home>
...
http://forum.kodi.tv/showthread.php?tid=...id=1434401
http://forum.kodi.tv/showthread.php?tid=...id=1021635
But this didn't help me (they were Windows users). I did notice that the working and non-working buttons are on different /dev/input events (4 vs. 5), I assume because the left/right/up/down buttons are actually keyboard entries.
Code:
11:02:43 T:140137722700480 DEBUG: LIRC: Update - NEW at 89000:69 0 KEY_LEFT /dev/input/event4 (KEY_LEFT)
11:02:45 T:140137904600480 DEBUG: LIRC: Update - NEW at 91085:ac 0 KEY_HOMEPAGE /dev/input/event5 (KEY_HOMEPAGE)