Posts by balbes150

Quote from sertem

Mini MX 1/8

Did I understand correctly that there is an archive with the remote control settings file for this model in the attachment (zip) ? Is this a working file ?

Quote from Tidav7578

I have a S905 clone with lastest Kzaq build.

I just need to download the gz in the update directory and reboot and it works or do I need a dtb and other preparations ?

Thanks !

I recommend performing a first test of these images on your TV box , through running from external media. If everything works as you want from external media, then you can try installing to internal memory or updating your existing system via a tar file. Please note, these are test images and there may be errors in them, so do not hurry up to update your operating system immediately, from the beginning, try working with external media.

To all

New test image 20180506.

Quote from erbas

Gentlemen tried everything I could not get by the remote to work

If someone here uses KI Pro and got it to work please say how

If possible remote control file.

Try using this file option (copy to the specified directory named "remote-ir.conf"). Please note, this is a test version with a minimum set of buttons. The rest of the buttons you can add by analogy (the file you have attached , the first part of the line is the desired code). The names of possible keys "KEY_*" can be found in the files of other models.

Nothing found — Yandex.Disk

Quote from muya

is it the same kernel like for kodi 17 or whats the difference to 8.2.5 please?

Kernel 3.14 with the latest patches.

Quote from Michaelbates

What is difference between 4.x and Leia 18 based builds in download section? I have nexbox s905x andriod tv box which one is suitable for me (arch or arm based) Where is device tree also. I m newbie any help. Thanks in advance.

Version 4.x was created long ago and is no longer relevant. You can check the operation of the test images from the Leia-18 catalog.

Quote from erbas

I can not connect the remote control.

Below is the remote.config used in the kszaq version

This file variant will not work with newer versions (Leia-18). The desired option with the new format. You can find a new file suitable for your model or create it yourself.

LE9.0 remote configs ir-keytable Amlogic devices

Quote from erbas

I tried this method more unsuccessfully

KI pro the remote

Sorry, but I do not understand you managed to connect the remote control or not ?

Quote from roel

Would be nice to test on the Khadas VIM.

This has already been tested, but it is not yet time to publish (not all issues are fully resolved). When a decision is made in the Libreelec development community, you will see test images.

I want to offer all users, beginners and knowledgeable testers.

1. Respect each other. We were all newbies once.

2. There are two scenarios for a given question.

a. The answer is not known

b. the answer many times was published and there is no sense to repeat it again.

In both variants of answers-the user needs to try to look for the answer independently. This means that if there is no answer to your question for a long time, perhaps it refers to one of the options and you need to make an effort to find an answer.

Added option for image "S905_arm" . At the same time I updated the images S905_aarch64 and S912_arm. Now in all the images is the configuration file of remote control for Vega S95.

e123enitan

Checked the image with three S905_aarch64 dtb (gxbb_p200_2G_1Gbit gxbb_p200_2G_1Gbit_OTG gxbb_p200_2G_wetek_play_2) - on my Vega S95 Telos all starts with SD and USB. You may need a more detailed check on your Vega S95 Meta.

Quote from e123enitan

I tried this build LibreELEC-S905.aarch64-17.6_20180106 which is fine, then update LibreELEC-S905.aarch64-18.0_20180425tar it hung at at Tronsmart logo or splash.

If you upgrade to the new version of KODI 17 - >18, it is recommended that you completely clear all settings. They can cause a failure. There are no identical settings, each user changes something for themselves. Therefore, it is impossible to create a transition scenario that can take into account all such nuances.

Quote from e123enitan

I tried this image LibreELEC-S905.aarch64-18.0_20180425.img, nothing hapen, just hanged at Transmart splash displayed.

Try using dtb "week_play_2" or check out the rest of the 8 options in turn.

Quote from e123enitan

which device tree is appropriate for Tronsmart s905 metal.

If you need a file for the remote (for Vega S95), here's a link to it. In the next versions, it will be immediately included in the image. Again, to use the configuration file, you must put it in /storage/.config/rc_keymaps named remote-ir.conf

Nothing found — Yandex.Disk

Quote from Sholander

OK, normaly that nothing is forced, but what is the advantage of using one or the other?

