I own the device but cannot risk to brick it right now as it is my only phone, see the first post. 
When I have confirmations (or the Galaxy S7 under /e/OS ) it works I’ll happily install it.
How do you upload images and more importantly, where ?
Thanks for the support, and I guess this model was a bit more painful than others. At least you can happily use my small patches to the kernel source tree so that everything works. The build scripts are there : https://github.com/jaubin/eos_j5y17lte
I’m using ecloud for rom’s.
Why don’t make a full backup of your device with TWRP, store it on externalSD or PC and try your rom. Waiting of an user makes no sense.
I’ve created a small project which could make it easier to both share roomservice.xml and build ROMs - something very simple.
Could you please have a look and tell me what you think ?
Nice effort @julek . In this thread itself we have team members who have put in a lot of effort to organize the roomservice xmls. All can have a look at your tool and if the consensus is in its favor it can be added to gitlab so that it helps all.
Don’t hesitate to adapt the script. Anyway it will make this thing much simpler :
Not exactly confident in my ROM. I guess I’ll have to by a new /e/OS phone first, so that I could use my current one as a scratchpad - dedicated to science…
hi. just wanted to say I will start building for that device soon
I ported together with nailyk LOS to that device but haven’t done anything since then.
@julek so you did some stuff already, can I find everything at your github?
Yes I have created a script that automates the building process and makes it much easier to do than with the official documentation, and I have a patched kernel because some of the makefiles were broken and some files were missing as well. All is on my github. However my script does not do magic and the toughest work is still to create a custom roomservice.xml or sometimes patching the code.
Entry point is :
Samsung has released a security fix this June for this phone, still on Android 9. I guess it would be possible to port the kernel sources from repo Exynos7870 to /e/OS but no confirmation at all. We need first to start making all work with Android 8.1 and maybe later Android 9. I don’t really care of the Android version, but I do for security fixes.
thx dude.
I am using another approach for building:
and I’ve updated my j5y17lte manifest including all the RIL fixes which are missing on nailyk’s repos here:
https://code.binbash.rocks:8443/MVA-VoLTE/local_manifests
I had to first sort everything but the manifest repo is now clean (haven’t build yet though 
). If you want to use my manifest and do not want to create or link an account on my git server then ensure you comment these lines and instead remove the comment tags from here . That is not needed when you have an account on that server and SSH key set though. If you like I can add your account then for commit access as well…
anyways now that I have finished my /e/ builds for the LG G4 I begin with that one here 
Thanks ! If it works I’m interested
looks good so far
EDIT 2020-08-04:
haven’t found any issues yet. RIL working fine, Cam (pic and video rec) working fine, audio works, screen lock works, fingerprint works, sync with /e/ is working fine as well. ah well and GPS is working good as well (just a quick test with the F-Droid app “GPSTest”)
Next thing will be be backporting the security patches to the kernel and making a current TWRP build.
GPS tested on my bike tour for 2 hours. worked fine.
EDIT 2020-08-05:
custom build + TWRP is online. Details can be found here: [CUSTOM BUILD][OREO] Samsung J5 2017 - SM-J530F (j5y17lte)
Great thing !
One thing would be to have reproducible builds (a make build is by definition not reproducible since it could build on your env but not on mine for example).
what exactly do you mean by that?
it is reproducible. take the manifest follow the guide to add vendor/e and build
its 100% the same unless you change anything else.
I’m kinda purist towards C-I servers. Part of my day-to-day job. 
I use jenkins for that
But the make approach takes far less time when it comes for debugging and things like this - with docker it can be painfully slow.
everything is better using the make approach IMHO the only reason NOT using it is when you never build before and do not want to spent any time on learning (much)
I learnt quite a lot by patching the kernel (okay, a change in a makefile, diagnosing error messages, adding missing sources) and playing with the resourcemap.xml file. But even with that I hardly scratched the surface.
Hi Julek
I have a J5y17lte and want to help with your build.I am a noob but eager to help. Maybe you can work with me? if you are interested let me know.
