Update. Somehow LE sees only 761MB. No wifi with M3 image.
there are two reasons either not the correct dtb, or you actually have 1 GB of RAM in the TV box (no matter what the regular Android firmware writes, it was specially "taught" to lie)
Posts by balbes150
-
-
check/alter data_to_emmc_uEnv.ini(in BOOT) to fit the same dtb file working for you with sd card
This file is not related to eMMC installation. In eMMC you use a shared file "uEnv.ini". Therefore, you must configure this file for eMMC to install correctly. The file you specify is used to start the system from external media and to place all data in the eMMC.
2. boot to libreelec from your card
3. choose the libreelec icon in settings and navigate to services
Between these items, I strongly recommend that you create a full backup (the menu item to create a copy is located in the same place, just below the installation). This allows you to always return to the current state of the system. By the way, creating a full copy can be useful before any updates. If something does not suit the new system, you can always return to the exact (with all the settings and other) current state of the system. Please note that the process of creating a copy can take up to 20-30 minutes. You can store files with backup archives in a safe place to have many different copies. The created copy is stored in the "/storage/backup/ddbr"directory. You can easily copy it to your PC (via network). Please note-in this case, a full copy of eMMC is created along with the boot loader and all other elements, regardless of what is installed in eMMC (Android or Libreelec or other system).
Importantly. Installation, Backup, and Recovery work only from external media.
added the working LE 8.0 dtb
From which specific version of the image are you trying to use dtb ?
-
1. If I install your LE version to eMMC (and erase the Android OS), then update settings on it, how can I then copy back this .img LE version to USB/SD card ?
To return to the previous system in eMMC, you must run LE from external media before installation and perform a full backup via the "Libreelec/Service/eMMC/Create backup"menu item. The backup process can take up to 20-30 minutes (depending on the eMMC and the speed of the external media). After that, you can restore the state of the system at any time when the copy was created. Start the system from external media and perform the reverse procedure (restore from backup). Please note that the creation and restoration of a full copy of the eMMC must be performed by the specified commands (or by running scripts via SSH). Do not confuse this option to create a backup with options for backup for KODI is a totally different function.
2. I only saw Khadas Vim section under the Add-ons folder link. Has the arm vs aarch64 problem been solved for Kodi Add-ons on other TV box models too?
all add-ons for the aarch64 version apply to all models that run the selected image
Is there a solution to the AV problem at least?
I do not have such equipment, so I do not test it
Can I use this with my Nano Pi K2? Which file should I use and which device tree file will work with my board?
Thank you very much 🙏
Maybe it s905 (you can try option 2 for wetek_play)
I've got the 812 version running on a tronsmart s89, thank you for that.
Only question is where are the CEC controls, will they return?Questions s812 should be placed in the relevant subject. This theme on s9xxx
Is the aim of this thread to test ports of LE v9 on Amlogic devices, essentially picking up where kzsaq left off? Or are the builds using LE v8, with Kodi v18 installed instead of v17?
These versions are not extensions of the Kszaq images. This is the result of merging the work of many developers with my additions.
-
Hi Balbes, Please assist every time that tried to write into emmc fails
For now, you need to use version kernel 3.14. Be sure to update the multi-boot. New versions only work with the new multi-boot. Only after that, you will be able to install and run LE in eMMC. To completely clean up the old version of LE (17.6), use the install mode with Android erase.
-
Together with chewitt managed to build and publish Addons for aarch64:
The new version (20181019) of the image with the kernel 4.18 aacrh64 with updated addon location:
-
I don't remember that, but then I don't remember lots of things. I keep the arm repo up to date so no harm in using it. If you want to keep building aarch64 it's best to create another repo though. I can setup some webspace if you need it - ping me in Slack.
Ok
I installed successful,but the IR remote controller failure.
... and the version of the image LE we need to guess ...
Here still waiting for some test image for S905 processor with 4.18 kernel
Are there plans for the same?
balbes150
Thank you if you can respond!The 4.18 kernel version is available for testing and details are available in this thread earlier, or you can find more details on the Khadas forum.
-
It's because balbes150 persists in creating "aarch64" images and the image is probably still configured to point at the "amlgx" repo that I maintain which only contains "arm" addons. No bug, and I have no intention of building aarch64 stuff
@chwitt You yourself asked to disable the amlgx repository in m'y test images (4.18).
Or can I enable it now ? @chwitt mentioned that if necessary, I can use a share to host images or Addons. I plan to soon master the build of Addons for aarch64 (if I can't get kicked out of the community LE)
-
New kernel image 3.14 (20181008). By default, when you select the menu item "Libreelec->Services - >Install to eMMC", the installation option is executed in eMMC with full saving of the regular Android. This means that if you select "Reboot from Android" in the shutdown menu, the system will be rebooted and the regular Android will be started. For a "clean" installation in eMMC (with the removal of the standard Android), you must first rename the script "erase_android_install2emmc.sh" to "install2emmc.sh". In this case, all data from Android in the "/dev/system" and "/dev/data" sections will be erased and Librelec will be written instead.
Please note that for the correct operation of the installation in eMMC it is necessary to update the universal multi-boot using these images.
To properly start the system with the desired DTB option, you now need to edit the file "uEnv.ini" (edit the file name that will be used at startup).
-
New image 20181005 kernel 3.14.
Fix install to eMMC. -
downloaded aarch64 images which i installed to my SD.
what image have you tried ?
I just did a fresh install to external drive which was fine, but I could find any addon such as PVR, I got message like system cannot connect to repository, is there a way to side load Libreelec repo?
Wait for psychics who will guess what model of TV box you have, what version of the image and so on.
-
Please note that for the correct operation of the new installation system in eMMC it is NECESSARY to update the universal multi-boot using the latest LE image. To update the universal multi-boot, you can use either the toothpick method or by running the Android application (local update using the archive "aml_autoscript.zip"). Without this procedure, after you install LE in eMMC, LE will not start, would only run regular Android.
-
I am using the latest image LibreELEC-S912.arm-9.0-devel-20180920164743-905fd26.img.
I put a link to the dtb as part of the name in the last post.There is no such file in the image. Therefore, it is built outside the source kernel that is used in the image and will not be able to work with it.
Edit : I tried to manually test your install2emmc script via ssh
The first command fails
Show the entire output of the script. The specified error may not be critical (in some cases). What system is installed in eMMC ?
-
I just installed your new build to emmc (after doing backup with your implemented).
The system shut down, then it restarted OK direct to LE.
But I have no "reboot to Android" in power off menu.
Any idea?
1. What model of TV box ?
2. What is the version of the LE image used ?
3. Write in detail the steps you did.
I decided to give this a test and initially was able to boot up from the SD card successfully but I noticed that whilst I had WiFi, there was no Ethernet connectivity shown.
So I swapped out the q201 2g dtb with the one that I had previously been using that has ethernet (gxm_q201_2g_1gbit.dtb) but then unfortunately it would not boot at all.1. The version of the image LE ?
2. Where did you get this dtb (gxm_q201_2g_1gbit.dtb) ?
For all.
When asking a question, be sure to specify the version of the LE image that you are trying. Without specifying the version of the image, there will be no response.
-
A very interesting option to run LE and Android in parallel from eMMC but my question is what is the procedure for switching between the the two?
Since the regular Android does not know how to work with other systems, it is implemented through the menu item in LE. Start LE and the selected item in the menu off "Reboot to Android".
-
New images 20180920 (kernel 3.14).
I draw attention to the changes. Now the process of installing the system in eMMC has changed. The default install of the additional copy of the LE at eMMC without uninstalling regular Android. Now, to install LE in eMMC, there is a special menu item in "Libreelec->Services->eMMC->Install to eMMC". When you select this menu item, LE will be copied to eMMC in parallel to Android (Android is fully saved and can be used). Also in the new images added two menu items to create and restore a full copy of the eMMC on external media (along with the bootloader, settings and all data). I recommend that you make sure you create a full copy of eMMC before installing LE on eMMC. Depending on the type of external media and how busy eMMC data is, the backup process can take anywhere from 5 to 30 minutes. After the copy is created or restored, the system automatically shuts down. It is not recommended to use the system during creation and recovery (to reduce the risk of errors). For those who want to install LE in eMMC with delete Android, you need to rename the script on the external media beforehand "full_install2emmc.sh" to "install2emmc.sh", start the system from external media and also select the item in the menu. The system will execute the installation LE to replace eMMC with Android on LE.
-
Update image LE 20180902 kernel 4.18 (for s905x).
-
Test version 20180902.
This version includes HW hardware acceleration (including 4K). But when testing on my MXIII Plus I see one bug. If you try to stop the video file from playing or the file reaches the end, the system freezes. Perhaps it is a feature of my particular model of TV box (lately, I've noticed various oddities in his behavior). If anyone has the opportunity, please check the work of this option and write the result.
No offense, but you guys are posting/asking/suggesting things I already mentioned in my post.
In the current version of the kernel S812 no support for the remote control.
-
can you rebuild dtb.img for box : Dune HD Sky plus "S905D" ?
In theory, this is possible, but there is not enough time for everything.
If you have not run LibreElec on your M8S before, then you need to first activate multi-boot from an image written to USB (you only do this once)
To activate the multi-boot for s8xx need SD card. After a single activation, to run images , you can use any type of storage media - SD card and USB flash drive.
can you make a 64bit build for Odroid C2 ? I am having adamg's latest coreelec build.
I want to upgrade it to your build and test if the video stuttering problem is solved.
Specifically for the Odroid C2 I do not release the Assembly. There is a universal version for aarch64 S905.
Is it possible for you to just look at the LibreElec remote.conf and mxq repo for many such files?
It takes time and test equipment to convert these files to the new format. I don't have that right now.
2. Does installtointernal (to eMMC) eliminate remote.conf incompatibility for IR remotes with your generic S905/X/W Kodi 18alpha builds?
This data is not compatible for direct use and requires additional processing..
To all update image kernel 3/14 20180831
