Posts by dtech

Quote from kiarov

Hi, first of all thank you very much for your amazing work, how you brought my old little mxq box back to life is charming. Although I'm having issues while trying to build an image from the source you provided, I dont know if here is the right place to ask for help but compilation is failing only 5 steps before completion would it be okay if I share the log with you? or where can I ask for help? by the way im trying to compile it using WSL2 with ubuntu 18.04.5 LTS and I'm trying with the code from the tag 9.2.8.10-S8XX, the command I'm running with make is make image PROJECT=S805 DEVICE=HD18Q ARCH=arm.

Thanks in advance

cheers!

It is not recommended to post logs on the forum. For this purpose, it might be better if you open a ticket on GitHub under my repo, and we can discuss the details there.

Quote from carsten888

[bit off topic]

Thank you. But how do you copy-paste without being able to select text? I just tried with a mouse. Got the key-stuff on a usb stick.

[/bit off topic]

In the case of local input, it is probably not possible at all, so typing remains there.

I wrote this only because even a USB keyboard is much faster than a long text entry with a simple IR or RF remote control.

Quote from carsten888

Any tips on how to copy-paste the api-keys? I've been typing on the remote control for an hour or so, and it still tells me its wrong. Going nuts here.

I tried to edit the settings.xml, but it does not save because of viewing-mode in linux (idk). And there is an issue on the yt github about the key not actually being saved in settings.xml. So there is also that. So it has to be saved by typing into the yt settings, unless someone real smart knows another way...

Try editing 'api_keys.json' via SMB:

\\<IP-address-of-your-device>\Userdata\addon_data\plugin.video.youtube\api_keys.json

... or directly under SSH:

nano ~/.kodi/userdata/addon_data/plugin.video.youtube/api_keys.json

But the simplest solution is the following:

In the Settings menu of the addon, there is an API menu item, where you need to enable the Enable API configuration page option. After you need to open http://<IP-address-of-your-device>:50152/api in a browser, then copy and paste the required values.

But, if you insist on local input, you can even plug a USB keyboard into the device, which is a little faster than using a simple remote control.

hiep.ton

Thank you for the feedback. Before I publish it again (but now with the current version), I will modify the updater script so that it doesn't save the remote configuration from Android at all, because it sometimes causes conflicts.

crubyape

You should try it with another 12V DC (center-positive) adapter. If it works fine with the another power supply, then the factory power adapter of the box is broken.

But if it produces the same with the replacement power supply, then the 5V voltage regulator (eg STI3470 or similar) or the boost converter IC (INN8186 on the tuner) responsible for producing the 18V LNB power supply may have shorted.

zuka1977

Please try the latest snapshot, because it already contains the Realtek WiFi driver you requested:

Index of /snapshots/20230825_master_aa4b7c2/

And one more thing...

If you use the factory remote control, try this config file:

https://libreelec.dtech.hu/remote.conf/FF00-Mecool/remote.conf

Quote from zainkamal95

Hi everyone,

Is it possible to use an animated boot splash like the boot on CoreELEC 20.2

I want to use it on version 9.2.8

Sorry, but I don't see much sense in this kind of visual development under a legacy LTS release.

If someone sends it in PR, I'll check it, but if you don't mind, I won't waste my time on it myself.

(M8)Baby steps...

Commits · dtechsrv/u-boot

UBoot for AML CPUs. Contribute to dtechsrv/u-boot development by creating an account on GitHub.

github.com

But the KMQN10006B-B318 chip on the PCB, which is an eMMC+LPDDR2 RAM hybrid IC, is pretty insane stuff without any documentation to be found. I'm done with the memory timings, but the system won't start at the moment. (It's booted, but there's still work to be done.)

Quote from crazyazz

Hi guys, I was wondering if HDR10 and Dolby vision is supported and past on to the TV with these builds?

HDR10 is also supported on my GXL/GXM images (h265 only!), but Dolby Vision is a licensed stuff, so it is not supported by Kodi even under the latest version.

Quote from icewhaler

I just wanted to say thanks for all the hard work keeping these old devices working. I've spent the past couple of days reading through these posts and trying several different .img until I realized my Matricom Q box (S802) seems to be happy with the K200-AP6330_2G.arm. version 9.2.8.10

Is this currently the newest version that will work with my box or is it possible to get LE 11 working ? I had attempted to get Chewitt's testing LibreELEC-AMLMX.arm-10.88.0-box.img version working with out any luck.

Sorry, but I cannot test mainline-based versions in current state, because I don't have an S802 box, and my S812 boxes can only boot with 1 core (M8S+, WeTek Core), so unfortunately none of them could start the AMLMX image by chewitt .

Quote from zuka1977

I just installed LibreElec 9.2.8.10 on my device Mecool KIII Pro (S912), but I have probelm with my orginal wifi on device and use external usb wifi (rtl8821CU), which one is not working with LibreElec 9.2.8.10.

Can you help me how to add this driver in LibreElec, if it is possible?

I will try to add the missing Realtek wifi driver, but I ask for a little patience until the beginning of September.

Just a quick thought:

Quote from tecc

Since CEC sudddenly does no longer work on a friend's TV of mine (who owns the same box), I was planning to use the original remote, so I've downloaded LibreELEC-AMLGX.arm-11.0.3-box.img.gz ...

It is not certain that the factory remote control will work under LE11 on-the-fly, but my LE9.2 build includes the stock remote.conf by default.

Quote from thegooddoctor

I removed the emmc module ...

