Well it appeared after an update. I'm using the nightly versions.
If the update means Kodi doesn't run there's a packaging/distro issue and it's an LE problem. If Kodi runs but the updated pre-release version of Kodi now has a specific feature regression, that's a Kodi problem, and Kodi feature problems are best reported to the Kodi developers who hang out in the Kodi forum. If it's reported here, it's unlikely anyone responsible sees it.
The correct place to report/warn/moan about a Kodi flathub issues is .. the Kodi forum. And if you expect some form of help there, you will need to provide some technical details on versions (of Ubuntu, flathub, etc.) and logs that show what the problem is, else it's just heresay and rumour and there's nothing for the Kodi mods/devs to investigate.
NB: I've edited the thread title because it was too long to read in a single breath. I'll try to remember to bin the thread in 24-48h.
If you want Android ROM firmware? - You are asking in the wrong forum.
If you want to install LibreELEC the AMLGX image has a p271 device-tree file. Read: https://wiki.libreelec.tv/hardware/amlogic for general install instructions.
I have a bizarre side effect though. if I try to use the RPi5 at all while a transfer is in progress, speed drops to zero almost immediately.
Fixing the network throughput probably shifted the bottleneck to the app writing to the SD card. You'll need to investigate with 'top' to see what's going on. There are probably caches within the LTFP server app. There are definitely caches in system memory and the filesystem. There's also invisible things internal to the SD card too. Something somewhere chokes 
It's probably a question that's best asked in the Kodi forums, as it's nothing LE specific.
What does cat .cache/timezone show?
I'd guess some LE12 version. Kodi doesn't support downgrades so download the update file to /storage/.update then rename the Kodi folder /storage/.kodi and then reboot. On restart you'll have a clean LE12 instance.
So along with the other development work for LibreELEC, an updated Realtek firmware file may need to be included.
Run "dmesg | paste" and share the URL. If there's a missing firmware it will probably be flagged?
If yes, the file can be manually added https://wiki.libreelec.tv/how-to/add-firmware (grab the file from the fedora image) and then tell us what's missing.
So would I gain anything running LibreELEC over running Kodi flatpak on Ubuntu?
Testing LE from a USB stick is free. That's the only way to tell..
It's something for the RPi developers to comment on, not the LE distro maintainers (we do not have the skillsets for that task).
Better to ask here: https://github.com/raspberrypi/linux
I have a very new AMD CPU with Radeon Graphics, so will i get full HDR or just tone mapping?
Same as Intel then. Nothing more, nothing less.
Assuming you have a recent Intel GPU with HDR support, then in current Kodi full = HDR, HDR10, and HLG. Dynamic HDR10+ is not supported but almost all media using HDR10+ has HDR10 fall-back so you still see somehing nice. DV is a mixed bag: some media has HDR10 fall-back so you'll see something fine, but other content (mostly from online streaming services) does not and then you'll see weird colours. There's some background progress on solving that with tonemapping, but these things take time. There is also limited HDR > SDR conversion through tonemapping. If you want 'full' HDR support you need to use an Android device that has full support (nVidia shield is the default recommendation).
The installer for the Generic image needs to create two partitions: one for boot files, one to be used as persistent storage, so it does not support installation into an existing partition. It only installs to the entire disk so if you have Windows and Ubuntu on the same physical disk it will nuke both. It's possible to manually remove the Windows partition and create the required two partitions in its place, copy files over to the boot partition, then create a grub2 (the Ubuntu bootloader) entry for LibreELEC, but you'll need to go figure that out on your own (there are some threads here if you Google for them). It's also possible to just boot LE from a USB key when you need it, or to install the Kodi snap in Ubuntu and use that instead.
Sorry, is this a potential fix if it gets completed?
No
The board was added after LE12 shipped so it only exists in the kernel used with LE13 nightlies. The Alpha tag represents Team Kodi dragging it's arse on the release cycle more than anything else. In reality K22 is more like a late-cycle beta than alpha and it's been like that for a year already. In short, don't sweat the label and use the nightly.
It's not an LE concept, Kodi supports this on all platforms. The final settings used are always a composite of default (which in our case are embedded in the SYSTEM file which make them read-only) + userdata (advancedsettings.xml) settings. Userdata settings only overwrite default if they exist in both places, i.e. you don't need to clone the entire default file.
Is there a post that gives the instructions on how to do this?
Probably not.
or can you please assist me in getting this sorted?
I already told you how to manually download and create the required files in the previous post. Go look at the sources folder and see how things are structured there.
--2025-03-20 21:25:12-- https://curl.haxx.se/download/curl-8.6.0.tar.xz
Resolving curl.haxx.se (curl.haxx.se)... 127.0.0.1
The build device is resolving the download location to 127.0.0.1 (localhost) instead of resolving to a CNAME which has 4x public A records (which are all available). That suggests a DNS issue at your end as the URL resolves fine from here (UAE).
--2025-03-20 21:25:13-- http://sources.libreelec.tv/mirror/curl/curl-8.6.0.tar.xz
Resolving sources.libreelec.tv (sources.libreelec.tv)... 65.109.172.87
Connecting to sources.libreelec.tv (sources.libreelec.tv)|65.109.172.87|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
It then falls back to our sources mirror, which appears to be down/offline or missing some config at the moment, so that fails too. I'll ping someone internally about that, but it might take time before it's restored.
It's possible to manually download the file to your local sources folder, but to fool the buildsystem into thinking the file has already been downloaded you'll need to manually create the .url and .sha256 hash files (the format can be cribbed from other downloads).
This hotspot would for example allow say an iPhone in that room access to the fibre network via said hotspot through to the LAN as if the phone was a wired device?
It will probably allow the phone to access the LAN (and thus the internet). I say "probably" because the only proof is trying it.
