Signal calls and allowlisting working intermittently
stef204 opened this issue · 5 comments
Android 11, DNS66 0.6.8
Julian, thanks for this great app. I am posting here as I am experiencing, as well as others, issues with Signal Calls even when I have allowlisted the app. The calls are at times garbled, at other times perfectly clear. The allowlisting seems to have some sort of issue where it is unstable with regards to this messenger app. The good news is that the allowlisting seems to work at times.
Is there anyway this on/off allowlisting problem can be looked at again and addressed?
(I have no problems with a SIP client which I have allowlisted, by the way--but I am disabling IPv6 for this SIP client.)
Also stopping DNS66 from the "start" tab at times resolves the issue, at other times not. Does one need to force close DNS66?
Possibly related info: here.
(edited for language)
Patches welcome is really all I can say here.
That said, we tell Android which apps should bypass the VPN, so if that only works sometimes, then it's an Android bug, and not something that can be fixed in an app.
Understood. In general, when I use Start or Stop from the START tab, do I need to force stop DNS66 or should it take effect immediately?
Same question for allowlisting in general: when I toggle an app in the APPS tab, should it take effect immediately, no force kill/restart required?
(edited for language)
You need to stop+start after changing a setting. The app list is passed to Android at VPN creation time.
Please stop using the terms with racist connotations and use allowlist or blocklist (or deny list) instead. Thank you. (I know, the code needs fixing too, but not all of it can be :/)
Thanks for clarifying the that the app list is passed at VPN creation time (thus the need to restart it.) Keep up the good work.
Edit: I completely uninstalled DNS66 to try to go to a host file solution (with adb root) and, lo hand behold, the problem re-appeared. So it seems it is a bug either in Android 11 or something to do with my device.
In a few words, the issue is hearing the other caller as a very high pitch garble (like a tape you are fast forwarding at high speed.) And this appears intermittently.
So it looks like it is unrelated to DNS66 -- I wanted to be sure to mention that!
I guess I just assumed that the allow/block somehow was not being applied properly to Signal; or there was some other problem, based on this.
assuming = bad
I've also tried it with a completely clean (default) hosts file and the problem is still there. So it is not the hosts file either.
Sounds like it is time to file a bug report upstream.