Ok, I did get e to work by more or less following the pdf description. Did anybody have the issue of not being able to turn off the software Navigator buttons at the bottom at the screen? The system seems to not care about the setting. It seems to not be activated. This unfortunately is a reason not to use the phone, since the A3 has hard buttons.
I’m on the newest version from the download thread (202204021).
This is what worked for me:
This is my e version: IMG-e-0.19-q-20211027142973-dev-treble_arm64_bvN
Hello.
Update from 0.19 to 0.23, camera’s bug went back. So I disabled all and reboot, then tested different settings.
Works : Expose Aux Camera (lonely).
1 Like
After reading the message from @trefix link I tried again the settings and now the video are working fine.
Works enabling: Expose Aux Camera.
In the end the only thing I’m missing a bit is the ability to share files via Bluetooth from the file manager, but I can leave without it. 
Even that version, the nav bar does not disappear when I turn it off in settings.
Is there a way to get icons to not all be the same shape? Normally Nova launcher does that, but I can’t use a paid app with /e/.
Hi anybody,
The description in the mentioned PDF is using Windows.
Is there a chance to do the customisation with Linux ?
I’m not sure of what you mean by “customization”. I guess you want to install /e/ os on your A3 2017. I did it entirely on Linux, I can confirm it works. The steps are pretty much the same, but you have to use a software called Heimdal instead of Odin to flash TWRP. It can be easily found directly in the repos for most distros.
Yeah thanks! That is what I meant: Installation of Custom-ROM, here /e/OS.
Great to here, that is works with Linux.
But isn’t it said here, that we need OrangeFox instead TRWP?
Btw.: Does the problem with file sharing over Bluetooth still exist?
Yeah it confused me too and I’m still not sure if there’s a better way to do it. I firstly flashed TWRP, did my backups, then flashed the repartitioner script which installed orangefox. After that it’s like installing a custom rom on any other phone. Put the .img or .zip in your sdcard and flash it from orangefox.
Bluetooth has been working fine for my earbuds and speakers but I never tried file sharing. Apart from that alsmost everything works just fine, but can be unstable at times. I got several black screens for no reason. Usually it just needs a few seconds to recover, but I had to reboot ~4 times in 7 months. I couldn’t get the full encryption to work (it bootloops) and the camera is a bit buggy (but this isn’t a good phone to make photos anyway, and it’s still usable).
TLDR: If you’re not too picky it can be daily driver, at least it’s mine
I see, that there are 2 LOS versions for the A3 2017:
- [ROM][A320FL/F/Y] LineageOS 15.1 | XDA Forums
- [UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble] | XDA Forums
The 1st seems to have less “bugs” and is stated OFFICIAL
What is the advantage, that you prefer the 2nd here?
The second would be Android 10. Installing that was quite messy and requires repartitioning the file system. Then you can’t install sub-10 android versions until you flash the firmware, which can be quite difficult because the right version is hard to find.
I remember the rom itself running well, but it wasn’t much different from a more stable lower android version.
Are you sure you can’t flash sub-10 android ? The repartitioner instructions state “You can flash any rom later, with or without vendor support”.
Still anyway, that’s why a good backup of the firmware is needed. Plus it’s quite easy to do as far as I remember.
You might be able to flash sub-10 android, I assumed once the partitioning is changed to android 10 it won’t fit sub-10 any more. I didn’t have a backup of my old firmware, so I had to download one. I just remember spending a lot of time with this phone, because these files are slow downloads and usually once you get them you find out it’s the wrong version. You might be lucky that it works out easily for you, but I had all sorts of issues. I had the damn phone bootlooping for months several times only to figure out how to fix it and then something else not working. Just installing android 10 was the easy part.
1 Like
Is that correct? :
LOS 15 is Andriod 8
LOS 17 is Android 10
Do you know a smart site about the differences of those versions?
Would it be neccessary and possible to go back to the old partitioning, when I want to go back to LOS 15 ore stock Android 8?
Is this a different task: flash ROM ./. flash Firmware?
Is there a documentation, how to backup the given original ROM (and maybe what else)?
What you suggest? In case, using the backuped ROM or download it from Samsung?
As I got my A3 2017, there was Android 7 on it, but I updated to Android 8 by the phone provided procedure.
How can I check, if my device already contains Treble?
There seems to be a tool, but I neither find the “/e/OS default Apps Store” nor “treble info”.
And for what is “GSI” standing?
There are 2 pages within https://doc.e.foundation/support-topics on Generic System Image (GSI)
- https://doc.e.foundation/support-topics/understand-and-use-gsi.html
- https://doc.e.foundation/support-topics/install-GSI
The A3 2017 is perhaps not a typical phone for GSI; this topic goes back some time (things may be done a bit differently now) but I think it is important to understand the concept introduced back at Post #8 that the device has to be “made treble compatible”.
@UlfZibis: The version numbers are correct. LOS seems to always be 7 more. All I really know about android versions is that “newer is better” according to Google, but all they changed since Android 7 is the UI, which became ever more plasticy and annoying. Oh, and I guess they spy on you more.
You go back to the old partitioning when you flash the stock firmware.
You can pretty much always just google search these questions. “How to do this or that”. That’s pretty much what we do. 
Much thanks for your valuable evaluation.
Few updates on my side:
- Bluetooth file sharing: it works if I select more than 1 file
- Bluetooth calls: on some cars it works without troubles, on some others (at least mine) it works also if you follow the procedure on post #64
- Video: ‘Expose Aux camera’ and ‘Force Enable Camera2API HAL3’ it works randomly, mainly does not work correctly.
- WiFi: on some networks it tends to disconnect from the WiFi when I lock the screen and it re-connects when I unlock it.
Still I keep using it as my only smartphone.