GrapheneOS version 2025100900 released

GrapheneOS

Gerolamo Did you see our response?

MrRoboto1212

MrRoboto1212 This is working for me so far

As I expected, RCS is back to 'Connecting' again...

MrRoboto1212

MrRoboto1212 As I expected, RCS is back to 'Connecting' again...

Upon re-updating the Aurora version through Aurora, RCS is back to being connected

MrRoboto1212

Vuraze I checked the verification of the Aurora version and it's correct, but Play Store is still giving me the 'this app isn't from PS' warning and I'm unable to update it. Idk wtf is going on. Cleared the cache; force stopped and restarted, still giving me the same thing

~~I'm going to keep the Aurora Store version 262371063 not updated for a few days and see if RCS disconnects again like before.~~ Never mind, can't do that. RCS says it's connected but it's still only SMS on that version

MrRoboto1212

MrRoboto1212 A few hours after this post, i switched to APKMirror version of Messages, successfully updated via Play Store, and RCS worked for a day again before flashing the 3000 / 3200 error.

Anyone under T-Mobile who's able to permanently fix this issue, please reply to me. Many users would greatly appreciate it. Not sure if the pool of users who this affects is large enough to warrant study time and a solid fix from the GOS team...

Rasta9

Not sure if it's from this update or not (my phone did about three updates in a day for some reason), but for the past few days now, my bluetooth earbuds are not automatically taking over phone calls when I get out of the car. Cheogram, and Signal are defaulting to the device earpiece when previously it had switched to the still connected earbuds that never disconnected. The apps haven't updated for me recently and the only change I can think of is the device update.

underhand

Vuraze this is what also worked for me, though it's similar to how I got RCS working even before the breakage and subsequent recent updates. So I'm not sure if it's this process or the updates that resolved it, but I couldn't get RCS working at all until doing this, regardless of the recent updates.

carlnickel

I did not receive this update - nor have I received any update since early september. I am still on 2025090600 (stable release channel). There must have been 6 updates since then, none of them showed up on my Pixel 8. I checked for updates manually by tapping in the system settings several times.

This never happened to me before on GrapheneOS. Has anyone an idea how to receive updates again?

Lucario1829

carlnickel did you disable the update chack notifications? some people do that because theyre annoying but theyre crucial to updating

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.

de0u

carlnickel Has anyone an idea how to receive updates again?

What happens if you reboot (once)?

Lock

GrapheneOS

How does VoIP over LTE/5G work when a user profile is connected to a VPN with kill switch?

Is everything routed over the VPN server and then to the carrier ?

lbschenkel

Lock As far as I know, in Android all telephony stuff including 5G will never be routed via the VPN.

If you want to use VPN for telephony, you must force the phone to use VoWiFi and then do the VPN at the router level.

Lock

lbschenkel I do hope that is how it works. Is there someway I can test this or a developer could confirm

carlnickel

Lucario1829 yah good idea but I have them enabled. Thank you however

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

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

Lock

23Sha-ger thanks, but what about VoLTE

LeslieFH

Just as an information, RCS wasn't working for me two weeks ago, now I see RCS chats are working again. :-)

zache

Vuraze This got it working for me on Mint Mobile on a Pixel 9a, thanks!

« Previous Page Next Page »