Posts by HiassofT

    Concerning touchscreen: there's the Estouchy Skin for Kodi Kodi Community Forum - Estouchy - I have to admit I never tried it though as I don't have any touchscreens.

    You can disable various main menu entries (like Movies, Videos, ...) in Kodi if you don't want/need them - just head to Settings -> Interface -> Skin -> Configure Skin...

    If you want some extended functionality in Kodi you'll need to check if there's some addon readily available that suits your needs or create a feature request for Kodi if some core functionality needs to be extended.

    LibreELEC is already quite stripped down but if it bothers you that some background processes like pulseaudio, eventlircd, ... are running and you don't want/need them you can simply disable them via "systemctl mask SERVICENAME". A while back ago I did that to repurpose a Wetek Play 1 running LE as a headless tvheadend server - I even disabled kodi as it'd consume a significant amount of CPU and memory when it just sat there being idle.

    As all of these are just configuration changes you can easily check yourself if it brings you nearer to your goal. If you discover that's a viable way to go and you want that config "out of the box" then you could start thinking about creating an LE community build or fork that ships with these changes as default.

    so long,

    Hias

    Have a look at the Yatse (and maybe Kore, haven't tried it since a while) apps. TV can stay off and you just browse through your music library and remotely control kodi from your tablet / phone. Works rather nicely IMO!

    so long,

    Hias

    Technically the LCDproc service addon and the Kodi LCD addon are 2 separate things. You could configure the Kodi LCD addon to connect to an lcdproc instance running on another computer (I've used that to test things) or you could run lcdproc in LibreELEC and have some other program / addon (even on another computer) display info there.

    If we automatically install the kodi LCD addon people might need to disable it if they want to use some other program / addon to show stuff on the display (not 100% sure what happens if 2 clients connect to an lcdproc instance at the same time). Probably a niche use case, but again something that needs to be kept in mind / documented.

    so long,

    Hias

    It looks like mainline has fixed the issue:

    media: rc: meson-ir: add timeout on idle · torvalds/linux@8d7a77c · GitHub

    They, fittingly, call these keypresses "ghost" keypresses. It looks to be caused by the hardware not generating a timeout after each keypress, so they added it in software.

    My question is this:

    Can we get this fix backported to our kernel in the official odroid C2 (and generic amlogic devices) builds?

    The fix is already in the LE amlogic-3.14 tree, see these 2 PRs: fix in-kernel decoding with meson-ir by HiassofT · Pull Request #83 · LibreELEC/linux-amlogic · GitHub fix flush_timer by danielkucera · Pull Request #98 · LibreELEC/linux-amlogic · GitHub

    LE 8.2.5 uses an older version of the 3.14 kernel without these fixes, but the current LE 9.0 development branch has these built in.

    so long,

    Hias

    Support for non-NEC remotes, like RC6 MCE remotes, is rather lacking in the 8.2.x Amlogic tree, you might have more luck configuring your remote as a Xbox One remote and then using a rc_maps.cfg with "* * xbox_one" - the Xbox One remote uses the NEC protocol.

    I fixed the kernel remote to support MCE and other remote handling in January, but these changes are only available in the 9.0 (preview) versions - this is why LE9.0 and CE9.0 preview builds work better than the 8.2 ones in this respect.

    I'm not sure why Lirc sometimes doesn't work on 8.2, IMHO it should be fine (unless you have some "killall lircd" or similar commands in your autostart.sh). But then I'm not really experienced with Amlogic boxes and the old 3.14 kernel, my only contact with these so far was getting in-kernel / ir-keytable decoding working (which I did "blind", without actual hardware to test).

    so long,

    Hias

    If you are using irsend it could be that you are hit by this lirc bug: LIRC / Tickets / #315 irsend / lircd hang when using repeats A proposed fix has been posted but it hasn't made it's way into lirc yet.

    Do you also get the error when you don't use irsend?

    I'm not familiar with usb-uirt so I won't rule out a bug in the uirt2-raw lirc driver, or it could also be a RPi USB issue (we saw plenty of those, also with serial usb devices). The checksum error certainly is odd.

    Also check dmesg for USB related errors and run "vcgencmd get_throttled" (you should get "0x0") to check if the power supply is OK.

    so long,

    Hias

    hmm, only rc-core is loaded but no there's no sign of a rc0 device being registered - and also no error message. Maybe some module is missing?


    fasigno could you grab dmesg and lsmod form a working Arch installation, maybe that'll give us some hints.

    so long,

    Hias

    I am using exactly the files boot2k3 was posting in #229. In Coreelec 8.90.1 it works in nightly-20150428 not.

    When using nightly ir-keytable is saying this for example:

    Thanks for testing!

    I was just told that there's currently an Amlogic specific bug in Kodi which prevents lirc events (which is used by default in LE for remote handling) from working.

    A workaround for that issue was PRed here: [aml]Register lirc in AML after #13761 by gelotus · Pull Request #13798 · xbmc/xbmc · GitHub - but it looks like it needs a bit of rework.

    It'll probably take a couple more days until this issue is fixed in Kodi, then a bit until Kodi is updated in LE. Until that's resolved IR remotes will stay broken in nightly Amlogic LE builds.

    so long,

    Hias

    I

    Thanks for your support. I tried both 1. and 2. but the remote won't work. I also tried the "original" odroid remote (see code below). Same result. So it is a general problem I think. I am testing with libreelec 9.0 nightly-20150428. But also with coreelec it's the same behaviour :(. What else could it be?

    Is that your complete keymap? If yes it can't work as it doesn't contain the header with the protocol. The first line of the file must always contain a line like this:

    Code
    # table odroid, type: NEC

    With out the "type: PROTOCOL_NAME" the IR remote protocol won't be configured which in case of Amlogic/meson-ir means that no protocol decoded is enabled.

    so long,

    Hias

    It's odd that enabling mce_kbd kills other input in kodi, this shouldn't happen. I haven't seen this on RPi yet and on x86 it also should work fine. Have you checked if restarting kodi helps?

    Combining MCE remote and MCE keyboard functionality is possible, and it's also rather easy to make that persistent.

    Copy the stock mce keymap from the system to .config/rc_keymaps, and give it a unique name so you later know what it's doing :)

    Code
    cp /usr/lib/udev/rc_keymaps/rc6_mce .config/rc_keymaps/mce_plus_keyboard

    then edit this file and add the "mce_kbd" protocol in the very first line - it should then look like this:

    Code
    # table rc6_mce, type: RC6,mce_kbd
    0x800f0400 KEY_NUMERIC_0
    0x800f0401 KEY_NUMERIC_1
    ...

    Now create a .config/rc_maps.cfg to activate that keymap. eg

    Code
    * * mce_plus_keyboard

    so long,

    Hias

    For mce_kbd everything's a lot simpler: just enable the mce_kbd protocol and Kodi should automatically pick up the device and everything should work.

    So just running "ir-keytable -p mce_kbd" (while kodi is running) should be enough. If not, try restarting kodi (systemctl restart kodi).


    so long,

    Hias

    mce_kbd is a bit different than the other IR protocols, if it's enabled a separate input event device will be created.

    To check if signals are properly received and decoded it's best to install the system tools addon and then use "evtest" (with kodi and eventlircd stopped) instead of "ir-keytable -t". Just select the event device that reads "MCE IR Keyboard/Mouse".

    eg:

    so long,

    Hias

    Thanks for the log!

    Unfortunately I can't help you here as you seem to be using a community build and I'm not aware of what changes there might be applied compared to official LibreELEC builds.

    So I'd suggest you ask the build maintainer, or maybe someone else familiar with these builds can chime in here.

    so long,

    Hias