A cincai Android fork based on LineageOS — built with love, duct tape, sarcasm, and occasional rage against jack-server.
Before we go all hardcore-cincai on your CPU, credit where credit is due:
- ❤️ AOSP — for allowing poor smartphone owner who cannot afford.. to get new device to build android upgrade using their code
- ❤️ LineageOS — for keeping AOSP alive and forkable.
- 🐧 Fedora Project — the only OS brave enough to handle this mess.
- 🤖 OpenAI / ChatGPT — for helping us fix stuff we broke without reading Stack Overflow threads from 2013.
| Label | Stage | Description |
|---|---|---|
| cincai | Stable | 💎 Official release. Tested, polished, and safe for your in-laws' phones. |
| almost cincai | Release Candidate | 🧪 Almost there. Good enough for daily use, but might still randomly vibe. |
| too cincai | Beta | 🐛 Expect some weirdness. We're experimenting... with feeling. |
| hardcore cincai | Development | 💥 Enter at your own risk. This is where dragons and dirty logs live. |
| peak-cincai | Bleeding Edge | 🚀 When this shows up, a major version upgrade is coming. Brace yourself. |
If you're new to ROM building, read this. If you're not — read it anyway.
Ubuntu users — you’ll get your own section below. Spoiler: it’s not flattering.
Click ==> Instruction to get the full list of packages needed and know How to prepare working environment
assuming that ~/android has been created,
cd ~/androidrepo init -u https://github.com/cincaiAndroid/android.git -b cc-23.2 --git-lfs
repo sync -c -j$(nproc)
repo sync -c -j28 --force-sync
🧠 Tip: If you have a Ryzen Threadripper — go nuts with -j32 or -j64.
With a proper SSD and net, syncing takes under 20 mins.
Just don’t be like that YouTuber Gary Explains, who synced AOSP on a 2-core laptop and called it a tutorial. 😵💫
. build/envsetup.sh
lunch <your_device_codename>
make bacon
Or:
brunch <your_device_codename>
The following is an example of how a device tree is structured...
OnePlus 7 Pro
device/oneplus/guacamole
device/oneplus/sm8150-common
kernel/oneplus/sm8150
hardware/oplus
vendor/oneplus/guacamole
vendor/oneplus/sm8150-common
🧠 Need Help with Non-AOSP Devices?
Building for officially supported AOSP devices is basically copy + paste + vibes.
But if you’re working with something unlisted, cursed, or forbidden, you’ll need serious help.
💡 Advice: Keep ChatGPT open.
It knows:
How to fix broken extract-files.py
How to patch broken BoardConfig.mk
Where to shove missing blobs
Why your tree fails without any error
ChatGPT won’t judge you. But it will save your build.
🙅♂️ Ubuntu? Not Recommended.
"What’s wrong with Ubuntu?"
Ohhh nothing… except:
Old toolchains
Missing packages unless you summon PPAs from Mordor
Weird Python symlinks
Broken build tools unless you babysit them
The cincaiAndroid team officially recommends:
✅ Fedora — the smoothest Android build experience.
🟡 Mageia — if you’re feeling French.
❌ Ubuntu — if you’re feeling lucky (or enjoy pain).
If Mageia is too much and Fedora too scary, please:
🧸 Visit the Ubuntu Forums.
🧙 Our devs are not trained in apt-induced trauma.
🧾 Legal Disclaimer
cincaiAndroid is not affiliated with LineageOS, crDroid, Google, or your warranty.
Everything here is provided cincai-cincai and without guarantees.
Flash responsibly.
“Building AOSP is easy. Building for your obscure 2018 Mediatek phone is Cincai ... cincaiAndroid might lead you to a discovery”
---