¶ Porting guide
Bringing PeacockOS to a new phone means giving the build system everything it needs to produce and boot an image for that device. It all lives in the peacock-ports tree under device/.
¶ What a device needs
Look at an existing device, for example xiaomi-daisy on Qualcomm or oppo-a16 on MediaTek, and mirror its set of ports:
- A kernel port (
linux-<device>): the device kernel, forked and patched to boot PeacockOS, with its config. - A bootloader:
- Qualcomm:
lk2nd-<device>, the lk2nd secondary bootloader. - MediaTek:
minkernel-<device>, the MinKernel chainloader.
- Qualcomm:
- A recovery port (
prp-<device>): the device's PRP build. - Firmware (
firmware-<vendor>-<device>): vendor blobs the device needs. - A device definition (
<device>): the meta port that ties it together, covering partitions, flash method, display and quirks. - Display and quirk fixes as needed. The
samsung-jflteset is a good example of how many small fixes one device can take.
¶ Rough flow
- Get a working kernel for the device, mainline or a vendor fork, and turn it into a
linux-<device>port. - Get past the bootloader: lk2nd on Qualcomm, MinKernel on MediaTek.
- Build PRP for the device so you have recovery.
- Write the device definition: partitions, flash method, display.
- Build through the Peacock builder, flash, and work through whatever does not come up.
¶ Notes
This is an outline, not a step by step yet. The fastest way in is to read the ports for a device close to yours and copy its structure. Questions are welcome on the forum.