I think it’s notable their repo kernel merges tags (e.g. LA.UM.9.16.r1-16900-MANNAR.QSSI15.0) from a stable msm kernel at codelinaro - instead of waiting to get this code through GPL’ed Motorola repos (what I used to see on older Motos).
Do you have some automation in detecting new LineageOS releases or is it just you browsing the ROM category each per devices on XDA?
hi Ronz98,
i have successfully build myself lineageos for fogos. Now i’ve tried to build e.os because on fogos the esim does not work correctly for me and on you build it does. May you help me?
First do you have any idea why the esim works flawless with /e/ and does not on lineageos?
Then i try to build /e/ with your guide but when building i get this exception, but the lib exists already in the hardware/ folder:
============================================
[100% 1/1] analyzing Android.bp files and generating ninja file at out/soong/build.lineage_fogos.ninja
FAILED: out/soong/build.lineage_fogos.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build")" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build")" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/so
ong" --out "out" --soong_variables out/soong/soong.lineage_fogos.variables -o out/soong/build.lineage_fogos.ninja --globListDir lineage_fogos --globFile out/soong/globs-lineage_fogos
.ninja -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.lineage_fogos.build Android.bp
error: vendor/motorola/sm6375-common/Android.bp:9183:1: "libril-qcril-hook-oem" depends on undefined module "libril".
Or did you mean ["libdl" "libgbl" "libgif" "libgsl" "libhidl" "libidl" "libiio" "libjail" "libkcl" "libkll" "libmio" "libnix" "libnl" "libqisl" "librcc" "libring" "libruy" "libryu" "libssl"
"libui" "liburl" "libvixl" "libxml" "libzip"]?
fatal errors encountered
08:25:30 soong bootstrap failed with: exit status 1
Third there are many tags for releases for /e/ but i cannot find any documentation what is the difference of these tags.
And fourth, in your build the geekbench benchmark results are 30% lower than on original moto rom. I’ve already provided a fix here
Just in case you are building new versions.
I did not yet have this error message.
You can try to setup new e-environement for A14:
repo init -u e / os / android · GitLab -b v1-u --git-lfs --no-clone-bundle
then
repo sync
Did you use A14 based sources for fogos?
Which /e/OS version of mine did you use? I need to check, I think I made 2 different version using different sources (need to check that again).
hi Thanks a lot, i will try another /e/os version.
But what is the difference between a14, rc.2-t, t, rc-s, rc-u, etc. in the tags.
I Guess that the prepending v2.7, v2.6.2, v2.6.3, etc. is the /e/Os version?
a14 is a synonym for U, rc stands for release candidate. Also there are beta version.
I prefer final versions like 2.7 or the current one 2.8
If you want to have a certain version you can use this (here: 2.7 U)
repo init -u e / os / 🚀 Releases · GitLab -b refs/tags/v2.7-u --git-lfs --no-clone-bundle
This is for latest version:
repo init -u e / os / android · GitLab -b v1-u --git-lfs --no-clone-bundle