GrapheneOS version 2025092700 released

GrapheneOS

hex Did you grant the Phone permission to Play services and the required permissions to Google Messages (you can use Contact Scopes, etc.) first?

akslr

GrapheneOS I think it's unclear in the announcement that you should grant the phone permission to google play services.

It mentions "granting the required permissions to Google Messages" and "access to the official Google Messages app which then also provides the official Play services app with the same access" makes it seem like permissions on Google Messages are sufficient.

My RCS is currently on 3000, please wait activation is in progress, I'll report back in the morning. I granted phone permissions to GPS and Google Messages.

GrapheneOS

Try installing Google Messages from the official Play Store instead of another method since it may check the installer. Some users believe installing Google's Carrier Services app was also required for it to work for them, but we haven't confirmed this.

akslr

akslr That did not work, but I wiped the cache and apl data and it connected immediately.

GrapheneOS

akslr It's already clear about that, it says this:

Using this requires granting the Phone permission to Play services to provide carrier information to it, granting the required permissions to Google Messages and then setting Google Messages as the current carrier messaging app.

It might be necessary to install Google Messages from the Play Store rather than elsewhere and some users may need Carrier Services but neither of those things is confirmed yet.

Watermelon

@GrapheneOS I suggest updating the usage guide with the RCS information and just pointing to it from the release notes instead of having the information in the release notes

akslr

GrapheneOS right.. No idea how I blanked that sentence, mb

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

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?

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.

ETA

RCS working for me :) appreciate it guys!

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.

« Previous Page Next Page »