There´ s no freezing anymore. Now I can stop or change between movies, tv shows, among others during playback smoothly, without problem!
I am glad that this error has been solved. I also experimented a lot with that M8S+ before I managed to fix it.
Besides the MAC address thing, it´ s working as expected to a old box as this one... hope it helps anyone with a Minix X8/X8H Plus.
I will be making a new image soon, which will include the ethmactool package. Maybe that will solve this problem.
Please test with this new image and send a feedback on whether it works or not:
I would appreciate it if you could test your device with this rebuilt image as well.
Hi! I also have a KII Pro mecool with Soc 905D and 3.14 kernel. What device tree have you used? and did you get tvheadend to work?
Try this one for S905D SoC-based KII Pro: gxl_p231_2g_dvb.dtb
Tvheadend needs to work because the KI Pro has the same tuner. I recommend the "dvb-latest" module package for the tuner.
I try this one "20210903"
Please also try 20210901. It contain datrh's original startup scripts and original platform_init script as well.
Rebuild: Index of /snapshots/20210906/
I apologize. Please tell me, do you have any ideas for rtl8723?
Thank you
Unfortunately, I have no idea at the moment.
Previously, there was a box with exactly same integrated SDIO wifi, but it was an S905 box and it eventually started with the external module.
Thank you so much for everything, but it no longer proves anything, that I don't have much time.
Thanks a lot for everything.
I'm sorry I couldn't really help you.
The truth is, I’m also trying to provide support for devices I’ve never had at all. And since I can't test these myself that way, and I can't debug any errors myself on them, so it's really just a remote series of experiments. And if something failed, it’s actually just a waste of time for me too. Unfortunately, I never know if actually I made a mistake or the tester messed up something. That’s when I usually come with this sentence: "Are you sure you did exactly that...?" Although I may have actually screwed up something.
Unfortunately, I start to get a little tired of these. 
--
Edit:
Which snapsot image did you test? "20210901" or "20210903"? Unfortunately, this is by no means an insignificant parameter.
For snapshots, the main version number matters much less, the build date matters first.
Not working
Based on the photo you sent, I would suspect the SD card in the first round.
Try rewriting the image, and if the situation doesn't change, try another SD card.
One more thing:
Be sure to use the toothpick method because aml_autoscript has changed since the previous version.
Affected page: LibreELEC Amlogic - LibreELEC
Latest Stable Version (2020.05)
LibreELEC 9.0
- Kodi 18.2
- Linux Kernel 4.19.x
Mistake #1:
Release date:
In fact, it should be 2019 instead of 2020, but May is true.
Mistake #2:
So, the Linux Kernel 4... WHAT?!
As far as I know, you only worked with 3.10 (Meson6, Meson8) and 3.14 (GXBB, GXL) on Amlogic devices, and never with 4.19. 
i am using window 10 *.img unpack is for linex (i think)
This program is required for unpacking Amlogic firmware images: Amlogic_Flash_Tool_v6.0.0 .zip
There are new snapshot images for Minix-based devices: Index of /snapshots/20210906/
- Every time I try to stop, it freezes... doesnt matter what I command then, just a reboot to make it alive again;
Okay, I replaced the platform_init script with the one I modified for M8S+.
This was preceded by quite a long experimentation, but there it finally solved the freeze on the M8S+.
Although it didn’t work on n200 (MXIII-based) devices, that’s why I didn’t apply it to anything other than M8S+ because I can’t test.
I would ask you to test it please.
There´ s no sign if it is on or off - the led is dead;
Unfortunately, I cannot comment on this. I use the datrh solution. Did it work under his image?
As far as I´ ve seen, the player isn´ t as smooth as before - some image tearing during playback.
Let's see now if the new initramfs script solved this as well. If not, I would like clarification as to which videos are not playing properly.
And last build 9.2.8.2 (also bluetooth don't work)
I don't know why rtl8723bs doesn't work even though it's turned back on.
...
CONFIG_RTL8723BS=m
...Neither the external nor the internal module works. I don't know why, but I'm going crazy about it! 
...
Okay, maybe we have one more option, so please send the output from these commands under the old 9.2.8.1:
cat /sys/class/net/wlan0/device/vendor
cat /sys/class/net/wlan0/device/deviceI need to know the vendor ID and the product ID of the integrated wireless/bluetooth SDIO module.
Here are some new test images: Index of /snapshots/20210901/
Momantai: LibreELEC-X8-X8H.arm-9.2.8.2.*
SerGioTenerife: LibreELEC-X8H-Plus.arm-9.2.8.2.*
blackride: LibreELEC-MXIII-Plus.arm-9.2.8.2.*
Please test them and describe your experiences. Thank you everyone. 
It now works with no issues.
Common cause of fault: solar flare?! 
Now the 8723bs module will have the problem.
I need some information about the integrated adapter from an older version that was still working.
lshw -C network
BTW I was using an custom image before (S802/S812-Libreelec images for 7/8/9).
Can you specify which image you are using? The topic link is a pretty broad concept.
Bluetooth adapter not found
I need a dmesg immediately after the boot.
The trouble is that most of the time your kernel log is full of junk like this:
[DVFS]aml_dvfs_do_voltage_change, no dvfs driverUnfortunately, your last dmesg is also full of this line and there is no useful content in it.
The built-in bluetooth box don't work.
One step forward, then one step back. This may solve the problem:
There is a new snapshot release (20210826):
Same driver, but I turned off the built-in modules in the kernel because those were turned on.
Please test it with V5 first and then with V4.
In the previous log, you almost misled me because the adapter connected for the second time was the V4:
[ 51.875978@2] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[ 51.977350@2] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8178
[ 51.977363@2] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 51.977370@2] usb 1-1.3: Product: USB WLAN
[ 51.977375@2] usb 1-1.3: Manufacturer: 802.11n
[ 51.977381@2] usb 1-1.3: SerialNumber: 00e04c000001
[ 52.015734@2] [DVFS]aml_dvfs_do_voltage_change, no dvfs driver
[ 52.018566@3] RTL871X: module init start
[ 52.018577@3] RTL871X: rtl8192cu v4.0.5_11249.20140422
[ 52.018582@3] RTL871X: build time: Aug 15 2021 17:12:24
[ 52.115740@1] [DVFS]aml_dvfs_do_voltage_change, no dvfs driver
[ 52.156781@2] RTL871X: rtw_ndev_init(wlan1)
[ 52.158665@2] RTL871X: rtw_ndev_init(wlan2)
[ 52.167744@0] usbcore: registered new interface driver rtl8192cu
[ 52.167759@0] RTL871X: module init ret=0These require completely different kernel modules:
V4 -> 0bda:8178 (rtl8192cu)
V5 -> 2357:0107 (rtl8192eu)
I will try to find out why it does not load the module for the V5 (rtl8192eu).
In your CE log the trace looks very ugly after connecting the USB wifi device:
https://paste.kodi.tv/idowabezoh
That looks pretty sick. 
i update LE with version 9.8.2.1 on 9.2.8.2 via tar archive.
The numbers were mixed up again: 9.2.8.1 -> 9.8.2.1 (Translator malfunction?)
However, if you could check the current image with V4, that would be good, because it also got a new driver.
If it doesn't work, I will go back to the old one.