I did, and there’s nothing I love more than random standard responses when the issue has not even been addressed by the update in question. It’s a very annoying problem and Fairphone’s handling of the issue is not making things any better.
I have the same issue for more than a month. Currently, I am on FP6.QREL.16.69.0. Please fix it. It is costly to disable WIFI.
I got a reply today from a guy from the support, saying he will “ask for advice from the relevant department”.
Let’s see if things helps anything…
Have you heard back?
Yes, I did.
Thank you for waiting!
I’m sorry to hear that you are currently running into this issue with your Fairphone. Thank you for bringing this to our attention.
We have forwarded the full details of your case to our technical team for a thorough investigation to identify the root cause. Please be assured that we are working to resolve this as quickly as possible.
While we work on a permanent software fix, we recommend trying the following temporary workarounds:
Option 1: Disable IPv6 on your home network (Recommended)
If you have access to your home router’s admin settings, temporarily turning off IPv6 (allowing the router to use IPv4 only) has successfully resolved this issue for many affected users.
Option 2: Switch to mobile data
If you cannot modify your router settings, you can bypass the local network conflict by temporarily switching to mobile data when you notice an app loading slowly:
On your Fairphone, swipe down from the top of the screen.
Tap Internet and then tap Wi-Fi to turn off.
Try loading the app again.
Note: Please remember to turn Wi-Fi back on shortly after to avoid using up your mobile data allowance.
We also encourage you to install any new software versions that are released, as these updates often contain important improvements and may deliver a fix for this issue: How to check and update your software version.
We will reach out to you immediately once we receive any news, an update, or a solution.
Thank you again for your patience and understanding.
So, no news here but it seems they are working on it.
Thanks for the update.
3 months of this now. What a joke.
Waiting for a fix since march (no ipv6 connections over wifi and mobile network w/o private DNS) i reseted now android system wifi/bluetooth and mobile network settings to factory default.
Now i have stable ipv6 connection w/o private DNS over wifi and mobile network for hours!
Fascinating. I may try this. It’d be inconvenient to have to connect to wifis again, but definitely worth it if it fixes this ridiculous problem.
Hell, I’m gonna try it now.
I tried that tip too, but it stopped working again after a short while.
That’s laughably bad to suggest as a workaround. Let alone give it as the first suggestion.
Yeah, when I checked a few hours later it was indeed not fixed.
Actively unhelpful to suggest as a fix 
Still, bonus of resetting Bluetooth: I can now select hd audio again (that had broken with the Android 16 update).
I could nog find the option to disable IPv6 on my modem (Ziggo in the Amsterdam erea). But I did find the option to set DHCPv6 to statefull (instead of stateless). This fixed the problem!!! It looks stable as well. Apps load data fast for more then a hour now.
Be sure to check in tomorrow when it stops working again!
Well, @BasB4 might be on to something. In the debug logs it fails with RA (route advertisements, in SLAAC (stateless config)). If you set this to a static config, you wouldn’t rely on this anymore and it could be an effective workaround. Let us know if it worked! IPv6 is not meant to be used statically, but for a temporary workaround it’s fine (if it works).
It was mentioned before…
And it was mentioned (and later apparently confirmed) that this simply disables IPv6.
Well as long as the workaround helps? All other ideas so far lasted not more than a few hours I think, so…
It’s not a valid workaround. Do you go around your friends and family, asking them to disable ipv6 in their routers when you visit? For most of my family, I could ask to flip the flux-compensator, it makes the same sense.
Could anyone please decide on their own what workaround works best for them? Thanks!