But i can't edit it with an editor. When i just open and save it back, the file gets bigger and booting from sdcard doesnt work anymore.
It's a compiled binary file (albeit one with lots of readable strings inside) so when you 'edit' the file you break it, and because boot depends on this file, boot from SD is broken. Like all compiled code, the source file can be edited, then it needs to be recompiled when you create the image.
sky42 maintains an LE image for x86_64 devices that includes support for encrypted drives (our default image intentionally does not support this). The drive needs to have a Linux filesystem, e.g. EXT4 and be locally mounted. You can then share the drive over SMB if desired but as it's already locally mounted there's no value (only pain) in trying to locally mount the drive a second time as a remote SMB share.
Have a read of his thread LE 12 added lvm2, luks (dm-crypt, veracrypt, bitlocker), mdraid, ext4 encryption
It looks like groundwork for USB support is here: https://patchwork.kernel.org/project/linux-…[email protected]/ and that series has been merged for Linux 6.19.y which we will bump LE13 nightlies too in the next month (once it ships) but looking at https://github.com/morrownr/rtw89 quickly I don't see obvious patches for RTW8922AU that could be simply picked on-top to add support, but if that codebase works then I'd be reasonably confident of support coming in the next couple of kernel cycles as the developers working there are quite active and constantly chipping away at upstreaming.
For the rtw88 driver we intentionally disabled the incomplete in-kernel driver in favour of using the lwfinger/rtw88 dev branches for a while, but that allowed us to drop older Realtek vendor drivers at the same time, so the additional hassle of regular bumps to keep track of development was acceptable. I'm not sure we want to repeat that for rtw89, but if you can build an LE images and look at git history to see how rtw88 was handled it shouldn't be too hard to add support.
IIRC the WeTek Play/Play2/Hub boot mode is toggled between WeOS and LibreELEC on SD card by pressing the power or pause (can't remember which) key on the remote while the WeTek splash screen shows. The boot choice is then remembered until you either remove the SD card and it will default back to WeOS/Android or you repeat the remote-key toggle. Using this original boot flow it will not auto-boot into LE simply by inserting the SD card. If you boot CE or the dtech image using the typical "toothpick" boot method the boot flow will be modified to boot on presence of SD card, but the LE 9.0 image will not do this as the autoscript files on the SD card do not have the instructions to modify the boot flow.
TL/DR; the issue was "PEBKAC" due to incorrect assumptions (based on some other distro) on how things work.
There is no underlying desktop environment in LibreELEC so if you saw a mouse cursor on-screen Kodi started. If the home screen did not then show, the kodi.log (hopefully a debug one) and/or the systemd journal might have clues. This is probably past-tense though and I've not seen anything similar; other than the Kodi database upgrade screen. NB: I'm not aware of anything in images that would result in kodi.service being disabled.
I'm not aware of any general issues with freezing/stalls on N100/N150 devices. There are less than a handful of reports with that kind of issue and most were triaged to some form of PEBKAC, or AI analysis of kernel crashes points to buggy wifi drivers (which newer kernels in nightlies might resolve) or users failed to provide meaningful information to investigate.
TL/DR; The latest nightly would always be the staff recommendation. The only known issue is a long-running one with [email protected] playback and pass-through audio on HDMI connections, but that has a known workaround (reducing display bit-depth).
If you then see issues, report them.
Test share images are updated with Linux 6.19-rc6 and a notable fix to gracefully handle uninitialised values during HEVC decoding which helps with 4K media files that spammed the system log with errors. I'm now able to play all the HEVC media in my test-file collection which includes a number of known-bad files. Playback of those sometimes takes 10-15 seconds to start, depending on the underlying kind of broken, but even those play which is great. That fix (the result of AI analysis of kernel splats) also pointed fingers to some related code that can be improved to not allow the uninitialised values in the first-place, so we should see some additional fixes on the mailing-list in the next week.
At this point the only things I feel are missing from RK3588 are HDR and hardware deinterlacing. The former will eventually happen through work Collabora are doing. Nobody is handling the latter though.
I'm back to buffer size AI guesswork and nagging Jonas to review old patches for older hardware so we can get closer to a unified kernel source for aarch64 boards.
See https://patchwork.kernel.org/project/linux-…@collabora.com/ for the main patches that added CEC support upstream, but there are follow-up fixes and everything becomes entwined in other DRM bridge work so backporting patches to an older kernel would be a painful task.
Thankfully current kernels have everything merged, so LE13 nightlies (6.18) and images in my test share (6.19) should have working HDMI-CEC support.
I installed LibreELEC on the ThinkCentre, then copied the Kodi configuration from the Pi.
For the sake of experimenting: stop Kodi, move /storage/.kodi to /storage/.kodi-old and restart Kodi. This gives you a clean Kodi install (reverting is just the reverse procedure). Configure the HDMI output and reboot a few times. Does the issue still occur?
Things work better on LE due to the OS being overall lighter and because Kodi setup with adjust-refresh and whitelists etc. requires less compute resources during playback than a desktop app under wayland that's forced to resample audio and video to run at the desktop rate of 1080@60Hz or 4K@60Hz.
The buffer size issue is the main thing to focus on for VDPU346. The VP9 patches seem to work well and I'm coaching Abhi Sarma on kernel etiquette so hopefully a v1 series can be sent for review soon.
The minor tearing/glitches that can be seen when the Kodi OSD is active are the result of refactoring in the ffmpeg patches (dealing with ffmpeg developer feedback/requirements) and additional work in Kodi is needed to get back to the previous state where there were no artefacts. More patch series need to be merged down, then some effort can go into investigating that.
Did you backup the RPi4 and restore to the ThinkCentre? or make a clean install on the ThinkCentre?
I've read the feedback. I'm still experimenting with AI tools to see if they can bridge the gap in my rather lightweight coding skills or we have to resort to nagging Collabora folks to take over (or cap the current driver at 1080p to get an initial merge).
HDR works, 8-bit only? (HDR is better when 10-bit but it's not mandatory) as RK3566/68 use the older Rockchip HDMI IP which has more colour support upstream. The newer one used with RK3588 etc. is still missing some infoframe handling IIRC.
btw, Jonas believes https://github.com/torvalds/linux…2fdfc001d044bee might have resolved the "wiotlb buffer is full" IOMMU issue that requires RAM to be capped under 4GB. I'm going to remove the cap on my boards and see if I still get a load of weird errors. Please do the same on your LE images.
docker run --rm --log-driver none -v `pwd`:/build -w /build -it libreelec make image^ from documentation, no script required. User claims Docker proficiency so you have to draw the line somewhere 
Read: https://kodi.wiki/view/Internet_video_and_audio_streams
Create .strm files for each Soundcloud URL that you want to use as media. Kodi treats these like a media file with no metadata.
Create .nfo files for each .strm file. This is required. It also provides a way to add metadata, e.g. pretty names, if wanted.
Scrape the .nfo files to the Library.
Add Library items to a playlist.
Do something with the playlist, like script it being started 20 seconds after Kodi starts (how you do that is .. Google'able).
Plan B .. get a Raspberry Pi and use one of the many good niche distros or RPiOS installable apps/containers designed for "signage" use-cases, as that appears to be the end goal and something Kodi is not really designed for.
axel I've spoken to Radxa about the AIC8800 wireless chip a couple of months ago as it's also fitted to one the boards I've been using to test. Radxa have no plans to upstream the driver as this would require a large effort, i.e. complete rewrite as the current quality of driver code would never be accepted into the kernel, and after years of working to rid our codebase of the maintenance burden of downstream (mostly Realtek) drivers we have no desire to add technical dept in the form of another vendor driver that has no plan to be upstreamed. I've shared our surprise/annoyance and position, and have strongly suggested they stick to using Broadcom, Qualcomm, Realtek (now upstream) chips in future iterations of current boards and future board designs so distros can avoid the need for crap drivers. I'm not sure LibreELEC's opinion will carry much commercial weight with them, but from our side, there's no action to be taken.
If you are proficient in Docker then it should be trivial for you to use the Docker files in tools/Docker that result in a pre-configured and working build environment for creating an LE image. Once you have a working LE image, add a package for the xone driver and build it into the image and push the changes to GitHub/Gitlab etc. so others can see the package.mk recipe.
It is not impossible to build a driver add-on, but the general challenge is that kernel modules must have the same 'version magic' as the running kernel, and in LE the add-on repo version is loosely aligned to Kodi API version and not kernel version. This means for each add-on repo version users will have a range of different kernel versions in use. The kernel's media-tree used to support 'media build' which provides a method for compiling and running 'DVB' kernel modules from an older codebase to run on a newer kernel version. LE has previously used this to package a bunch of DVB drivers for e.g. TBS cards as an add-on. We have since stopped doing this because it's a pain in the rear to maintain, but the prior art still exists in the buildsystem and you could use the same approach to create an add-on for the Xone driver.
Zero 3W, and it booted fine however, no wifi card appears to be detected, nor bluetooth
I can see that device-tree defines the module, but I can't see anything in documentation that states which Broadcom chipset is being used. It's probably something new(er) that we don't have firmware for, but as you didn't share the system log .. that's only a blind guess and could be wrong. In short .. no idea
axel I forget exactly what the issue is, but IOMMU errors are seen with RAM sizes over 4GB so LE currently and intentionally sets mem=3838M in kernel boot params to sidestep the problem. You are free to remove that param and see the full 8GB, but expect other issues. NB: LE runs in under 1GB so it has zero functional impact on Kodi use.
