Esch Cleared storage, set stock app as my texting app. Made sure play services had access to phone and then logged back into Messages (making it default for texting) aaaaaaaaand still stuck on verifying.
GrapheneOS It takes time if you were already rate limited. Some users say installing Carrier Services helped but it's not clear if it really did or if it just needed more time due to rate limiting.
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".
Emerald nandohyphen1 Pixel 6a user here, I am wondering about the same. After the reboot, no message was shown and I couldn't find a new entry in the settings. Does it mean that my battery should be fine or am I missing something?
GrapheneOS Emerald If you have 375+ charge cycles and do not receive a notification or a notice in the battery settings, then you do not appear to have a faulty battery. The throttling starts at 400+ charge cycles and you likely would have noticed it already if the capacity was being throttled. A bunch of users unaware of the Pixel 6a battery issue reported terrible battery life recently and we raised the priority of adding the UI even without the Android 16 QPR1 sources with the upstream code for it available. We had to do the userspace part ourselves since Android 16 QPR1 still isn't pushed. The throttling was introduced to GrapheneOS in early September when we moved to the Android 16 QPR1 kernel drivers and firmware since it's implemented in the battery management kernel driver.
Emerald GrapheneOS Thank you for the quick reply! The battery has over 500 charging cycles and it felt like the capacity was throttled with the mentioned changes early September. But that might have been just an illusion or the battery draining was caused by anything else. Glad to hear that my battery isn't one of the faulty ones. I wouldn't want to willing have a known fire hazard in my pocket and household.
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.
GrapheneOS With 400+ cycles it should also now display the battery health as Dead which it a bit of an exaggeration but it's what the stock OS does and shows they don't expect people to actually use it crippled but rather take the free replacement, take the cash and replace it yourself or get a newer Pixel using the credit.
vactorio Is there a reason, as someone who doesn't look at the source code, to not enable the security preview releases?
GrapheneOS vactorio We recommend using the security preview releases. It will be added to the setup wizard as a recommendation along with a notification for existing users. We didn't automatically opt people into it because the early patches aren't allowed to be open sourced until the embargo ends. If that wasn't an issue we would have just continued having 1 set of releases instead of 2.
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
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?