Posts by HiassofT

9.1 are the alpha/beta versions, 9.2 will be the final stable version after finishing alpha/beta tests It follows the same scheme that we used eg for 8.2.

See also the wiki page: Releases [LibreELEC.wiki]

so long,

Hias

Quote from hat_dk

Where did you read about the crappy IR-receivers?

Sorry, can't remember, could have been on kodi or intel forums.

Unfortunately IR problems with NUCs seem to haunt a lot of (linux) users. An easy workaround is to use an external USB MCE receiver. The HP branded one for example works fine, it's not exactly a small or beautiful thing but it's well supported in Linux (I have one here too) and rather easy to get (package with HP MCE remote plus IR receiver costs about 15-20 USD shipped from China on ebay).

so long,

Hias

Quote from psifi

Is it possible the the missing shared library (libssl.so.1.0.0) could cause my problem?

Yes, this is quite certainly the problem. Make sure you have the current tvheadend42 addon installed. Kodi log will show that info, just use the logfile uploader in LE settings and post the link here.

BTW: very often (addon) update problems are caused by slow network initialization (kodi log will show that, too). Enable "Wait for network" in LE settings makes sure the network is up before kodi start and fixes these issues.

so long,

Hias

Try to update your NUC to the latest BIOS version (this may require Windows) - Intel has quite a history of screwing up IR. IIRC a BIOS update about half a year ago solved that on the gen7 models.

Also check with "ir-ctl -r" if your NUC receives any IR signals at all (you should get some "pulse" and "space" messages if you press a button).

Plus try placing the IR transmitter / hub very close to the NUC. IIRC there were also reports that the sensitivity of the IR receiver on some NUCs was very bad.

so long,

Hias

Quote from psifi

After upgrading to LibreELEC-Generic.x86_64-9.1.001.img.gz from 9.02 the TVHeadend-Server does not startup anymore. I had to connect an external TVHeadend-Server from another PC to the Libreelec-HTS-Client, otherwise TV would be unavailable.

Not much we can do about it unless you post some logs.

Provide Log File [LibreELEC.wiki]

so long,

Hias

This should be doable with a .kodi/userdata/keymaps/remote.xml with the following content:

<keymap>
  <global>
    <remote>
      <zero>Number0</zero>
      <one>Number1</one>
      <two>Number2</two>
      <three>Number3</three>
      <four>Number4</four>
      <five>Number5</five>
      <six>Number6</six>
      <seven>Number7</seven>
      <eight>Number8</eight>
      <nine>Number9</nine>
    </remote>
  </global>
</keymap>

The default for 2..9 on remotes is JumpSMS2..9 to get T9/SMS style input. With Number2..9 you'll only get numbers and have to use the on-screen keyboard if you want to enter text.

so long,

Hias

I'd recommend getting a good quality "A1" rated SD card. I'm using the Sandisk Extreme 32GB A1 here on various RPis (1-4) and they perform really well.

Having just a SD card makes the setup a lot simpler.

so long,

Hias

No, there are no more 9.0.x releases planned. Please upgrade to 9.1/9.2 - RPi0-3 and x86 should work without problems, as the 9.0 releases before.

so long,

Hias

Quote from HCI

does the "Raspberry Pi VNC" addon on Rasp4 4GB work?
Thank you for your answer.

I haven't tested with the one that's currently in our addon repository but with a locally built one and that worked fine.

so long,

Hias

Quote from BallerShotCaller

I don't really get it. I understand that this is an alpha build for Raspi Pi 4 but what about this build for generic devices which is available for download too? Is this also in alpha state?

See the release notes linked in the first post

Quote

LibreELEC 9.2 for Generic x86/64 and Raspberry Pi 0/1/2/3 devices is a solid beta quality release.

so long,

Hias

Can you upload a full log using the log uploader function in LE settings or by grabbing it from the Logfile samba share? Provide Log File [LibreELEC.wiki]

kernel/journal logs would also be helpful, the issue could be related to USB issues seen with some devices xhci: add quirk for host controllers that don't update endpoint DCS by P33M · Pull Request #3066 · raspberrypi/linux · GitHub

so long,

Hias

Stuttering and a/v sync problems on very high bitrate files (eg "Sony Surfing 4K Demo", 4kp60, avg 77Mb/sec, peak 118Mb/sec HEVC) are known issues and are being looked into.

Stuttering with interlaced videos is already fixed, either use the updated firmware or wait for the next LE release (which should be out soon).

so long,

Hias

Quote from KaraokeAmerica

You ran a command line in LE? How did you do that? All I see is the GUI.

You have to use ssh from another computer. See here for details: Accessing LibreELEC [LibreELEC.wiki]

so long,

Hias

Quote from KaraokeAmerica

So is there normally a need for updating firmware that is independent of the OS itself or is that normally part of the OS in the Pi world?

Until the RPi4 came out all RPis didn't contain any flash/eeprom chips with firmware, everything was part of the OS / sdcard.

With the RPi4 things changed a bit, it now has an eeprom with the bootloader firmware and another one with the USB controller firmware.

so long,

Hias

I've tested updating the USB controller firmware from LibreELEC (as described in the article, just drop "sudo" as it's not needed in LE) and it worked fine.

Beware though, the current firmware version is known to cause issues with several USB SSDs (and maybe other USB devices), so I'd recommend waiting for an updated version.

so long,

Hias

I'm using two K400 (original version) on various RPis (0-4) with and without a USB hub in between since several years and haven't seen such an issue yet.

Are you sure the batteries are fine? They last almost forever but after about 5 years I had to replace them on my very first K400.

Edit: also check with `vcgencmd get_throttled` after you experienced the issue if you get anything else than 0x0 - marginal power supplies and undervoltage conditions are known to upset a lot of USB devices.

so long,

Hias

Quote from adrock

I saw that suggestions a few times, but MyHarmony won't find that, it keeps matching it to 'Media Center PC [Microsoft Windows Media Center]'. Is that what you mean?

I take it I can keep the old MCE Keyboard one too, as it'll let me map buttons to keys (particularly t, y, and o) that aren't showing up under the Media Center PC one?

I don't have a harmony myself and am not too familiar with their config software but "Media Center PC [Microsoft Windows Media Center]" sounds correct to me.

It'd be better to stay away from the MCE Keyboard profile/protocol, it's not enabled by default in LE and will cause troubles with newer kernels (eg on x86) or when you enable one of the additional DVB driver sets (on any system).

If you need to (re-)map additional buttons better to it through Kodi's remote.xml (or using the keymap editor addon) or Lircmap.xml.

See Infrared Remotes [LibreELEC.wiki] LIRC - Official Kodi Wiki and Keymap - Official Kodi Wiki for details.

so long,

Hias

Configure your Harmony to use the Microsoft Media Center Remote profile(not MCE keyboard as in the 4-year old kodi forum post) and it will work out of the box.

so long,

Hias