LibreELEC (Krypton) v8.1.1 BETA
This is the second BETA of our 8.2 release; a mid-year version bump to enhance hardware support and capabilities. This beta addresses issues in our OVA image, a Broadcom WIFI firmware vulnerability for Raspberry Pi 3 and Zero W users, and MPEG issues seen with some nVidia cards. It also adds support for the inexpensive Xbox ONE (DVB-C/T/T2) USB tuner (about €12 on eBay), and LibreELEC settings gains new options for changing the embedded Samba server Workgroup and adjusting the SMB protocol versions supported for security and SMB share compatibility. Kodi is bumped to 17.4 final.
Changes since LibreELEC 8.1.0 include:
- Fix VMware OVF template, drop OVA .img suffix and force ‘installer’ mode
- Update RPi kernel to 4.9.43
- Update RPi wifi firmware to resolve CVE-2017-9417 (Broadpwn)
- Update to Samba 4.6.7
- Update to Kodi 17.4 final
- Update nVidia main driver to 384.69
- Update LibreELEC settings add-on to expose more Samba config options
- Revert Hauppauge DualHD tuner support (back to single-tuner, which works)
- Add support for Xbox ONE (DVB-C/T/T2) USB tuner
See detailed changes on GitHub – and the change summary for LibreELEC v8.1.0 BETA
!!! SAMBA UPDATE – IMPORTANT !!!
The fall “Creators Update” for Windows 10 removes SMB1 client/server support and NAS devices now ship with configuration that only supports SMB2/3 – causing problems because all versions of Kodi before 17.4 can only make SMB1 connections. This release includes changes that allow the Kodi SMB client and our embedded Samba server to work with SMB2/3 connections; improving SMB security and performance. However, it is a disruptive change:
- The Kodi SMB client sometimes fails to negotiate SMB3 with old Samba versions. There is a new option in Kodi Settings > Services > SMB client > that allows SMB2 or SMB1 connections to be forced for compatibility with legacy SMB servers.
- The embedded Samba server now defaults to minimum SMB2 and maximum SMB3 and the LibreELEC Settings add-on allows the supported SMB protocol versions to be changed for compatibility with legacy clients. It also allows configuration of the WORKGROUP name.
- Samba 3.x /storage/.config/samba.conf configurations must be updated to use the new Samba 4.x template (samba.conf.sample) as some Samba 3.x configuration is incompatible. The embedded Samba server may fail to start until this is done. If the reason for older changes was workgroup name please delete the file and use the new in-GUI configuration method.
- Browsing SMB shares via “Windows network browsing” in Kodi requires the browser service on the SMB server. This SMB1 service is removed from Win10 in the creators update and there is no equivalent for SMB2/3 versions of the SMB protocol. When Kodi makes SMB2+ connections (which is now our default) Kodi network browsing to add sources will not work. Windows SMB shares can still be added using the full server/share path. It is still possible to browse non-Windows Samba/NAS devices that advertise SMB shares via ZeroConf (aka Bonjour/Avahi).
- Connection failures to anonymous and guest shares are solved by creating a new local machine (not Microsoft ID) user and strong password for Kodi to use on the server, then assigning appropriate read or read-write permissions to the shares Kodi will access.
SAMBA CONFIGURATION FILES
The active configuration for the Kodi SMB client is stored in /storage/.kodi/.smb/smb.conf which can be extended with personal changes in /storage/.kodi/.smb/user.conf. Posts in the Kodi forum often refer to configuration files in ~/.smb/smb.conf – this location is incorrect for Kodi 17.4 which is modified to use its own ‘internal’ smbclient configuration.
The active configuration file for the embedded Samba server is /etc/samba/smb.conf unless a personal configuration exists in /storage/.config/samba.conf. Samba is started with an explicit declaration of the config file to use so it will not detect ~/.smb/smb.conf if it exists (this location is used on some other Linux distributions).
We see frequent forum postings where users attempt to change the Kodi smbclient configuration through the /storage/.config/samba.conf file. This is pointless. The embedded Samba server configuration has no effect on the Samba client connections made by Kodi.
If you experience issues with SMB shares (client or server) please post in the forums sharing information on the Windows and Samba versions, and a Kodi debug log, and we will do our best to help.
!! LIRC CHANGES !!
In LibreELEC 8.0 the Lirc service is enabled when an IR receiver is detected in the system, but it is not started unless used with the lirc_rpi or lirc_xbox drivers or a personal lircd.conf. In LibreELEC 8.2 the Lirc service supports all drivers. This can result in the service starting and interfering with normal IR operations. If you experience “double button presses” after updating the Lirc service can be disabled in the ‘Services’ tab of the LibreELEC settings add-on. The Lirc service is disabled in new installations and must be manually enabled. Thanks to @HiasoffT changes the Lirc service is now configurable using a combination of /storage/.config/lirc_options.conf and lircd.conf – the same approach as most desktop Linux distributions (and howto instructions users find via Google searches).
AUTO-UPDATE
After recent security issues with Kodi and Samba we need to ensure more users are running the latest release to benefit from feature and security bug fixes. To achieve this we have changed the default setting for auto-update from manual to auto. Auto-update provides maintenance updates, e.g. 8.1.0 BETA to 8.1.1 and 8.2.0 and from 8.2.0 to 8.2.1 etc. in the 8.2 release series. Major version updates are still manual (user-initiated) updates, e.g. 8.2.0 to a future 9.0.0 release. Users can revert to manual update in the LibreELEC settings add-on. NB: LibreELEC operates a 24-hour canary period between new release files being available and auto-update being enabled.
or donate by purchasing a LibreELEC teeshirt or hoodie
New installations using the LibreELEC USB-SD Creator app
LibreELEC.USB-SD.Creator.Linux-32bit.bin (info)
LibreELEC.USB-SD.Creator.Linux-64bit.bin (info)
LibreELEC.USB-SD.Creator.macOS.dmg (info)
LibreELEC.USB-SD.Creator.Win32.exe (info)
New installation using 3rd party USB or SD writer apps (.img.gz)
LibreELEC-Generic.x86_64-8.1.1.img.gz (info)
LibreELEC-RPi.arm-8.1.1.img.gz (info)
LibreELEC-RPi2.arm-8.1.1.img.gz (info)
LibreELEC-Slice.arm-8.1.1.img.gz (info)
LibreELEC-Slice3.arm-8.1.1.img.gz (info)
LibreELEC-imx6.arm-8.1.1.img.gz (info)
LibreELEC-Odroid_C2.aarch64-8.1.1.img.gz (info)
LibreELEC-WeTek_Play.arm-8.1.1.img.gz (info)
LibreELEC-WeTek_Core.arm-8.1.1.img.gz (info)
LibreELEC-WeTek_Hub.aarch64-8.1.1.img.gz (info)
LibreELEC-WeTek_Play_2.aarch64-8.1.1.img.gz (info)
New Install to WeTek internal NAND (.zip)
LibreELEC-WeTek_Play.arm-8.1.1.zip (info)
LibreELEC-WeTek_Core.arm-8.1.1.zip (info)
LibreELEC-WeTek_Hub.aarch64-8.1.1.zip (info)
LibreELEC-WeTek_Play_2.aarch64-8.1.1.zip (info)
Manual Update from LibreELEC 7.0, 8.0, or OpenELEC (.tar)
LibreELEC-Generic.x86_64-8.1.1.tar (info)
LibreELEC-RPi.arm-8.1.1.tar (info)
LibreELEC-RPi2.arm-8.1.1.tar (info)
LibreELEC-Slice.arm-8.1.1.tar (info)
LibreELEC-Slice3.arm-8.1.1.tar (info)
LibreELEC-imx6.arm-8.1.1.tar (info)
LibreELEC-Odroid_C2.aarch64-8.1.1.tar (info)
LibreELEC-WeTek_Play.arm-8.1.1.tar (info)
LibreELEC-WeTek_Core.arm-8.1.1.tar (info)
LibreELEC-WeTek_Hub.arm-8.1.1.tar (info)
LibreELEC-WeTek_Play_2.arm-8.1.1.tar (info)
Thanks! Will give it a try now.
Hope it will fix the laggs by using simple PVR on rasperry by switching channels….
Nope. Not until the stream caching process is overhauled in Kodi Leia. Krypton is a dead codebase at this point so nip/tuck fixes only, nothing major.
LibreElec has an issue with HLS-encrypted streams on Raspberry Pi. Streams won’t load but works fine if I switch back to RTMP.
HLS works fine with stock Kodi 17.4 from Google Play on Android.
Works brilliant on my NUC, did the manual update via SSH.
Use the GUI in future .. less hassle.
Nah, love SSH 🙂
Just did a fresh install incl. TVHeadend service. Sadly recordings that get initated from EPG start and stop immediately with nothing showing up under “Recordings”. This worked without issues using LE8.0.2
False alarm! After another EPG scan everything works as expected.
Problems with colors while playing this file:”Passengers.2016.2160p.BluRay.REMUX.HEVC.DTS-HD.MA.TrueHD.7.1.Atmos-FGT” with LibreELEC 8.1.0 beta.
Same HW (i3-7100) with Windows10 and Kodi 17.3 plays flawlessly. Thanks!
File info:
General
Unique ID : 196111560429071496423225027923511346863 (0x9389B67159A17699B07475E7A0AC06AF)
Complete name : \\Nas\uhd\Passengers (2016) [2160p]\Passengers.2016.2160p.BluRay.REMUX.HEVC.DTS-HD.MA.TrueHD.7.1.Atmos-FGT.mkv
Format : Matroska
Format version : Version 4 / Version 2
File size : 54.1 GiB
Duration : 1 h 56 min
Overall bit rate mode : Variable
Overall bit rate : 66.6 Mb/s
Movie name : Passengers.2016.2160p.BluRay.REMUX.HEVC.DTS-HD.MA.TrueHD.7.1.Atmos-FGT
Encoded date : UTC 2017-07-25 16:26:59
Writing application : mkvmerge v13.0.0 (‘The Juggler’) 64bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5
Cover : Yes
Attachments : cover_land.jpg / small_cover.jpg / small_cover_land.jpg / cover.jpg
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main [email protected]@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 56 min
Bit rate : 52.9 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.266
Stream size : 42.9 GiB (79%)
Title : Passengers.2016.2160p.BluRay.REMUX.HEVC.DTS-HD.MA.TrueHD.7.1.Atmos-FGT
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : SMPTE ST 2084
Matrix coefficients : BT.2020 non-constant
Mastering display color pri : R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000
Mastering display luminance : min: 0.0050 cd/m2, max: 4000.0000 cd/m2
Maximum Content Light Level : 1529 cd/m2
Maximum Frame-Average Light : 380 cd/m2
Audio #1
ID : 2
Format : TrueHD
Format profile : TrueHD+Atmos / TrueHD
Codec ID : A_TRUEHD
Duration : 1 h 56 min
Bit rate mode : Variable
Bit rate : 4 044 kb/s
Maximum bit rate : 8 229 kb/s
Channel(s) : Object Based / 8 channels
Channel positions : Object Based / Front: L C R, Side: L R, Back: L R, LFE
Sampling rate : / 48.0 kHz
Frame rate : 1 200.000 FPS (40 spf)
Compression mode : Lossless
Stream size : 3.28 GiB (6%)
Title : Passengers.2016.2160p.BluRay.REMUX.HEVC.DTS-HD.MA.TrueHD.7.1.Atmos-FGT
Language : English
Default : Yes
Forced : No
Does this release address the issue with the RPi3 and decoding of TrueHD 7.1 w/ Atmos? Sometimes the channels are not mapped correctly. For instance, sometimes the rear surrounds are coming out the front and I have no center channel voices.
Hey, I like those cats in the version release photo. The one for the 8.1.0 release looks like my good buddy Harry when he was a kitten. He was always curious about everything. :).
Nice touch.
Later…
Everything works perfect over here! For anyone struggeling to access Samba shares on their LE/Kodi box using Windows 10 consider applying a registry entry according to these instructions: https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows
this was the solution on the previous beta, but not on this one. some one please fix this
I didn’t use the previous beta. I started with the 8.1.1 beta and made the registry entry after setting up 8.1.1 and everything works as expected.
whaaaaaaaaaaaaaaaaaaat?????????????
i did a clean install back to 8.0.2 and did this but get the same issue.
some times i can browse samba, but cant transfer anything to it.
other times windows cant see the network path
then i did a clean install to beta 8.1.1
same thing
so, tell me obi one. whats wrong?
i use windows 10 with a update post 1703 creators update
wait a minute. registry entry you say? i only did the command in cmd.
Everything works fine here! (I’m not using SAMBA, so I don’t know if it works)
Still no HQ scalers in 2160p resolution unfortunately, really miss Lanczos scaling of 1080p to 2160p, it did a better job than my TV. I hope they get re-enabled again in the final, it seems they were disabled because of performance issues on RPi? But they should be enabled in Generic version as there was no issue on a NUC whatsoever.
Kodi have received too many bug reports about HQ shaders not working correctly at 4k resolutions and investigations have repeatedly shown users with inadequate spec hardware – so to reduce the noise we were asked to patch out support. HQ scalers are still present for normal HD media. If you really need it; self-build an LE image without the patch that disables them.
GUI autoupdate rocks!
Yesterday I was nicely surprised seeing a bump from 8.1.0 to 8.1.1 on a boot screen. Came to check the website for changelog then.
How about letting users to decide about upscaler?
Make a checkbox, disable it by default and hide under expert settings..
My setup is 1080p, just a solidarity.
Indeed, that would be incredibly useful (if only because I have no idea how to self-build and exclude a specific patch) 🙂
Can’t connect with Samba from my Android phone to Kodi, SMB from Windows 10 works ok.
SMB on Win10 speaks SMB2+ and your Android phone probably speaks SMB1. You can enable SMB1 support in the LE settings add-on. For any further help .. post in the forum please.
It works! Thank you. I didn’t noticed the libreelec option.
Chewitt, good work interface on odroid C2. Thankx!!!! 🙂
Not sure what changed in this version but after installing the beta, my harmony remote is doing double inputs when I click a button on the remote. If I revert to the previous stable release the problem goes away, so it is something with the beta release.
Maybe help https://forum.libreelec.tv/thread/9580-v8-1-0-beta-key-presses-on-remote-are-repeated-twice/
Thanks for that info. I didn’t see this post when I posted my issue.
It’s probably due to LIRC changes – as written in the release notes above that nobody appears to read 🙂
Afer update to 8.1.1 I have problem with booting my msi cubi 2 (kaby lake u) – sometimes I need to cycle power on/off few times to boot, otherwise IT freezes on msi boot logo, without any message. When it finally boots, it works flawlessly – stable and fast, including hardware hevc decompression. Reverting back to 8.0.2 resolves booting problem.