@itsclarence, thank you for your updated /e/ OS ‘Q’ version 2021
.
Exposure Notifications
Off
Why do the /e/ sources use a different microG version in the Exposure Notifications section?
Great stuff, just like Christmas again 
Thanks @itsclarence
I have flashed this one and await a phone call 
I still suspect I may have done some damage to the antenna connections when I put in the new battery and charging board so that may necessitate a further opening up of the phone .
Anyway, all went well and the ROM is working in all the respects it was previousl and I will have to delve deeper to spot the updates and test them.
Thanks again.
James
On reflection…
It seems this update has broken the phone dialer for me?
When I go to set up a call the original blue calling screen flashes up for a second and then disappears however, the call is setup anyway and then I have no control over it…i.e. the call is going on in the background but I have no evidence of it other than the fact that my landline (which I tested with) is being held open.
I’m going to re-flash the previous version just as a control test and then try th update again
Just out of interest, should I be wiping the phone before applying the new ROM or not?
I didn’t and it seemed to work but, without the phone working I guess it didn’t really work at all
What a shame and it was all going so well.
J
@itsclarence I’m a bit late in relaying my experience with the updated build, but better late than never!
For those who are following at home, let me explain the steps I went through as it may help someone:
A caveat to report: Even though TWRP reported SE Linux Enforcing while installing the build from ZIP, “Trust” reports that it’s “Disabled” (Non-Enforcing). Now, this is NOT likely the fault of the build, as I previously rooted the phone to attempt to remedy a known issue with this device: when using the “regular” phone/dialer, the other party hears themselves with a slight delay. This phenomenon persists in this build even when using other dialer apps like “Simple Dialer”.
Interestingly, there is no “echo” effect when using Signal or Telegram for phone call functionality.
After a week of daily use, all is working as expected and kudos once again to @itsclarence for maintaining this device within the /e/cosystem! Well done and thanks again 
A new build for the zerofltexx. Cooked with february security patch and on some updated repos from @enesuzun2002.
Unfortunately this rom isn’t builded with private key’s (yet)
Thank you @mcmd and @Forumsnutzer for testing.
Enjoy…
Good morning/afternoon/evening @itsclarence!
I’ll get the S6 charged up and take the new build out for a trial run today- I i’ll let you know how it goes.
Thank you again for keeping this device alive within the /e/OS universe! 
Smakelijk, @itsclarence.
Actually, I just wanted to do a ‘dirty flash’ from e-0.15-q to e-0.16-q. However, I didn’t pay attention and instead of just deleting the cashes I swiped the factory settings. Well, no big deal, it’s just a test device.
In the near future, can we also expect to see signed builds with our private keys?
e.g.: Signing Builds
Generating the keys
Please @itsclarence: Stay healthy. Stay alert.
Well @itsclarence I performed a dirty flash with no issues whatsoever. Build recognized WiFi and SIM immediately and MicroG self-check is good. As @SuzieQ noted, SELinux is disabled, but all Android patches show “up to date”.
I’m going to “walk around” with it for a while and report back, but initially all systems are go and this build looks like another success! 
Thanks again for maintaining this device within the /e/cosystem and be well.
I installed @itsclarence e-016-1-20210323 unofficial on SM-920W8. The ROM changes the phone into SM-G920F
Unfortunately, there is no audio during phone calls. It appears to make and receive calls. But no audio either way.
Is anyone else experiencing no audio?
That’s interesting- didn’t know/think that the “W8” variant of the S6 would load /e/OS. I believe this may be the first time I’ve come across this. @oneearth you are on the well past the “cutting” edge and at the very “bleeding” edge of /e/OS operability!
Audio issues plague the S6 with AOSP OSes (such as /e/). A work-around some have used with success is to replace the default dialer with the app Simple Dialer which can be found on f-droid. This didn’t work for me though- the only work-around I have found is to use the calling capability of Signal and Telegram exclusively and not use the native phone at all.
Let us know how you make out and good luck.
I might have accidentally loaded a ROM not meant for SM-G920W8 and that’s why it got changed to G920F.
The current state of @itsclarence 202010323 unofficial is close to making the S6 a daily driver. The major obstacle is that attachments cannot be sent or received via text/SMS.
A workaround would to use email instead of text/SMS.
A tolerable bug is that one has to go into recovery mode in order to be recognised by the computer.
Otherwise, contrary to my previous post above, audio is working during calling. Yay! I might have not had the Canadian build loaded at that time.
Same for me. I’ve installed 4 different ROMs on an S6, /e/ being the last one that my dad now uses. Many of the ROMs recognized the phone as the F (international) model.
Man that phone gives me nostalgia, even though it wasn’t that special.
Greetings!
First of all, Thank you clarence for keeping the phone alive! Found out about it through channel48 on youtube.
Waiting for a motherboard ( got the rest of the parts for sm-g920f). Going to flash e-0.16-q-20210323-UNOFFICIAL-zerofltexx.zip. Will post about bugs and issues. As a matter of fact I do have experience with fullstack programming on python and also have xeon with quad channel 32gig memory so technically I can build images at a fairly reasonable speed and participate actively If you are willing to cooperate. Been flashing images to phones for the last 10 years ( starting with nokia symbian) , however never participated in active development of a ROM. I assume I have to clone the e foundation repo. Running arch so I am familiar with building from source. The part about device specific config is what I do not know. I assume I have to clone android_device_samsung_zero-common from gitlab. Generally need an 101 on building device specific roms, patch merges, debugging.
Clarence, check out my recent message in the thread. Curently syncing repo. Which kernel and common trees you used to build ?
But replace https://github.com/Exynos7420/android_device_samsung_zero-common in
https://github.com/itsclarence/android_device_samsung_zero-common or you will probably get a build-error
Nice thank you for a tip. I see you set selinux to permissive and adjusted gralloc.
According to https://doc.e.foundation/how-tos/build-e its built via docker. Are you doing it the same way or like in https://wiki.lineageos.org/devices/zerofltexx/build ? A bit confused. If you have spare time I would like to kindly ask you to talk via discord ( or any other platform ). MOBO will arrive in 10 days.
