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.
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.
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.
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.
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
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).
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).
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.
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.
sorry for noob question - but ..
will the image run from sd card and let android untouched as any other libreelec imageor 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.
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
you can compile the aarch64 for s912 version ? Thanks.
To do this, need to collect "libhibris" in aarch64 mode. But such version not.
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
How to increase gpu clock rate in s905x boxes?
What for?
What steps i need to install on usb flash drive?
What system is now in eMMC (what kernel and dtb are used in it) ? Depends on whether or not you want to add a separate dtb to the LE image.
I have a emmc 32gb attached to my odroid c2. Is it possible to install your build on my emmc?
I recommend that you first run the test LE-KODI-18 from an external USB drive. If everything works correctly (all the functions you need will work), you can easily migrate this system to eMMC. Do you have any USB flash drive > 2GB?
Hi is this working on odroid C2?
It's possible. There is no built-in u-boot as part of the images, so additional steps are required to run on the Odroid C2 and LePotato models. Depending on the launch plan, you need to take different steps. For example, you can have a basic SYSTEM (it can be any system - Linux, Libreelec etc) in eMMC and run this test Le image from SD or USB stick (without changing the existing system in eMMC). Ie. please note: if the eMMC runs full-time system from eMMC if I connect a external storage with SD card or USB flash drive, at power-up will automatically start the system with these carriers. I described one possible use case. There other SD + USB or SD only. Write, what option you are planning to use and I will write what steps need to be additionally done.
Added a version of the image for KVIM assembled in "arm" mode (32 bits). In the near future, i'm adding a similar option (arm) and For the s905 version.
To test this version myself (arm and aarch64), I found that the version of "arm" noticeable increased load on the CPU and higher heat TV boxes. I'm ask those who have the ability to compare the behavior of arm and aarch64 versions to estimate the load and heat.
For those who want to simplify the process of adding support for your remote, I suggest to send me the settings files (to include them immediately in the image). This will allow you to easily (simply rename the file in the shared directory), immediately turn on the desired remote control.
1.
This thread is for discussion of LibreELEC images created by myself. If you prefer to use another OS, please keep discussion about that OS in other forums. Off-topic posts about other OS will be deleted to moved to other threads.
2.
The start system in Coreelec is not compatible with LibreELECE Armbian etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
I'm not interested in "opinions" about which system is better or worse. Want to discuss it - create your own theme.
I'm not interested in advertising other systems. Want to discuss it - create your own theme.
I'm not going to persuade anyone to use any system. Everyone decides what to use.
Test images LibreELEC KODI-19 for platform Amlogic S9xxx
To start the system from external media, you must use a universal multi-boot. This variant of multi-loading system is fully compatible with Armbian etc systems for TV boxes.
Please note that the DTB configuration order has changed.
Now a single configuration method is used for all Rockchip Allwinner Amlogic platforms. The file (uEnv.txt) is used for configuration DTB all platforms.
Now a single configuration method is used for all platforms, using the file (uEnv.txt). You need to edit this file to configure it. You need to uncomment the two lines that are responsible for your platform and specify the correct DTB for your model. If you use this image to run on the one platform, you can delete it from the settings file (uEnv.txt) strings from other platforms.
Pay attention. Starting from version 20200826, the configuration order for the used DTB changes.
Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", is now used the file "/extlinux/extlinux.conf " . The rules for editing a file remain the same.
You no longer need to manually add the u-boot.ext file , it is included in the image.
Pay attention.
The installation algorithm in eMMC has changed. My recommend that you perform a clean installation in eMMC. Be sure to make a full backup of eMMC before installing it in eMMC.
For this purpose, the universal multiboot for AML has been updated. For the system to work correctly on AML, you need to update the multiboot.
Fix for correct color to G12
For models based on g12 (s905x2 s922), which have a problem not the correct color , to SD card to write the image and rename u-boot.sd to u-boot.ext, to USB to write the image and rename u-boot.usb to u-boot.ext
Important. Changed the directory location of the images. Now all images (for all supported platforms) are in one place.
Important information. Starting from the date 20200327, the order of updating the system via the TAR archive changes. Now all images are divided into two groups (directories on the site) G12 and RK+AW+AML. Each group has a single TAR file, which is intended for updating all images from this group. I no longer release separate TAR files for each hardware variant. The TAR file is universal for all models in its group. Expanded the list of images for initial launch (writing to external media). The amlgxbb image is optimized for models with the s905 chip (in the future, it will be added to the EMMC installation mode for the s905). Currently supported installation in eMMC via the GUI is Kodi interface for s905x\s912\s905x2\s922x rk3328\rk3399 H6.
Please note that before installing in eMMC, you must create a full backup of eMMC. this will help in case of problems during installation, or you can return to the current state of the system in eMMC before performing the installation. Important. For the installation to work correctly in eMMC, you must update the universal multiboot to the latest version using the image from which you start the installation, i.e. before starting the installation re-activate the multiboot.
Creating a full eMMC backup is easy. Deploy the latest LE system from this theme (or Armbian) on any good media (SD card or USB media). The size of the media (SD card or USB flash drive) is selected depending on the EMMC data filling. For example, to create a full compressed copy of eMMC standard Android, media size of 8 GB is sufficient. Start the system on the TV box and in the LE settings menu, select work with eMMC and create a copy. The copy creation procedure starts, and the system shuts down automatically when it is complete. Depending on the parameters of the data size and speed of the media where the backup is being copied, the time may take approximately 5 to 40 minutes. After creating a copy, it is recommended to save the copy file in a safe place (PC, NAS, additional USB flash drive, etc.). The created copy file is located in the directory (/storage/backup/ddbr). When using Armbian with DE, the DDBR utility is used to create a copy (select the compressed copy option). Ease of using Armbian to create a copy, you can clearly see the entire process of creating a copy with progress indicators, and after creating a copy, you can immediately launch the browser from Armbian and place a copy on a shared resource. The copy in Armbian is located in the directory (/ddbr).
Chewitt is the official maintainer of AML, so its test images should be considered as "official" and discussed in the appropriate topic (which is specially created for such discussion). This topic only discusses images that I create. Please note that the official versions and my versions have a significant difference in the launch methods, settings, and functionality, so information about them should be placed in different topics (so as not to confuse users who try to use different images with incorrect configuration and management steps). We kindly ask everyone to correctly place your information in the appropriate topics, do not create unnecessary problems for others.
