Using RCS with Google Messages on GrapheneOS

stuntinmurda

T Mobile. I did the work around of installing an older version of the messaging app on Saturday evening. It worked great until Tuesday morning.

B1naryB0t

tebriel How do I add the device identifiers setting on the phone? Can't find any gui options

emb

B1naryB0t First enable "Developer Options" by clicking seven times on "Build Number" in Settings > About Phone. Then enable USB debugging from Settings > System > Developer Options > Debugging. Next plug in to a laptop with adb (Android Debug Bridge) installed, and run adb shell to get a shell on the phone.

Then do the appops command in the post you replied to.

5rlyn

5rlyn I can confirm that the message i sent at 00:37 Zulu was sent RCS. The message I scheduled to send at 00:46 Zulu fell back to RCS. At present, I am "Connected," and can still receive RCS, but I imagine I will lose that capability at my next reboot or shutdown.
Bit disappointed that Carrier Services wasn't the magic bullet, but I trust @GrapheneOS to solve the problem.

GrapheneOS

The issues with some specific carriers are a separate thing. We've determined Google Messages appears to have started requiring a bunch of privileged permissions for certain carriers recently. That's why old versions still work for those users on T-Mobile, etc. but it will likely stop working properly if you update even if it doesn't take appear to stop working right away. We recommend against using an old app version since you won't have security updates if any have been done, which is likely due to the type of app it is.

5rlyn

GrapheneOS when you say "separate thing," is the proper course of action to wait for updates, or to find a new carrier?

ButtholeBlackhole

GrapheneOS I have Mint and even the old version doesn't connect for me. It just says my carrier doesn't support RCS. Doesn't even try to connect.

Amuser6949

GrapheneOS Thank you for your continued work on this issue. I have a recurring donation coming your way as soon as my financial situation allows for it.

tebriel

GrapheneOS is there an issue to follow on github or elsewhere to keep track of updates?

GrapheneOS

5rlyn We know it could be resolved by granting the privileged permissions requested by Google Messages but that doesn't fit out approach. It could be done as an opt-in toggle similar to Android Auto. However, for Android Auto, the wired Android Auto toggle only has to grant USB access so it's not invasive at all unless you want more functionality.

BuckWylde

ButtholeBlackhole I've also had that issue (also on Mint). It resolved after uninstalling messages, rebooting, and starting over with the routine. I hope you can get it working for now. It seems that sometimes the uninstall reinstall combo doesn't quite stick.

emb

chenxiaolong Oh, interesting. I wonder which apps (if any) do use it, then. Thank you for checking!

chenxiaolong

emb No problem! I just did a quick check with:

for package in $(pm list packages | cut -d: -f2-); do
    echo "${package}"
    cmd appops get --user 0 "${package}" | grep USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER
done

The only packages in the stock OS where that permission is allowed are:

android (system server)
com.android.qns
com.android.settings
com.google.android.iwlan
com.google.android.satellite

5rlyn

BuckWylde I've lost the ability to receive RCS messages, and my messages app has gone back to Trouble Connecting Awaiting Retry.

jumpdeer

The old apk doesn't even work for me anymore unfortunately. It says Connected but only SMS works on Tmobile

mousetrapreplica

jumpdeer I've been using the workaround of installing the older version APK and then updating. When RCS stops working I uninstall Messages, reboot, installed the older APK again, make it the default SMS app, open Messages, RCS says connected but only SMS sends. I then reboot, update Messages via Play Store, check to see if I'm chatting in RCS and if nor reboot again and wait a minute or two before chats switch to RCS.

Nora

Stuck between "setting up" and connection failed. Carrier is FirstNet/ATT, called pretty helpful, reprovisioned SIM, still not working.

Judgeadam

Hey guys, bit of a good news, bad news situation.

So it looks like individual RCS chatting works for me. The problem is, in RCS chats with multiple people on iPhones, even though it's blue and it has the double check mark, they aren't receiving the messages, and I tested this on multiple chains. I have even had those people restart the chains and I've restarted the chains using only phone number making sure it's not using iMessage. I would advise you guys to make sure to test that the group chains are really getting your text messages because it's easy to just say something and think everyone is ignoring it, which is what was happening to me.

Just wondering if anyone else is experiencing this, I am on Verizon, by the way, on a Pixel 9 Pro. In the Northeast. I'm on the latest Google messages beta chain and GOS latest.

Nora

Judgeadam Same issue, group chats appear to be the issue. Although I still can't get RCS to fully connect. Added in Google Carrier Services App, didn't help (yet). FirstNet/ATT PIxel 7a, fully updated, full permissions granted to everything at this point.

5rlyn

tebriel I believe this is it.

My question reading through is will GOS be able to sort out these specific carrier configs for RCS to work? Or do I need to start reevaluating my cell provider if I want RCS?

iudnu

After struggling and getting several different errors (SIM not supported, device not supported, various error codes) I de-registered my number with RCS on Google's service page, and left it alone for a week or so until coming back to it.

I followed the instructions here: https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/1185

But when I tried turning RCS on, I was greeted by "this SIM does not support RCS" or something to that effect. Neither my SIM nor provider (Fido; Rogers network in Canada) have changed.

Following someone else's advice I went in to cellular settings and turned OFF my primary SIM, toggled on an eSIM I had but which had been off, then toggled the two back how they were with my primary SIM being the only one on.

Then when I opened Messages, it showed "connected"!

HOWEVER, I don't believe it's actually working. All messages continue to be sent as SMS or MMS even when I know the recipient had RCS enabled.

Messages to multiple iPhone users are going through, including images (as MMS). And messages from them are being received. But images from multiple iPhone users are not being received.

So it's an improvement, but still not working properly it seems...

PayingPiedPiper

I can get it working no problem in the main owner profile but can not get it working in secondary profiles. Is there some permission that I need to give secondary profiles so they have the same identifiers that RCS needs or something? 🤔

« Previous Page Next Page »