Posts by chewitt

    I've never understood how/when passwords.xml gets used .. I've always defined sources in sources.xml which has a similar format, see above. I'm not sure that's even remotely a solution to the problem. For kicks, use CAPITALS for server names and paths.

    I'd guess that you've install a bad/broken add-no and this is causing Kodi to crash repeatedly which triggers safe mode. Debug logs will show what the problem is, but if you've been installing pirate crapwhere (which is a frequent cause of such issues) please save yourself the effort as we'll auto-refuse support. NB: Disabling safe mode will probably give you a system that you can't get into due to crashes/restarts .. so not the best advise.

    I'll summarise that i've never even heard of it and i'm as close as the project curently gets to a Samsung maintainer (the Exynos image for XU4 devices which is broken for 4+ months due to my work/life busy and deliberate neglect). So there is no LE image for this board and I doubt you can create one since mainline Linux kernel support for Samsung hardware isn't so great (boot = maybe, hardware video decoding in Kodi = forget it). Stick to RPI :)

    thank you for your reply, your announcement was giving me hope that my box wouldn't be redundant. Although I can carry on using Kodi 18 for a while I will have to have a look for an alternative

    The "box" image should still boot a hub (using vendor u-boot on emmc) if you want to experiment with a spare SD card, but I can't claim to have tested with 1GB devices recently and as noted there are some challenges with hardware decoding. Using WP2 for a bit recently it's annoyingly close to being quite good, but also far-enough away that the initial euphoria of booting a modern kernel etc. wears off.

    RPi4 is my recommendation for replacements. There are technically better spec'd things but the software support on Pi hardware (as in, the level of people and engagement in supporting the software) is in a different league to everything else.

    LibreELEC-AMLGX.arm-10.0-nightly-*-*-odroid-c2.img.gz files contain mainline u-boot and are designed for writing to SD card or eMMC module. You cannot update older installs as we move to extlinux style boot which has different files in the first/boot partition. Clean install is required.

    NB: The image in Index of /testing/ has better playback performance than current nightlies due to some experimental ffmpeg changes and other bits. Don't pay any attention to version numbers of files in that folder, only dates count.

    Hello there,

    Thank you for the information and the hard work provided by the libreELEC team!

    May I just confirmed that my understanding of the announcement is correct, LE v10 which will run Kodi 19 - Matrix will be available for Wetek Hub (Soc S905-H revision C) done the line?

    Also, following the announcement from coreELEC to stop supporting amlogic S905 & S912 due to their kernel not being maintained by amlogic any longer. Is there plan to stop supporting those SOC in the near future?

    The statement makes it very clear (or so I thought) that there will be no LE10 release for Amlogic devices. Nightlies exist but mainline kernel support for Amlogic chips is not where it needs to be; there are challenges with hardware coding. I've been poking mainline u-boot support for the older WeTek devices and now have Play2 working well (within the caveats on hardware decoding) but I've been unable to get the Hub to boot so haven't done any work on it in some time - I need to dig up the vendor files and test the hardware with those again. If the status of decoding improves we can release something in the future. S912 is easier since it has more CPU grunt and you can disable problem hardware decoderss and use software decding on 1080p content (forget 4K). Same for newer chipsets with have even more CPU power. There is currently nobody working on the hardware decoding as I don't write code and nobody is funding commercial development. So not likely to see progress anytime soon, but we'll get there at some point. The images in my team share Index of /testing/ are a little more usable then current nightlies due to experimental ffmpeg work. Note - the "box" image is the one to use with any device that uses vendor u-boot.

    The Samba change on 26/1 is where fingers naturally point, but I use SMB(2/3) from an assortment of devices in the same share configuration that has not been touched in several years (Synology NAS with SMB shares and SQL) so it's something nuanced and not a general SMB problem.

    Start by describing the sharing environment with SW versions, and if Windows is the server target, state the credential types being used.

    Regarding Tiger Lake, then how is the Intel NUC supported ny Libreelec -->

    Intel NUC11TNKi3 Tiger Canyon - Core i3-1115G4 - Barebone | Billig

    Intel NUC11TNKi5 Tiger Canyon - Core i5-1135G7 - Barebone | Billig

    And if they both are fully supported and good for LibreElec, then what is best for 4K. The I3 or I5 ??

    I am not a big fan on the PI hardware for mediacenter....

    I have no opinion on which one as it's several years since I used Intel hardware. I'm basing the recommendation on the hardware I see being actively used and developed on by the Intel graphics devs who have access to the Kodi team chat. They also still work on Gemini Lake.

    I'm not a fan of older Pi hardware as compared to a previous Intel board (Xtreamer Ultra 2) and Amlogic hardware it always felt underpowered. I have no real complaints with RPi4 though.

    I asked about that in a other post and was told that it was not supported by LibreElec at all but Kodi Android would support it.

    My plan was to get a nVidia Shield Pro but if not supported by LibreElec then that's no godd. :(

    nVidia Shield / Shield Pro is the Team Kodi reference device for Android so in the past we've never bothered to investigate support, and in the future it becomes technically impossible (or complicated beyond the point where it's worthwhile) because the nVidia video driver stack isn't compatible with the GBM/V4L2 direction Kodi is taking for Linux. Android is not without occasional faults in Kodi, but the main issues are vendors not following Google API standards. The shield seems to have fewer quirks and is better maintained (has updates) compared to other devices.

    RPi4 .. because while there are many technically superior hardware devices and RPi hardware always has compromises, the level of software support we get from the Pi Foundation developers is second to none; and they care deeply that Kodi runs well on their boards. There are still some feature gaps to plug, but now initial support for HBR audio and HDR are done the number is shrinking quickly and an RPi4 is a solid daily-driver. Or an Intel Tiger-Lake device, as that platform has massive commercial backing and is effectively the reference design for non-ARM things.