Device Bring-Up
Guide

🌳 Do I Need a Special Tree?

🔄 LineageOS Tree vs CLO Tree — What's Different?

The main difference is that LineageOS trees use some AOSP components where CLO uses Qualcomm's QTI CLO ones.

But here's the thing — if you have a Qualcomm device, you're most likely already using QTI components for display, audio, etc. from stock. The one area where LineageOS trees commonly differ is the power HAL:

Start here. The goal is just to get your device to boot Flare.

Use our minimal bring-up template as a reference for your device tree:

Clean Up Telephony Lines

Delete any telephony lines from your device tree that are already defined in the Flare source. If they're defined in two places, you'll hit a build error. The reference above shows exactly which lines to remove.

Once you've done this, you should be able to build and boot Flare on your device.

Once your device boots, you can start switching over to proper QTI/CLO components for a better experience. This section assumes your device is already booting.

Should You Even Do This?

Only switch to a QTI component if something is broken. Examples:

• Telephony (calls/SMS) broken → switch to QTI telephony
• Audio broken → switch to QTI audio
• Bluetooth broken → switch to QTI BT

Switching the Power HAL (Lineage → QTI Perf HAL)

If you were using the Lineage power HAL (libperfmgr) for your first boot, here's how to switch to QTI Perf HAL properly.

You need to switch three things together:

1. Perf HAL blobs
2. Common QTI init files
3. Common QTI overlay

How to do it:

1. Open our device_qcom_common repo
2. You'll see two folders — system/ and vendor/
3. Check the init/, overlay/, and perf/ directories in both
4. Remove from your device tree any files that are already defined in device_qcom_common

For perf HAL specifically, the blobs are proprietary, so you also need to clean up your proprietary-files.txt:

1. Check the proprietary file list inside the perf/ directory of device_qcom_common
2. Remove any matching blobs from your device tree's proprietary list

💡 You can use AI to speed up the comparison — just paste both lists and ask it to find duplicates.

Reference commits:

Using Exclude Flags to Skip Blob Adaptation

Switching blobs can be tedious, and for some components you can actually skip it entirely using exclude flags.

Add any of these flags to your device.mk:

TARGET_EXCLUDE_QTI_PREBUILT_AUDIO := true
TARGET_EXCLUDE_QTI_PREBUILT_BT := true
TARGET_EXCLUDE_QTI_PREBUILT_DISPLAY := true
TARGET_EXCLUDE_QTI_PREBUILT_GPS := true
TARGET_EXCLUDE_QTI_PREBUILT_TELEPHONY := true

Or to exclude all common prebuilt blobs at once:

TARGET_EXCLUDE_QTI_PREBUILTS := true

After cleaning up your proprietary files list, you need to regenerate the vendor tree so everything stays in sync.

If you've done this before, you already know how. If not, don't worry — you don't need to fully regenerate blobs from a device dump.

1. Make sure you've fully synced the Flare source and cloned all your trees
2. cd into your device tree directory
3. Run the setup script:

./setup-makefiles.sh
# or
./setup-makefiles.py

4. Commit and push your vendor tree

Note: Unused blobs may still remain. That's fine for now. Later, learn full blob regeneration from a stock device dump.