DNS over TLS/IPv6 issues- Apps don't load data over Wifi

That’s possible. I’ll try that thanks.

It does work. Even toggling wifi off and on seems to do the trick.

Hope they’ll fix that though.

1 Like

Disabling ipv6 … thats what i did now. I dont actually have any ipv6-only needs and better than dis- and enabling wifi couple times a day. Also this ipv6 issues come unnoticed, so sometimes i wonder why my phone is so silent the whole day, just to see the notifications flying in once i restarted the wifi.

I havent gone through all posts of this thread, but did someone confirm that it works with other android 16 devices? I only see that some of you tested with orther fairphones and other androids. But nobody tested if it is generally a problem with android16?

It has been anecdotally mentioned as a problem on FP Android 15, and I’m having no problems with v6 on Android 15 (but I’m using LineageOS on that device).

1 Like

Having the same issues. Fp6 w/ Android 16. Toggling wifi does the trick, but the phone just goes silent until noticed. The last update really killed the fp6. Re: Screen glitch….. it’s a PITA** now

Hi all,

After the update to Android 16 I am also facing connection problems.

While reading the posts about DNS I thought to check my settings.

For me the solution seems to be setting the ‘Private DNS’ to ‘Automatic’.

Not a clue why that seems to work. But before changing the setting, it was on ‘disabled’. And for me the solution to hanging apps was also disabling WiFi.

This sort of software glitches really tick me off. Might be the last Fairphone for me if the software keeps disapointing me.

1 Like

At first I though I’m not affected with this, but now it is so.

By checking https://test-ipv6.run/ the result is

When toggling WiFi off, waiting about 10 Sec and turning off, the test also passes for IPv6 DNS

Don’t ask why, but this points very strong right to Android 16 in correlation to IPv6/DNSv6. And this is only in WiFi.

2 Likes

I have the exact same results on my FP6 with Android 16.
Honestly, my patience is wearing thin. We are talking about a “stable” release that fails at basic networking and security tasks (2FA).

2 Likes

For clearification:

My default setup was already “automatic” so the workaround to change it to that doesn’t work for me:

You are right, problem just reappeared for me. This is really really bad.

Is e/OS any better?

Edit: I made a support ticket. I think everyone should who has the issue. Otherwise the problem will mostly not exist.

I had similar issues since android 16 and only in my home-wifi. I solved it by still using ipv6.

i operate a fritzbox 5690pro. Previously the default option “use native IPv4 connection” was set. I changed it to the second option “use native IPv6 connection”.

here my new configuration. sorry, german:

best regards

2 Likes

Unfortunately, this also only has a temporary effect, at least for me.

IPv6, biometric authentication and 2FA over WiFi are broken again after ~10min.

Anyhow, I also submitted a service ticket on that subject

After trying a lot (moving my router and repeater to the latest lab versions of the OS, changing the repeater to an old model with WiFi-5) and achieving nothing but making things even worse I decided to give up and make a clean install.
So I reverted the router (FRITZ!Box 5690 Pro, placed at the entrance of my flat) to the latest stable version of the OS, which forced a factory reset. I then set up everything from scratch (esp. giving my devices fixed addresses). Settings were kept as close as possible to the AVM setup (using the router as DHCP server and DNS resolver, only widening the range of the home network, not splitting the WLAN). My FRITZ! Repeater 1700 (placed at the entrance of my living room, serving as WLAN/LAN Bridge) is still on the latest lab OS.
After some reboots and purging of the WLAN entries of the FP6 and cleaning data and cache of “MyFritz! app” and “FRITZ!App WLAN” everything was up and running.

The results so far:

(1) FP6 in my living room connected to the repeater:

(2) After shopping, FP6 in my living room connected to the repeater, no manual WLAN reset!

Fingers crossed…

1 Like

I’ve disabled ipv6 in my network entirely. No ipv6 DHCP, no DNS broadcasting. Seems to do the trick, but is of course completely unacceptable.

1 Like

Having this problem

One note is less good, BBC sounds often just doesn’t work until I restart my phone

This seems to be an android bug: https://issuetracker.google.com/issues/429703129

You can vote “I am impacted” in the top right corner.

7 Likes

Hi,

it was NOT the solution. It works for some hours, but then it starts again.

best regards

nyenyon

I’ve been experiencing the issue where apps don’t load (or take a very long time) when connected to Wi-Fi, while mobile data works instantly. A temporary workaround was toggling Wi-Fi off/on, but the problem always returned after a few minutes.

After some digging (including Issue Tracker 429703129), this seems related to an Android network stack issue where IPv6 routing is not properly restored after certain Router Advertisement (RA) events.

Setup:

FRITZ!Box (Dual Stack (IPv4+IPv6) enabled)

Pi-hole + Unbound as DNS

Android 16 on Fairphone 6

Symptoms:

Device has a valid IPv6 address

IPv6 connectivity becomes unstable or partially breaks

DNS queries go over IPv6 and may time out

Apps hang or fail to load, even though IPv4 still works

Potential workaround (still testing):

On the router (FRITZ!Box):

Home Network → Network → Network Settings → IPv6

Disable the following option:

“Announce DNSv6 server via Router Advertisement (RFC 5006)”

Result so far:

DNS is resolved via IPv4 (e.g. Pi-hole)

IPv6 is still used for actual traffic

No more hangs observed so far

No need to toggle Wi-Fi anymore

That said: still early, so consider this a potential workaround rather than a confirmed fix.

Quick verification (before / after):

You can check if the change took effect:

Go to Wi-Fi → your network → details

Look at the DNS field

Before:

IPv6 DNS present (e.g. fdxx:…)

plus IPv4 DNS

After:

Only IPv4 DNS remains

no IPv6 DNS entry

If the IPv6 DNS entry disappears after reconnecting Wi-Fi, the change was applied correctly.

(This does not disable IPv6 itself – only DNS over IPv6.)

1 Like

Quick follow-up:
Disabling IPv6 DNS advertisement (RDNSS) on the FRITZ!Box did not fully resolve the issue for me. After some time, apps still stop loading on Wi-Fi

I still need to toggle Wi-Fi (disconnect/reconnect) to recover. So the underlying problem is still there

What changed:
DNS is now only via IPv4 (no IPv6 DNS anymore). This seems to avoid immediate DNS timeouts. But it does not fix the general IPv6 instability

Observation:
Right after Wi-Fi reconnect → IPv6 works fine (10/10 on test-ipv6.com)
After a while → IPv6 degrades or breaks again
Behavior matches what others described

So this looks more like a routing / IPv6 recovery issue rather than just DNS.
Conclusion (for now):

The RDNSS tweak may help a bit (less DNS-related hanging)

But it’s definitely not a full Workaround.
Still testing, but for me the issue is clearly not solved yet.

Curious if others see the same behavior.

Somehow today the phone is performing normally.

Although I did set a private DNS (DNS4EU) so it seems to me now that it has something to do with the problem.