Not sure how you come to the conclusion that 1,2,3 and 5 are broken on the official build.
4 should be looked into, but doesn’t seem very critical given noone really complained within nearly a year of unofficial builds.
If you’re not happy with auto brightness on stock, you might not be happy with the one on lineage either. Battery drain between 30 and 50% is too vague to comment on and i’m not aware of any notification drop down issues.
Re-installing lineage with google apps is not the only fix, as mentioned in the FAQ: Frequently Asked Questions | LineageOS Wiki
You can avoid running into FRP by following the instructions, specifically point 6 of the basic requirements: Install LineageOS on FP6 | LineageOS Wiki
I was just pulling from a few comments on the thread already & quickly summarized to get a quick list of what issues were listed. I was looking for confirmation & to get the conversation started So 1,2,3 & 5 are not really issues, so low mic pickup is 1 bug not present in the base ROM, are there any others?
Usually I find with lineage, the issues that go unspoken about because some arise from how you installed it, so its chalked up to that & never addressed, even if shown to arise another way. Once I take this leap with my fp6, I don’t plan to go back So I really wanna know is it marginally better then the base ROM or marginally worse?
As for the battery drain, since the sept 2025 update the battery took a hit from what I believe is cell tower idle state on base firmware. When I got the fp6 for the fist 4 months I had 2 days battery life & since that update it lost 30-50%. I wondered how much lineage might have done to address this? Usually I find lineage builds can sometimes double battery life. My wife’s phone a oneplus got a 1 day boost when she switch to lineage & I was hoping for something like that. However so far no one is claiming that here, so I must suspect its the same as the base ROM.
Hi - FWIW: I’m still running unofficial build from March 22; no issue with WiFi at all - works like a charm. The issues discussed in “DNS over TLS/IP6 issues forum” seem to remain, so I’ll wait before re-switching to Official.
Hi—can I ask what’s probably a naive question? Based on the unofficial March build: everything works. June build: Wi-Fi is choppy—a bug that’s sparked wild speculation—and it’s still there.
I thought that if I compared both versions, filtered out the differences, and examined them in isolation, I’d be able to pinpoint the bug. That’s how it works with text—but apparently not with operating systems. I don’t know anything about this—what’s the difficulty here—which there must be. We’re using the same phone model but very different apps and hardware environments—is that it? Or is there simply no suitable analysis tool?
Pretty complex. Please stay on top of this!
That WiFi bug would really annoy me because I have limited mobile data & I’d hate to go back to previous months version just for that. So till I hear its resolved I think I’ll stay on official. I’m a beta tester also on the official ROM, so jumping ship isn’t what they would want to hear..
Well, did you actually try to compare the versions? I think it gets quite obvious how this is different from a text file then :')
First of all, the scope here is gigantic, Android is a project with millions of source code files (the source code, excluding the out folder, is 470GB on my machine [though, that includes compile toolchains and other prebuilts for the build, but still]. It’s enormous and by dimensions larger than the typical software project you’ll find in other places… Then of course, if you want to diff the broken and the working builds, you will notice that all the code is compiled and you’ll have a very hard time understanding anything from the diff, it’s not really feasible. Instead, you usually check the source code and the recent changes (in the git history).
However, since this issue arised after upgrading to the Android 16 firmware provided by fairphone, which is proprietary, we do not have access to the source code and the changes done to it. We can not really change anything in there either due to missing source code, and patching the built firmware is not possible, since it must be signed by the OEM and we (LineageOS) do not have access to the signing keys of course. (No, an unlocked bootloader does not allow you to change any partition as you wish.)
Due to this, the only feasible way to solve this for us is selectively rolling back these “black box” components until it starts working, which is an incredibly annoying process, since i can not really reproduce the issue and there seems to be no way to systematically trigger it as far as i know. If i find some time for it, i might be able to share multiple builds with different components rolled back to help isolate the root cause. But i currently don’t have a lot of time for this and rather spend that time on upgrading the kernel to linux 6.6 to ease the long-term maintenance.
If anyone else is interested in debugging this, it might make sense to start by reverting FP6: Update to FP6.QREL.16.48.0 · LineageOS/android_device_fairphone_FP6@57f0d04 · GitHub, extracting the firmware and blobs from the android 15 ROM again and get that running using the latest LineageOS platform code.
@Madhits you seem to have misunderstood the issue, it’s explained here: DNS over TLS/IPv6 issues- Apps don't load data over Wifi - #460 by sebseb01 and also affects the stock android 16 software.
So the WiFi issue is not ip4, only ip6? Thats the same bug as on OEM ROM then? I thought it was a different & new bug..
@ArianK16a Uff - thanks a lot for explaining! No, I had no idea about the dimensions and yeah, now I got it.
So I admire your work furthermore, keep glad with the March build and wish you all the best!
I’ve uploaded a new build which rolls the proprietary components back to the last Android 15 firmware, please report whether the ipv6 issues are improved!
I’ve also fixed mobile data and the moments switch on kernel 6.6, so this build is using the linux 6.6 kernel again, but it should be as stable as before.
Hi! Sideloaded new build; first checks : my special problematic apps RadioDroid and AntennaPod connect immediatly: no delay also for downloads; browser redirects to new TABS -
this is great! Wow - let see a second time tomorrow; now it feels superb! 
Thanks! Once you are confident enough, please upgrade to this build:
It includes the latest firmware again, but rolls back just the specific wifi firmware.
Additionally i have adjusted the microphone to use both microphones in handset mode, this should siginificantly improve the quality of the microphone, for example in the pre-installed recorder app. Please report back about that too 
Hi—task completed; it’s working! Except that the boot animation looks a little choppy (just my impression!), everything works great.
I really hope these extra builds not only make me happy, but also help find the bugs. I know I’m repeating myself, but: thank you so much for your work 
!
Hi! I am thinking to change from fairphone os to lineage os. My question is: what is the relation of the builds of the official lineage os page and those you provide here?Info about FP6 | LineageOS Wiki
Are those here the beta?
Looks great how the community and open source provide more transparency and trust.
Hi, yes you can consider my unofficial builds the beta!
Instead of what is merged at the LineageOS github organization, they are built with the trees and kernel i push to my github at the linux-6.6 branch. Everything being tested here that turns out to be good will eventually be merged into the LineageOS repositories and thus arrive on the official builds.
Glad it works so for. Unfortunately, even if this works, it won’t help a lot figuring out what is actually the issue here. FP6: Pin wifi firmware from FP6.QREL.15.176.0 · ArianK16a/android_device_fairphone_FP6@c167aaa · GitHub is what i’m currently using, and that only rolls back some firmware files that are proprietary, and we have no way to change them (as even patching without source code would break the signature and we can not re-sign) or understand what changed since the faulty upgrade since we do not get to look at the actual source code. However, that’s still a feasible fix (if it turns out to keep working fine) until fairphone fixes it with the newer firmware.
I tried to test the build, too, but got stuck in a bootloop after installation. Recovery tells me my data may be corrupt and I might have to do a factory reset. Am I right to assume that you can do the installation without wiping data? If so, what did I do wrong? I followed the installation instructions of the official builds except wiping data
If you were on a build with july security patches you can not install it without wiping data, as android prohibits that. My unofficial is still on june patches. In that case you should just sideload the latest official again and you should not loose any data.
Alright, thanks for the quick reply! Yes, I was on the latest official build, I’m going to go back to that one now. Also thanks for the great work, I really appreciate your efforts to fix the issue
Hi folks! Big thanks to whoever helped to make lineage official on FP6. Works great.
I’ve been using the unofficial build for a long time, updated recently and I’m just a bit annoyed by an issue I’m still having. My color scheme is stuck and I can’t change it no matter what. The Monet thing. The scheme changes when I select another one in the Customization settings but goes back to purple every time I click Apply. Contrast settings don’t work at all.
Do you have any idea what could cause this?