Posts by HiassofT

  • How to Remap my media center remote buttons

    I haven't used the keymap editor for ages so don't know if it's working or if it maybe has some issues.

    Mapping remote buttons via a remote.xml file in /storage/.kodi/userdata/keymaps/ is working fine though.

    Here's the remote.xml I'm using for my Hauppauge remote. I've remapped the power button to show the shutdown dialog window so my RPi doesn't unconditionally shut down if I accidentally press it.

    Enable debug logging in kodi and watch the kodi log with tail -f .kodi/temp/kodi.log while you press buttons to see which buttons are mapped to which keynames ("power", "red", "forward", ..).

    The available actions and general info about remote/keyboard mapping are described in the kodi wiki Keymap - Official Kodi Wiki

    so long,

    Hias

  • Adding a IR receiver on rpi 3

    With LE9 you can just put a lircd.conf file in /storage/.config/ and then reboot. in LE 8.2 you have to enable Lirc in LE settings.

    But I recommend following the wiki guide and create an ir-keytable configuration, this is the modern standard in Linux and more flexible and hassle-free. Only use lirc if you have an odd remote that is not supported yet by ir-keytable.

    so long,

    Hias

  • serial_ir on Biostar J3060NH

    Thanks a lot for the ir-ctl output!

    It looks similar to a rc-6 signal, but not quite. The pulse/space lengths should be 222-666 or 666-1110 (except for the first one and another pulse/space mark at the beginning which are longer).

    Your output shows some very small values of about 100 or less, so the signal can't be decoded properly.

    Which rev of the atric IR-Einschalter are you using? The manual of rev5 mentions changes that resolved issues with some com ports. A mismatch in signal levels would explain these length deviations.

    There were a couple of posts on the atric forum mentioning issues with unclean/noisy power supplies (and having to add resistors and/or filtering caps or a newer/fixed IR receiver+cable to cure them). This could also explain the issues, most IR receivers are rather sensitive to noise on the power supply.

    On the system/software side the only thing the only thing that could cause these timing variations is IRQ latency. Check /proc/interrupts and make sure serial_ir is the only device using IRQ4, if some other device is using this IRQ as well go into the BIOS setup and move that device to it's own interrupt.

    so long,

    Hias

  • serial_ir on Biostar J3060NH

    Which LE version are you using?

    The timeouts reported by ir-ctl are fine, they should be shown after each pulse/space train (or at least after button release).

    I've tested serial_ir a couple of months ago on an ancient P4 motherboard with on-board COM port and it worked fine there.

    I can't really comment on your mainboard, but post the ir-ctl -r output of a short button press - this could already give some hints on what the issue could be.

    It could be an electrical problem, so it would be good if you described the hardware you are using. In my tests I used a 5V compatible TSOP IR receiver and picked up +5V from an USB port of my PC. Then just connected GND and the TSOP IR output to the COM port.

    so long,

    Hias

  • Miro SD speed affect LE/Kodi performance?

    The maximum speed or class (10, UHS, ...) rating is rather meaningless, the important thing is random access performance.

    As a rule of thumb stay away from noname / generic brand cards (they can be terribly slow or even utter crap) and go for cards with Class A1 rating.

    Here's a recent speed comparison: https://forum.armbian.com/topic/954-sd-card-performance/?do=findcomment&comment=49811

    I recently bought a bunch of Sandisk Extreme A1 32GB cards and I'm very happy with them. Samsung EVO are also OK, but with "EVO", "EVO+" and "EVO Plus" (yeah, I have all 3 variants) and different performance of these series I'd just go for Sandisk A1 where the situation is a bit simpler :)

    Edit: Oh, and only buy from reputable dealers, there are a lot of fake cards out there.

    so long,

    Hias

  • Keyboard doesn´t work properly

    There's an eventlircd udev rule with the USB id (idVendor=04f2, idProduct=0618) of your wireless HID receiver, so LibreELEC will treat your keyboard/mouse as a remote.

    Can you copy /usr/lib/udev/rules.d/98-eventlircd.rules to /storage/.config/udev.rules.d/ and then remove these 3 lines?

    Code
    ENV{ID_VENDOR_ID}=="04f2", ENV{ID_MODEL_ID}=="0618", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="topseed.evmap"

    As an easier alternative to editing the rule you can test with eventlircd disabled, run systemctl mask eventlircd - but note that then IR remotes won't work properly.

    Not exactly sure why this udev rule was added about 7 years ago eventlircd: add support for more Chicony and Topseed remotes · LibreELEC/LibreELEC.tv@c73b3bb · GitHub - in OpenELEC 0.99 days - probably the same receiver is/was also used for some wireless remote.

    The rule seems to be too unspecific. The receiver registers many input devices, the rule matches all, but should only match the one used for remotes. We'll have to think about the best way to fix that.

    so long,

    Hias

  • LibreELEC-RPi2.arm-8.2.5 and AV Video Out

    Try adding this line to config.txt

    Code
    audio_pwm_mode=1

    LE 8.2.5 comes with an updated firmware which should improve analog audio output quality, but needs a bit more GPU power. Setting audio_pwm_mode to 1 switches to the previous analog audio output implementation.

    Details about that are in this thread Analogue audio redux - Raspberry Pi Forums

    I'm using analog video on a RPi3B+ with LE9 testbuilds and it's working fine - but I also have a soundcard on my RPi so don't use analog audio out of the RPi.

    so long,

    Hias

  • Protocols changed to mce_kbd rc-6

    Follow the instructions from the post vpeter linked to.

    Then first test if your custom keymap works

    Code
    ir-keytable -c -w /storage/.config/rc_keymaps/mce_plus_keyboard

    If that worked, this means the keymap is fine.

    Then test if rc_maps.cfg works

    Code
    ir-keytable -a /storage/.config/rc_maps.cfg

    Please check the wiki for more details, especially the "Configuration, the easy way" section - this is very similar to what you need to do.

    Infrared Remotes [LibreELEC.wiki]

    so long,

    Hias

  • Shutdown on single button press

    A couple of months ago I tested with the gpio-shutdown dtoverlay on LE9 and it worked as expected (power off and on by a button on GPIO3) -no need for any additional python scriptery.

    I haven't used the gpio-poweroff dtoverlay yet, but if it doesn't work please drop me a line and I'll look into it.

    so long,

    Hias

  • Remap MCE Remote SUSPEND button

    If you dont't have /sys/class/rcX, then the remote receiver is quite certainly a HID device and the remote appears as a keyboard to the system.

    Changing scancode-to-keycode mappings via ir-keytable is not possible in this case, but you can change the keycodes with a udev hwdb file - see eg here: Ok button doesn't work on H1 remote

    To see all keycodes generated by the receiver you can use evtest (from the system tools package).

    Some of these "keyboard" remotes are routed through eventlircd, by udev rules matching the device attributes. In that case the button presses show up as LIRC events instead of keyboard events in kodi debug log.

    so long,

    Hias