Before submitting, please confirm
Flutter Doctor output
Platform
Android
Build mode
Release
Environment details
- OS: Android 15
- Device: Sony Xperia 10 VI (XQ-ES72)
- Architecture: arm64
App version
v2026.8.18
Steps to reproduce
- Enable Private DNS in Android settings
- Add a server to your TrustTunnel app that has a domain name address, not an IP.
- Reboot the phone
- After the reboot go to TrustTunnel and try to start the tunnel.
Expected behavior
The tunnel is established
Actual behavior
For at least a couple of times it will almost instantly fail to start. On this Xperia phone, I am able to establish the connection eventually (when I tap the button 5 times). On my personal Google Pixel phone with GrapheneOS I can't establish the connection at all after reboot until I disable Private DNS.
Screenshots
Additional Information
It is my understanding the netd is responsible for resolving the domain name provided in server address.
I tried to feed the logs to Claude, and from what I understood in some occasions it is possible for the establishing tunnel to kill netd's connection to the DoT server. But at the same time netd has a cache, so if you "warm it up" by resolving the domain beforehand, it will work.
Before submitting, please confirm
Flutter Doctor output
Platform
Android
Build mode
Release
Environment details
App version
v2026.8.18
Steps to reproduce
Expected behavior
The tunnel is established
Actual behavior
For at least a couple of times it will almost instantly fail to start. On this Xperia phone, I am able to establish the connection eventually (when I tap the button 5 times). On my personal Google Pixel phone with GrapheneOS I can't establish the connection at all after reboot until I disable Private DNS.
Screenshots
Additional Information
It is my understanding the netd is responsible for resolving the domain name provided in server address.
I tried to feed the logs to Claude, and from what I understood in some occasions it is possible for the establishing tunnel to kill netd's connection to the DoT server. But at the same time netd has a cache, so if you "warm it up" by resolving the domain beforehand, it will work.