Posts by roel

    Yes, indeed. With ir-keyrable you can determine the scancode of the buttons of your remote and save it in /storage/.config/rc_keymaps/doesn'tmatterhowyoucallit as you already did before.. This is described in the libreelec wiki and on the forum thread for amlogic devices. The point is you can map how you want it just choose any available action from the lircmap.xml to a button of you remote. It's not because on the button there is a 1 you should map it to KEY_1. If you want epg on button 1 then you map it to KEY_EPG. If you don't find the specific key in lircmap.xml then you take just a available KEY_ you don't want to use for another action and then you map it in remote.xml to the action you want iti to do.


    For example my red button on my remote is mapped to opening the netflix plugin: <red>RunAddon(plugin.video.netflix)</red>


    The default actions of your remote that or connected with lircmap.xml or defined in /usr/share/kodi/system/keymaps/remote.xml


    Just read the wiki and forum post on the libreelec site and the wiki on the kodi site. Check some examples of remote.xml, rc_keymap and the lircmap.xml put them next to each other and find the links. adjust some stuff just to test and test it. Eventually, you willl figure it out.

    You should just make a remote.xml file with your custom actions in ~/.kodi/userdata/keymaps/


    for example this is mine:


    <keymap>

    <FullscreenVideo>

    <remote>

    <zero>AudioNextLanguage</zero>

    <seven>subtitledelayminus</seven>

    <nine>subtitledelayplus</nine>

    </remote>

    </FullscreenVideo>

    </keymap>


    So keypress 0 on my remote is next language, 7 is subtitledelayminus. Just follow the kodi wiki about keymaps: Keymap - Official Kodi Wiki

    If I remember correctly only the <remote> actions will work with a ir-remote.


    A while ago there where problems with ir-remotes on amlogic devices and then the guys of coreelec had set the ir-remote in keyboard mode so the remotes should work, but I don't know if you can do that through configuration or you should rebuild libreelec with this option.

    But why working with lirc? Find the protocol of your remote and use ir-keytable -t, or do it in once as described in the wiki:


    "Then, for each of the protocols (except lirc, which isn't a real protocol) run ir-keytable -p PROTOCOL -t, then press some buttons on your remote.

    If you discovered the correct protocol you should see EV_MSC events together with the scancode of the button. eg:

    Code
    1. LibreELEC:~ # ir-keytable -p rc-5 -t
    2. Protocols changed to rc-5
    3. Testing events. Please, press CTRL-C to abort.
    4. 1503592437.660155: event type EV_MSC(0x04): scancode = 0x101a
    5. 1503592437.660155: event type EV_SYN(0x00).
    6. 1503592437.774129: event type EV_MSC(0x04): scancode = 0x101a
    7. 1503592437.774129: event type EV_SYN(0x00).
    8. 1503592437.921009: event type EV_MSC(0x04): scancode = 0x101a

    If you see no events stop ir-keytable with CTRL-C and try the next protocol from the list."


    And create your own remote. Maybe you there is already a configuration for your remote, check in teh amlogic subforum:


    LE9.0 remote configs ir-keytable Amlogic devices


    If you find it, don't forget to change the rc_maps.cfg and replace the meson-ir with a *

    Same problem on 8.95.2 image, but now it gives a error message: the joystick addons are required, but they are listed as not available.

    I tryed also mr boom, there retroplayer works, but gives a black screen. When I call the menu with pressing C button on keyboard, the retroplayer menu pops up and I see in the background the start screen of Mr.Boom. When the retroplayer menu goes away, the screen turns black again.

    IR should work well with very latest update. I'm not sure when I created tritium image, before or after update. Just make sure that you follow LibreELEC Infrared Remote tutorial.

    Seems it was a typo in my remote.conf. It's a very good libreelec you build for us, it's the most responsive libreelec I have (I have also AML S905x en S812). Especially the network is fast, seems a mainlined kernel really pays off! Thanks a lot for this, it was worth the wait.

    Just to inform that retroplayer is not working on the wetek core. When I want to load roms, kodi crashes. When I go to the libreelec addon installer and want to install a core manually (I tested snes and nes cores) it says the installation failed. Libretro installs without a problem.

    jernej


    I tested yesterday evening the libretech ALL-H3-CC image in a hurry. First thing I noticed is that I couldn't configure my remote. Didn't check further what could be the problem as I didn't have a lot of time. I will come back about this later.

    Nothing else tested, expect I can tell you the sound comming out of this board is a lot loader then from my KVIM. My amplifier was set on the KVIM but I had to turn it down for the Tritium H3, so good points for that.

    what board would you recommend? A64 or H3? are orange Pis to recommend or is the missing HDMI ESD protection a show stopper for a TV Box? unfortunately the beelink X2 is no more available. maybe friendlyelec or ALL-H3-CC (Tritium)?

    lumpi,


    I should recommend the ALL-H3-CC, Libretech invest in mainline for Allwineer, Amlogic and probably also rockchip + most of their boards fit a raspberry pi case, so a lot of choices of cases. Probably, the kodi/flirc case should fit also (I didn't try it so don't blame me if it doesn't).