Posts by HiassofT

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:

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:

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

AFAIK a Kodi game frontend (plus all the kodi backend database stuff needed to manage this) had been planned for Kodi 18 / Leia but retroplayer / games turned out to be more work than expected, so this had to be moved to Kodi 19.

so long,

Hias

Quote from wwessel

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

Quote from hundrakg

Why is the Pi3b+ so much more unstable? or is it?

Quite a lot of kernel and firmware issues with the RPi3B+ have been fixed since 8.2.5 came out. If you are experience instability on your RPi I'd recommend switching to the latest alpha release (8.90.006).

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

Quote from darksky

My goal is to build kodi on a different distro using the innovations the LibreElec team have created, for example, the HEVC support on RPi3.

These innovations / optimizations aren't from us, they come from popcornmix and other people from RPi.

If you want to build kodi and ffmpeg with all the optimizations it's probably easiest to just use his newclock5 branch (that's the current development tree). In LibreELEC we're doing the same, only difference is that we split out the ffmpeg patches to a separate package (but the changes are the same as in the newclock5 branch).

I'd recommend sticking to the tags in the repo (unless you want to track bleeding edge stuff, like in milhouse builds), in LE 8.90.005, which is based on Kodi Leia beta2, we built from this tag: newclock5_18.0b2-leia

so long,

Hias

Hyperion NG is still in a very early state and according to the maintainer the code isn't in too good shape Hyperion.NG release soon? | Hyperion - Forum

Not sure if/when there'll be a stable version available, the github repo hasn't seen any additions since December last year. GitHub - hyperion-project/hyperion.ng: PRE ALPHA - The reworked version (next generation) of Hyperion

AFAIK no one of us has tried creating an addon yet, this may change if/when a stable version of Hyperion NG is released. For now just stick to Hyperion as the readme in the Hyperion NG github repo recommends.

so long,

Hias

You can define both global defaults (in the "global" section) and window/screen specific settings (that override the defaults) in the kodi keymap.xml. See the kodi wiki for more info Keymap - Official Kodi Wiki

I'm using this in my remote.xml files to eg bring up the TV channel list when I press the "TV" button while watching live TV and then use the same button to close the list when the OSD channel list it's open:

<keymap>
  <FullscreenLiveTV>
    <remote>
      <livetv>ActivateWindow(PVROSDChannels)</livetv>
    </remote>
  </FullscreenLiveTV>
  <PVROSDChannels>
    <remote>
      <livetv>Close</livetv>
    </remote>
  </PVROSDChannels>
</keymap>

Note: this is for remotes, your (bluetooth) remote might actually act as a "keyboard".

You can use the keymap editor addon to easily assign actions, then you don't need to care about xml files or if your remote is seen as a keyboard by kodi.

so long,

Hias

To configure IR repeat settings you can use a udev rule like this - place it eg in .config/udev.rules.d/90-ir-repeat.rules

ACTION=="add", SUBSYSTEMS=="rc", SUBSYSTEM=="input", KERNEL=="event[0-9]*", RUN+="/usr/bin/ir-keytable --delay=750 --period=200 --device=$devnode"

so long,

Hias

You don't need to use the installer if you don't want to. Just download the gzip-ed image from the downloads section and then, as root, write it directly to your USB pendrive, SD card etc - but beware, don't choose the wrong device our you might nuke your harddrive

eg (replace /dev/sdh with the device node of your pendrive, SD card, ...)

zcat LibreELEC-RPi2.arm-8.90.004.img.gz > /dev/sdh

so long,

Hias

You have to install it from the LibreELEC addon repository -> VideoPlayer InputStream -> InputStream Adaptive.

so long,

Hias

RPi2 and RPi3 use the same build - the addon I linked to will be fine for you.

I tested it yesterday evening on my RPi3B+

so long,

Hias

The latest widevine needs a newer version of inputstream.adaptive (2.2.27), we fixed this last night inputstream.adaptive: update to 2.2.27 · LibreELEC/LibreELEC.tv@47767b9 · GitHub) but it could take a bit until the addon is rebuilt for all architectures and available from the LibreELEC addon repository.

In the meanwhile you can download inputstream.adaptive 2.2.27 for RPi2 from here inputstream.adaptive-2.2.27.0.zip and install it manually.

so long,

Hias

If you enable debug logging (in Settings->System->Logging) you'll see the key code received by kodi and what action it'll execute in the kodi log - just run tail -f .kodi/temp/kodi.log to see that info while testing.

You can also run evtest from the system tools addon to see the keycodes - but you have to stop kodi (and maybe also eventlircd) as they'll grab the input devices and then evtest can't show any info

systemctl stop kodi
systemctl stop eventlircd

so long,

Hias

Interesting, I hadn't noticed the "dtoverlay=hifiberry-digi" print on my PCB ("HifiBerry Digi-Pro HW 1.1") before

Adding that line won't hurt, but it doesn't seem to be needed. Just tested here on a 3B+ using LE 8.2.5 and it was detected fine, without anything added to config.txt (yesterday I tested it on a 3B using bleeding edge LE9 build with kernel 4.19-rc2).

LibreELEC (official): 8.2.5 (RPi2.arm)
le8:~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

If you can't get the card working, add the following line to config.txt:

dtdebug=1

then reboot, ssh in and post the output of the following commands

vcdbg log msg 2>&1 | paste
dmesg | paste

Then add "dtoverlay=hifiberry-digi" to config.txt (maybe it's indeed needed on some version of the card, who knows), reboot, run the two commands again and post the output as well.

so long,

Hias