Which security features?
Have there been any updates regarding this issue, or has anyone heard from support? From rereading posts on this topic, it doesn’t even seem like this issue has been acknowledged or even understood by the Fairphone software developers.
They have it’s been on the issue tracker see; https://support.fairphone.com/hc/en-us/articles/9831446296849-Public-issue-tracker
Not sure, but since I’ve updated Google Play Services in the morning, I haven’t had these issues anymore: In Android Settings, search for “google play” and select “google play system update” (or similar, it’s “Google Play-Systemupdate” in the German version). My Google Play Update is from April 1st and even after toggling WiFi, everything’s still working.
Nope, it doesn’t change anything. The April update has actually been out for a few days now.
Yeah, you’re right, sorry about that :-/ Maybe it was the reboot that made it work for a few hours. 
It helped for me!
Thanks!
Honestly I am about to sell my FP6 after one week with it. Constantly having to disable and re-enable the Wi-Fi is horrible. No other device has this issue and disabling ipv6 is no option for me as I need it for matter/thread…
I recommend you just trying a local dns app like rethinkDNS (mozilla) or cloudflare 1.1.1.1 vpn app as a workaround till a fix is released.
It’s an extremely annoying bug. Using my VPN on my phone to bypass the IPv6 is a lifesaver, but has its own set of issues of course (slower, roundtrips, extra captchas and loading buffers).
This should have way more prio.
This has prio however as mentioned above is in first place a Google issue
Thanks for the tip but I rather reconfigure my network than bypassing it. For now I went ahead and rebuilt my VLAN structure so IPv6 is only needed in two VLANs, not affecting my FP at all. I didn’t need to toggle Wifi for 3 days straight now. So for me it’s solved but that’s because of my new network structure.
It is astonishingly bad that this problem persists. I’m honestly thinking of replacing my FP6.
The FP3 was plagued by poor software support - new bugs with every update - and I had hoped that by now things would’ve improved.
As the saying goes: fool me twice, shame on me.
Blame Google, head over and add your voice over there
It’s always easy to shift the blame onto others. But why does it only happen on Fairphones? Wouldn’t all other Android devices be affected as well?
They could add a button “Disable IPv6” in the network settings, or another workarounds but this error handling looks a bit embarrassing.
My FP6 broke a while back and I had a Pixel 10 Pro for a few weeks. I noticed the same apps having issues. Not sure if Pixels have it solved by now. But at that point I first thought it was because I was messing with my network. Since I only had it at home.
It does NOT only happen on FP6.
Did you even dare to click on the link and read or read above?
I also see the problem with Fairphone. Afaik there is not even a confirmation, that this issue is the exact problem we are seeing here. I really tried to look into the details and could not reproduce the problem in my network, as the proposed trigger did not occur here. Even then, the thread already provides a fix, which Fairphone could have implemented and tested by now. Also, our Pixel phones work fine, so Google would fix their brand line and not feed the fix back into AOSP?
Current status from Fairphone is still “under investigation” and there are no reports here that somebody heard something specific from them.
So this annoying bug is still standing and the only working solutions for me are toggling WiFi or using a VPN, which has its own drawbacks. As somebody already mentioned, I am not the master of all networks I connect to and the problem also occurs outside our home network.
I can tell you I heard from them
You mean the fix that probably was implemented with QPR3 for Pixels, so after approx 9 months of first report in the issue tracker?
It’s also worth mentioning that the Pixel March update is different from the March (Android Security Bulletin) update that other phones get. The March update rolled out QPR3, the third quarterly update of Android 16, which updates many parts of the OS, not just security fixes. So, it has fixes that other phones do not have or get (other OEMs can release major and QPR2 updates).