Let me make a few things clear to help stop this argument.
- The vim1 image I linked to was built on the Volumio server, based on @balbes150 work, with the addition of myVolumio functionality.
- This image was NOT meant to run standalone, it continues to use the afore mentioned multiboot principle.
- To get this image working on other boards, e.g. the vim2, can be done with the information @balbes150 supplied . All the other dtb’s are still there were they should be.
- This version will work on eMMC as well, again, using the information @balbes150 supplied to move the partitions to eMMC.
That said, yes, it would be nice to have a standalone version on SD or eMMC. Many Volumio users do not care to preserve Android and bought the vim1/ vim2 (and the new VIM3L) board for audio only. We would like to have the opportunity to supply such a version.
Also, last year @balbes150 built a version with kernel 4.18, which failed at the web interface. At that time we could not help, due to other priorities. I’m offering support now as this is a known problem with Volumio armv7 userland on an arm64 board with a mainline kernel. There is a simple solution for it, needs a few new kernel configuration settings and an addition to the volumio config build script. Succesfully done for odroid n2, rock64, sopine64, cubox pulse, nanopi etc.