Hi indeed, I was just reading the thread, thanks for pointing it out.
Is there an official issue/bug open?
Can we track progress somewhere?
Tks,
O.
I think the best you can get is the official list of known issues at https://support.fairphone.com/hc/en-us/articles/9831446296849-Public-issue-tracker
And the community effort at ✏ Known reproducible and reported issues of the Fairphone 6
Hi and thanks for the link. I see the issue is mentioned on the support link so I guess that’s good news. Even though I don’t see a timeline or anything else. Isn’t there a corresponding issue tracker somewhere? So it’s wait and see I guess. My own workaround is just to momentarily switch to mobile for app login.
On the second link (the wiki) the list seems to not include this major bug… I will not edit the page since I don’t know enough about the status etc…
Thanks again @Ingo
O.
Has Google already solved this issue so that fairphone could implement it in the current software update?
I still really much doubt it’s just directly a Google issue. or if it is even the Google issue pointed to in this thread. Maybe more the combination: Hardware, Driver, Android16 ?
There are several reports that this is linked to Google and Android 16 in general and not limited to Fairphone only.
Edit: typo
[My provider is P&T Luxembourg. I have the latest Android v16 on FP6. ]
Following the latest update (FP6.QREL.16.95.0) I have noticed that several of my apps lose wi fi connectivity.
The main one is the BBC Radio 4 app, which I listen to regularly. When I fire it up, if goes away and tries to download the ‘live’ stream. This used to take a moment, now it takes many many minutes. [Workaround - I switch off / on the Wi-Fi (Settings > Internet > Wi-Fi) and it reconnects.] It is also happening to my FusionSolar app (Huawei) which monitors the status of my photo-voltaic panels . Same workaround as above.
It’s an inconvenience but not a disaster. Anyone else seeing this odd behaviour since the latest update?
Moved your post here its a known problem with ipv6 connections, Fairphone is working on it and shortly disabling is a workaround
Thanks. I see I’m not the only one. I’ll wait to see how this resolves.
Please note that there are different bugs which are sometimes mixed here in this thread.
In the Google issue tracker they are talking about loosing WiFi connection: “…unable to maintain a stable Wi-Fi connection. The network appears as “Saved” but the connection never establishes, or connects briefly and then drops.” This fairphone thread is not about this Google issue.
Here in this fairphone thread we mainly talk about “apps not loading data over WiFi” and the WiFi connection is established and stable. See this post for a detailed technical analysis.
Hi, I just started having the same issues, and had an overlap of upgrade to e/os 4.1.1 (probably switched to A16 at that point or if that came with 4.0), but I also updated my router (RB4011) to 7.23.3.
I just downgraded the router to 7.22.3 and the problem is gone, so something happened between 7.22 and 7.23 that caused an IPv6 incompatibility for the Fairphone. No other device on the network seem to suffer from the same problem, so suspecting that it still is the Fairphone at fault. However, the change log for 7.23 might hint on what might be the cause.
In 7.23 I had a lot of neighbour addresses in failed state, and on 7.22 it is marginal. Haven’t made extensive tests yet though.
These were the relevant RA changes
*) ipv6,ra - added option to ignore MTU and DNS servers;
*) ipv6,ra - added router-advertisement-route-distance setting;
*) ipv6,ra - allow receiving DNS servers over multiple interfaces;
*) ipv6,ra - clamp valid-lifetime to minimum of 2h on deprecation;
*) ipv6,ra - extend processed RA logging;
*) ipv6,ra - fixed advertised DNS parameter logging;
*) ipv6,ra - fixed changing default “all” interface configuration;
*) ipv6,ra - fixed DNS and pref64 property unset;
*) ipv6,ra - fixed sending only DNS or MTU when prefix is set to “none”;
*) ipv6,ra - improved service stability;
*) ipv6,ra - warn when interface is under the bridge;
It could be this:
Hm, my conclusion was premature. While ipv6 seemed to work for a few hours after downgrade, it now seems broken again so something is still iffy.
And regarding the issue you linked, wouldn’t they affect all devices on the network? It’s just my FP6 that is acting up, all other devices are just fine with my ipv6 setup…
Not it’s not linked to this, My fairphone receive RA and update lifetime of Route. So it’s not linked with this change.
That link wasn’t meant to be in response to you.
Jishi’s problem sounded like it could have been the bug fix in RouterOS 7.23 which ended up breaking a load of people’s IPv6 configs.
Also, I’ve now done what I called out earlier so back to the core problem.
Same problem here, after the upgrade to latest e/OS which has Android 16. How is a fix going on? Any more details needed?
Dear Fairphone Team,
thanks for working on the issue and letting us know.
With the latest build for Lineage 23.2 (Aug 10th 2026), @ArianK16a temporarily fixed the ipv6 problem by pinning the wifi firmware from FP6.QREL.15.176.0. So it might be worthwhile looking into this.
You’re probably already aware of this, but I thought it couldn’t hurt to mention it (again). Better safe than sorry 
I’ve had my FP6 for a few weeks now and hoped teething problems would have gone away now. However, I am finding there are apps that just won’t work reliably like they did on my FP3. The worst is BBC Sounds, which may play one programmer but then hangs with a spinning wheel when I try to return to the home screen. This rarely resolves, even after 20 minutes. I have similar with the met office weather app and sometimes others, although they usually do resolve eventually. How do I investigate what is happening here, please?
Is this only happening when connected to wifi?
Thank you, I will test it