Then it's a skin issue and should be reported to the skin authors via the skin support threads in Kodi forums.
Posts by chewitt
-
-
Code
- Do not post or promote external URL links to products, a name description is enough - Companies who create "advertorial" postings for their products in our forum are not welcomeMediPi Your enthusiam for the Radxa X4 is noted. However this forum isn't interested in hosting full-page adverts for products and this has already been pointed out when I've deleted the advertorial content in two posts to this thread. If you want to ask in the N100 thread if anyone has an opinion on the device, you are welcome to do so. However if asking involves you posting another full page advert for the product at the same time the post is going to be deleted (again). And if I need to delete a fourth post I'm going to assume you are working for Radxa to promote the product and your account will be banned (final warning). NB: We are happy to have Radxa staff active in our forum; as long as the accounts are tagged (and they stick to support not promotion).
-
It would be helpful to see a full Kodi debug log that demonstrates the issue and how the source is configured in sources.xml. Note that Windows requires you to use username/password authentication (anonymous shares no longer exist). This means even if you configure a share as open and accessible to anyone, the connecting client still needs to present itself as 'someone' else you are 'no one' and access is denied.
-
If the intention is to boot/run from a USB drive (not an internal drive)? - Write the LE image to the 2TB USB drive then boot from the drive but interrupt boot at the syslinux prompt and type 'run' to boot from the USB drive instead of booting into the installer which is used to install to another drive target. I can't explain why the normal installer approach isn't working (there are no errors in the log file you shared) but if the device is booting to the installer from a USB device, see if that continues?
-
Random guess: Is your router acting as an NTP source (some do) and is its clock correct?
The LE settings add-on will allow you to configure NTP servers, so perhaps force {0,1,2}.pool.ntp.org and see what happens. They are the default ones we use anyway, unless something like DHCP configures an alternate (like when the router sets itself as one).
-
I'm not sure RK3399 supports 10-bit output at the current time, so you'll have 8-bit output which results in banding.
There are improvements being submitted to the kernel, but these things take time.
-
Switch back to Estuary and check whether it works there? If it does, the issue is with the skin and you need to report it to the skin author via Kodi forums. If it's broken in Estuary too, then it's either something in Kodi or LE. Please check.
-
I started working on "nvmetool" based on the existing "emmctool" script in Amlogic images:
https://paste.libreelec.tv/credible-osprey.sh
The basic workflow is to download an LE .img.gz file to /storage and then run "nvmetool w <filename>.img.gz" to write it to the nvme drive, expand storage to 100% size, then relabel the partitions so they don't clash with an SD card. The last step (not implemented in the script) is to set the eeprom for nvme boot.
NB: It's not particularly tested.. I ended up using the nvme drive instead of developing and testing it properly

