āRequirements [ā¦] 2. Make sure your computer has working adb and fastboot . Setup instructions can be found here.ā
ā¦ where here is a page explicitly telling you to download adb and fastboot directly from Google.
One issue is Linux distributions offering seemingly outdated or otherwise unfit adb and fastboot commands.
Another issue is interested users not following written instructions telling them to āmake sureā something works, and how exactly to achieve that if in doubt.
No act of moderation here will fix either issue.
Perhaps /e/'s install instructions could use some bold, signal red lettering in the right place instead.
This was neither necessary nor my intention. Your post was not noise.
Anyway, I created a topic over at the /e/ forum, letās see whether something can be done to make it clearer the instructions are really to be followed to avoid trouble.
Iām sorry if thereās a running Lineage thread somewhere, but I couldnāt find the current status of Lineage for FP3.
I saw on the official page that there were a few nightlies for FP2, but is there an active group of people unofficially curating an FP3 version? Or is it more advisable to install /e/ at the moment and customize from there?
I could have sworn there was a thread here but I canāt find it anymore.
EDIT: thanks @Ingo!! I had only searched in Discuss and Help, but forgot about Development.
In the new firmware (v0120 at the time of writing), there is a vendor.img. Canāt I just flash it on the vendor partition with fastboot instead of reflashing everything?
I just joined the forum and wanted to send a big Thank You for writing this post. That was massively helpful for me as a new Android user, and without this (and the TWRP port) I probably wouldnāt have been able to run Resurrection Remix for the last few months
I donāt know if you are still having an issue with fastboot -w but it is probably because your mke2fs tool is out of date like me. I fixed it by installing the platform tools strait from Google rather than the Debian repos like they recommend in the LineageOS guide here: https://wiki.lineageos.org/adb_fastboot_guide.html
Iāve added a custom GSI build of /e/ Android 10 to the list in the first post.
Have not checked it out yet, itās absolutely fresh. Itās provided by a heavy contributor of custom /e/ builds.
I just posted an issue regarding receiving texts on my FP3. I am not sure if it is related to the GSI ROM I have installed so I thought to post it here to confirm or rule this out. AOSP GSI: Can't receive texts (but sometimes can)
Tried it myself with LOS 17.1 GSI just now and it seems to be working fine so far.
Edit: now that Android 10 has arrived for the FP3 I wonder if it would help to use the new vendor partition instead of copying a few libraries from another phoneā¦
@pigpig: phhusson has added a hardware overlay for the FP3 on my pull request. So with the next GSI builds by phhusson or AndyCGYan installation should become easier. You may want to replace steps 3.-6. simply by fastboot --disable-verity flash vbmeta_a vbmeta.img && fastboot --disable-verity flash vbmeta_b vbmeta.img - there would be no further need to enter twrpā¦
BTW, on the most recent 0045 firmware LineageOS 17.1 works smoothly - at least my own build which is based on the same sources like AndyCGYanās but includes a quick & dirty OTA option.
That is very kind. But I would prefer an official version of LOS17.1 for the FP3 and FP3+. I need a working phone. So I want to wait till it is official.
@The_Little_Death: I fully understand your position as Iād prefer an official LOS17.1 for microG myself. However, as nobody so far appears to volunteer as a maintainer, I went my own GSI based route, which is likely easier and provides at least myself with a working phone. AFAIK, so far the GSI approach hasnāt become part of LOS - so my route has virtually no chance to become official.
Maybe you can help the guys in the LOS16.1 for the FP3 thread. I think it would be the best to drop LOS16.1 and switch to 17.1. Because the FP2 has Android 10 now.
At first: Big thanks to [pigpig] - great post and I easily (https://forum.fairphone.com/u/pigpig)
installed LineageOS 17.1 with OTA 3 days ago.
The only thing I noticed is that no sound is being redirected to my bluetooth headset (it gets connected, every service incl. HD Audio shows as in use but sound only comes out of the speaker)
Has anybody also seen this issue?
.
for writing this post. That was massively helpful for me as a new Android user, and without this (and the TWRP port) I probably wouldnāt have been able to run Resurrection Remix for the last few months 
