ubports / ubports-boot Goto Github PK

If you build a hybris-boot image while the ubports-boot source is in the Halium tree, the hybris-boot.img does not work as expected. It simply bootloops uselessly.

This does not seem to be related to the workaround for #2 and #1, since @vanyasem has not modified his device's fstab and instead changes the cmdline of built ubports-boot images to point them to the right data partition.

Currently we check for the file /data/.writable_image when deciding whether to remount the rootfs image as read-only or not. We should also check the rootfs itself for this image, so that OS developers may always have their rootfs read-write.

In our initramfs, block devices' friendly-named nodes (like mmcblk0p53) are placed in /dev/. In most other systems (Including Android and Halium proper), these nodes are located in /dev/block instead. If possible, we should change our behavior to be more like the others'. This would help us use scripts like Halium's fixup-mountpoints to solve issues with finding the userdata partition.

Currently we only check a device's default fstab to find the userdata partition. This causes problems since we don't have the appropriate drivers or config in place to have device nodes at /dev/block/by-name where most Android devices place them. Halium has a similar issue and solves it with the fixup-mountpoints script. We could just reuse that, except for #1 being an issue.

We need to create ubports-initramfs.gz from source, the issue now is that git does not preserve links so we need to do this in Android.mk on build.

A Halium build tree should, in theory, be able to make Halium images even though ubports-boot is present. This is not currently possible in the current implementation.

These are the issues that must be fixed to coexist in a Halium tree:

• #1 Block device nodes with friendly names should be in /dev/block rather than /dev itself
• #2 Write a better way to embed the /data partition
• #3 hybris-boot won't boot when ubports-boot is in the source tree

This issue should be closed when it is possible to build working ubports-boot and hybris-boot images from the same Halium source tree without modifying any device sources.

Halium developers have expressed concern that ubports-boot is shipped as binary blobs which are built into the initramfs. This is desirable so the initrd will be predictable between build configurations, however it makes sense to allow builds from source as well. Either change the configuration of ubports-boot so that it builds its binaries from source, or provide instructions so that other developers can do this.