-
The obvious alternative is RPi5, which is technically inferior to half the devices out there, but "just works" reliably with no fuss and does all the things I need it to do. Different users have different needs for "Just running LE" though, so what works great for me might be a heretical suggestion to others.
How does it compare? .. fcuk knows. I only learned of the Radxa X4's existence an hour ago, and I generally avoid offering opinions on things that I haven't used.
-
Posts edited to remove all the advertorial content. The second post was completely unnecessary so deleted.
In terms of thoughts, it looks interesting: decent overall specs although most users will want emmc flash onboard which is promised but not shipping yet. There is one outstanding DRM bug affecting N100 devices that Intel devs are being rather slow at, but overall it should require nothing to be supported with LE.
-
The 1080p limitation applies to devices newer than S912, but 4K HEVC and VP9 media should work (with some caveats). No idea what the issue with WiFi is .. run "journalctl | paste" after boot and share the URL.
-
The video=Composite approach is correct if the kernel drivers support composite output. If it doesn't work, I'd assume composite support hasn't been implemented. These days HDMI is generally the priority so composite isn't always guaranteed.
-
Da Flex all of those 'errors' are normal and harmless on Amlogic hardware. The bootloader being un-aligned is just a quirk of the platform. Amlogic hardware has no separate power regulators on the Mali chip (as the SoC was designed not to require them) so the kernel (correctly) reports they are not found on every Amlogic board. Broadcom WiFi clm_blob files are board-specific tuning files and the only boards in LE's entire line-up that have them are RPi boards, so all other ARM SoC devices with Broadcom WiFi chips (Amlogic, Allwinner, Rockchip, etc.) also fail to load them and report that error.
mr-bledi The one issue that I can see in logs is this:
Code2024-07-19 10:13:58.522 T:904 info <general>: [WHITELIST] Searching the whitelist for: width: 1920, height: 1080, fps: 59.940, 3D: false 2024-07-19 10:13:58.523 T:904 info <general>: Display resolution ADJUST : 3840x2160 @ 60.000000 Hz (16) (weight: 0.000) 2024-07-19 10:13:58.534 T:904 info <general>: CDVDVideoCodecDRMPRIME::Open - using decoder V4L2 mem2mem VP9 decoder wrapperThe log is not a debug log (so missing a load of useful info) .. but that shows 1080p 59.94 VP9 media being upscaled to 4K@60 which Kodi will struggle with on an ARM SoC device. Kodi needs to scale the media 4x and also handle the mismatched refresh rate.
However that shows an underlying issue with fractional rates (they are all missing):
Code
Display Moreinfo <general>: Found resolution 1920x1080 with 3840x2160 @ 60.000000 Hz info <general>: Found resolution 1920x1080 with 3840x2160 @ 50.000000 Hz info <general>: Found resolution 1920x1080 with 3840x2160 @ 30.000000 Hz info <general>: Found resolution 1920x1080 with 3840x2160 @ 25.000000 Hz info <general>: Found resolution 1920x1080 with 3840x2160 @ 24.000000 Hz info <general>: Found resolution 1920x1080 with 1920x1080 @ 60.000000 Hz info <general>: Found resolution 1920x1080 with 1920x1080i @ 60.000000 Hz info <general>: Found resolution 1920x1080 with 1920x1080 @ 50.000000 Hz info <general>: Found resolution 1920x1080 with 1920x1080i @ 50.000000 Hz info <general>: Found resolution 1920x1080 with 1920x1080 @ 30.000000 Hz info <general>: Found resolution 1920x1080 with 1920x1080 @ 25.000000 Hz info <general>: Found resolution 1920x1080 with 1920x1080 @ 24.000000 HzI've previously created https://patchwork.freedesktop.org/patch/573860/ which is now merged in the kernel. However including that patch now seems to cause fractional rates to go missing - If I revert that kernel change 23.976, 29.97, 59.94 rates are restored to the list of detected resolutions. However that won't help with playback, because then the original problem with 59.94 rates reported in the patch will resurrect itself. I'd guess that something else changed in the kernel, but right now I don't see anything obvious, and I don't have free time to bisect and find the breaking change at the moment.
-
-
One of the few SMB client changes in LE12 (in Kodi 21) is SMB chunk size. This is now configurable in Settings > Services. Perhaps have a fiddle with those settings to see if they improve (or worsen) the issue?
-
Can the problem occure when some special x264 settings are used?
Well, yes it's entirely possible to encode things with settings that result in problematic media files, but more likely it's about refresh rates and the lack of modes on the TV. Connect the playback device to another TV with those modes and .. be amazed that problems magically vanish.
-
I recently swapped an RPi5 from SD card to an NVME drive to see what the fuss was about (as I had a spare drive, and there are lots of cheap HATs). It boots a little faster, and it scrolls in large menus a little faster due to the better small file I/O performance, but I'd put heavy emphasis on "little" faster. It is a marginal gain and not some huge leap forwards. TLDR: Yes it's better. No you're not missing out if you stick with an SD card.
NB: LE is rather lacking in proper NAS features, so as long as you regard it as "something that shares files" and not "something that protects your data" (esp. if running from an SD card) .. you won't be disappointed.
-
I've submitted this to merge support for LE13: https://github.com/LibreELEC/LibreELEC.tv/pull/9101
It can probably be backported to LE12 too .. but I'm being lazy this morning.