Posts by MoonKid

  • [Solved] First steps with NFS (wiki not enough)

    I know the Wiki-Page about the topic. Is there betteranother one? :D

    There is no info about where the config should be written. And no info about if it is able to run Kodi with a different uid. Because with LibreELEC 8 and Kodi 17.3 it looks like that kodi runs as "root" (uid=0).

    Do I have to give Kodi root-rights on my NAS to access an NFS-share from there? I won't. ;)

    Or can I modify the Kodi users itself?

  • perl modul present but missed by build-tool

    I tried to build LibreELEC from git on a Debian unstable (x86_64) für a Pi2. I used the howto-build from the wiki, which is damn nice! :)

    But at the end is an error I don't understand. Perl is present but XML:Parser misses it. ?

  • [SOLVED] FLIRC and the KODI keyboard shortcuts

    I won't suggest editing the xml file. I found a solution in the FLIRC forum.

    When using non-US keyboard-layout it doesn't work by default. You have to map the keys one by one. And you have to map them twice when using e.g. a One-4-All because there are always two different signals on the same button. This is described in the FLIRC help articles.

  • [SOLVED] buy codec licence?

    It is an usability ergonomic bug. Keep in mind there are other types of users - you are not the center of the universe.

    I opened the ticket not for me but for Kodi to keep it improved for ALL users. I am not selfish when opening tickets. I always think about if this is related and good for the project.

    btw: It is painfull to move the SD-card. I would prefere SSH-shell. ;)

  • [SOLVED] FLIRC and the KODI keyboard shortcuts

    Please correct me if I am wrong: FLIRC could be described is a keyboard emulator. It translate signales from a infraret remote control into keyboard commands (e.g. the arrow keys, ENTER, ...) right? So KODI doesn't know that there is a remote control. It only "see" buttons pressed on a keyboard, right?

    I configured my One-4-All remote with a "Microsoft" code out of the codebook. Then I used the FLIRC software to setup each(!) key in the "KODI" key map. No problems at this point. I can definitly say that all keys on the remote are mapped in FLIRC because FLIRC gave succuess message and the button light on the remote is wokring when I press the button.

    But KODI doesn't react on all buttons (e.g. switch off, fullscreen) on the remote.

    There are a lot of keyboard shortcuts for KODI. But how can I tell FLIRC which of the shortscuts should be emulated when pressing a specific button on the remote? And before that I first would check which shortcuts does FLIRC on the current setup.

  • How to install packages?

    Quote from CvH

    if you can tell what script - maybe there is an alternative

    The Pi2 has no hardware-power-switch. My Pi is on a "main power button" (german: stromsteckerleiste mit schalter). All devices (TV, Wii, ...) are on it.

    On switch and everything goes to standby except the Pi, which boots. When we use the Wii with the TV the Pi starts, too. But know one in my family will remember to shutodown the Pi correct before switch off the power button (when finished with playing Wii). See?

    The point is the Pi/LibreELEC/KODI should know if no one use it and shutdown itself. One idea was to check if there is a monitor present.

    And extra power button for the Pi is a solution but not elegant.

    Another idea (disclaimer: not from me): While booting a timer (e.g. 3 minutes) could start and check if an input (via remote controll over FLIRC) by the user was done or not. If not it should shotdown when the timer is finished. What do you think?