Posts by dtech

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

    Quote from zuka1977

    there is the problem with play HEVC video content (stuttering, audio out of sync)

    I will need a little more information than this, because the format of the file is only one thing, besides that, there are quite a few other parameters of that media file.

    A log would be good (pastekodi), and a part of the file that was played incorrectly would be also helpful if you could upload it somewhere.

    Quote from zuka1977

    I have installed CE 9.2.8 on device and HEVC video play without issue on this system.

    I made backup of CE 9.2.8 system and restore it on LE 9.2.8.10, but problem with HEVC video still existing.

    Please, do not restore a CE backup on LE, because although the two systems are similar, there are quite a few differences between them.

    It's even worse if you try to use pre-compiled CE binary addons under LE, even just a simple pvr addon. This two systems are not (fully) compatible with each other, so please don't do that!

    I can only help if the answer to this question is "Yes":

    Does the above issue persist under a "clean" LE 9.2.8.10 installation?

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

    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.

  • Youtube and Tubed errors

    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. :)

  • Youtube and Tubed errors

    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. :)

  • Mecool Ki Pro unstable

    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.

  • No WiFi at MXQ PRO 4K 5G

    (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.)

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

    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.

  • Bricked Wetek Hub ... now what

    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.

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

    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... :)

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

    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.

  • No WiFi at MXQ PRO 4K 5G

    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... 8o

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

    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:

    Code
    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

  • Bricked Wetek Hub ... now what

    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.

    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?