Posts by dtech

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

    Quote from y0ush4

    Because I am tired trying roms after roms

    If it's not the factory one and there's no backup, it's not exactly a good base.

    Quote from y0ush4

    m8m2_n200_1g

    Then there is a problem, because I don't have a 1GB image for S812, only for S802 (MXIII-1G).

    There was a test kernel for the 1GB box, it might work with that (but it was not made for the latest image):

  • [RPi4] Steam Link Launcher

    Quote from Meekys

    Has anything changed in your environment since December when it was working?

    I don't know after all this time.

    Quote from Meekys

    Updated LibreELEC?

    Yes. I have now installed the current 11.0.6 but the error still exists.

    Quote from Meekys

    Different raspberry pi? (3 vs 4)

    Nope. I don't have an RPi3, so it would be difficult to replace it. :)

    I'm sending a log excerpt for this, if that helps:

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

    Quote from lilian29

    Here is the remote.conf:

    Okay, this is actually a config of two different remotes integrated into one file. Well, not exactly the best solution. But one of these codes is also included in the image by default since v9.2.8.12 (0xff000001).

    Question:
    Does the remote control work even without your custom config?

    If the answer is no, then the other one will be, then try this: MXIII-G Remote (0x7f800001)
    (Of course, there is no guarantee that all buttons will work.)

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

    If you want to use your box to run network services, then LibreELEC is not necessarily the best choice, not least because everything runs with root privileges, and the kernel is also very old.

    In the past, there was an attempt to run OpenWrt, but I don't know if it is still available, because I don't see any published images:

    GitHub - joycechu/openwrt_meson: Amlogic S905/S805 OpenWrt
    Amlogic S905/S805 OpenWrt. Contribute to joycechu/openwrt_meson development by creating an account on GitHub.
    github.com

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

    Quote from jim_p

    Vnc will also need port forwarding, plus an extra app on my end. Tbh, last time I tried vnc it was locally on the rpi3b+ running the nightlies of le 11 (before it was stable) and the results were dissapointing because the image that reached the client was very distorted.

    This is far from the VNC server for the RPi, it is based on the continuation of kszaq's previous work, which I have since optimized a bit:
    https://github.com/dtechsrv/aml-vnc-server

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

    Quote from jim_p

    When something happens on the tvbox and needs my intervention, I connect via anydesk to the family's pc and then via ssh (the built in command of powershell) to the tvbox. Annoying procedure I know.

    If you want to access and/or configure something remotely that is more easily accessible through the GUI (or specifically accessible only from there), then I recommend the VNC server addon, which can be found in the LE repository under my images.

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

    Quote from jim_p

    That's all I had to say. Thank you for listening. Have a nice day :)

    Thank you for your description. In LibreELEC 9.2 there was a bug in curl that caused some addons to not work (or work incorrectly) if the URL contained an & character.

    Unfortunately, I didn't know the reason for this before, but a security vulnerability has since been discovered in curl, which is why I updated it to the current version, and with that the above error suddenly disappeared.

    That's why I thought you meant something similar, but in your case it was a different story. ;)

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

    jim_p Sorry to quote you from another topic, but what's wrong with the pvr.iptvsimple addon under Leia?

    Quote from jim_p

    Ideally, I would rather install dtech's 9.2.x build on its emmc, since there is no real benefit of using the latest version of kodi or le just for iptv.

    Just because, if curl's error also caused it, it has already been fixed in 9.2.8.12. However, if it was caused by something else, please provide a short description and/or a link where the error is written in more detail. Thanks.

  • Wetek Play 2 how to downgrade ?

    Quote from Old-guy

    I tried all "unbricking" methods but LibreElec won all battles and still is booting bravely every attempt I made (Tried several unbricking methods using the reset button on the bottom of the device as found in the Unbrick resources of Libre Elec

    Unfortunately, at the moment there is no (easy) way to restore, because the factory bootloader is overwritten by the LE11 image, and the function of the recovery button in the upstream uboot is not implemented.

    Quote from chewitt

    Upstream u-boot has no support for Amlogic proprietary restore image formats and sequences.

    Currently the only solution to boot from recovery sdcard is the emmc pin shorting method (I haven't tested this):

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

    Quote from jim_p

    Any idea on how to make this gamepad work on the all black mxq? It works fine on the pc (tested only on windows' built in app for checking the controllers) and it does show up inside kodi as you can see on the image below, but nothing happens when pressing the arrows/keys/joysticks. I have tried connecting it on all 4 usbs and changing its driver from linux to udev.

    This is a common problem under LE 9.x, whatever platform you use.

    Maybe try this:

    Post

    RE: [LE 9.0] Xbox One S Gamepad - no inputs are recognized

    The problem is in the Kodi 18 switching to libinput. It handles keyboards and mice but doesn’t handle joysticks so you need to tell the libinput to ignore this device by assigning the LIBINPUT_IGNORE_DEVICE flag to it.

    Updated quick solution:

    nano /storage/.config/udev.rules.d/99-gamepad.rules





    Copy this 2 lines and replace “Gamepad” with your device name (for me it is "Xbox Wireless Controller") (check that the ENV part is kept on the same line and is not wrapped like on the forum):

    …
    ManuStrozor
    April 15, 2020 at 11:36 PM