Posts by balbes150

    is the "please_resize_me file" problem resolved? I don't have a Linux machine to resolve this problem.

    I think this problem is related to the garbage in your u-boot. Try to install the standard Android firmware from your TV box via USB Built Tool (to clear all the accumulated errors in the internal memory). And then perform the activation of the universal multi-boot.


    So it seems meson-ir is not used by the system.

    I have not yet published the changes to git that are used to build the latest s812 image. The meson-ir driver is built into the kernel.


    can it be possible you should change

    Option "amremote" disabled in the settings.


    -> on your github page it's still there

    Now I will try to remove " remote.conf " and collect a new image.

    The new version 20180601.

    Working repository Addons Libreelec (thanks chewitt for the added link for s812).

    Added support for the remote control, but I can not figure out what is the reason that "ir-keytable" does not accept codes from the remote control. Perhaps need additional settings, but I do not know what is missing. I will be very grateful if more experienced users will tell me the reason. By the way, there is "mc" in the image (which can be run via SSH), for quick editing of settings.

    1. That would not confuse users Libreelec, discussion Armbian need to do on the forum Armbian.

    2. For the image LE you may try all options dtb gxl_p212* gxl_p230* gxl_p231* gxl_p281* .


    For all. Update versions S905 and s912 arm 50180601.

    Thanks for the tests. Yes, a problem with different aml_autoscript is possible. Therefore, it is desirable to run with clean firmware. In this case, there will be no impact from old "tails" (incorrect data). Errors in systemd are not critical, it is from different module variants. Installation in the eMMC is still in the process of verification. I have only one unit of TV box with S812, which is intensively used for different tasks and therefore has some problems with the healt of the eMMC. :)

    Would be helpful if you could start another thread for Leia S802/S812.

    Perhaps the moderators can split this topic and make posts about Leia in a separate topic.


    I see on the download page there is a folder for the 100Mb network with two folders, both with an image. What is the difference between all the 100Mb images. I used the one from the front page.

    Try to test all three variants of images. They use different kernel and configuration options.

    No Idea about the Vim2. But I doubt it will be as easy to get LE started as just flashing a SD card / USB Stick and then simply holding down the box's power button for 6 seconds or longer to start LE installation.

    Khadas products have the best support for all multi-boot options from any media.


    The U9 (and U1) has the best thermal management out of all the AMLogic devices simply due to it's massive heatsink.

    Very handy for GPU Overclocking.

    What material of the case is plastic used ?

    Nice to hear the mainline kernel for the S812 is also getting shape. Your armbian build made me dust of my M8S. Now I have to find the proper DTB. Hopefully HDMI will be functional soon.

    All images Armbian for s812 core 3.x works with HDMI and all other components. I don't have enough time to add KODI with HW to them.

    Updated image 20180511 (in catalog 20180511_1).

    The main change in the composition of the image added a data_to_emmc_uEnv.ini. Which allows the use of LE in the mode with the placement of the system on external media, and the data in the eMMC. Details of how this works can be found in this thread.

    [HOWTO] Boot from SD card, use internal memory for data

    Please note that to use the system in EMMC mode, you only need to rename the script on the media (SD card or USB flash drive) from

    data_to_emmc_uEnv.ini

    to

    uEnv.ini

    You do not need to perform other steps. Not in itself a eMMC not need to change.


    Please note, uEnv.ini is a plain text file that contains the variables to run the kernel. You can easily add or remove variables. For example, you can add a variable with its MAC address mac=you_Mac_address

    Thank you for answer...I did not understund what information?If you mean his latest build for m8s you can find here: Releases · AlexELEC/AlexELEC-AML · GitHub.

    I will be very thankful if you make script to load Alexelec build for m8s android box.Thanks again...

    To create a script, need support in the image to be able to work with it. Ie need to make small changes to the image itself, then I will be able to collect the right script. If Alex is interested, can easily resolve this issue, I am ready to take part in it.


    when i insert libreelec for m8s latest 17.6 from 22.01.2018 on usb and after i turn off later i cant turn on libreelec from usb and it show me on tv "no signal".I dont know what is problem...Can you fix that in future version for proper turn off/on for my box m8s s812 AP6330 .Thanks!

    I hope to release an update soon, maybe it will fix the error.


    is the still being developed ?

    the alexelec seems to be Russian only ?


    i'm not into retro gaming

    Yeah, I keep working on the LE for the s812. The good news is Martin is gradually adding support for the s812 to the kernel mainline. Now you can use s812 as a server (there is no HDMI output yet).

    This is the file for the old use case. Now you need to have a different file format. You can create it by following the instructions I gave above. Or you can build the necessary file using analogy. All codes that are used in the new format, you can get from the old file, they go to the first column of the old file. Next, in the old file is the code that is common to all models, you can find a description of the common codes and create your own file on the table.

    For example, for General code 116 "shutdown", in VIM models, the code corresponds to "0x14". Similarly, you can find your codes and create the desired file.

    remote.conf.vim#l57

    remote-ir.conf_vim#l12