I can do that if given directions..
You will fail in the task because the drivers for Silicon Village WiFi chipsets are designed for (at best) Linux 4.9 era Android kernels and will not compile against the modern-era kernels that LE10/11 use. The changes needed are not cosmetic nip/tuck .. it's more like a lung replacement (lots of crypto differences).
Seeking works well for H264 but other codecs need further development. LibreComputer are likely to sponsor some development work to improve things, but there's no specific schedule at the moment. Until then, things are what they are.
Windows 
I'd suggest using WinSCP to transfer files over SFTP (SSH) rather than SMB. It's marginally slower but for 5MB file who cares. If you get weird errors from that process there's probably something funky with the disk/filesystem and-or how it's mounted to investigate.
FWIW .. I don't see any issues with ordering changing with favourites (we use quite a few at home) .. the possible difference is that I use a shared SQL database on the back-end, so they are stored there not on local disk.
Best to file the bug with Kodi forums or GitHub with screenshots showing the issue
Note that if you enable SMB1 to SMB3 .. Samba will probably use SMB2 (default) not SMB3. I'm not sure that matters much - If it works, no need to fix things 
LE's implementation was done by me to suit my use-case, which is remote access to home from whatever hotel I'm working from this week with all traffic tunnelled. If people have other use-cases; pull requests on GitHub that improve functionality without complex or onerous configuration are welcomed. Note that few people on staff use WireGuard and I have very little time for anything at the moment; so don't expect a particularly quick merge on the submission.
I'm personally liking Tailscale these days, as the setup is super-trivial (when there's a GUI) but packaging it into an add-on requires more time/effort than I currently have. I'd pay a bounty for someone to add it with a simple GUI to handle initial setup.
You can use the "disable SSH password authentication" option in the LE settings add-on, which has existed since ~2013.
Crash report available at /storage/.kodi/temp/kodi_crashlog_20220906055000.log^ that's the only useful log that you can share.
There's probably different levels of sophistication you can do, but as a minimum you can share content from the 'server' box over SMB to the client device. Connect both to the same Gigabit Ethernet switch and Cat5 of better cables and playback (not streaming) over the LAN should be a breeze. If you will still watch content on the server box; install an SQL database (use Docker) and migrate the Library data there so you can maintain the watched/unwatched status between boxes. If you like pain, connect the client device over WiFi
dd if=/path/to/LE/image.img of=/dev/diskX .. where diskX is the SD card device.
You can try this too https://www.dropbox.com/s/s4fj9ebj8278….macOS.dmg?dl=0 .. but I think it only works for me because I have the code signing certs installed on my laptop.
RPi4 2GB and up .. because it's a simple playback device and the Foundation provides the best vendor support of all hardware we run on.
Is the ! character the first character in the passphrase, or somewhere later?
Any ideas?
You either need to implement support for /storage/.config/xorg.conf.d/ mapping to /usr/share/X11/xorg.conf.d .. or (easier) patch the files that we get from xf86-input-libinput package with a custom image or (easiest) overwrite them with a file in projects/Generic/filesystem/use/share/X11/xorg.conf.d with whatever you like. All of the above require a custom image.
Just wondering if you're trying to use a passphrase that's too long.
Add-ons > Add-on Browser > My Add-ons > Information Providers > (pick category) > (disable everything apart from local info)
Rinse/repeat for other data types as needed.
Even if the GUI does not come up, the rest of the OS is probably running fine. Cold boot the box, then SSH in and run "journalctl | paste" and share the URL so we can see what is detected and what boot errors might be present in the system log/journal.
LE10/11 have deinterlacing support, but using all-new driver code (the entire video pipeline is different) so it's completely possible to have different results. Can you create some sample files to share so we developers can have a look?
Ping popcornmix ^