^ What does that mean? Did you unsolder the eMMC chip from the PCB?

Quote from thegooddoctor

well that again didn't work

BootcardMaker writes u-boot.bin to sector 0 of the SD card, so the bootloader should start even without the eMMC module.

If this doesn't work either, then maybe you didn't follow the instructions correctly, or the SD card (or possibly the slot) is also faulty.

Quote from chewitt

It was clear to me ..

I'm glad it's clear to you, especially since you wrote it, but I think this sentence means nothing to non-expert users.

Quote from tecc

The legacy version booted straight to LibreELEC without the need for pressing the reset button on my device ...

^ With this kind of wording, I think "You must press that button again to boot LE11 from SD card" is much more understandable than "you MUST invoke recovery mode boot". I don't like to complicate things unnecessarily...

Quote from chewitt

Legacy images use different boot-scripts and boot files to the AMLGX image so you MUST invoke recovery mode boot so the vendor u-boot searches for aand finds/loads/stores updated boot-scripts that tell it what files to use. If this is not done u-boot is looking for boot files that don't exist and .. it isn't going to boot. Similarly if you have been running AMLGX and want to revert to the legacy image you need to do the same else u-boot is looking for the AMLGX boot files and won't find/use the legacy ones.

chewitt

You described the reason, but you didn't detail the solution.

tecc

In short: it is necessary to execute the "toothpick method" again, because aml_autoscript is executed only in this case.

Unfortunately, the Android ROM developer ( willie.xu ) didn't respond to my numerous inquiries, so I might end up trying to compile my own uboot for this box, to fixing these errors, if that's possible. (I haven't done this before, so it might not work.)

But CEC will probably never work because it doesn't seem to even be physically connected.

At least I have a small sense of success that I was able to carve out a hole for the UART socket at the bottom of the box:

So don't have to leave this piece of garbage all the time disassembled...

thegooddoctor

https://libreelec.dtech.hu/misc/wetek-unbrick-resources/WeTek_Hub_Restore.zip

^ Download this file, unpack its contents and follow the instructions in README.TXT.

Quote from tecc

Thanks for replying with this to my question from some time ago. I've been running LibreELEC (dtech) 9.2.8.8 - Kodi 18.9 Leia ever since but for the life of me can't remember exactly what dtb.img I actually did use (here's the MD5: 4c723801b797f26828caed55ebec8b32 in case that helps).

The answer:

LibreELEC:~ # find /usr/share/bootloader/device_trees -type f -exec md5sum {} \; | grep 4c723801b797f26828caed55ebec8b32
4c723801b797f26828caed55ebec8b32  /usr/share/bootloader/device_trees/gxl_p212_2g_nand.dtb

Quote from tecc

Since CEC sudddenly does no longer work on a friend's TV of mine (who owns the same box), I was planning to use the original remote, so I've downloaded LibreELEC-AMLGX.arm-11.0.3-box.img.gz and tried renaming each of these ...

For versions based on the mainline kernel (LE10+), the dtb setting is different compared to legacy versions.

Please check if you have done the settings correctly as described in the description:

https://wiki.libreelec.tv/hardware/amlogic#box-images

I'm not sure if the kernel in the WeTek Hub LE11 image is working. I tried booting from an SD card with it and it didn't work either.

## Booting kernel from Legacy Image at 01080000 ...
   Image Name:
   Image Type:   AArch64 Linux Kernel Image (lzo compressed)
   Data Size:    11576293 Bytes = 11 MiB
   Load Address: 01c80000
   Entry Point:  01c80000
   Verifying Checksum ... OK
      Amlogic multi-dtb tool
      Single dtb detected
load dtb from 0x1000000 ......
"Synchronous Abort" handler, esr 0x96000010
ELR:     37ef1760
LR:      37ef167c
x0 : 0000000000000000 x1 : 0000000000000000
x2 : 0000000033ec8c18 x3 : 0000000000000016
x4 : 0000000037f73a40 x5 : 0000000037f73b40
x6 : 0000000037f73b48 x7 : 0000000000000020
x8 : 0000000000000031 x9 : 0000000000000000
x10: 000000000000000f x11: 0000000037f45f58
x12: 0000000000000000 x13: 0000000000000000
x14: 0000000000000000 x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 0000000033ec2e28 x19: 0000000037f73a40
x20: 0000000000000000 x21: 0000000033ec8c18
x22: 0000000037f73b40 x23: 0000000037f73b48
x24: 0000000000000016 x25: 0000000037f73b40
x26: 0000000000000000 x27: 0000000037f49f20
x28: 0000000000000000 x29: 0000000033ec2030

Resetting CPU ...

resetting ...

However, the box image boots flawlessly from the SD card.

chewitt Is it possible that the Hub image is not compatible with the WeTek factory u-boot?

Quote from AppleCross

I am looking for kernel source code (DTS, kernel Config and some other files for building Linux) . Can you give me hint where to find those files?

The information you need can be found in the leading post in this topic:

Post

Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

Latest version: LibreELEC 9.2.8.18 (Release date: 2025-05-20)

IMPORTANT NOTICE!

Due to the switch to GLIBC v2.34, all binary addons have been rebuilt. The main version of the add-ons has been changed from v9.2.0 to v9.2.1, so after the system update, the binary add-ons will also be updated. In addition, the default transfer protocol in the repository has also changed from HTTP to HTTPS.

NOTICE: If the auto update is enabled, but the installed version is not the latest, then the supported devices…

dtech

February 7, 2021 at 2:33 PM