I think this addon is kinda like an orphan child and as long as it works (mostly) I doubt the devs have the time nor inclination to dedicate their time and energy to a limited audience of users as it will only work on the x86 builds.
That's a reasonable assessment of the situation. We *would* like it to always work, but it's never the highest priority.
It appears I need builds marked as 'box'. Is my only source http://test.libreelec.tv/11.0/Amlogic/box?
Builds for 10 are not for Amlogic (http://test.libreelec.tv/10.0/Generic), so unsuitable?
Experimental LE11 test images are here: https://test.libreelec.tv/11.0/Amlogic or https://chewitt.libreelec.tv/testing/ nothing else will run on Amlogic hardware. If there is no specific device-tree for your box you will need to experiement (lots of devices are similar.. we have no idea what specs/hardware your box has). Note that the boot process is different to legacy images. There are no LE10 images (or nothing worth using). There is zero support for piracy images like AE in this forum.
The V4L2/GBM video pipeline changes don't make software grabbing as simple as it was before, so I wouldn't expect to see much movement on the add-on being updated anytime soon. If Hyperion is a must-have for you, an external/hardware grabber is the way forwards.
I've blind copied the udiskctl command from your original script. On closer inspection we don't bundle this utility in the OS; hence the failure message that you see. You'll need to sub some other method for turning disks off (or at least parking heads) - perhaps hdparm?
#!/bin/bash
for mount in $(awk '/\/dev\/sd/{print $1}' /proc/mounts); do
umount -f $mount
sleep 2
done
for disk in $(ls /dev/sd* | sed 's/[p0-9]*//g'); do
udiskctl power-off --block-device $disk
sleep 2
done^ Split into two steps
Moreover, please tell me if your le 10 AMLMX image can boot straight from usb/sdcard (all black mxq running le 9.2.8.x from emmc). I have a 30-45 minute break tomorrow and I want to test it as much as possible.
It's highly experimental and I have no time to coach users on what it might be like .. so I'd rather you ignored it.
Can you please show me the AMLGX thread?
Kodi and its scrapers are designed to work with relatively standardised naming formats and the single best way to avoid naming issues is to use the right formats when you rip original media. You can start by sharing Kodi debug logs showing a library update/scrape so we can see what might be happening.
2023-01-07 11:55:21.524 T:852 debug <general>: OnPlayBackStarted: CApplication::OnPlayBackStarted
2023-01-07 11:55:21.525 T:1231 debug <general>: Thread BackgroundLoader start, auto delete: false
2023-01-07 11:55:21.531 T:1186 debug <general>: Loading settings for /media/ExternData/HDD/Filme/0-Test/4K/Dolby Vision FEL Test Samples/FEL_test_for_AVS.mkvThere is no support for Dolby Vision at this time, and that file doesn't appear to have other (normal HDR) tracks to fall back onto.
I'm not familiar with OpenATV .. so how does it save/record media and what format/location are subs being save to (or embedded in)? - And how are you playing back the recordings? (from a shared, IPTV list, etc.)?
#!/bin/bash
for i in `ls /dev/sd*`; do
umount -f $i
sleep 2
udiskctl power-off --block-device $i
sleep 2
done^ That should unmount disks before powering down the drive. Also, you probably want to block the shutdown process while this is done so background the commands like autostart.sh
Hi i dont suppose you know of any newer more capable devices that can support 480i over component? I have tried searching but have not seen anything only devices supporting composite
Nope. I'd probably search on Amazon or eBay for some kind of component converter so you can use a modern source device.
If using personal keys they are accessible (readable, and thus copyable) by other users on the host. On a multi-user system that would be bad from a security perspective. LE only has one user (root) so it's not really the same security issue, but openvpn doesn't know that so it shows an error. The following command run over SSH probably fixes it:
chmod 600 /storage/.kodi/addons/service.vpn.manager/UserDefined/pass.txtThen reboot and check again.
History shows that these changes are rarely permanent (where there's a will, there's a way) but since fixing depends on part-time developers giving time for free, things aren't always quick, esp. in early Jan when everyone heads back to their day jobs again. Keep a watch on the Kodi add-on support thread for more info.
I bought this tuner because it was recommended to work well with LE/Kodi. Can you suggest another model or manufacturer which works well in combination with a RPi4 ? I actually just want a setup that works reliably.
I've always recommended people run the server on a separate device to the player. This allows you to keep the server end on something that works; often a conventional distro where you can (re)compile the kernel with whatever set of shitty hacked-up drivers are needed to make the tuners work reliably, and then never change it while the no-longer-dependent-on-weird-kernels player device runs whatever latest LE/Kodi release you fancy. Linux DVB drivers suck 
It looks like it got missed somewhere (we will investigate). You can always download 10.0.2 then do a manual update to 10.0.3 using the regular Generic .tar or .img.gz file (both contain KERNEL/SYSTEM which are the only things updated).
Textures13.db has become corrupted so a query to the DB fails; this is shown in the second and third errors. The DBus error is harmless.
Delete the Textures13.db file and the thumbnails folder. The DB will be recreated on Kodi restart, and thumbnails will be re-downloaded on access to GUI views that require artwork. If you don't remove the thumbs the cache references will be incorrect and you'll have blanks all over the GUI and you'll need to manually refresh everything to repopulate content.
