GrapheneOS version 2025100900 released

jumpdeer

Has anyone on T-Mobile gotten RCS to work?

Vuraze

jumpdeer
Yes. It seems that people who are on the T-Mobile network need to use an older version of Google Messages for RCS to initially connect.

Here are the steps I did exactly:

Give Play services the Phone and SMS permission (you most likely don't need the SMS permission, I did it just to be on the safe side).
Download and install an older version of Google Messages. I used Apkmirror, but you can use Aurora Store's "manual download" feature. The version I used was messages.android_20241120_00_RC07.phone_dynamic (262371063). Make sure you have the genuine version installed. Confirm using AppVerifier from Accrescent.
Set the Google Messages app as the default SMS app before opening it. If you accidentally open the app before doing that, simply just clear all app data and you should be fine.
Open the app and wait until it says RCS is connected in the RCS Settings menu. It should only take a few seconds to a minute.
Once RCS is connected, update Google Messages from the Google Play Store.
If you can't send or receive RCS messages, reboot the phone. All missed RCS messages should come flooding.

Here is the correct hash for Google Messages:
com.google.android.apps.messaging
CC:75:52:6D:6C:0F:80:AC:3B:3A:84:EB:44:83:84:40:DB:BE:6B:12:44:43:A7:C7:D7:BD:19:18:2A:C0:22:C9
F7:E7:3D:4E:DC:2B:7F:55:EE:CD:3F:89:8D:3C:CA:7D:A9:CB:BF:51:69:4E:BA:14:F8:16:E2:EC:CF:01:50:35

If someone who uses the T-Mobile or its MVNO's like Mint and Tello has a different way of getting it to work, please post your steps.

brawfx

Vuraze Thank you for this! I'm on T-Mobile and could NOT get anything to work. I ran through your steps exactly, and suddenly in debug I see Etouffee provisioned: true, and I have an RCS option in my messages. It may have been that I was being rate limited, or did something out of order, but your steps worked for me.

WestQuester

Vuraze Excellent, that got me (Mint Mobile) back online. I tried the Aurora store first and while that worked I couldn't update from the Play Store (wrong signature I think) so had to go with APKMirror instead. Thanks for sharing this!

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

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.

abednego

Hyperlink to #2025100900 is commented out on releases.html yet:

<li> <a href="#changelog">Changelog</a> <ul>  <li><a href="#2025100300">2025100300</a></li> <li><a href="#2025092700">2025092700</a></li> [...]

Thanks for another impressive release.

Ssl117

So I just updated and was wonderingwindering why I suddenly have an app under device admin called find hub. I understand its for find my phone/remote wipe, but there's no way to delete it with out deleting sand boxed google play services ? Is this normal to have or no?

Bunts

SillySaurus yup can confirm, Telus esim rcs working great here.

After it said connected and all my convos upgraded to rcs it did take a few hours for it to actually work but now it's working as intended.

Thanks graphene team 🥂

nandohyphen1

GrapheneOS

System Updater, Setup Wizard: integrate support for recommending opting into security preview releases during the initial Owner user setup and for existing users via a persistent notification which is disabled after making an explicit choice on whether to use security preview releases (this is necessary to inform all users about the option with an explicit choice)

Could you please explain what exactly this means? Should I opt in? Thanks

GrapheneOS

nandohyphen1 See https://discuss.grapheneos.org/d/27068-grapheneos-security-preview-releases for more details. There's also an explanation included in the OS in the UI shown for choosing whether to use it. You can always just dismiss it and decide to opt-in to it later too. It will show the notification again each boot until you choose enabled or disabled explicitly, but you can still change it in the update settings too.

nandohyphen1

GrapheneOS Does it affect how the phone works? Like if I'm on Stable and I enable this, is it more of a 'testing' feature or does it not affect anything?

yore

nandohyphen1 I asked a similar question in another thread. Here is the project's response:

GrapheneOS It's exactly the same as the regular release it's based on other than a set of future Android Security Bulletin patches still under embargo being applied to the source tree before building. We plan to provide a toggle in the setup wizard for it which will likely be enabled by default. We expect it to be well tested.

nandohyphen1

yore haha, just as you posted that I finished reading through that thread. Just saw that response from GrapheneOS. Thank you. :)

Eirikr70

6a here. Works fine as always

andrej567

it appears to work as always, but this time the apps were optimized twice.
there was the first reboot,
then apps started to optimize and then there was the notificaton for another reboot.
i waited until optimization finishes, then pressed reboot.
after reboot it optimizes again.

Lefteros

I'm experiencing something after latest update in stable..

I had touch to display time and notification count while locked and now it doesn't seem to work.

Did we change something in latest patch?

Lefteros

It was fixed after app optimization finished its thing false alarm..

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

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...

« Previous Page Next Page »