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.
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
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.
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.
Looks like someone already has a working build - check there :
As of now I put my own experiment on hold since I badly need security updates and cannot afford either to brick my phone or to let it with big security holes. This was my primary motivation to switch to /e/OS alongside having a Google free phone, but on the other hand a working phone is still better than a bricked one. I will first by an /e/OS S7 and then be back to my J5 dedicated to science.
Thanks for the prompt reply.
I bought a second phone as a testbed but I found it was blocked and it doesnt work with a SIM. However I managed to install an unofficial build of LineageOS on it and it worked fine through WiFi.
I now have an unofficial build of /e/ on it. Not sure where i got that from without checking… It might be the same as above but i was just thrashing around the internet and thought I would give it a go. i figured I couldn´t do a lot of damage given that the phone is pretty borked without a SIM.
The unofficial /e/ build does work on WIFI so I tested all that I could. However I am waiting for an official build before I install it on my main phone.
So thanks for the link i will head over there and try to see if i can help, in some small way, to get it up to official status.
I hope you get your new phone soon, please feel free to contact me when you come back to this IF you think i can be of any help.
yes that’s possible - in theory. Astrako did really an awesome job there and supports the whole SoC but!!! -> as I do not own any device other then the j5y17lte I personally won’t. It is a principal of mine to not develop for devices I do not own (it makes dev a lot harder and I can’t give full support and it is in general not a good idea).
if you find someone who is willing to build for your device point him/her to my thread/sources and it should be possible to port it.