I opened this topic in order to place how to start LibreELEC with external media and install to eMMC.
ver Krypton 17
To write the image to the media (SD or USB)
Delete media file “dtb.img” For image versions with the suffix KVIM this item does NOT delite. File “dtb.img” should be on the media.
Rename the file “remote.conf.vim” in “remote.conf”
To activate the multi-boot using this media (as an option, using the launch application in Android “Update&Backup”, details are in the subject of Ubuntu). Start LE with external media, to verify and customize yourself. If you are satisfied, choose off menu item “Reboot to Install to eMMC”. The system will automatically install the LE in the internal memory (eMMC).
To work the remote control, you need to use the old version of the firmware (with Android 6). The new version of the firmware (with Android 7) changed the format of the processing codes for the remote control and this format is not compatible with existing images LE. Therefore, the remote LE will not work if you attempt to run LE on a version 7 Android. So for those who wanted to install the LE in the internal memory (eMMC), you need to have the firmware in eMMC with the previous version of Android 6. Only then, after the install LE in the eMMC, will operate the remote control.
LEIA 18
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).
If you have something specific to write about my LE build, you can write in this thread.
If you want to advertise CE - create a new topic and there can write what she wants.
This topic is about my build LE.
If you want to discuss CE-create your own theme and there you can write whatever you want. On this, the debate about CE in this topic are closed.
Pay attention all, this is the last issue of images Libreelec with the kernel 3.14 for the s9xxx. In the future, I stop releasing LE with kernel 3.14 and completely switch to using mainline kernel
@balbes150, you are unhuman
You’re a machine mate!
Thanks for your efforts.
Do you know by incident, how to avoid transcoding for DSD music files to PCM in Libreelec/Kodi? Sorry for asking so specific question, but I’m desperate
This is what I have discovered after more than a month of trying to get DSD native playback on Kodi and reading all the internet for Hi-Res playback and just to save some time in case someone else have plans to try it:
Kodi can’t passtrough DSD music by itself. Kodi only can play them by transcoding to PCM and the quality depends from the user configurations. Actually VIM can handle transcoding for all known DSD standards at “Low” (Low means fast real time transcoding in this case) from the Kodi settings. And can’t do smooth playback at High transcoding quality only for numerous top-end 256bit, 11289k bitrate tracks.
The workaround for playing DSD native or DoP (DSD over PCM) without transcoding in Kodi is possible only on Linux based installations of Kodi where actually Linux take control of playback for DSD files (MPD or LMS for example).
I installed your image, but I have some stability problems with the wifi, so I wanted to know if you took the amlogic wifi driver with your images or if it is vanilla.
If you don’t know, that’s fine, I will investigate more.
For firmware versions with DualOS is necessary to update u-boot. Files to update here. This must be done manually (for console UART).
I suggested to add support for multi-boot in the firmware (source code level) that would multiboot was download initially users didn’t have to do it, but don’t have it.
but why this way? isnt it possible to burn this with uboot ?
update 2: running marshmallow 20170303
this doesnt work for me. only the VIM logo shows up on screen
i use external reader (wit status led) nothin happens!
uart debug stops at:
InUsbBurn
[MSG]sof
Set Addr 15
Get DT cfg
Get DT cfg
set CFG
update3:
i’ve tried different android images same result
i’ve put all from the tar to sd card and set all the env var from the amt_autoscript but this causes a stop too:
“rsvmem check failed
ee_gate_on …
InUsbBurn
[MSG]sof
Set Addr 33
Get DT cfg
Get DT cfg
set CFG
”
update: i dont know why, but i did now set the envs from the aml_autoscript again and today it worked fine. i must have made a mistake yesterday
thank you!
Pay attention to use this version of the LE into VIM firmware Android 6 need, download and replace the file “dtb.img” on this option. Without a file “dtb.img”, this version of LE will not run on VIM.