Posts by chewitt

The mismatch between BB kernels and our system frequently causes weird intangible problems that take an age to diagnose and magically go away when you run our kernel and our system. We have no idea if BB is the source of your issue or not, but if you insist on running BB we have sub-zero interest in investigating further - because we've wasted too much time on BB installs in the past.

GitHub - procount/pinn: An enhanced Operating System installer for the Raspberry Pi is an enhanced/evolved version of noobs that might be worth looking at.

1. Create a .strm file that links to the direct URL of the camera stream: Internet video and audio streams - Official Kodi Wiki and browse to the file via the Videos view then add to the favourites list.

2. There are no camera drivers or camera apps in the OS so you cannot stream 'from' LE to YouTube (or any other service)

3. BLE devices may not work correctly on Amlogic devices due to the older kernel. Otherwise BT devices should just work.

4. No, because there is no Miracast or AirPlay (video) support in Kodi.

The Kodi trademark rules require you to completely rebrand Kodi if you make any modifications to default Kodi and this includes the installation of add-ons (regardless of the source). Although it is still technically breaking the rules, the one type of add-on that nobody would complain about is a language pack add-on so the customers GUI and first-run experience is in their local language.

Use the LE settings add-on to edit the active network connection and set specific nameservers.

Quote from Squatta

I have been experiencing some issues running LibreElec on BerryBoot (bootloader). Any ideas?

If you install the engine from a Ford Fiesta in a BMW it still looks like a BMW but it doesn't run/go like one. LE is much the same.

Choose between:

a) Using a native LibreELEC install so you are using OUR kernel and drivers with our core system.

b) Using whateverthefcuk kernel BerryBoot happens to have packaged this week, with all the driver mismatches with our core system.

If you choose B, we consider all bugs and misery to be self-inflicted and we refuse further support.

Hopefully that clarifies our ongoing opinion of BerryBoot installs

The LE repo only contains pre-packaged zips, nothing is being built on-the-fly. It's a 32MB download so it might take a minute or so to download.

Switch from Basic to Advanced or Expert settings mode?

I can't speak for the Kodi Android repo but the pvr.mythtv frontend is both our 8.2 and 9.0 repos for a number of ARM devices.

a) Your website has screenshots that include Kodi logo's. Under the Kodi trademark rules if you are modifying Kodi in any way (one byte of code changes) you MUST either seek formal permission from the Kodi board for your changes (which will be refused automatically for anything related to piracy or pre-installing add-ons) or you MUST fully rebrand to remove all references to Kodi. As LibreELEC ships Kodi branded as Kodi, you should assume and apply the same rules to the entire LibreELEC distro (rebrand and remove all references to LibreELEC).

b) Your website appears to be offering managed bundles of links to "movies, tvshows" etc. "for the community" which is wording that we normally see on IPTV streaming and Kodi addon sites associated with content piracy. LibreELEC has zero desire to be associated with piracy in any way, so if you cannot figure out how to embed your addons in our distro image (or even how to use GitHub, as per your PM) we are delighted and we offer no assistance.

If we are wrong (because the website I have seen is light on information) please feel free to provide more information on your player/service. It's not what is written on the website that is suspicious. It is what is not written, i.e. If you were providing a legitimate streaming service you would want to positively attract attention and openly promote things in a very different way.

Go test a Kodi leia alpha release. If the issue still exists report it to Kodi developers via their forums. If you're lucky it's either been fixed or can be resolved for Kodi v18. There will be no LE 8.2.6 release

No idea. I regularly discover my kids left tvshows or movies playing in sequence for hours; also using WP2 with the stock 8.2.5 image (not on the internal RAM, but that's irrelevant).

It's a startup timing/sequencing issue. The USB device hasn't initialised and loaded drivers before Kodi starts. Kodi evaluates the available audio devices once at startup and nothing is present; hence the device "disappears" and reverts to some other default. If the device has loaded drivers before Kodi is started the device is visible and can be selected.

You can solve the problem by setting the badly named "wait for network" startup delay in LE settings. A small delay should give the drivers time to load before Kodi starts. Something like 5 seconds should do the trick if it's borderline.

/storage/.kodi/userdata/

2GB RAM is more than enough for any LE install. 16GB of SSD is more than enough for a huge library; assuming media is on a NAS somewhere else. These days it's hard to find anything smaller than 64GB though. LE 8.2.5 should be fine on Kabylake. It's only the very latest generations that need newer kernels.

Thanks for reporting back. I'm not surprised things work better. Good to confirm though.

We currently expect to retire the WC image after LE 9.0 due to upstream changes in Kodi related to the next-generation rendering and decoding pipeline and subsequent cleanup (removal) of proprietary interfaces including amcodec that the 3.10/3.14 kernels depend on. The new pipeline will require a mainline kernel, and while meson8* hardware support in mainline continues to improve positively there is still no visible work being done on a DRM (direct rendering manager) video driver, which is fundamental for LE/Kodi support. It's something we continue to track; if things change our plans can change.

awiouy  gfduszynski I experienced a layer-8 networking problem yesterday! so librespot updates were built for 8.2 and 9.0 but only 9.0 files were pushed to the repo. The 8.2 files are now also published to the repo.

I've got no idea what the issue is or how to debug SATA initialisation problems, but I'll pass the observation that you're running tests on the drive *after* it is has completed initialisation, and it looks like the initialisation process is where the delay is incurred.

Can you connect the drive to an alternative SATA port? .. any firmware/BIOS updates available for the HTPC?