Display More
LibreELEC 9.2 Beta1 (Leia) has arrived based upon Kodi v18.4, the 9.2 Beta1 release contains many changes and refinements to user experience and a complete overhaul of the underlying OS core to improve stability and extend hardware support.
Changes since LibreELEC 9.1.002:
- updated to Kodi 18.4
- improvements for the RPi4
- bigger fonts at the update screen for 4k screens
- several Bugfixes
Change for Raspberry 4:
With LE 9.1.002 and later you need to add “hdmi_enable_4kp60=1“ to your config.txt if you want to use 4k output at the RPi4. Before you needed “hdmi_enable_4k=1“ that is now deprecated.
Beta Notes:
LibreELEC 9.2 for Generic x86/64 and Raspberry Pi 0/1/2/3 devices is a solid beta quality release. Raspberry Pi 4B images are more “late stage Alpha” and are not feature complete or perfect. Normal LibreELEC testing rules apply; if you do not want to experiment on your family’s primary entertainment system – please stick with your current version and wait for the final/stable release. If you do want to experiment – please be prepared to submit log files and work with developers to hunt down problems and test solutions.
Raspberry 4:
It would be nice to have the 4B running the latest mainline kernel as other devices in LibreELEC 9.2, but adding support for an all-newSoC chipset is a huge effort and the Pi Foundation needed to align initial 4B software with the current Raspbian release to maximise compatibility with existing softwar and to keep the workload sensible. Generic x86/64 devices are running Linux 5.1, while Raspberry Pi devices (0/1/2/3/4) are using Linux 4.19 with some new/extra code.
In this initial release 1080p playback behaviour and performance on the 4B are broadly on-par with the previous 3B/3B+ model, except for HEVC media which is now hardware decoded and massively improved. New 4K video capabilities still have plenty of rough edges to be smoothed out, but the Pi Foundation developers have been pushing fixes to the Alpha test team at a phenomenal rate over the last month and that will continue as the userbase expands.
The 4B now uses SPI flash for the bootloader. Current firmware supports SD card boot only – Network and USB booting are still on the Pi Foundation to-do list. Also on the list is HBR audio (current audio capabilities are the same as the 3B) and 3D video. The 4B hardware is HDR capable, but software support has a dependency on the new Linux kernel frameworks merged by Intel developers (with help from Team LibreELEC/Kodi) in Linux 5.2 and a kernel bump will be needed to use them. Once the initial excitement and activity from the 4B launch calms down, serious work on HDR and transitioning Raspberry Pi over to the new GBM/V4L2 video pipeline can start.
Rockchip:
Our Rockchip releases remain in an Alpha state with limited support. The Kodi version is updated but there are no significant video/audio improvements to the Rockchip 4.4 kernel codebase – and none planned. Our work on Rockchip support has refocussed onto the Linux 5.x kernel to use the modern kernel frameworks needed for the next-generation Kodi video pipeline. This work is progressing nicely, but it means the 4.4 codebase “is what it is” until a future kernel bump.
Amlogic
Our original goal was to announce Allwinner and Amlogic images alongside Rockchip as part of the LibreELEC 9.2 release, but while overall readiness has greatly improved in recent months – each has specific technical challenges to overcome before they meet our basic critera for a public release. On the human side of the project several maintainers also have reduced availability for support due to work and family commitments, and the summer vacation season is about to start. Combining these factors together, the team felt it was better to be patient and not rush releases.
So instead of releasing LibreELEC 9.2 alpha images we are announcing the start of official nightly images from our master development branch. At the moment the master branch uses Linux 5.2 and Kodi v18 so nightlies mirror LibreELEC 9.2, but in the near future we will start moving master towards Linux 5.3 and Kodi v19.If you experience problems, please open an thread at our forum. You can also open an ticket at our issue tracker.
Upgrading
On first boot the Kodi media database will be upgraded. Depending on your hardware and media collection size this could take several minutes. Please be patient.
Downloads
LibreELEC (Leia) 9.2 Beta1
- LibreELEC
- Closed
-
Is the version of 9.2 Beta1 = 9.1.501?
Confussing numbering and btw not available over the download_new web page
-
Are there any RPi 4 specific changes between 9.2alpha2 and 9.2beta1? It looks like the notes were mostly copied over from alpha2....
-
I had to download it via the USB creator tool.
-
Is the version of 9.2 Beta1 = 9.1.501?
Confussing numbering and btw not available over the download_new web page
libreelec-rpi4.arm-9.1.501.img.gz
works fine...
-
9.2 Generic download is not updated and links to 9.1.002
-
event this build also not the latest one i guess, it was uploaded on 2019-09-03
-
Running fine here on my Rpi4 so far.
I first thought that updating broke the Youtube addon, because I get "no streams found" for every video I tried to play. But it seems that the problem is due to a Youtube API change. See No streams found · Issue #661 · jdf76/plugin.video.youtube · GitHub
Btw.: Downloadlinks on the Webpage have been updated.
-
what makes you so confident ?
if I follow the download links I see:
so it seems 9.1.501 is the last one - at least on that mirror - !
maybe it was late mirrored after some internal testing or waiting on an late fix since 2019-09-03, I guess ...
btw. after an short test on my NUC: it runs well - so far - Thanks guys !!!
-
Is it possible to automatically update from v 9.2 Beta1 to the next (eventually stable) releases without losing the database and settings etc?
-
Is the version of 9.2 Beta1 = 9.1.501?
Confussing numbering and btw not available over the download_new web page
Yes... and I agree it is a little confusing, but our update process is based entirely on numbers so we have to use something less than 9.2.0 to represent builds that are not yet quite 9.2. Prior to this beta we were using 9.1.001, 9.1.002 to represent the "alpha" builds, so you can see there is a progression towards 9.2 with each release.
-
Is it possible to automatically update from v 9.2 Beta1 to the next (eventually stable) releases without losing the database and settings etc?
Kodi only change database format with each major release, so if you're already on Kodi 18.x then you should not have to update database again until Kodi 19.
-
event this build also not the latest one i guess, it was uploaded on 2019-09-03
Date when the images were built, not when they were uploaded to the release server - since then they've been undergoing testing, and were only published today.
-
Are there any RPi 4 specific changes between 9.2alpha2 and 9.2beta1? It looks like the notes were mostly copied over from alpha2....
Probably not so you'd notice, but it is using a new 4.19.y kernel with various bug fixes and new firmware for RPi4. Visual issues such as tearing in the GUI unfortunately remain.
-
9.2 Generic download is not updated and links to 9.1.002
Issue with the Wordpress caching server, should be fixed now...
-
Video playback on rpi4 is still very stuttery as on the previous release ( LibreELEC (Leia) 9.1.002 ALPHA ) hope you guys will address this as it is pretty game breaking.
-
EDIT: removed, figured out how to find the .TAR file from within the GUI. (Scared to use .IMG.GZ, might over-write the whole disk, isn't it?)
Does anyone know if Linux 5.1 will have more overhead on the Pi 1,2,3 and may reduce performance? What about 5.2 which is coming soon right?
-
(Scared to use .IMG.GZ, might over-write the whole disk, isn't it?)
Don't worry you can use .tar or .img.gz to manual update device from existing installed running build to latest beta as mentioned in Update Libreelec section of wiki. Just ensure you have correct .tar or .img.gz file for your specific device, transfer downloaded file into update folder of device (using your chosen method to transfer file to device) then reboot.
