Hmmm, I managed to get myself into trouble. I wiped the data partition and installed 23.2 (latest build) and MicroG, but now I’m unable to change anything as I first need to log into Google as ‘The device already had a screenlock’. Any way to get rid of this catch 22?
I want to ditch Google, but to do so I need to install gapps (as it seems) to be able to use the device. Would installing a gapps, remove screenlock (set it to none) and then wipe work?
before switching to any alternative OS,
to avoid “FRP-Lock” (Factory-Reset-Protection) of the device…
you now will need to restore FairphoneOS to remove the locks, then reinstall Lineage4microG
(maybe LineageOS+Gapps could do the job regarding FRP, but only booting stock FPOS is able to reset bootloader unlock_ability to 1)
Nice, so to get rid of that junk I 1st have to install the original OS, remive everything and tyhen get my device back the way I want it.
However, I managed to get back in. 1st try via NickGapps (20251128 version works with this image) worked, then tried with MicroG… Got my phone back again. Now to recover without gapps…
Maybe next time I want to reset the device I’ll got the ‘remove FRP-Lock’ route. It seems that wiping system works as well, but the recovery we have (now) is very limited, no way to format anything apart from data.
Just did an OTA update from the 23.0 build to your most recent one. Works perfectly so far and kept everything the same except one small thing.
In the status bar settings I had the network traffic settings set to be visble. They are no longer visible and can’t seem to turn them on. Also in the status bar but in the display settings, “show network name" seems to be stuck on and always have my carrier name in the top left corner. Very small minor thing.
Otherwise looking good! Thank you again for your hardwork!
Edit: I just learned about desktop mode in android 16 but it doesn’t seem to be available in the current build. Curious about plans to try and implement?
Not a bug, found a option to disable that.
I have this issues also on 23.2 from the 11. Januar build.
Another bug I found is that the Night-Time/Do not Disturb gets randomly disabled. I guess it belongs to the physical switch on the side as I have configured it to switch between normal and vibration only. A little bubble that informs me that I switched to normal comes every few minutes even without touching the phone.
Can you share the “option to disable that” with us? I found myself with the same issue, didnt know there was an option.
Security & Pivacy → Device Unlock → Fingerprint →Touch to unlock anytime
they hid this one pretty well
There is new security patch release for february 
.
I think the only “wishes” 
remaining of the ones I mentioned earlier are:
The carrier label in the status bar to optionally be enabled/disabled. The setting is searchable but does nothing.
I’m not quite sure, but I think the touch feedback (vibration>interactive haptics) doesn’t change when moving the slider.
Something I newly observed in the latest build is that it seems to me that auto-rotation has become overly sensitive. Can someone confirm? My display often rotates while the phone is in almost horizontal position but not really tilted.
Cheers
This might be a stupid question, but why is it not possible to reuse the work that Murena / EOS is doing for LineageOS ports ?
Sorry to say that, but it indeed is a somewhat stupid question…
Why would it not be possible? Why would someone want that?
It is possible to use their code, but, unfortunately as we’re used to from them, their code is not too nice and it was released after we brought LineageOS up.
Got it. I’m jealous because they have the official Fairphone camera app running on Murena.
I personally have zero interest in working on this, we usually consider proprietary apps with system privileges an anti-feature. It requires some framework changes which won’t be merged into lineage without a lot of effort. Just my opinion, but i felt like the stock camera app is quite horrible anyway, in terms of looks and post processing of the images which really doesn’t motivate me to work on this.
Sorry if that’s an important feature for you, lineage might not be the right thing for you then.
Otherwise if you’re not happy with the default lineageos camera app, i would suggest to look into opencamera and tune it to your preferences or, if you’re fine with proprietary apps, find a google camera port which suits you best.
Understandable. I never tried the FP6 camera app to be honnest but I was hopping it would be more well integrated than open camera or Gmods are.
Lineage just got 23.2 update! 
Hope to see an official build for Fairphone 6 soon! ^^ (Obliviously take your time :DD)
Im not sure if this is a bug with LOS and your build but want to see if it’s reproducible or not.
Using the gestures navigation my active app becomes frozen if I begin to swipe the bottom of the screen to swap apps but don’t complete the gesture (either lifting me finger to soon, or just reversing/returning to the first app).
Fix by completing the gesture, swipe up to enter overview mode, or close and open app.
Kinda weird.
Seems that Trebuchet (the los stock launcher) is a bit buggy here. At least I never experienced this behavior with my third party launcher (Niagara) but can reproduce it when setting Trebuchet the default launcher. The recents page becomes empty at times (not always) on swipe-up + hold.
Oh neat. I’m actually using Law chair launcher… maybe these are unique behaviors to the launcher apps themselves and not os build?
Hi guys,
Will i be able to switch to the official release from this “unoffical” release, once there is an official one?
Or will it be painfull and one have to start from scratch/factory reset?
PS: how can there be an official iodé release, which is based on lineage, when there is not even an official lineage release?!
Yes, that is what I suspect. And as both Trebuchet and Lawnchair are based on AOSP launcher 3 this could be the reason for common bugs.