This is the CPU opp-table: https://github.com/torvalds/linux…3399-t-opp.dtsi
It looks like support for the 4SE board has been submitted and merged upstream: https://patchwork.kernel.org/project/linux-…@collabora.com/ .. although I don't see that in torvalds/master (will become Linux 6.6) yet, bu you should be able to pick/backport those patches onto the Linux 6.5 kernel we use in LE master easily.
I moved all my devices to LE12 for testing so can't test LE11, but in LE12: Settings > Display > Calibration > Video Calibration exists. You may need to have the GUI in advanced or expert mode to see the option.
Kodi is not a heavy-CPU application unless you're software decoding lots of media, but using the non-T device-tree means you are over-clocking the board, so you need to ensure it's properly cooled via fan or case.
Kodi feature requests should be made to Kodi developers via the Kodi forums: https://forum.kodi.tv/forumdisplay.php?fid=9
Kodi feature requests should be made here: https://forum.kodi.tv/forumdisplay.php?fid=9
I suggest reading the link I already posted.
It's a while since I played with an RPi3 but something around 10s is normal for most of ARM boards we support.
You figured out that you need to replace <service> with the actual service name, right?
Put the passphrase in a temporary text file, copy it, then paste it when prompted by connmanctl for the passphrase.
I'd advise against trying to run the Kodi GUI at 4K, Please have a read: https://wiki.libreelec.tv/configuration/4k-hdr
resize2fs /dev/sda3Partitions and Filesystems are separate things and I'd guess you've resized the partition to 100% but not the filesystem within it. The ^ above command should fix that.
The screenshot shows the T version to be slower than earlier versions; which means it will need a dedicated device-tree file that as a minimum defines the correct CPU opp-points and voltages to be used. If the T version is just a way to recycle low-yield chip that don't clock high enough to be sold as regular non-T chips that'll be the sole difference, although the voltages needed for stable ops might be difference from the regular chips. If it's a deliberate "low power" variant there are likely other minor silicon differences that need to be accounted for. Radxa probably have RK vendor kernels with device-trees that contain that information. I'd argue it's also their responsibility to submit support for the board to the upstream kernel. You might want to have a dig around in the Armbian forum to see if there's any prior-art there as Radxa often target Armbian support for their boards.
If the SMB share is active you can use the Kodi file manager to copy the TVH add-on config folder to a location accessible via the SMB share to back-up the data. Then you can nuke the setup and restore the TVH files (using SSH) later.
CTRL+ALT+F3 will not work as we're not using Xorg/X11.
If this is a WP2 box not a WP(1) as previously stated, which LE release is installed?
Also see if you can restore this asoud.state config with alsactl .. rename without the .txt extension (needed else the forum complains of an invalid filetype). I found the contents in the Ardour forum. I am a long way from being a Linux audio expert, but I believe the root issue is that this is not a simple USB audio device and it needs a proper alsa conf to define its inputs/outputs. NB: Kodi only detects audio hardware at startup so if restoring the state file does something you will need to restart Kodi (systemctl restart kodi) for it to see changes.
Can you share the output of "amixer controls | paste" and "amixer contents | paste" ? .. You might need to --help and tweak the commands so they show the output against the USB device instead of the host system audio device.
LE is intentionally appliance-like and not really designed for pre-configuration of services. ConnMan manages the content of the settings file for any specific ethernet/wifi service. This means if you edit the file while ConnMan is running it has no knowledge of your change and it will probably be overwritten when ConnMan updates something (can happen during normal operations or shutdown). The two supported ways for changing connection info are the settings add-on or connmanctl. If you want to do other things and it 'seems' to work, that's fine. But if/when 'seems' is proven wrong .. it's not something we support.
I'm not aware of any upper limits on SD card size for pi boot (might be worth Googling to check) but whatever size is used will be formatted EXT4 and used for /storage so if that's easiest for you it should be fine. I personally avoid buying more expensive larger capacity cards since SD media does die eventually (another reasons for preferring NAS devices) .. but original and better quality cards should last a decent amount of time.
Do you have access to the /storage/.config folder? .. If yes, you could create an autostart.sh script file that runs commands at the start of userspace boot to set/change permissions on the folders.