Posts by HiassofT

    Hmmm, the remote doesn't seem to follow the rc5 protocol too well - or there's some bug in the IR receiver driver of your card that then causes rc-5 decoding in the kernel to fail.

    On quickly repeated button presses you should see the toggle bit flipping instead of getting different scancodes for the same button. eg

    Code
    799.923295: lirc protocol(rc5): scancode = 0x1015 toggle=1
    800.183294: lirc protocol(rc5): scancode = 0x1015

    But that's no big deal, you can work around it with 2 scancodes for the same button in your keytable - like you already did.

    The more problematic thing is that the signals seem to arrive at about 250ms interval instead of 110ms which is the standard for the rc-5 protocol. Therefore the kernel will interpret the scancode as distinct button presses and the normal repeat handling won't work.

    You should be able to work around this by increasing the IR receive timeout with eg ir-ctl -t 200000 - you can play a bit with the value, 150000 should probably work as well and give a bit better response or you can go up a bit, eg to 250000. Just test what works best for you.

    so long,

    Hias

    Thanks a lot for the info!

    This seems to be a race between kodi and eventlircd grabbing the input device and if you're unlucky (and kodi "wins the race") the OK button won't work. So far this hasn't shown up during testing.

    We'll have a look how we can best solve this issue and hope we have a fix soon.

    so long,

    Hias

    Add "ssh" to the end of /flash/cmdline.txt, after "quiet". Note that everything has to be in a single line and that there has to be a blank between "quiet" and "ssh".

    You can also edit this on your PC, cmdline.txt is in the first (FAT) partition of the SD card. If you do this make sure the file is saved with unix lineendings, so eg use Notepad++ on Windows.

    Or connect the RPi to some HDMI monitor and perform initial configuration there before switching to the problematic DVI cable setup.

    so long,

    Hias

    ssh into libreelec and then run tvservice -s and post the output.

    I'm using a HDMI-DVI cable on my test setup without issues and the tvservice output here looks like this:

    Code
    state 0x120006 [DVI DMT (36) RGB full 5:4], 1280x1024 @ 75.00Hz, progressive

    You should get a similar line, with "DVI" and "DMT" in there. If the HDMI cable is disconnected the RPi will switch to analog (CVBS) video output and you get a line like this:

    Code
    state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced

    Note the "NTSC" in there, this means analog output is used.

    If auto configuration via DDC/EDID doesn't work you might need to manually set the video mode, using hdmi_group and hdmi_mode parameters in config.txt - see the RPi config.txt docs for details: Video options in config.txt - Raspberry Pi Documentation

    so long,

    Hias

    15:35:13.799 T:140619617347328 DEBUG: LIRC: - NEW 16d 0 KEY_EPG devinput (KEY_EPG)

    15:35:13.805 T:140619625744512 DEBUG: HandleKey: two (0x32) pressed, action is ActivateWindow(TVGuide)

    Does it mean that the setting for key 16d has changed?

    Yes, this was a fix in kodi. KEY_EPG should bring up the EPG / TV guide, previously it was mapped to the "title" action KEY_EPG is wrongly mapped to title instead of guide · xbmc/xbmc@5e3e056 · GitHub

    You have to change your remote.xml if you want to map the EPG button to bring up the context menu.

    so long,

    Hias

    Until Kodi gets a native frontend for selecting games the easiest way is to use the Internet Archive Game Launcher addon by zachmorris Internet Archive Game Launcher

    A lot of more info is available in the retroplayer section of the Kodi forum Kodi Community Forum - RetroPlayer

    Basically you just have to install a mame addon from the LibreELEC repo and setup your controller. Then use the game launcher or enter the konami code, setup advancedsettings so that zip etc files aren't associated with audio/video files and select ROMs via the file list in the Games section of kodi and open them via the context menu / play with...

    so long,

    Hias

    The big rainbow screen appears for a short moment during powerup on all RPis. If you ubigse a too old OS, eg LibreELEC 8.0 or early 8.2 versions, on a RPi3B+ it'll be stuck on that big rainbow screen plus you'll have a lightning bolt in the top right corner.

    So, the description is correct, only inaccuracy is that they shouldn't call the RPi3B+ just B+ as there also was a (RPi1) B+ model.

    If your 3B+ boots fine into LibreELEC this means the OS is new enough. If you then occasionally see a lightning bolt in the top right corner it means the power supply (and/or power cable) isn't adequate and should be replaced.

    After a lot of frustration with PS issues in the very early RPi days I switched to using only the official RPF power supplies a couple of years ago (also bought them from Farnell/RS)- and didn't have any issues at all with them. So that's a clear recommendation from my side.

    so long,

    Hias

    Viewing photos seems to be a good method to fill up the thumbnails folder / texturecache - and it looks like kodi doesn't automatically garbage collect that.

    I've noticed a similar situation when I last visited my parents, the thumbnails folder was at 1.4GB. They mainly view photos and use TV catchup services (ORF, Arte, ARD/ZDF tvthek addons).

    Running texturecache P brought that down to a much more reasonable ~300MB and the log showed that it was mainly thumbnails from photos and those video streaming addons.

    Milhouse then gave me this additional info about texturecache / thumbnails cleanup:

    • texturecache.py R to remove "orphan" images from Thumbnails (ie. delete artwork from Thumbnails that is not referenced by a row in the Textures13.db database).
    • texturecache.py Xd to remove Textures13.db database rows that reference non-existent Thumbnails artwork.
    • texturecache.py P to "prune" the cache of all artwork which is not referenced by the media library.
    • If you run all three (P, R, Xd) then that's about the best you can do to trim the fat, and fix any inconsistencies.

    I ran all tree options but P was the one that helped the most (R removed some 200 Thumbnails / 5MB total).

    BTW: 1GB storage is a bit small. I'd recommend using a larger partition / SD card

    so long,

    Hias