I have an S22 while my wife has an A71 5G. We are both on T-Mobile. My phone has the Samsung skinned Google Messages - with RCS services provided by T-Mobile. My wife has the standard version of Google Messages with RCS services provided by Jibe. We both have RCS enabled and are connected. Most of the time, if my wife wants to send me a message - Messages says it will be sent by RCS, but the message is never sent - until she manually commands it to be sent via SMS (and yes, we have enabled the automatic fallback to SMS - but that doesn't work either). If she uses Samsung Messages, RCS messages are transmitted without issue. I have seen many other posts of a similar nature - trying to use RCS between T-Mobile's RCS and Google's is prone to failure.
Samsung Messages is a SMS/MMS based app (with RCS if your carrier allows it, (which Tmobile, AT&T, and a few others do allow), which requires a network connection.
Google Messages is RCS via the internet and does not require a network connection, (Though your carrier may provide the internet, as opposed to tapping into a Wi-Fi signal for service), nor does it require that your carrier to support RCS.
Google Messages doesn't require your carrier to support RCS to use the Google Messages app. That's the whole point of the app. However, if the recipient doesn't have Google Messages, the app will default back to sending the item via SMS/MMS via your carrier's network.
Having a T-Mobile Samsung s22 ultra, T-Mobile is now running the back end for RCS. I think most of T-Mobile phones are now on the T-Mobile back on of RCS. T-Mobile's back on is very bad compared to Jibe. I have constant issues using Google messages with RCS messages not going.
@TMobile customers are getting an upgraded Messages by Google experience, now powered by RCS and Google's Jibe platform. This means customers will get all new features instantly and have a better experience messaging with businesses thanks to Rich Business Messaging (RBM). pic.twitter.com/JqciAtY1ft
