[Walkthrough] device.xml for local_manifests

/e/ has a few in stock https://gitlab.e.foundation/e/os/local_manifests/-/tree/v1-r?ref_type=heads.

Supported devices (LineageOS or /e/OS) when built produce roomservice.xml saving these to some location might be useful, as done once before Place for manifest.xml samples.

But it is really for an unsupported device this technique will be useful.

Someone might try to “work the example” proposed https://gitlab.e.foundation/e/os/docker-lineage-cicd/-/tree/master#build-for-a6000-not-officially-supported-custom-keys-restricted-signature-spoofing-with-integrated-microg-and-fdroid as that example is difficult to follow if one had not practiced the method.

Thanks to @smu44 in the post below. Only understanding the creation of the a6000.xml

is of use to /e/OS learners !
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="dev-harsh1998/android_device_lenovo_a6000" path="device/lenovo/a6000" remote="github" />
  <project name="dev-harsh1998/android_device_lenovo_msm8916-common" path="device/lenovo/msm8916-common" remote="github" />
  <project name="dev-harsh1998/kernel_lenovo_msm8916" path="kernel/lenovo/a6000" remote="github" />
  <project name="dev-harsh1998/proprietary-vendor_lenovo" path="vendor/lenovo" remote="github" />
  <project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
</manifest>

The example carries on with LineageOS method.

3 Likes