Table of contents Summary Pre-boot tips Tips for when the systen is booted with shell Tips for when the system is up with Phosh Summary When porting a new device, you might (will) encounter some issues. It’s unlikely that everything will work fine the first time you boot, so strap in, read this document twice and enjoy your ride. Note that that this document assumes TWRP is the recovery used.

Summary Devices released before the treble/GSI move require a system image to be built because the default image will not provide the required libraries to the system. This guide should only be used for legacy devices (devices released without a vendor partition) which have an Android 9 port (device tree, vendor tree and kernel source). Any device released with Android 8.1 or later can use the generic system image provided in Droidian and skip the image creation guide.

Summary The stock Android kernel is unfortunately not enough to be able to run Droidian. The good news is, that on GSI-capable devices, often only kernel changes are necessary. Table of contents Summary Prerequisites Package bring-up Kernel info options Kernel adaptation Compiling Obtaining the boot image Committing changes Summary Droidian runs on Halium. If your device was launched with Android 9 or above, it is possible to port Droidian to it.

Table of contents Summary Prerequisites Package creation Building the rootfs Automating nightly images Summary After debugging you should start building a rootfs specific to your device to make installations more consistent and user friendly. This process involves creating an adaptation package and an apt repository. Adaptation package is a debian package that holds all the device specific configurations and custom binaries and scripts needed for the device to function correctly.