Posts by milhouse

    Hi Milhouse,

    Everything is stock, including skin, I don't use any add-ons other than those already installed in Libreelec.

    Here are the results of the test at idle:

    Are you using hdmi_enable_4k=1 in config.txt? This enables 4Kp60 but (currently) increases clocks/voltages which leads to higher temperatures.

    Quote from popcornmix

    The reason that is optional is it increases clocks/voltages which means higher temps. We did lower these just before LE image was made but a. Issue with WiFi meant we reverted it. The latest rpi-update does lower this again (with a fix for WiFi.).

    Hopefully the next LibreELEC 9.2 alpha update (9.1.002) will have the updated firmware and thus lower temperatures with hdmi_enable_4k=1.

    Have you limited your GUI size to 1080p as this will give better performance (and thus potentially lower idle temperatures) than running the Kodi GUI at 4Kp30 or 4Kp60 (Settings > System > Display > Limit GUI Size - needs settings level set to "Expert").

    Can you upload your kodi.log from the RPi4 using the "upload kodi log" option in the LibreELEC Settings addon and post the link?

    this screenshoot is taken from a clean install.

    Is the screenshot taken at a time when your system is "idle"? If so, isn't it showing a temperature of 60C-61C? Where are you seeing 70C? Is it only after you install the addons that you start to see temps of around 70C?

    And why is one of your CPU cores spiking to 100% every 3-4 seconds on a "clean" install - that's not what I'd call an "idle" system (in my screenshot, CPU load was consistently low on 3 cores, with 1 core servicing kodi.bin at about 30%). From your screenshot, it appears that your system is hammering the SD card almost constantly writing large amounts of data (to the SD card) - try disabling Backup and Artwork Beef and see if the "iowt" column goes down to 0.00.

    Sorry, just a bit confused about your "idle" status and what the screenshot is telling me, and the lack of 70C temps.

    Same issue here. I have a 2GB RPi4 with official case, PSU and HDMI cable. Clean install, room temperature is 20c and the Rpi4 idles at 70c and goes up to 75c during video playback.

    While idle at the Kodi "Home" menu (presumably you are using the stock Estuary skin?), can you run the following command in ssh (make the ssh window quite wide/high - at least 186 columns, and 40+ lines):

    1. -ZCxpyd1

    Leave it running for a short while (20-30 seconds) then take a printscreen of the ssh window and upload it to (then post the link). With this we can see if something is hammering on the CPU core(s) and driving up the temperature abnormally. Thanks.

    I'm not sure about the high temperature, this is an uncased 4GB RPi4 (no heatsink) with 9.1.001 while idle at the Home menu for 7 hours:


    Have you installed any add-ons? Is this a clean installation or upgrade from RPi3 - try a "clean" /storage/.kodi without any third party add-ons and see if you still have issues (maybe an add-on has gone nuts and is spinning on the CPU).

    Does the GUI look washed out or is it just videos? Presumably the washed out videos are HDR videos? As previously stated, there is currently no HDR support until this is baked into the Linux kernel, probably 5.2 or 5.3 so I'd expect the HDR metadata to be ignored. Can you upload a small sample video (or link to a sample video) that demonstrates the problem?

    documentation/ at master · raspberrypi/documentation · GitHub

    In /flash/config.txt, add the following to enable 4Kp60 support:

    1. hdmi_enable_4k=1

    HDR metadata should be ignored for now, so if your display looks washed out try toggling Settings > System > Display > Use limited colour rage (16-235).

    I will check it when i get back to home, because I'm not sure. Anyway, it's a chance to get 4k h264 video in future?

    How about that audio? Should Dolby Atmos and DTS HD MA now work properly?


    I don't think the hardware will support 4K H264 decode. It's more likely that 4K videos will be HEVC.

    Initially DTS HD-MA should work same as RPi3B, ie. LPCM, but HBR audio support is planned for the future which is when Atmos should work too.

    Yesterday I tried to play few movies in Kodi in 4k - results are not good, stuttering, freezing etc.

    Dolby Atmos and DTS HD MA not worked only DD 5.1 (yes i had enabled passthrough and Dolby Atmos and DTS HD MA capable receiver, this option worked with my S905X).

    Were these h264 or HEVC 4K videos? 4K video playback is HEVC only.

    From the announcement post:

    * HEVC decode to [email protected] (with HDR)

    * H.264 decode to [email protected]

    If these were HEVC 4K videos, can you post the media info?

    milhouse I will wait for the USB booting then. I was wondering if I can use the following method (I guess it should be faster):

    1. Download RPi4 image and manually upgrade my RPi3 with it (update folder).
    2. After rebooting my RPi3 should show the rainbow screen (firmware not right)
    3. Activate USB boot on my RPi4 (when available)
    4. Plug in my USB HDD in the RPi4 and cross fingers

    What do you think?

    You'd need to create /storage/.update/.nocompat to allow the RPi3 to upgrade using RPi4 image/tar, but then once it has finished upgrading to the RPi4 version of LibreELEC it will fail to boot as the new RPi4-based installation (when running on your RPi4 hardware) would not be able to boot from the USB drive to which it has been installed.

    If you left the RPi4-based installation running on your RPi3 hardware it may actually boot from your USB HDD, but the "RPi4 on RPi3" user experience is not good at the moment.

    My advice would be to install the RPi4 image to a fresh SD card, boot it and restore a backup of your RPi3 installation. Once USB booting is supported by the RPi4 - instructions will be posted detailing the bootloader flashing process - you should be able to attempt upgrading your RPI3 without the SD card using the latest RPi4 image and the nocompat method above. Then replace your RPi3 with your RPi4.

    soyxan USB and network booting are not yet supported, this is on the RPi Foundation to-do list - USB booting should be along soon (few weeks) followed by network boot support. The RPi has 512KB of flash memory so the bootloader can be updated with new features and bug fixes.

    Assuming you're happy to boot from SD card it should be possible to restore a backup of your RPi3 installation to the RPi4 system.

    I installed RPI4 arm 9.1.001 on my Rasberry Pi 4 and everything is very lazy and slow. Moving between menus is not smooth and just ugly.

    After some time in Kodi appeared a thermometer in right corner, so RPI is burning.

    With Noobs is not possible install Raspbian and LibreELEC, Noobs doesn't recognize LibreELEC image.

    Tearing in the GUI is a known issue.

    It's best to run the Kodi GUI at 1080p rather than 4K as this will result in snappier performance (Settings > System > Display > Limit GUI Size > 1080p).

    RPi4 shouldn't be overheating in normal usage, you can try running to monitor temperatures.

    It's possible that NOOBS needs to update with RPi4 support (guess, as I've never used NOOBS).

    Any plans to do version for RPI4 faster and smoother? Or I'm just using wrong version?

    This version is unusable with RPI4

    Yes, this is the first release on brand new hardware, of course things will improve. As mentioned in the blog, this RPi4 release is essentially an "alpha" release. The feedback from this and subsequent releases will lead to improved RPi4 kernel and firmware support which will be a huge benefit to LibreELEC with Kodi 18 and, eventually, Kodi 19.

    To be totally honest I have found the RPi4 version of LibreELEC 9.2 to be entirely usable, and stable. I'm confident the more obvious issues will be addressed quickly.

    If Mainline support where the great bugbear that is claimed why release a Rpi4 none mainline Leia build of LE - its simply inconsistent and that tells the lie.

    Why? Because RPi4 is going to be massively popular, and we took the decision to push out a short-lived branch with experimental RPi4 support as - unlike the AML situation - there is no other *ELEC option for RPi4 users. RPi has always used modern kernels so rounding out support to include RPi4 wasn't a big deal, and not only that, this RPI4 release is an important learning curve for both us (LibreELEC) and RPi Foundation for brand new hardware.

    So just to summarise: AML users have options - they're not being hung out to dry - but RPi4 users don't have the luxury of options, hence this exceptional release. Do you not see the difference?

    BTW, the situation in LibreELEC master for RPi (including RPi4) going forward will be entirely different to the way it currently is in libreelec-9.2, particularly once we transition closer to Kodi 19 when MMAL will be dropped.

    Progress is happening, sorry it's not the way you'd like it to happen, but it's being coordinated in the best way possible between those that are involved with the code building Kodi and LibreELEC for the future. Continuing to shout from the peanut gallery isn't really contributing anything.

    Shoog we (the LibreELEC developers - you know, the ones that actually do the heavy lifting to maintain this stuff) just don't want to waste time maintaining a dead-end 3.14 kernel. There are alternative options available for those that _do_ want to continue using the 3.14 kernel with the latest hacked up versions of Kodi. For everyone else, they can continue using their current version of LibreELEC and Kodi until we have something better to offer them. Iterating on 3.14 in the short term is utterly pointless. And with 100% focus now on maineline, progress is going to happen sooner than it would have done if we still had the distraction of 3.14.

    So that's the reality, that's why we have done this - because there are other options now (nobody is forced to use LibreELEC), and 3.14 is a developmental brake that is slowing progress for everyone.

    Digital passthrough can work perfectly on 3.14

    Please stop with your obsession for 3.14. We both know it's a total patch-fest, there's no vendor support, full of never-to-be-fixed security holes, and even upstream packages which are vital to LibreELEC are starting to have problems supporting such old kernels. Ultimately there's no long term or even short term gain by continuing to maintain a kernel this old.

    3.14 has been dropped and the way forward is the mainline kernel - it's a cleaner solution and we don't have to waste time trying to keep old crap building, which is a major distraction.

    If you want to continue using builds based on 3.14 then you know what to do.