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.
The thread is 50 pages now. Should I close it? Users don't read the whole story anymore.
No one needs to read the whole thing, I was just referring to the very first post.
I don't want to close this topic yet, because I'm still adding minor updates to it.
Latest version: LibreELEC 9.2.8.11 (Release date: 2023-09-11)
^ In short, this topic is not completely dead yet.
Dtech, thanks for the quick response. I understand you. But there is another problem, and it is related to wi-fi. For some reason, when connected to 5G Wi-Fi, the TVbox periodically restarts itself and loses the network. On 2.5g there is no such problem - everything works stably. Maybe the problem is related to the Wi-Fi channels?
Why doesn't anyone read the leading post of this topic?
IMPORTANT NOTES - Please read them carefully before asking:
...
- I can't do miracles with the wifi and bluetooth drivers built into the kernel, so I can't do anything about "cannot connect", "the signal is weak" or "the connection is slow" errors either, so please don't expect a solution from me.
Hello dtech. I have a question about assembly for X8-X8H. I own a MINIX Neo X8-H device. It claims 2 GB of RAM, but in the system information I see that the system only detects 1553 MB of RAM. Is this how it should be? or do I need to configure something?
You will be surprised, but you are not the first to ask this. Kodi displays the amount of memory it can use as total memory.
If you run a dmesg, it also becomes clear to you that the device pre-allocates certain memory areas for some built-in purpose.
For example, it looks like this for the M8S-Plus:
[ 0.000000@0] physical memory start address is 0x200000
[ 0.000000@0] reserved_end is 20afffff
[ 0.000000@0]
[ 0.000000@0] Total memory is 2046 MiB
[ 0.000000@0] Reserved low memory from 0x06000000 to 0x20afffff, size: 427 MiB
[ 0.000000@0] mesonfb0(low) : 0x06100000 - 0x0c100000 ( 96 MiB)
[ 0.000000@0] mesonfb1(low) : 0x0c100000 - 0x0c200000 ( 1 MiB)
[ 0.000000@0] deinterlace0(high) : 0x7df00000 - 0x80000000 ( 33 MiB)
[ 0.000000@0] mesonstream0(low) : 0x0c200000 - 0x0e200000 ( 32 MiB)
[ 0.000000@0] vdec0(low) : 0x0e200000 - 0x1e200000 (256 MiB)
[ 0.000000@0] ppmgr0(high) : 0x7bf00000 - 0x7df00000 ( 32 MiB)
[ 0.000000@0] vdin00(low) : 0x1e200000 - 0x1e300000 ( 1 MiB)
[ 0.000000@0] vdin10(low) : 0x1e300000 - 0x1f300000 ( 16 MiB)
[ 0.000000@0] amlvideo20(low) : 0x1f300000 - 0x20b00000 ( 24 MiB)In addition, a few other things require reserved memory, so in the end this will be the amount that can actually be used freely:
[ 0.000000@0] Memory: 64MB 16MB 1460MB = 1540MB total
[ 0.000000@0] Memory: 1545608k/1545608k available, 31352k reserved, 1250304K highmemI hope it's clear now.