When you start up kodi you get a popup in the top right
Okay, now it's clear to me what you were talking about earlier, this is originally a patch from OSMC.
So far, no one has asked it, and I haven't dealt with it in particular, because I wasn't bothered by that popup message, but I added the patch at your request.
The build is in progress, I will post the download link when it is done.
The answer came sooner than I thought:
In newer Kodi versions, they have been replaced with the following, which no longer has a backport for Leia:
metadata.tvdb.com -> metadata.tvdb.com.python
metadata.themoviedb.org -> metadata.themoviedb.org.python
metadata.tvshows.themoviedb.org -> metadata.tvshows.themoviedb.org.python
Sorry for the late answer...
When scanning TV Shows it scans the folder's and adds the images for the folders but never scans the files in the folders
when you go into the addons there is a typo on the TV Shows addon which is suspect is what's causing the problem
i think maybe people who have updated to this build instead of going straight to this build may not get this problem
See image atached
I have installed metadata.tvdb.com-3.3.0 and that is working fine (What i used on Kazaq 8.2.2.3)
This is not a LibreELEC specific issue, but there might be some confusion in the Kodi repo, I will try to find it and report it on GitHub to the Kodi devs.
Until then, you can access the latest version for Leia here: https://mirrors.kodi.tv/addons/leia/metadata.tvdb.com/
I dont know if you do requests but if you do can i request that the cec popup's are suppressed unless its an error
Whilst looking how i can disable it on every boot i ran into coreelec added a patch to suppress them unless there's an error so you could most prob see what they did
I would need a little more detailed information than that, because I don't know exactly what you mean by that.
I have some dvb-t2 android box, see post (unknown s905d dvb-t box), and tried your ROM, but did not work. It wrote DDR init failed...
Any kind of ROMs should not be installed on a box that is not properly identified. Moreover, this is particularly true for boxes with tuners. If you have several pieces of this box, it would be best to make a flashdump from one of the working pieces.
In PRi4, there is no hardware decoding option for AV1 codec, so I am not surprised that these videos are stuttering.
Thank you for your description. However, a small improvement was made in the last version. In the second half of November, I published v9.2.8.12, which includes a new Generic_S805 image.
Although this may cause problems for some older bootloaders, that's why I also published the classic HD18Q and m201d images.
If you are trying the Generic_S805 image and the bootloader of your box supports multi-dtb loading, you do not need to choose which box is yours, the bootloader will do it instead of you. In addition, the configuration of both remote controls can be found in this image.
So, for a new installation, I recommend that trying the Generic_S805 image as the first attempt.
I have another question: I have a S912 box (Generic H96Pro 2GB/16GB) that has a problem with the shutdown process: Basically it doesn't work as the machine simply restarts instead of powering off. In Android there's no such problem.
As I have seen in the first round, this is a common problem with this box:
Of course, I didn't look into it enough, I didn't really have much time for anything yet...
Is there really no hope for the newer dav1d on this legacy build?
I'm not saying it's impossible, it's just extremely time-consuming, and unfortunately I don't have enough of it right now.
In addition, there is also the pitfall that it turns out in the process that it is not feasible. (Just like the HDR with VP9 under 3.14 kernel.)
I want run LE without any HDMI.
But when cat /sys/class/amhdmitx/amhdmitx0/disp_cap > /storage/.kodi/userdata/disp_cap
If the HDMI is not plugged in, the source is also empty, so you will create an empty file without any contained resolution.
Instead of this method, try to add a resolution statically, like this:
echo 1080p60hz > /storage/.kodi/userdata/disp_cap
It is also more than enough for simple VNC remote connection. 
Unfortunately, I can't help you with other distros, try their own forum.
This is the dtd patch in my release (v9.2.8.12) for the 3.10 kernel:
But it wasn't so hidden that it couldn't be found. 
What is the purpose of searching for this dtd/dts? And which LE version are you trying?
Can I use LibreELEC-Generic_S805.arm-9.2.8.12.tar for update, or better use LibreELEC-HD18Q.arm-9.2.8.12.tar?
Yes, it can be used as an update from HD18Q, although you won't notice any added extras.
This image is especially beneficial for a new installation because it is created by merging the separate HQ18Q and m201d images.
I originally planned to replace these two images above with the Genecic_S805 image, but it turns out that some bootloaders don't handle multi-dtbs. But, in the case of your box, there is no such problem.
Its kodi leia or up and python 3 ?
This version is still based on Kodi Leia v18.9, with Python 2 support only.
Display Morehi f all
i newbis with bad english
just small question
my device mecool kiii pro s912/3/16
can i use it with tuner dvb just for free channel
thx
Of course, the built-in tuner works perfectly with my LTS version. I have an exact same box.
Statements like this make me regret trying le 11 even more
How did you manage to install LE11+ without this button?
And the reset button was supposed to solve all that compatibility mess.
If you press the button for a long time (10+ seconds), does Android recovery load? (This can take up to half a minute afterwards.)
What else can I do?
The aml_autoscript of LE 9.2 and the new LE11+ image are not compatible with each other. If that button really works, it should be able to load the current autoscript from the sdcard when it is pressed.
So, if this is not the case, then even though the button was eventually soldered in, maybe also missing a single bias resistor that needs to be connected in series with the button. (But this is just a guess.)
Don't be angry) did you know that because of this the console goes into reboot? let it lose connection, but rebooting is not a logical behavior for a TV set-top box when there is no connection
I'm not angry, I just sometimes feel that the time I spent on description is a waste of time.
Unfortunately, I can't/wouldn't like to touch the kernel driver for these reasons:
The reason for the restarts may even indicate a hardware error. Unfortunately, even the logs do not help to find this out.
My general recommendation is to use an Ethernet connection, but if that is not possible, I recommend the 2.4 GHz range if it works properly.
