GrapheneOS version 2025092700 released

Saint

GrapheneOS Is there a list of what permissions are required by what apps in order to get RCS working following this new update? It just seems like it's stuck in "Setting up".

skorge

ETA Can you give me a detailed explanation of what you did to get it working? I followed the permission guide and enabling the read phone numbers permission thru appops but it still just continuously says Connecting... for me.

ETA

skorge

Make sure google account is connected to phone number and phone number verification is enabled.
Give google place services phone permission as mentioned with the GOS update.
Download google msgs and connect to rcs.

This worked for me

EDIT: I should add that it took 5 min to connect and verify my number

DeletedUser458

I have two different Pixel 9 Pros and I noticed after updating to the latest that the 6 GHz band SSID on the router is no longer able to be connected to as I normally do. It only allows me to use the other 5 GHz band SSID and the 6 GHz one no longer shows as an option even. I checked an old pixel 6 that did not update and it still shows that 6 GHz band SSID and can still connect to it. Please are we able to allow the pixel 9 pro to connect to 6 GHz WiFi again or was it more secure to just use 5 GHz? I know wpa3 is most of the security however I thought maybe since less tools or devices can utilize or abuse 6 GHz it may be a little bit better than 5 GHz.

DeletedUser458

DeletedUser458 I rebooted a few times later on and I seem to be able to connect again. 6 GHz working now.

Aru

Just wanted to report on the "device is corrupt" issue I got on my Pixel 6 after the previous update. Installing this update fixed it.

grish

RCS also not working for me still - I've tried:

Rebooting
Disable Google Messages
Clear both the storage and cache
Reenable the app
- At this point, all permissions except Location are enabled
Open Google Messages, select my account

At the moment I'm stuck at Setting up..., prior to this I was getting the 4006 "Your device does not meet the safety requirements" error that others have mentioned

latetothegame

grish
Same. Pixel8, US Cellular.

ntop

All

It seems like it has broken Barclaycard app now after the update.
Getting
Error 00006
Ops... Something has gone wrong

Can't even register again..

Will call Barclay's and see what I can do

wizoatk

ntop

FYI. Recent update of the app too.

https://play.google.com/store/apps/details?id=com.barclays.bca
Updated on Sep 22, 2025.

ntop

wizoatk already check for update and I have the below version..
Version 2.72.1
com.barclays.bca
versionCode 6721
targetSdk 36
minSdk 26
Installed: 5 Jul 2024; 07:12
Updated: 26 Sept 2025; 23:20

GrapheneOS

We think Google Messages needs Play services to have some additional access for a subset of users and are looking into it.

lcalamar

GrapheneOS Would that mean a new release for that? (I've repeated all the steps several times - an still can't get RCS to work).

I wonder if using Google FI as a carrier is causing issues? (maybe that's the subset?0

GrapheneOS

Vuraze

GrapheneOS
I'm also having issues enabling RCS, even with doing the steps provided. This seems to affect a lot of T-Mobile users, which I am apart of. Do you need us to send more logs to see what's going on?

Boss777

Hello here! Sorry to bother you again with my 7 Pro updates troubles ;). Now it's all bad. After update and reboot and app optimisation finished I left the phone on the wireless charger. I forgot that it will not wirelessly charge after the update, so it got fully discharged. I plugged in the cable and left it for the night. Now I cannot turn it on. The screen is black, but the phone is probably alive. Long press on the power button produces one haptic feedback. Plugging the charger makes usual sound. But nothing else. It is not connected to wifi, connecting USB to a computer doesn't show any USB device.
Is there any way to "reset it" not in a sense of re-flashing, but fully power off without screen controls?

yore

Boss777 It's best to leave it plugged in for a couple of hours and then try using it. If for some reason the OS is booted but there's no input, you can hold the power button for 30 seconds to do a hard shutdown

W1zardK1ng

Boss777 connect the charger, press power button while phone is starting to pause the boot process. Leave the phone like that for sometimes. Resume the boot by pressing the power button again. Phone should start like normal.

Boss777

yore This was the state after spending a night on the wire charger. The hard shutdown keys are Power+Volume UP, so I did and it has rebooted in the working state.

skorge

lcalamar I dont think the carrier is the issue, I'm on Mint and having the same issues after following all the steps. Multiple people on Mint, Verizon and AT&T have said it doesn't connect to RCS for them either

lcalamar

GrapheneOS When I go into the phone app permissions I don't see anything specific for play services?

Here is what I've checked:

Play services, app permissions - phone is allowed
Google Messages, app permissions - phone is allowed
Google FI, app permissions - phone is allowed
Phone, app permissions

Am I ok on Permissions?

lcalamar

skorge Ah- I see. I guess it is good to know 'it isn't me!"

Saint

I'm on Verizon. RCS setup still says "Connecting". If I touch the little ⓘ symbol, it says, "RCS is provided by your mobile carrier under their terms of service". Despite it still saying "Connecting", it seems to be working. I'm not positive though. When it worked in the past it said something else. I just can't remember what it was.

GrapheneOS

Carrier Services does not appear to be required by Google Messages for RCS and we recommend uninstalling it. We've determined that there's likely another sandboxed Google Play workaround require which will potentially require a toggle for granting special access to use RCS.

« Previous Page Next Page »