Manifest for GX290 Lineage 18.1

[schoeller]

Dear all,

thanks for your work.
I am trying to compile for the GX290+ and lineage 18.1. Compiling for 19.1 works. What I have tried so far is:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <remote name="gs290-dev" fetch="https://github.com/GS290-dev" revision="lineage-18.1" />
  <project name="android_device_gigaset_GX290-unified" path="device/gigaset/GX290-unified" remote="gs290-dev" />
  <project name="android_device_gigaset_mt6763-common" path="device/gigaset/mt6763-common" remote="gs290-dev" />
  <project name="android_kernel_gigaset_mt6763" path="kernel/gigaset/mt6763" remote="gs290-dev" />
  <project name="android_kernel_gigaset_gx290" path="kernel/gigaset/gx290" remote="gs290-dev" />
  <project name="proprietary_vendor_firmware" path="vendor/firmware" remote="gs290-dev" />
  <project name="proprietary_vendor_gigaset" path="vendor/gigaset" remote="gs290-dev" />

  <project name="android_packages_apps_MtkFMRadio" path="packages/apps/MtkFMRadio" remote="gs290-dev" />
  <project name="android_device_mediatek_sepolicy_vndr" path="device/mediatek/sepolicy_vndr" remote="gs290-dev" />
</manifest>

Unfortunately it throws the error:

Makefile:3488: error: BOARD_AVB_RECOVERY_KEY_PATH must be defined for if non-A/B is supported. See https://android.googlesource.com/platform/external/avb/+/master/README.md#booting-into-recovery

Lateron I would like to update the recipe for e/OS/.

Any hints on how to proceed are highly welcome.

Kind regards

Sebastian

[nift4]

Ahoy, you need to pick this commit: GS290-dev/android_device_gigaset_mt6763-common@bf9c41d

[nift4]

Also be warned that you need to pick those commits to have FM radio working
https://review.lineageos.org/q/topic:eleven-mtk-fm

[schoeller]

@nift4 thanks for the sound reply at lightning speed. My nooby question in return: is there any way to pull a particular commit from within the local_manifest.xml?

[nift4]

well no, you need to fork the repo and pick the commit onto the branch because that commit is inside the android 12 branch. the proper solution would be to pick an build system change but that will only benefit you if you have the OEM keys (these trees originate from paid work by Volla)

[erfanoabdi]

as main developer of this trees i'm adding a small note here
this trees can be used as personal usage by everyone but /e/ developers for any kind of commercial usage
https://github.com/GS290-dev/local_manifests/blob/main/NOTICE

[schoeller]

@nift4: Hey, managed to cherry pick as pointed out in 1#. Have forked android_frameworks_av as indicated in 2# without commits first, but local manifest not working yet. Subsequent error is thrown:

error: frameworks/av/apex/Android.bp:90:15: unrecognized property "use_vendor"
error: frameworks/av/media/ndk/Android.bp:127:1: unrecognized module type "llndk_library"
13:05:42 soong bootstrap failed with: exit status 1

Any hints highly welcome.

[nift4]

Good question - no idea. It all looks correct to me. Are you 200% sure you are in the android 11 folder?

[schoeller]

Good question - no idea. It all looks correct to me. Are you 200% sure you are in the android 11 folder?

Works after having used repo sync --current-branch --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j$( nproc --all )

Below recipe seems to be working

repo init -u https://github.com/LineageOS/android.git -b lineage-18.1
repo sync --current-branch --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j$( nproc --all )
mkdir .repo/local_manifests
curl https://raw.githubusercontent.com/schoeller/local_manifests/main/gx290.xml > .repo/local_manifests/gx290.xml
repo sync --current-branch --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j$( nproc --all )
ccache -M 50G
export LC_ALL=C
source build/envsetup.sh
lunch lineage_GX290-user
mka bacon

[schoeller]

as main developer of this trees i'm adding a small note here this trees can be used as personal usage by everyone but /e/ developers for any kind of commercial usage https://github.com/GS290-dev/local_manifests/blob/main/NOTICE

@erfanoabdi: Thanks for your work. Is there any chance that it will end up one day in LineageOS repo and thus eventually be available one day in LineageOS for microG through OTA update?

[erfanoabdi]

as main developer of this trees i'm adding a small note here this trees can be used as personal usage by everyone but /e/ developers for any kind of commercial usage https://github.com/GS290-dev/local_manifests/blob/main/NOTICE

@erfanoabdi: Thanks for your work. Is there any chance that it will end up one day in LineageOS repo and thus eventually be available one day in LineageOS for microG through OTA update?

we're using some leaked and illegal codes so it's not gonna be acceptable by official lineage right now

Maybe someday.. I'm not sure

[schoeller]

as main developer of this trees i'm adding a small note here this trees can be used as personal usage by everyone but /e/ developers for any kind of commercial usage https://github.com/GS290-dev/local_manifests/blob/main/NOTICE

@erfanoabdi: Thanks for your work. Is there any chance that it will end up one day in LineageOS repo and thus eventually be available one day in LineageOS for microG through OTA update?

we're using some leaked and illegal codes so it's not gonna be acceptable by official lineage right now

Maybe someday.. I'm not sure

Thanks for your reply. Do you know of any Lineage-based distribution for GX290 with microG included and OTA server attached?