This effort was started and mostly realized thanks to @TeamB58, see the unofficial 18.1 topic with past contributions by @Max_S, @k4y0z, @sooorajjj, and others. We were faster this time and even beat the stock Fairphone and /e/ releases of Android 11.
This topic will collect user feedback, helpful hints, feature wishes and future milestones such as Android 12. To post bug reports, please use the official LineageOS site .
Here a collection of relevant external links:
Official LineageOS Wiki site . A list of supported devices including FP3, instructions for installation and building yourself.
Micro-G for LineageOS : popular as an open-source alternative to the Google Mobile Services (a.k.a. Google Apps). They also provide monthly builds of LineageOS for FP3 with Micro-G patches included.
Yeah, looking forward to many more moments in this journey with Fairphone 3/3+. We’re actually sorry for such a long delay in getting LineageOS 18.1 official.
The pleasure of a well-organized and well-maintained distribution (to all of us) with now, as a bonus, a world premiere of Android 12 for the FP3! Kudos to all for getting this done
I did not spot a downloadable build (at LineageOS Downloads), I guess this will take some time? Or would the first build be available tomorrow (as with 17.1)?
Looking forward to this! I’ll be joining the FP gang after my last phone (Poco F1 LOS 18) was snatched from me, so nice to know I can pick up relatively from where I left off
I haven’t been able to patch the rom using the nanodroid patcher that worked perfectly on the previous version even though services.jar are already deodexed.
I remember reading something about the choice to not include signature spoofing directly into the main rom, is it an official guideline for lineage developers?
Yes, it is. No signature spoofing on official LineageOS roms. The entire story can be found here. But this has always been The Way, and your problem is probably somewhere else.
Thanks for your work on this! I just updated using the LineageOS recovery and adb, applying OpenGApps nano. Got a warning about failed signature verification but chose to ignore and install anyway. Everything seems to have worked fine but after booting, I noticed that Bluetooth can not be enabled. It just indicates that it is loading for a little while and then goes back to deactivated. Does anyone else share this experience or even have a suggested solution?
I’ve installed LineageOS 18.1 on my FP3+ today and it works pretty well.
The only problem i am encountering is that i can’t turn on bluetooth.
When i restart the device my phone tells me bluetooth keeps stopping.
And when i try to turn it on the switch goes back to off after some while.
Any ideas what the problem might be or does somebody else have this problem?
* 10.0 / SDK 29 (Q)
* Patcher works if your ROM's services.jar already contains classes.dex
* [> Deodex Instructions](https://github.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md)
* 11.0 / SDK 30 (R)
* Patcher does not work from TWRP
* Patcher works from Magisk if your ROM's services.jar already contains classes.dex
* [> Deodex Instructions](https://github.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md)
so there are no big differences between the two versions of android, but it doesn’t work on the los 18.1 and I’m quite surprised.
I’ll make some tests and see what happens.
Wow that’s really a show stopper. Just upgraded. Sideload did work good. But now know bluetooth, so no corona contact tracing.
Is it possible to go back to 17.1? Without wiping data? Did bluetooth work while 18.1 was in beta?
Another question related to the LOS camera app for the fp3. With fp2 you can scan qr codes with (did work with 17.1 and works with 18.1) With fp3 an LOS 17.1 and 18.1 you can only switch between camera and video-mode. What’s the clue on that?
And don’t get me wrong. Thank you very much for your work to give the community an alternative rom without google - espacially lineage os is my favorite - running on bq Aquaris X, Moto G7, Samsung Tab6 lite, fp2 and fp3 within my family. This is so great.
Very helpful of you, but no - since I can see the problem on my own device, I have all the info I could want. I will try to get it fixed in time for the release next week.
