I am seeing temps of 140-150F in system info of Kodi. That seems way too high.
150ºF = 65ºC, which is getting warm, but comfortably within the operating range for an RPi board. These things are designed to be stuffed in a case that's suffocating in dust running some industrial use-case. You can run them considerably hotter than yours. As long as the CPU is not being thermally throttled, all is fine.
I have no idea what is different/special about a C300 pro and you're not sharing boot logs or anything that would be useful, so nothing that I can do.
This image contains ffmpeg 6.1.1: https://chewitt.libreelec.tv/testing/LibreE…h64-12.80.0.tar
No idea if that fixes or adds problems. Have a play..
I'm closing this thread as the LE12 development period has come to a close with LE12 release.
LE13 continues here: Official LE13 Test Images for Amlogic (Kodi-22)
This thread is for discussion of AMLGX (aarch64) development images for LE13 with Kodi 22 (P). There are no real-world "Amlogic" enhancements in LE13 since previous LE11/12 images so previous disclaimers on what does and does not work still apply. Please do not post "bug reports" on hardware decoders; they are experimental and incomplete code, there are known issues with them, and you should expect to find those issues. As a general rule there is a low pace of development and you should have similarly low expectations of fixes.
These are official nightlies: https://test.libreelec.tv/13.0/Amlogic/
These are my own builds: https://chewitt.libreelec.tv/testing/ <= You will receive zero support on these images. They are experimental. The version number of these never changes but the dates tell you when it was created, and that corresponds to development here: https://github.com/chewitt/LibreELEC.tv/commits/amlogic
Enjoy 
Not possible. The tethering functionality is intentionally simple and originally created for a mobile phone hotspot feature so on/off and the ability to change the SSID/passphrase are the only options.
The "direct update from LE9 is not supported" line is all about dissuading average users with low(er) skill levels because when add-ons go crashy and prevent the GUI from coming up those average users with zero CLI skills panic and generate a large amount of forum traffic. However if you understand your way around Kodi and the LE filesystem it's a fairly trivial update. The core OS updates from LE9 to anything newer with no issues since everything is packaged into KERNEL/SYSTEM. Add-ons are where all the problems occur; due to the Python2 > Python3 change that took place between LE9 and LE10 and then the multi-year version jump. However, after downloading the update .tar to /storage/.update all you need to do is stop Kodi and "rm -rf /storage/.kodi/addons/*" to ensure nothing to do with old add-ons remains except for settings in /storage/.kodi/userdata/addon_data, then let the update run, and reinstall add-ons from the respective repos once on LE12. Total time elapsed should be 5-10 mins at most.
I wouldn't expect any issues with a mix of RPi4/5 boards.
I've put the file on the sources.libreelec.tv server .. try again and it should be found now
I'm not 100% sure whether the newer display hardware in RPi4 boards supports 3D either. I do know 100% that the original (dated) RPi4 boot firmware in the LE 9.2.8 image will not boot newer iterations of RPi4 hardware, although that's fixable if you manually update the firmware files in the root folder of the SD card to current ones.
NB: I have no interest in the Amlogic 4.9 kernel and have no patches of any kind for it, so you're on your own with that quest. I'll give you the heads up that once you start changing Amlogic BSP kernel versions you will need to re-hack Kodi and pile of other dependencies to align with the new kernel. In short, any assumptions you are making on interchangability are most defiinitely wrong, and a world of version and dependency pain awaits you. Good luck, and please don't post here looking for guidance on that direction.
RPi3B+ on LE9.2.8 is the best (and final) RPi to support 3D things. RPi switched to the GBM display pipeline from LE10 onwards and the RPi4/5 have never supported 3D matters. It remains something that could technically be added and it's the RPi devs long list of rainy-day tasks, but I have low expectations it'll ever show. NB: I believe OSMC still support it with their devices, so that could be an option too. Best to check first by asking in their forum though.
I'm fine without a pile of stats being posted. Everyone has slightly different use-cases and test results are thus not universal truths to be followed. And in forums such discussions always end up with someone trying to prove something is/isn't better/worse/faster/slower than something else. I choose ignorance and less forum drama. If people want to run an RPi5 on an NVME drive .. go nuts. If people are happy running on an SD card .. go nuts. Go forth and watch movies.
Feel free to send a tested pull request to bump the versions. I place strong emphasis on the word 'tested' ..
LibreELEC (chewitt): 12.80.0 (RPi5.aarch64)
RPi5:~ # ls -l /
total 17
lrwxrwxrwx 1 root root 8 May 9 07:40 bin -> /usr/bin
drwxr-xr-x 17 root root 4240 May 16 15:26 dev
drwxrwxr-x 22 root root 1004 May 9 07:40 etc
drwxr-xr-x 5 root root 16384 Jan 1 1970 flash
lrwxrwxrwx 1 root root 8 May 9 07:40 lib -> /usr/lib
lrwxrwxrwx 1 root root 10 May 9 07:40 media -> /var/media
dr-xr-xr-x 218 root root 0 May 15 21:58 proc
drwxr-xr-x 21 root root 600 May 15 21:58 run
lrwxrwxrwx 1 root root 9 May 9 07:40 sbin -> /usr/sbin
drwxr-xr-x 21 root root 1024 May 6 21:24 storage
dr-xr-xr-x 12 root root 0 May 15 21:58 sys
drwxrwxrwt 9 root root 180 May 15 21:59 tmp
drwxrwxr-x 10 root root 153 May 6 07:15 usr
drwxr-xr-x 9 root root 220 May 15 21:58 varThe error is self-explanatory ^ the /opt directory does not exist in LibreELEC and you cannot add it, so you need to modify the script to use some location on the persistent /storage area.
RPi5:~ # cat /etc/resolv.conf
# Generated by Connection Manager
nameserver 172.16.20.1
nameserver 8.8.8.8
nameserver 1.1.1.1resolv.conf not resolve.conf ^
mount -o remount,rw /flash
nano /flash/config.txtI have no issues with 1080p H264 and sync on an RPi5 (self-built nightlies) so I would make a random guess that you aren't using adjust-refresh and no mode whitelist is defined.
If there is no uEnv.ini file in the root of the SD card you are not using the AMLGX "box" image.