Since there is no info of the diferences, do we have to use both versions to find them out?

As Coreelec it is a fork from Libreelec, you'd have to ask about the differences from the creators Coreelec (what they changed).

Quote from Sholander

If I may ask, what is the difference between your LibreElec images and CoreElec images?

Or, why should one use this images instead CE, to what advantage?

1. My image are based on the official version of LE (except for some changes that I think are unprincipled).

2. You are not forced to use my builds. You can use what you see fit.

Added Libreelec images 20180425 for S912

I draw the attention of all. In the new images uses a generic multiboot. It allows you to run any system from external media (libreelec Armbian ArchLinux OpenSUSE, etc.). The new multi-boot is compatible with the previous Kszaq images (allows them to run from external media without additional operations). I. e. Universal multiboot can run new Libreelec, Linux images and old Libreelec images (kszaq assemblies) in which the FAT partition has the script s905_autoscript.

To switch to the new multi-boot option, you must reactivate the multi-boot option. This can be done through the update menu in the regular Android or button (if this mode is in the TV box).

Quote from bylderup

Fyi. Image won´t start on Mecool KI pro. Tried with and without dtb.img. Then copied and renamed Kipro dtb from device tree folder. Didn´t start. See a Libreelec screen and something with debugging shell (can´t read it because of overscan from Monitor)

Update your multiboot. All new versions image use a new version of the multi-start system.

For now, as a workaround, you can use the menu items “Reboot from NAND” and “Reboot install to eMMC” in two steps.

1. Click on the desired item (there will be no external reaction of the system).
2. Click the “Reboot” menu item. The system will reboot and simultaneously execute the selected menu item from the first item.

Also, to install the system in the eMMC, you can use the old standard version, through the execution of the script "installtointernal".

When checking I found an error in the image S905_20180425. The kernel does not start if do not specify any dtb option during Assembly. As a workaround, I've compiled a variant with the included dtb from Khadas VIM. After recording the image (if you do not have a VIM1 model), you need to delete the current file "dtb.img " and try the first run without it. If the system does not start, then you should try copying the appropriate option from the device_trees directory, as described earlier . I hope in the future I will correct this mistake.

Now on the website the corrected version with dtb from VIM.

Quote from bylderup

sorry for noob question - but ..

will the image run from sd card and let android untouched as any other libreelec image

or will it install to nand and remove android ?

Yes, this version works with any external SD or USB media without removing the native Android firmware. If desired, you can (after checking with external media) install it in eMMC instead of Android.

Quote from e123enitan

which device tree is appropriate for Tronsmart s905 metal.

For "S95 Meta" should fit the files "gxbb_p200_2G*"

For VegaS 95 Telos I checked the file "gxbb_p200_2G_1Gib"

Updated image Libreelec_s905_aarch64_20180425.

Other options for s912 and arm will be added later as build and test.

Major change.

1. The shared dtb file (dtb.img) is excluded from the image. The startup script will attempt to use dtb data from internal memory. If the system fails to start in this mode, you must manually copy the correct file from the /device_trees directory to the root and rename it to "dtb.img " (this principle is exactly the same as it has long been used in all Armbian images). You can try all the files in a row, until you have selected an option with full support for all iron TV box.

2. Added the ability to easily connect the settings file for the remote. It must be copied to the directory /storage/.config/rc_keymaps named remote-ir.conf. Additional manipulations are not required. Now already have one settings file for Khadas VIM\VIM2. If someone wants to add their own choices in the images - to send it to me indicating the model of the TV box.

add image s905_arm

Quote from danxc

you can compile the aarch64 for s912 version ? Thanks.

To do this, need to collect "libhibris" in aarch64 mode. But such version not.

Quote from Michaelbates

sometimes subtitles stutters in S905x ( Some 720p movies occasionally creates subtitles stuttering 8 or 9 builds). I m also using nougat based 7.0j build (Kszaq). No subtitles stuttering are visible in 7.0 based build.

By default, the frequency in dtb is already enabled at 666. The above parameter is no.

linux-amlogic/gxl_p212_2g.dts at amlogic-3.14.y · LibreELEC/linux-amlogic · GitHub