Oh sh…t, I think I have forgot 2 patches before building. Sorry 
2 Likes
I hope Laurent has the patches included
Yes I have but the build is really long and, my VM on which I build was almost full when I left this morning… So I think the build will fail 
Building on vm is a pain. To less ram. You will need more rhan.8gb ram and around 250 gb hdd space
Yes, I just want to valid building.
Then, I’ve got a server running openmediavault… I guess (and hope), I will be able to automatize builds…
That’s the plan
1 Like
Hi @philipp,
I made a build, I installed on my phone yesterday night and it seems to be working without issue (for the moment…)
Here is the build : https://ecloud.global/s/dMrkx9gwNpoiGQo
Of course, @Guenter, you can test it 
1 Like
Hi @LaurentG, you have quickly learned to build a /e/ OS ROM. This is great! 
At first sight it seems your version e-0.9-p-20200626 works as well as @harvey186’s debut e-0.9-p-20200530.
The security patch level is also identical to the 5th of May 2020. ROMs based on LineageOS 17.1 have already integrated the security patch level June 5, 2020.
It would be great if you would create an updated build at the beginning of the month after the official Android security patches are released.
Okay,
I have no idea how I can be sure about the security patch included in my build… @harvey186, any idea ?
If you have synced the repository after 2020-06-09 13:32 UTC, then it must be june 5th security patch
You can check on your phone also : Parameters / System / About the phone
It comes automatically with repo sync as @blaes has written.
The security patch in my builds are from june, 5th
Ok thanks for the feedback (and happy that the build is correctly working not only on my phone 
)
I’m looking with my mentor @harvey186 why the security patch is not in my build…
FYI, I tried a new build last night and the result was the same : 5th of May 2020
Hope I will figure it out quickly
Update :
@harvey186 has investigate much more than me and, finally, it sounds to be a bug. He has created an issue on Gitlab
Hello,
Just to say thank you for this build. It works pretty well on my S7 !
Wekcome and enjoy it
Hi everyone,
I made a new build but the security patch is still on May 2020…
So, I guess, this build is useless until the /e/bug is open
Anyway, here is the link for the “new” version : e-0.9-p-20200725-UNOFFICIAL-herolte.zip
https://community.e.foundation/t/unofficial-build-e-pie-for-samsung-galaxy-s7-herolte/19205
[UNOFFICIAL BUILD] Unofficial Pie Build for Samsung Galaxy S7 (herolte)
”Who loves ya, Baby?“ In 3 months 3 unofficial Pie Builds for Samsung Galaxy S7 (herolte). This is really really good and a remarkable progress!
Following the feedback from users, the most stable build is from the great build master harvey186.
@harvey186, I read that you are endlessly on /e/ in use and insanely busy - but when the new Android security patches are released in August 2020, you could update your excellent e-0.9-pie build “on the side”. As a pro, you’ve probably saved the essential shortcuts and just have to press “rebuild” button 
I only found the issue, that the pulse sensor doesnt work - but I think this is really a very little problem, because dont know, if anybody uses it 
For me it is important to know, if this built will further be developed in the future. The Nougat /e/ built for S7 is good, but its out of time.
I need my phone daily and it is very important for me, that it works. So if the built will not be developed further, I will change to LOS with micro g.
The messages about developing for the S7 I found from the /e/ foundation, are not clear. Or does anyone have other information? Thanks very much for the work of the devs! Great.
It will get updates in future. There is a post about ‘roadmap’. There you will find more information
Thanks. The information there is not really clear or me, but gives hope for the future. Maybe.
Hi, did you use the “v0.9-pie” tag ?
repo init -u https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v0.9-pie
No problem with the “v0.9-nougat” tag on my side.
Absolutely,
Check the bug opened by @harvey186 : https://gitlab.e.foundation/e/backlog/-/issues/1482