I was testing out if there were issues with the source and build an unofficial Oreo build for FP2. It is here in case any one is interested in testing it out.
For those interested in building /e/ ROM’s using the Docker method : The build instructions are here
For those interested in building /e/ ROM’s without using the Docker method and through the traditional method you will will find an excellent script here
Want to build for a device without LOS support we have an article here
Thanks for the details!
IMHO as /e/ is based on lineageOS, its version is relevant and not that of the vendor (FPOS or FPOOS).
The official lineageOS link I’d already added above.
The link of the according thread on Fairphone forum you can find here: https://forum.fairphone.com/t/lineage-16-0-android-pie-nightly/50287
Not sure that I understand very well. Is /e/ forket from different versions of Android depending on the phone? If so, why? Why not progress simultaniously on all phones, avoiding this situation where an app works on Oreo but not on Nougat? Newbie question, I know.
Hi @cedricoola the reason is development on the Lineage side is dependent on users called Device-Maintainers. They usually own these devices and help build the ROM’s for them. These maintainers also maintain the device tree files on git-hub. These are critical files for the ROM building. They also apply the latest google security patches as and when they come in. Some of them even do a basic level of debugging for the device issues.
Now after a couple of days some DM’s loose interest or something happens to their device or the buy a new one and stop building the ROM’s. This is when Lineage drops support for those particular devices. In the case of /e/ we are dependent on DM’s as well as build for devices on our own. The advantage is we are not dependent on DM’s the disadvantage is in some cases we end up building blindly ( where we do not have the device). In the case of FP may be the user base for nougat is small or the fix in Nougat code is not possible due to various reasons.
At /e/ we are trying to remove this dependency on Lineage Device Maintainers and maintain our own device files. That though will take time.
Thank you very much @Manoj . It’s a bit clearer now.
I see that a version of Lineage Os 16 exists. This is Oreo isn’t it? Why is /e/ for FP2 not forked from this version?
LOS is Pie. LOS 15.1 is Oreo. The upgrade of the /e/ code for Pie development has just started. There is a unofficial build of FP2 with oreo code here in case you want to test it out. I built it to test the builds were happening. Do not have a FP2 so did not test it myself. Shared it with of my friends on the support team to test it out.
I understand that the /e/ team works on the developpement of different versions of /e/, each forked from a different Lineageos version including the latest ones. The FP2 already has a Lineageos Oreo running, so I would assume that /e/ version is also Oreo. But no, because device-maintainers have to make the specific Lineageos version work together with its respective /e/ version that /e/ team has made ready. Is that correct?
How does it work to install it? Just click the link to download it on my phone and open the file on my phone? If it’s more than this then maybe i’m not the right public for testing. Thanks for your kind help and advice.
It is the same as for all the rest. You request for a device build here - which you have already done. The more the requests the better the chances of an official build.
Hi @ff2u please can you let me know what was the OS version on the FP2 when it was factory reset. We will need the info to share with users when we release the builds officially.
