Lock lbschenkel I do hope that is how it works. Is there someway I can test this or a developer could confirm
lbschenkel Lock How can it not be how it works? This is trivially verifiable by yourself: Configure your router to route all traffic through the VPN. Enable VoWiFi in the phone. Enable airplane mode. This will totally cut power to the modem. Enable WiFi. Check that VoWiFi is indeed working by making/receiving calls. There's no other route for the packets to go through but: WiFi -> router -> VPN.
Lock lbschenkel Well that's obviously easy to test. I mean testing that it's not using the android VPN I don't want my calls routed through a VPN
lbschenkel Lock The fact that Android does not use the in-phone VPN for telephony has been widely documented. If you search the Internet you'll find plenty of evidence.
23Sha-ger Lock https://discuss.grapheneos.org/d/3158-wifi-calling-bypasses-vpn This has been discussed many times
Lucario1829 carlnickel i would try manually sideloading the latest update, ive never done this so i cant really help but theres a guide somewhere on graphenes website
LeslieFH Just as an information, RCS wasn't working for me two weeks ago, now I see RCS chats are working again. :-)
spl4tt RCS is indeed working now kn my 9 pro fold. amazing, thanks a lot! Still the question remains: Is using google messages itself even save enough?
Johnnyloans T-mobile, I can get RCS to connect with an old apk but once I update via google play, it'll say "trouble connecting" in 12-24 hours. Thank you for your work
underhand Johnnyloans T-Mobile MVNO, same here. Worked using the process posted earlier (older Messages version then upgrading to new version) but it eventually craps out again as others here have stated.
GrapheneOS carlnickel When you press check for updates, it should show either the progress notification or already up-to-date notification. If it's not doing that, then something is wrong. You may have already installed the update but never rebooted and the reboot notification got dismissed. Our latest release coming out today prevents disabling the overall System Updater notification or the Reboot channel along with dealing with Android 15 QPR1 and later having a standard 3 day timeout for notifications.
gos27371 GrouchyGrape I just recently was able to setup and use RCS without even using my Google account in the Messages app. This is in the US and on a non-graphene phone, but I would assume it's the same. RCS is now the carrier's responsibility, so shouldn't depend on Google at all.
underhand I'm on 2025102600, switched to a non-T-Mobile MVNO, rebooted a couple of times, and I'm getting a new RCS error for registration: Status code 4006 - Your device does not meet security requirements Are further RCS fixes still being looked at?
de0u underhand I'm on 2025102600, switched to a non-T-Mobile MVNO, rebooted a couple of times, and I'm getting a new RCS error for registration [...] Which MVNO?
de0u underhand currently Verizon If a clear statement can be available of which Verizon MVNO is being used, perhaps other people who are using that carrier can indicate whether RCS is/isn't working for them. But knowing only that the problem is encountered with some unstated Verizon MVNO is less useful in terms of problem solving.