Kodi "master" is now based on Leia, or Kodi 18. See this thread for Kodi 17 (Krypton) testbuilds.
Fair Warning
Kodi 18 is currently alpha and there is likely to be a lot of activity in the coming weeks/months. There will be some breakage.
In addition, these are "bleeding edge" builds - they often contain cherry-picked commits that require early testing prior to merging upstream, and which won't be found in regular nightlies until after they have been merged.
Please continue to report issues in this thread, but as I'm often not responsible for bugs and regressions (unless it's build related) don't expect personal replies or for me to file any upstream bug reports on your behalf. The best you can hope for is that the developer responsible is monitoring this thread and responds appropriately. If you want to progress an issue, identify when the issue first appeared as that may help suggest the pull request (PR) responsible, then post a comment on the relevant github PR or - if it's VideoPlayer related, or you don't know which PR is responsible - on trac.kodi.tv.
Bug reports
Please include a debug log with all bug reports as this greatly increases your chances of anyone taking an interest in your issue.
Best way to do this:
Bug reports without a suitable log will often be ignored - no debug log, no issue - or at best will take much longer to be investigated.
Skin Usage
By all means use third party skins with these builds (if the skins are compatible), but please do not report problems that cannot be reproduced while using the stock Estuary skin that is included with every build.
If a problem is not reproducible with stock Estuary then it's most likely to be a third-party skin problem, in which case contact the skin maintainer.
Installing
You need a working LibreELEC system in order to install a test build. If you are starting from scratch, use an official LibreELEC disk image to create a working system on your SD card. Once you have a working system, install the test build by copying the tar file into your Update folder and reboot.
RPi 3/RPi 3+ users: Use RPi2 builds.
Recent builds (see next post for older builds):
Feature Requests:
I will not be adding extra add-hoc packages to these builds as that is not their purpose, which is to help test bug fixes and enhancements for existing features/packages/drivers in stock LibreELEC. New functionality may be included for testing purposes if it is considered both beneficial and highly likely to be merged upstream in the near future, and is available as a github pull request or commit.
I have no desire to create builds with unique features upon which someone becomes dependent, as this benefits nobody in the long term not even those using the unique features once I stop creating new builds. In theory, when I stop creating new builds you should all be able to seamlessly switch back to official LibreELEC builds which by then should be including most if not all of the enhancements originally tested in these builds.
If you care about long term support for your favourite package, feature or driver and want to see it included in a LibreELEC build, contact the LibreELEC developers on github or post on the LibreELEC.tv forum requesting the addition of support in the base LibreELEC build (or better yet, create a Pull Request with patch). That way everyone building or using a LibreELEC derived system "wins".
Additional Testing Notes:
Do NOT upload the log itself to the forum! Always us a pastebin-type site (or dropbox/googledrive if you have to compress the log).
Game Emulators
Access games via Internet Archive ROM Launcher (IARL):
Download Zach Morris Repo and install from zip (don't use "Install from zip file" Home screen widget - use Add-ons > Add-on browser > Install from zip file)
Install from repository > Zach Morris Add-ons > Game add-ons > Game providers > Internet Archive ROM Launcher
Within IARL, install emulators, launch games etc.
Odds and sods
What are newclock3, newclock4 etc.? Link.
A selection of addons are available here
Fair Warning
Kodi 18 is currently alpha and there is likely to be a lot of activity in the coming weeks/months. There will be some breakage.
In addition, these are "bleeding edge" builds - they often contain cherry-picked commits that require early testing prior to merging upstream, and which won't be found in regular nightlies until after they have been merged.
Please continue to report issues in this thread, but as I'm often not responsible for bugs and regressions (unless it's build related) don't expect personal replies or for me to file any upstream bug reports on your behalf. The best you can hope for is that the developer responsible is monitoring this thread and responds appropriately. If you want to progress an issue, identify when the issue first appeared as that may help suggest the pull request (PR) responsible, then post a comment on the relevant github PR or - if it's VideoPlayer related, or you don't know which PR is responsible - on trac.kodi.tv.
Bug reports
Please include a debug log with all bug reports as this greatly increases your chances of anyone taking an interest in your issue.
Best way to do this:
- Enable debug logging:
Settings > System > Logging > Enable debug logging
- Reboot
- Reproduce the issue
- Upload the log:
Settings > LibreELEC > System > Submit Log > Upload latest Kodi log
- Post the URL in the forum with a description of the problem
Upload latest Kodi crash log option.Bug reports without a suitable log will often be ignored - no debug log, no issue - or at best will take much longer to be investigated.
Skin Usage
By all means use third party skins with these builds (if the skins are compatible), but please do not report problems that cannot be reproduced while using the stock Estuary skin that is included with every build.
If a problem is not reproducible with stock Estuary then it's most likely to be a third-party skin problem, in which case contact the skin maintainer.
Installing
You need a working LibreELEC system in order to install a test build. If you are starting from scratch, use an official LibreELEC disk image to create a working system on your SD card. Once you have a working system, install the test build by copying the tar file into your Update folder and reboot.
RPi 3/RPi 3+ users: Use RPi2 builds.
Recent builds (see next post for older builds):
- #1117, 17-Nov-2018: RPi / RPi2 -- Release post ([JSON] Bump version to 10.0.0; fixed: Low read rate detection logic when VideoPlayer uses filecache)
- #1116, 16-Nov-2018: RPi / RPi2 -- Release post ([addons] Sort logged list of installed add-ons; inputstream.adaptive: Include codecId in decoder display name)
- #1115, 15-Nov-2018: RPi / RPi2 -- Release post (New 4.19.2 kernel)
- #1114, 14-Nov-2018: RPi / RPi2 -- Release post ([DetectDVDType]: fix Crash due to non-checked error state)
- #1113, 13-Nov-2018: RPi / RPi2 -- Release post ([pvr] Fix channel sorting. Fixes #14854; libcec-4.0.3)
- #1112, 12-Nov-2018: RPi / RPi2 -- Release post (inputstream-adaptive, pvr.vdr.vnsi updates)
- #1111, 11-Nov-2018: RPi / RPi2 -- Release post ([PVR] Remove 'Use simple Timeshift OSD' setting from settings.xml.)
- #1110, 10-Nov-2018: RPi / RPi2 -- Release post ([PVR] New PVR playback setting: 'Delay mark last watched'.)
- #1109, 09-Nov-2018: RPi / RPi2 -- Release post (pvr.zattoo: Fix segfault strlen)
- #1108, 08-Nov-2018: RPi / RPi2 -- Release post (samba: update to samba-4.9.2; libcec 4.0.3; [Settings] Implement FindIntInList in CSettingList)
- #1107, 07-Nov-2018: RPi / RPi2 -- Release post (Reintroduce crazycat: update to 2018-11-04)
- #1106, 06-Nov-2018: RPi / RPi2 -- Release post (libcec: drop python wrapper; iptables: update to iptables-1.8.1)
- #1105, 05-Nov-2018: RPi / RPi2 -- Release post (New firmware (increased bootcode timeout); trigger updateresolution on stream start to set fps in RM properly; [GUI] reinitalize addon path after returning with .. directory item)
- #1104, 04-Nov-2018: RPi / RPi2 -- Release post (New 4.19.1 kernel; eventlircd: prevent race with libinput / kodi; avoid managing ZeroTier network interfaces)
- #1103, 03-Nov-2018: RPi / RPi2 -- Release post (bump to v18.0 RC1; FFmpeg: Bump to 4.0.3-Leia-Beta5)
- #1102, 02-Nov-2018: RPi / RPi2 -- Release post ([GLES] VideoPlayer: more cleanup; libcec, p8-platform updates; cputemp fixes)
- #1101, 01-Nov-2018: RPi / RPi2 -- Release post (bump libdvdcss to 1.4.2-Leia-Beta-5 (kodi PR); [VideoPlayer] SetResolution synchronously instead RM::TriggerResolution)
- #1031, 31-Oct-2018: RPi / RPi2 -- Release post (Fix RES_DESKTOP calibration setting assignement; fix include auto-mounted drives remote access allowed check)
- #1030, 30-Oct-2018: RPi / RPi2 -- Release post (Correctly read artist art after Coverity scan fix; [Estuary] Video OSD and Music OSD enhancements/fixes.)
- #1029, 29-Oct-2018: RPi / RPi2 -- Release post ([GLES] VideoPlayer: YUV2RGB rework, Tonemapping, and other cleanup)
- #1028, 28-Oct-2018: RPi / RPi2 -- Release post (Resolution: Use v17 behaviour if whitelist is not present; [PVR][Estuary] Add GUI for Radio Data System (RDS).)
- #1027, 27-Oct-2018: RPi / RPi2 -- Release post (Fix RDS stream support)
- #1026, 26-Oct-2018: RPi / RPi2 -- Release post ([Estuary] bug fixes; fix DVD Menu issues with MMAL)
- #1025, 25-Oct-2018: RPi / RPi2 -- Release post (Various Game related changes)
- #1024, 24-Oct-2018: RPi / RPi2 -- Release post (Fix invalid "not available" add-on dependency message)
- #1023, 23-Oct-2018: RPi / RPi2 -- Release post (New firmware (backlight driver); new 4.19.0 kernel; Kodi 18 Beta 5 starts; pvr.iptvsimple: RapidXML new package)
- #1022, 22-Oct-2018: RPi / RPi2 -- Release post (New 4.18.16 kernel; libssh: update to 0.8.4; Game API: v1.1.0 - Sync with RetroPlayer test builds)
- #1021, 21-Oct-2018: RPi / RPi2 -- Release post (Scraper/JSON/GUI artwork updates; CCurlFile Exists/Stat changes; kernel: Fix for hw csum failure)
- #1020, 20-Oct-2018: RPi / RPi2 -- Release post ([jsonrpc] set movie collection plots and get/set season titles; DVB Updates: add rc/ir again)
- #1019, 20-Oct-2018: RPi / RPi2 -- Release post (busybox: update to 1.29.3; DVB addons - enable more options)
- #1018, 18-Oct-2018: RPi / RPi2 -- Release post (linux: XBox DVD Remote uses 12 bits scancodes)
- #1017, 17-Oct-2018: RPi / RPi2 -- Release post (kodi: add kodi-remote script; "eth0: hw csum failure" logging)
- #1016, 17-Oct-2018: RPi / RPi2 -- Release post (DVB driver addons update to latest)
- #1015, 15-Oct-2018: RPi / RPi2 -- Release post (New firmware; new 4.18.14 kernel; Too many other things to mention...)
- #1006, 06-Oct-2018: RPi / RPi2 -- Release post (ApplicationPlayer: Fix playlists by correctly switching players)
- #1005, 06-Oct-2018: RPi / RPi2 -- Release post (Adjust PVR context menus for timer and timer rule objects)
- #1004, 05-Oct-2018: RPi / RPi2 -- Release post (Minors)
- #1003, 03-Oct-2018: RPi / RPi2 -- Release post (Support "Play" on Home screen)
- #1002, 02-Oct-2018: RPi / RPi2 -- Release post (Start of Kodi 18 Beta 4; alternative fix for CMA induced stutter; RFC: Cve 2017 5982; lots of game/controller fixes)
- #1001, 01-Oct-2018: RPi / RPi2 -- Release post (New 4.18.11 kernel; aE, VideoPlayer and GUIInfo fixes)
- #0930, 30-Sep-2018: RPi / RPi2 -- Release post (Minors)
- #0929, 29-Sep-2018: RPi / RPi2 -- Release post (Minors)
- #0928, 28-Sep-2018: RPi / RPi2 -- Release post (Minors)
- #0927, 28-Sep-2018: RPi / RPi2 -- Release post ([guiinfo] Fix VideoPlayer.Title and MusicPlayer.Title; include missing BT_HCIUART options dropped after 4.14.y)
- #0926, 26-Sep-2018: RPi / RPi2 -- Release post (New 4.18.10 kernel)
- #0925, 26-Sep-2018: RPi / RPi2 -- Release post (Reintroduce DVB Sky revert commit; [JSON]Fix Player.GetItem during track change seg fault)
- #0924, 24-Sep-2018: RPi / RPi2 -- Release post (samba: update to samba-4.9.1)
- #0923, 23-Sep-2018: RPi / RPi2 -- Release post (Fix crash when playing back audio over smb:// (probeBuffer))
- #0922, 22-Sep-2018: RPi / RPi2 -- Release post (Fix for slow directories; RetroPlayer fixes/improvements; link with libnfs instead of loading it dynamic; scripts/image: use 256kb blocksize; samba-config.service: fix destroying .cache structure)
- #0921, 22-Sep-2018: RPi / RPi2 -- Release post (New firmware; new 4.18.9 kernel; ffmpeg update - should fix green frames; busybox: drop NFS support for linux < 2.6.23 (enable NFSv4))
- #0920, 21-Sep-2018: RPi / RPi2 -- Release post ([fix] iterate over reference and only copy the variable if needed)
- #0919, 19-Sep-2018: RPi / RPi2 -- Release post (RetroPlayer: Fix no game input after controller shuts off)
- #0918, 18-Sep-2018: RPi / RPi2 -- Release post (Couple of EGL fixes)
- #0917, 17-Sep-2018: RPi / RPi2 -- Release post (New 4.18.8 kernel; SQLite 3.25.0)
- #0916, 16-Sep-2018: RPi / RPi2 -- Release post ((Potential) fix for CMA-related audio stutter; [keymaps] Map key 'numpad period' to action 'channel number separator'.)
- #0915, 15-Sep-2018: RPi / RPi2 -- Release post (curl: update to curl-7.61.1 with latest CA cert bundle; revert reverted CMA changes)
- #0914, 14-Sep-2018: RPi / RPi2 -- Release post (AEBitstreamPacker: Differentiate between DTS-HD-MA and DTS-HD-HR; revert "Merge pull request #14429 from ace20022/bd_mouse_select")
- #0913, 14-Sep-2018: RPi / RPi2 -- Release post (samba: update to samba-4.9.0; revert "mm, compaction: allow compaction for GFP_NOFS requests")
- #0912, 12-Sep-2018: RPi / RPi2 -- Release post (VideoPlayer: rt streams - flush demux queue if sync error is too big)
- #0911, 11-Sep-2018: RPi / RPi2 -- Release post ([Music]Fix forced expansion of .m3u playlists)
- #0910, 10-Sep-2018: RPi / RPi2 -- Release post (New firmware; new 4.18.7 kernel (with RPi POE support); input: libinput: add setting to allow changing keymap layout)
- #0909b, 09-Sep-2018: RPi / RPi2 -- Release post (Kodi Beta 3 begins; VideoPlayer demux and sync fixes; revert CServiceBroker pointer and PVR OSD changes until newclock5 rebase)
- #0909, 09-Sep-2018: RPi / RPi2 -- Release post (Increase systemd TimeoutStop for kodi service to 30 seconds; VideoPlayer: fix timeshift on demand; [PVR] Guide window: Fix deadlock; update to mesa-18.2.0, wireless-regdb-2018.09.07, Python3-3.7.0; ath9K improvements)
- #0907, 07-Sep-2018: RPi / RPi2 -- Release post (inputstream.adaptive with Widevine api 10 implemented; [videoplayer] [bluray] Fix playback of disc with truehd tracks in menu mode.)
- #0906, 06-Sep-2018: RPi / RPi2 -- Release post ([PVR] trac#18022: Add support for ACTION_SHOW_INFO to CGUIDialogPVRChannelGuide; pvr.dvbviewer and pvr.mediaportal.tvserver fixes)
- #0905, 05-Sep-2018: RPi / RPi2 -- Release post (New 4.18.6 kernel; HID: core: fix grouping by application)
- #0904, 04-Sep-2018: RPi / RPi2 -- Release post ([PVR] Simple timeshift OSD (optional); GLES logging cleanup and unused extension removal)
- #0903, 03-Sep-2018: RPi / RPi2 -- Release post ([PVR] PVRChannelGroup::ResetChannelnumberCache; [Estuary] Music OSD: Remove 'Previous' button for non-seekable stream)
- #0902, 02-Sep-2018: RPi / RPi2 -- Release post (Minor change)
- #0901, 02-Sep-2018: RPi / RPi2 -- Release post (Show EPG image on the PVR screens)
Feature Requests:
I will not be adding extra add-hoc packages to these builds as that is not their purpose, which is to help test bug fixes and enhancements for existing features/packages/drivers in stock LibreELEC. New functionality may be included for testing purposes if it is considered both beneficial and highly likely to be merged upstream in the near future, and is available as a github pull request or commit.
I have no desire to create builds with unique features upon which someone becomes dependent, as this benefits nobody in the long term not even those using the unique features once I stop creating new builds. In theory, when I stop creating new builds you should all be able to seamlessly switch back to official LibreELEC builds which by then should be including most if not all of the enhancements originally tested in these builds.
If you care about long term support for your favourite package, feature or driver and want to see it included in a LibreELEC build, contact the LibreELEC developers on github or post on the LibreELEC.tv forum requesting the addition of support in the base LibreELEC build (or better yet, create a Pull Request with patch). That way everyone building or using a LibreELEC derived system "wins".
Additional Testing Notes:
- Build references
When reporting issues, refer to builds using only the published build codes, ie. #0215, #0216 etc. The build code is visible on the boot screen, and by typing "lsb_release".
Do NOT use any other reference, as these are often meaningless. For instance, the LibreELEC github revision identifier, 20272, 20281 etc. can be used by more than one build if nothing changes in LibreELEC between successive builds meaning such references could identify multiple builds, rendering it useless as a unique reference.
Anyone using the wrong reference will be ignored by me, possibly others, as I'm just not interested in working out which build you may or may not be referring to.
- Usage information
Starting with build #0529(2014), very limited usage information will be collected during the first boot of each newly installed build. The information collected is: build#, Pi memory size (256MB, 512MB or 1008MB) and maximum ARM frequency. No IP or personal information is collected!
If you wish to opt out of data collection, run the following command:
The purpose of this data collection is really just to get an idea of how much testing is being carried out and on what hardware, and would otherwise be achieved via non-opt out server logs if such logs were available (which they're not).Code:touch /storage/.config/milhouse.dnt
- Migrating LibreELEC from RPi1 to RPi2, and back again
Note #1: Prior to migration I would recommend disabling all overclocks, as a Pi1 overclock may not work successfully on a Pi2, and vice versa.
Note #2: LibreELEC now includes a compatability check to intentionally make it more difficult to upgrade the RPi1 or RPi2 with the wrong software. In order to switch from RPi1 to RPi2 (or vice versa) you will need to disable this compatability check by executing the following command in ssh BEFORE commencing the upgrade:
Code:touch /storage/.update/.nocompat
From RPi1 to RPi2: While using the RPi1, upgrade with the RPi2 tar. Once the upgrade is complete, the system will reboot to a rainbow boot screen (as you're now booting the ARMv7 kernel). Shutdown (pull the power) and transfer the SD card into your RPi2, which will boot normally.
From RPi2 to RPi1: While using the RPi2, upgrade with the RPi tar. Once the upgrade is complete, the system will reboot to a rainbow boot screen (as you're now using the ARMv6 kernel). Shutdown (pull the power) and transfer the SD card into your RPi1, which will boot normally.
- Builds since early Dec 2014 include crashlog support
In the event of a crash, the file /storage/.kodi/temp/kodi_crashlog_<ccyymmddhhmmss>.log will be created. The symbolic link "/storage/.kodi/temp/kodi_crash.log" will always point to the latest crashlog. Upload one of these files to a paste site and post details on the forum.
Debug builds are occasionally uploaded to the debug folder. Debug builds will usually include more detailed crashlog information, but require a larger System partition (at least 384MB) and more RAM.
Use the following command to upload the most recent crashlog:
Code:cat /storage/.kodi/temp/kodi_crash.log | pastebinit
- Resizing partitions for debug-enabled builds (or undersized partitions that result in "CHECKING SIZE: FAILED" errors)
The default FAT partitition created by a disk-image installation (prior to OpenELEC 6.0.1) is too small for a debug-enabled build (and even some of the more experimental non-debug builds depending on what features are included), and will need to be increased in size to 512MB using some of the free space allocated to the second ext4 partition.
To resize the FAT and ext4 partitions of an existing installation: - Linux: use gparted to resize FAT/ext4 partitions
- Windows: use MiniTool Partition Wizard. See this post for more details - unfortunately partition move/resize is not supported by MiniTool for ext4 filesystems so backup, delete/recreate ext4, then restore to resize the Storage partition
- Windows: An alternative solution is to boot a Linux "LiveCD" and then use gparted
- Amazon Prime / Netflix / inputstream.adaptive
Amazon is working working (as of 03 July 2017)
Netflix is currently working (as of 29 Jun 2017)
These builds include the inputstream.adaptive addon, which is enabled by default.
With inputstream.adaptive it is possible to view Netflix and Amazon Prime content.
Amazon Prime addons (valid Amazon Prime account required):
https://github.com/liberty-developer/plu...me_instant
https://github.com/phil65/plugin.video.amazon65
If the Amazon addons do not support the Inputstream Helper addon then you may have to install libwidevine manually - this is an unsupported method, contact the Amazon addon maintainers if it doesn't work:
Code:curl -Ls http://nmacleod.com/public/libreelec/getwidevine.sh | bash
Netflix addon (valid Netflix account required):
The Netflix addon with Inputstream Helper can be installed from the Kodinerds Netflix repository - once the repository is installed you can install the Netflix addon, and when a video is watched if the libwidevine library needs to be installed you will be prompted to do so.
Netflix support: https://github.com/asciidisco/plugin.video.netflix
- LibreELEC Settings add-on Development Updates
For these builds since #0612, enter a URL into a Custom Channel, selecting from the following URLs based on your hardware:
then select "Milhouse-9.0" as the Update Channel (or "Milhouse-8.0" for builds before #0202).Code:RPi Zero/RPi1: http://milhouse.libreelec.tv/builds/master/RPi
RPi2/RPi3: http://milhouse.libreelec.tv/builds/master/RPi2
Generic (x86): http://milhouse.libreelec.tv/builds/master/Generic
- Clean builds - what are they?
There are two ways to build LE: a "clean" build, where everything (every package) is built from scratch - this takes 2.5 to 3 hours - or there's an "incremental" build where only the packages that have changed from the last build are re-built - this is much quicker, usually 10-15 minutes depending on the number of packages that have changed.
Obviously "incremental" builds are the preferred method since they're so much quicker, however there are consequences when packages have inter-dependencies and only some of those packages are changed (and thus rebuilt) which may result in unpredictable results at run-time. For this reason, every now and again it's a good idea to "clean build". Also, when there are a large number of core packages being updated/bumped it's also a good idea to "clean build" since the likelihood/risk of inter-dependency is so much greater.
I'll sometimes make a point of mentioning in the build highlights when a build is of the "clean build" variety, mainly so that I remember this if/when I come back to this build for any reason in another 6 months time... Note that I won't always do this as I'll sometimes forget to mention it, so the lack of any reference to "clean build" should not be taken as confirmation that the build is incremental.
- Uploading debug logs
Without a debug log there's often no way to investigate a problem, and you can expect your bug report to be ignored as a result. This is the easiest way to upload a debug log:
- Enable debug logging. If this is not possible in the GUI (because Kodi is crashing) then add the following to /storage/.kodi/userdata/advancedsettings.xml:
Code:<advancedsettings>
<loglevel>1</loglevel>
</advancedsettings> - Reboot, so that debug logging is in effect from the very start of Kodi
- Reproduce the problem
- Using ssh connect to LibreELEC (username: root, password: libreelec)
- Execute the command:
then paste the resulting url to the forumCode:cat /storage/.kodi/temp/kodi.log | pastebinit
Alternatively, if you have a Linux system available and are creating a fresh SD installation, manually creating the partitions may be a quicker option (the linked instructions will create a 512MB FAT partition).
Starting with OpenELEC 6.0.1, disk image installations will now create a 512MB FAT partition although this will wipe all existing data - use the backup/restore procedure to save existing data.
Do NOT upload the log itself to the forum! Always us a pastebin-type site (or dropbox/googledrive if you have to compress the log).
Access games via Internet Archive ROM Launcher (IARL):
