Posts by dtech

  • [9.0.0] LibreELEC builds for MX2/G18

    Quote from qUE_ARM

    I've got Libreelec-AML 9.2.8.7 to build and boot on the MX box, but I'm having an issue with the Realtek 8188ETV wireless.

    Libreelec doesn't allow me to enable the 'wireless active' option. I've SSH'd and lsusb, the device is present so I assume the drivers are working.

    Various places have mentioned Realtek wireless support is a bit of an issue of contention for the libreelec team, so I'm expecting some pain getting this working.

    Unfortunately, this is my first outing in compiling the linux kernel so I'm really a n00b when it comes to this. Is there any recommendations in tackling this issue?

    I can post dmesg dump if that would be any help.

    The Realtek 8188* is a general USB chip, I also have an external one (TP-Link TL-WN722 v2).

    I use an external module for this in my builds, instead of the integrated module of the kernel.

    First, you need to check if it is enabled in your kernel configuration, because if it is, it should be disabled:

    Code: linux.arm.conf
    # CONFIG_RTL8188EU is not set

    Next, add RTL8188EU-aml to the ADDITIONAL_DRIVERS variable in the options file in your project directory.

    If that doesn't help either, then please send me a log file: journalctl | paste

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

    Quote from bhouseski

    Hey all, does anyone know if/where one can purchase/source one of these boxes? I have an MXQ pro+ running the latest build, and would like to add another one or two to my arsenal. The challenge is finding one.

    It is quite difficult to buy a used box these days, because on the one hand it is rare, and on the other hand, if you find one, the seller sometimes gives it at a price that is usually not worth it.

    Quote from mulderfox

    Interestingly enough, I managed to get Libreelec working on my amlogic s805 based box, only With MXQ image (which more closely resembles the specs of the Freesat Angel V8 box I got) I only managed to get to the Kodi splash screen (where it got stuck), and with the lower speced M201D firmware - it booted without a hitch - although Bluetooth does not work, the network speed is a tad slow, and some things just get the box frozen. It still works MUCH better than with the Android 4.4.2 that comes with the box (and cannot be updated). So thanks.

    The limiting factor and the reason for the freezes, may be the lack of memory. 512 MB is not too much.

    Bluetooth and Wi-Fi are also quite a gamble. The quality of the drivers integrated into the 3.14 kernel and chips themselves are not very good.

  • ID Error 1 at boot

    Quote from InvisibleRasta

    i get an ID error 1

    It is not an ID error, it is an HID error. One character is missing from the beginning of each line due to display overscan settings.

    Read more about this issue:

    HID error and network install · Issue #458 · raspberrypi/rpi-eeprom
    Describe the bug See https://forums.raspberrypi.com/viewtopic.php?t=339219 It seems some users are seeing "HID error" and that's stopping the…
    github.com

  • [9.0.0] LibreELEC builds for MX2/G18

    Quote from qUE-ARM

    Although I'm currently trying to build LibreELEC-AML 9.2.8 with the necessary tweaks to get it running and updating on the MX2 boxes. I've stumbled at the Mozilla stuff not building on 32-bit, so I've switched to 64-bit and may have a build to try in the new year (it's not a simple task, so fingers crossed). I'm really hoping it'll sort that hanging issue with Amlogic hardware decoding.

    If you think so, maybe I can help you with that.

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

    Quote from thadrumr

    I have an S805 HD18Q box running version 9.2.8.6 and I noticed it has two offline CPU cores. Is there a way to re-enable the additional cpu cores 1 and 3 it currently is only using cpu cores 0 and 2.

    Changing the base frequency of the SoC and dynamically turning some cores on and off is controlled by the CPU governor. The reasons are very simple: saving energy and reduce heat dissipation. If the CPU load requires it, these cores are also activated on the fly.

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

    Automatic system update has been enabled for the following devices since 2023-01-05:

    • WeTek Play 2 (GXBB),
    • Mecool KI Pro (GXL),
    • Videostrong KI Plus (GXBB),
    • WeTek Core (Meson8m2),
    • OTT M8S+ (Meson8m2),
    • MXQ HD18Q (Meson8b),
    • MXQ m201d (Meson8b).

    If the auto update is enabled, but the installed version is not the latest (v9.2.8.6), then the listed devices will automatically download and install it after restarting. If anyone is experiencing any issues with the update, please report it here.

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

    Quote from punter

    hi

    can we make python 3 work on this version? i get an error when trying to install iplayer

    cheers

    Under Kodi v18 (Leia) only addons written in Python2 can be used. Python3 is only available under Kodi 19 (Matrix).

    So, if the add-on requires Python3, it is not made for Leia.

    Please check if there is a supported version for Kodi 18. If not, I can only quote myself from the first post:

    Quote from dtech

    At the same time, the version of Kodi v18 (Leia) is no longer developed, so it may happen at any time that an external add-on stops working (especially online add-ons) and no longer receive updates for this version of Kodi.

  • Cannot update

    ErVeTeBe

    The system update will not work, because the manufacturer did not release a newer LE9.2 image.
    But, I looked into the 9.2.5 image of EM7680 and maybe this is causing your problem:

    Code: /usr/share/kodi/addons/service.libreelec.settings/defaults.py
    updates = {
    'ENABLED': True,
    'UPDATE_REQUEST_URL': 'http://www.venztv.com/ota/update.php',
    'UPDATE_DOWNLOAD_URL': 'http://www.venztv.com/%s/%s',
    'LOCAL_UPDATE_DIR': '/storage/.update/',
    }

    The update URL returns an HTTP 404 error, so the update channel is now dead.

    But, as I have seen, there is a bigger problem with this image:

    Code: /etc/ssl/cacert.pem.system
    Certificate data from Mozilla as of: Sat Sep 15 08:29:09 2018 GMT

    You can no longer access a lot of repositories with this outdated cacert.pem.

    The quick solution is this:

    Post

    RE: SOLVED: Cannot Install/Update Addons (on LE9.0 and older versions)

    LE 9.0 (and before) use the old openssl 1.0.2 version which is tripping over the DST Root CA X3 expiration end of September - read more about it here: https://www.openssl.org/blog/blog/2021…RootCertExpire/

    Fortunately applying the workaround 1 (removing the cert) is quite easy:

    First create the directory /storage/.config/system.d/openssl-config.service.d:

    (Code, 1 line)

    then create a file drop-dst-x3.conf in there (full path is /storage/.config/system.d/openssl-config.service.d/drop-dst-x3.conf)…
    HiassofT
    October 13, 2021 at 1:16 PM

  • [9.0.0] LibreELEC builds for MX2/G18

    Quote from digi_tal

    pls help

    image of screen

    Try to write the image to another SD card, because either the file system or the card may have been damaged.

    Quote from Pepev82

    Leia 18.1 on Matricom device.

    All Add-ons failed to install and/or update.

    I think this is what causes the error:

    Post

    RE: SOLVED: Cannot Install/Update Addons (on LE9.0 and older versions)

    LE 9.0 (and before) use the old openssl 1.0.2 version which is tripping over the DST Root CA X3 expiration end of September - read more about it here: https://www.openssl.org/blog/blog/2021…RootCertExpire/

    Fortunately applying the workaround 1 (removing the cert) is quite easy:

    First create the directory /storage/.config/system.d/openssl-config.service.d:

    (Code, 1 line)

    then create a file drop-dst-x3.conf in there (full path is /storage/.config/system.d/openssl-config.service.d/drop-dst-x3.conf)…
    HiassofT
    October 13, 2021 at 1:16 PM

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

    Quote from 1234LP

    Yeah,the original MXQ(5G)...only do not know what version Amlogic or else.

    Have reset button but will not get into dual boot.

    Evry time boot into normal no metter how long reset button is pressed.

    MXQ(5G) -> It is not an exact type, just a fancy name. However, I cannot recommend a dtb without the correct specification.

    By the way, there are actually some of these that do not even contain an Amlogic SoC. (e.g. Rockchip RK3229)

    You should somehow find out what it contains and how much RAM is in the box.

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

    Quote from 1234LP

    Something went wrong...i`m not able to boot into libreelec any more from sd card.

    WeTek images do not need aml_autoscript, but standard images need it. However, this only runs if you use the toothpick method:

    Quote from dtech

    Start LibreELEC from SD card:
    If you want to boot the device from an SD Card, you need to perform the 'toothpick method':
    Disconnect the power plug, insert the prepared SD Card on, which the image file is written (img.gz), and then press and hold the reset button. Reconnect the power jack while holding down the reset button, then release it after about 3-5 seconds.
    NOTICE: If the Android recovery menu appeared, you pressed the button for too long.

    The toothpick method only needs to be run once, but it is an important step because it sets a bunch of uboot variables, which are needed to boot LibreELEC from SD card or USB (and if it can't find them, it will boot from eMMC/NAND automatically). However, the aml_autoscript of LE8 and LE9 are not compatible with each other, so if LE8 was installed earlier, this may be the reason why LE9.2 does not start. But the toothpick method will solve this problem.

    WeTek devices do this whole method differently: Power button -> whereToBootFrom uboot variable. This is one of the main reasons that WeTek images are really only for WeTek devices.