Help with vendor and device files building e/OS/ for FP6

Using /e/OS Build /e/OS
, ,
2

as they are not yet shared on the muppet repo, you will have to extract the proprietary vendor blobs from the device or from an official /e/ build and add them into the /vendor/fairphone/FP6/ folder

.

for an officially supported device, just running breakfast FP4 must download the missing files

.

but you can also :

clone the repo using a terminal from the /device/fairphone/FP6/ folder and from the /kernel/fairphone/FP6/ folder

or

download the sources code .ZIP from the repo and extract its content into the /device/fairphone/FP6/ folder and into the /kernel/fairphone/FP6/ folder

or

compose a /.repo/local_manifests/FP6.xml to point to the device specific repos,

proposition (mix of steadfasterX and /e/ manifest ) 
<?xml version="1.0" encoding="UTF-8"?>
<manifest>

    <!-- KERNEL
    #####################################################-->
    <project path="kernel/fairphone/FP6" name="/e/devices/android_device_fairphone_FP6-kernel" remote="e" revision="a15" />

    <!-- DEVICE TREES
    #####################################################-->
    <project path="devices/fairphone/FP6" name="e/devices/android_device_fairphone_FP6" remote="e" revision="a15" />
    
    <!-- modifications regarding Lineage (to build /e/ from /e/ sources repo) 
    #####################################################-->

  <remove-project path="device/qcom/sepolicy_vndr/sm8650" name="LineageOS/android_device_qcom_sepolicy_vndr" groups="qcom,lanai-vendor" revision="lineage-22.2-caf-sm8650" />
  <remove-project path="frameworks/opt/telephony" name="LineageOS/android_frameworks_opt_telephony" groups="pdk" />
  <remove-project path="hardware/qcom-caf/sm8650/audio/agm" name="LineageOS/android_vendor_qcom_opensource_agm" groups="qcom,lanai-audio" revision="lineage-22.2-caf-sm8650" />
  <remove-project path="hardware/qcom-caf/sm8650/audio/pal" name="LineageOS/android_vendor_qcom_opensource_arpal-lx" groups="qcom,lanai-audio" revision="lineage-22.2-caf-sm8650" />
  <remove-project path="hardware/qcom-caf/sm8650/audio/primary-hal" name="LineageOS/android_hardware_qcom_audio-ar" groups="qcom,lanai-audio" revision="lineage-22.2-caf-sm8650" />
  <remove-project path="hardware/qcom-caf/sm8650/audio/graphservices" name="LineageOS/android_vendor_qcom_opensource_audioreach-graphservices" groups="qcom" revision="lineage-22.2-caf-sm8650" />

  <project path="device/qcom/sepolicy_vndr/sm8650" name="e/os/android_device_qcom_sepolicy_vndr" groups="qcom,lanai-vendor" revision="a15-caf-sm8650" remote="e" />
  <project path="frameworks/opt/telephony" name="e/os/android_frameworks_opt_telephony" groups="pdk" remote="e" revision="v1-a15-FP6" />
  <project path="hardware/qcom-caf/sm8650/audio/agm" name="e/os/android_vendor_qcom_opensource_agm" groups="qcom,lanai-audio" revision="a15-caf-sm8650" remote="e" />
  <project path="hardware/qcom-caf/sm8650/audio/pal" name="e/os/android_vendor_qcom_opensource_arpal-lx" groups="qcom,lanai-audio" revision="a15-caf-sm8650" remote="e" />
  <project path="hardware/qcom-caf/sm8650/audio/primary-hal" name="e/os/android_hardware_qcom_audio-ar" groups="qcom,lanai-audio" revision="a15-caf-sm8650" remote="e" />


    <!-- PROPRIETARY VENDOR (not yet available)
    #####################################################-->
#    <project path="vendor/fairphone" remote="github" depth="1" name="TheMuppets/proprietary_vendor_fairphone" />
    
    <!-- /e/ vendor repo (to make a custom build using steadfasterX method)
    #####################################################-->
    <project path="vendor/e" name="steadfasterX/android_vendor_e" remote="e" revision="main" />

</manifest>

and then run repo sync again.

.

my entry will be reading README.md · main · steadfasterX / android vendor e · GitLab
it is a fantastic and flexible way to make “CUSTOM” /e/ builds
(be carefull about the missing / in </manifest> at the end of his local manifest exemple)

07: Building an e ROM the Repo Sync way · Wiki · e / documentation / A Generic Guide on porting eOS · GitLab

How-To: Building an /e/OS ROM the Repo Sync way for an unsupported device using LineageOS sources

Ultimate how-to guide: Unofficial Builds using repo style for using lineage or other aosp sources that are not supported by /e/OS

also have a look at /e/ official manifest :
FP6.xml · a15 · e / os / local_manifests · GitLab

2 Likes