New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable toggle for Wi-Fi calling always and make it fully disable DNS resolution and ePDG connections when disabled #887
Comments
This may instead turn into an option to have a SetupWizard screen to enable it, discussion needs to be had around this. |
Isn't it already disabled by default? On fresh setup or changing a sim card, I've found it is necessary to manually switch wifi calling on to make it work. |
It depends on the carrier |
It's necessary when signal strength is low - is there detection? |
Carriers or the user can decide when it automatically kicks in. We aren't going to remove the option for the user to enable/disable it. |
Can someone provide some details about VoLTE? I can't find, how this feature is implemented in the OS / Chipset of a phone. Where does this feature sit? Is the traffic going to be routed via VPN or is there an exception? My personal opinion is, that it's much more safer to get VoLTE Calls instead of regular calls. Because via Mobile Carrier the phone can be triangulated. With VoLTE only the IP gets exposed. The IP you have control over. |
VoLTE traffic is carrier traffic and not user defined traffic, it won't go via a VPN.
LTE is the telecoms network. This statement doesn't make sense. What generation of mobile network technology you are using doesn't change the fact that the carrier can always obtain a coarse location. |
I do have a branch: This seems to be on a branch GrapheneOS didn't fork, so I had to do it myself. Sorry if I got anything wrong here. A barebones Android 13 branch without my patch is here in case it's needed for forking: This will need GrapheneOS to fork the My patch unconditionally disables VoWiFi unless a user enables it themselves. |
@neelchauhan We can just remove this option from all the CarrierConfigs since we process them before shipping them using https://github.com/GrapheneOS/carriersettings-extractor. But also, sadly this alone won't fully disable it. The OS will still make ePDG // DNS traffic despite this option being removed/ignored so that will need to be investigated. |
I have a This doesn't take care of the ePDG/DNS traffic but I will also look into this. |
@neelchauhan looks good, thanks. as a pointer, easiest way to capture traffic to assist with debugging is a userdebug build and use tcpdump (comes with the build). |
I believe this will need a new repo: https://github.com/neelchauhan/platform_packages_services_Iwlan/tree/13_disable_wifi_calling This is the I will need to test tomorrow, or whenever I can. I need to charge my Pixel 6 since my Pixel 7 is my main phone and I don't want to run userdebug on my 7. |
@neelchauhan Looks good so far but you might need to add more changes for carriers where they specify a custom ePDG hostname or IP address where they do not stick to using a 3GPP hostname. For example Jio in India does this in CarrierConfig:
|
If you want to have a chat about it in further detail at all or have any questions feel free to join https://app.element.io/#/room/#dev:grapheneos.org |
Thanks! I realized I may be able to do a more global block of ePDG traffic in If that is an issue, my existing branch also has a new commit blocking custom ePDG names as well. |
No description provided.
The text was updated successfully, but these errors were encountered: