Unfortunately no, my laptop has only 8GB of RAM. I didn’t know building roms is that resource heavy 
I will get stronger computer soon though.
I requested developer status on androidfilehost so that I can upload files but it hasn’t been reviewed yet.
I don’t know how long it takes but I will try something else if it isn’t granted today.
yes, you need at least 16 GB for building.
Androidfilehost and upload of data is a gamble…better use Sourceforge or other URLs
I can build a 2.0 R version and you can take this to apply your fixes?
Man, oh man, this is not straightforward at all.
On Sourceforge, I registered, created project with all the requiered details, linked phone number but upload through website is limited at 500MB. I tried through FileZilla and it did upload /somewhere/ on SF but I don’t see the file on my project.
So here is mega link, please try it out and provide feedback:
https://mega.nz/file/ObRWTBxB#ddHxRKdmYoKf1zKMfX6addFLzubUSvsa_GFAb6v47_0
@ronnz98
We can try it out if rom works for other people too. I just reinstalled it again to make sure (not to embaress myself) and wifi works but let’s wait for others to confirm. Btw I used PitchBlack as recovery to install it. Phone will reboot two times.
Many many thanks: I could download your ROM “e-1.18-r-a7y18lte-wififix.zip”
On how to install it, I suppose I should follow the directions from https://xdaforums.com/t/rom-unofficial-11-0-open-source-encryption-testing-sm-a750fn-g-f-ds-lineageos-18-1-for-galaxy-a7-2018-exynos.4634413/#post-89083719 ?
We have the habit of flashing Samsung devices with the mentioned tools (heimdall, adb). However, twrp is said to be not supported as a recovery. The XDA forum tells to use the lineageOS recovery (which I downloaded, too). @sethdot you mention PitchBlack recovery, but I don’t find the A7 model in https://pitchblackrecovery.com/devices/?vendor=samsung ? Where did you get it from?
I think that any recovery in which you can flash rom will work.
You can find PBR here:
https://xdaforums.com/t/pitch-black-recovery-project-based-on-twrp-sm-a750fn.4267027/
Update for /e/OS 2.0:
e-2.0-r-20240523-UNOFFICIAL-a7y18lte.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-2.0-r-20240523-UNOFFICIAL-a7y18lte.zip/download
@sethdot: maybe you want to include your wifi fix into it
Hi @sethdot,
thank you very much! The version is perfect.
Best regards to Croatia!
Hi, @LePoissonLibre managed to install this version 2.0 at our flash-party last weekend, and it seemed to work well! The user was so happy.
Many thanks to all of you who helped
I can confirm that e/os/ works with A750F model also.
I used @ronnz98 last ROM and wifi problems are indeed fixed. I recommend his 2.0 version as it’s the newest.
Update for final /e/OS-R 2.2:
e-2.2-r-20240719-UNOFFICIAL-a7y18lte.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-2.2-r-20240719-UNOFFICIAL-a7y18lte.zip/download
Hi @ronnz98,
habe vorhin deine neue Version installiert. Leider ist das wifi Problem in dieser Version wieder drin.
Yes, I will try. Give me just a few hours.
All right, here it is:
It is tested on A750F and wifi works now for me. Please provide feedback when you try it out.
Thank you very much! It’s all fine 
hello there! i noticed that you liked my post about the a3.
Is there any way you could message me on here so i dont have to be out of topic?
Few years ago i built my pc with an i9 10gen 64gb ram and multiple TB ssd drives for VMs and such, as of now its only used for youtube and occasional game sessions.
I would really like to learn how to build roms but i was never able to get it done due to out of date and or confusing guides, im more than happy to cooperate and learn!
I have AFH developer access under a different alias since 2018~ for some ports ive done in the past.
If anybody wants to jump in feel free.
Hi @gianncap994 as you have an A3 (2016) I checked the lineage build page Build for a3xelte | LineageOS Wiki, it is fairly recently updated in that it mentions adjustments for Ubuntu versions 23.10 (mantic) and 20.04 (focal).
… to get your environment correct but not hard when you allow time to follow the early stages of the build instructions. I use Debian 12.
The advice there on java and python appears to be up to date if using Ubuntu, When using Debian you just have to ensure that python is python3. I prefer to keep my build environment clear of any Java installed from any other sources.
a3xelte will just build from docker, (and the environment is expected set up for you, but this is not everyone’s experience 
) but I prefer not to get involved as I find it harder to learn docker than to learn to build Android.
To establish that you have a useful working environment I would suggest building your own LineageOS at Android 11 (R) 18.1, once you know LineageOS builds it is easy to upgrade your workflow to /e/OS.
People often get stuck at “Extract proprietary blobs”, but when you get to that stage you could check out [Walkthrough] device.xml for local_manifests where this technique is explained
and a full device.xml for a3xelte is shown.
Feel free to start a new thread perhaps under UnOfficial Builds for further support. Good luck.
Hello, I’m sorry but I’m on vacation right now and don’t have access to my setup.
I will respond in more details when I come back but just quickly - official tutorial is how to build rom with docker from example (I think it was for Samsung S9 when I started, now it’s Google Pixel 5) so it’s very easy to follow and it’s not confusing.
https://doc.e.foundation/support-topics/build-e-for-a-device
If you don’t like docker, check @ronnz98 tutorial for command line. I used mostly his work and just adjusted some settings where I noticed problems in the rom.
His tutorial is here:
I see in this thread that your builds seem to be working fine on a7y18lte. I installed one myself at a flash-party (but it was not my device, so I don’t have more feedback in the mid-term).
If they are really stable, maybe it might be worth adding the device as a “community” build in Smartphone Selector
I talked to Murena about that, and they answered it could be asked through a new gitlab issue, with all the detail needed to compile it.
Would you be interested in creating this ticket, to see what Murena thinks about that?
The issue is the /e/OS-R (A11 based) reached end of life so I don’t think its making much sense (this is true for all /e/OS-R unofficial ROMs). If there are A12 or A13 sources for this device then it would make sense