Thank you @andrelam, your post makes it clearer to me what’s in the game of building /e/ (and LineageOS)
And i’ve finally seen that my note4 (snapdragon) is trltexx while note4 (exynos) is trletexx: these are very different names 
i’m gonna try building /e/ for trltexx in the next days and let you know how it goes
nice article! I’ll read it again because I’m not use to it
Thank you very much. Really nice and descriptive article despite that you write that is not an A - Z guideline is extremely useful. Now I’m building /e/ for Motorola Sanders (Motorola G5S Plus) lets hope it works. If everything goes well I’ll publish it just in case someone like me need it.
Hi zerohasherbn,
did you manage to get a working build for the Moto G5S Plus?
I’m in no position to build it right now, but at the point of deciding what to firmware to flash my G5S Plus with.
Graphene doesn’t appear ready. Done Lineage already on previous Moto G2, and if can’t get /e/ build will go back to Lineage and deGoogle it: https://old.reddit.com/r/LineageOS/comments/cl5c90/degoogling_lineageos_instructions_august_2019/?st=jzit8h5p&sh=96bc42ff
hi @andrelam , your thread his very intersting and i managed to build /e/ for codename davinci device but my desktop OS is under linux solus and this OS repo lack some dependencies so i ask if you can build it from those device repositories ? It’s an unofficial lineageOS build . Thank a lot for reading and hope answering and fingercross can do it 
For uncompatible but Treble-enabled (Shipped with Oreo or more recent) devices, you can also check the topic about the GSI :
@andrelam, is it possible in your opinion to do this for Raspberry pi 3B+ for an x86 ARM processor? I am eager to try. Also, I am wondering how long it took you to do the build? What were the specs of your virtual machine? I have one with 4 cores and 16GB ram, hoping that’s enough… Or is it in system memory? I could increase that to 50 gb if necessary anyway!
If you will find lineageOS sources for the Rpi or any other sources you can try.
But as far as I know, there are no x86 sources available
Thank you very much. I will try compiling sources today!
I would really appreciate if anyone could help with dropping links here… Thanks!!!
What kind of links do you mean ??
As in software I will need to compile to create /e/ for RPi 3B+.
I think everything is described in the builde.sh from first post
Thank you. I’ll just use it I was trying to use docker but now it feels a little futile… RPi doesn’t have a codename that I know of
Hi,
I’ve just tried to build /e/ (BRANCH_NAME=v1-pie, DEVICE_LIST=a70q) for Samsung Galaxy A70 by strictly following this guide and after several hours I got this error on the linux terminal:
[sáb nov 16 04:08:32 CET 2019] Missing “vendor/lineage”, aborting
And in the log file I found:
error: Cannot checkout e/os/android_device_lineage_sepolicy: ManifestInvalidRevisionError: revision v1-pie in e/os/android_device_lineage_sepolicy not found
error: in sync -c --force-sync: revision v1-pie in e/os/android_device_lineage_sepolicy not found
Any idea on how to fix this error? Any help would be much appreciated.
I’ve used repos from https://forum.xda-developers.com/galaxy-a70/development/rom-lineageos-16-0-t3968893 (unofficial ROM LineageOS 16 for Galaxy A70)
For the first try I used all the repos and manifest you can find in the previous URL. For the second try I used only the propietary, kernel, device, android_pacakges_resource_devicesettings and a manifest similar to that included in this guide. For both builds I got the same abovementioned error.
An additonal thing that catched my attention in the build process was that in some moment the build script asked for the username and password for [https://gitlab.e.foundation’:]
is that strictly needed? Do we have to register in /e/gitlab to succesfully build? I jus pressed enter for both username/password, the process continued…
Thank you very much for your help
Best regards,
I can’t find this repo on gitlab.e.foundation … Maybe it’s on lineage repo’s and there is no v1-pie branch. Can you post screenshot of manifest file?
Hi,
Thank you @andrelam
As you mentioned, as I didn’t find e/os/android_device_lineage_sepolicy on gitlb.e.fodundation but I found it on LineageOS/android_device_lineage_sepolicy, I launched a find and grep on my local working directory to find that string, and I found a match on src/PIE/.repo/manifests/snippets, so I replace the affected line in the following way:
I then re-launched the build script and the build process seemed to continue OK. As I running it on a old ubuntu laptop it is taking too, too long.
Do you think this ‘fix’ is ok?
Thank you for your support.
Btes regards,
in my previous post the ‘diff’ output was cut. It is the following: I replaced the line:
project path=“device/lineage/sepolicy” name=“e/os/android_device_lineage_sepolicy” remote=“e”
with:
project path=“device/lineage/sepolicy” name=“LineageOS/android_device_lineage_sepolicy”
Best regards
Thank you @harvey186.
Before reading your answer and @andrelam’s , yesterday night I finally applied the ‘fix’ I have just described on my previous post.
Thanks for your support
Best regards,
The problem is fixed, the e/os/android_device_lineage_sepolicy repo on gitlab was set to internal, so it was not accessible. Sorry for the inconvenience.