T-Mobile RCS Messaging Stability Issues

  • 24 July 2023
  • 41 replies
  • 7486 views

Userlevel 1
Badge

Since moving to the S23 with official locked Tmobile ROM, RCS messaging has been terrible. Fails to connect to RCS servers, fails to send text, fails to receive text all at random. Rebooting phone, clear Google Messages cache and deleting all text threads helps for a while, then it's back to terrible again.

I have researched online and others have the exact same issue. It all started when Samsung moved from Samsung Messages to Google Messages for the text app. The problem is that Google Messages which is now the official messaging app on Galaxy phones, still uses T-Mobile’s unreliable RCS services. They can reprogram the Google Messages app that official Tmobile Samsung phones have to use the stable Google Jibe RCS services instead. This only effects official Tmobile phones and not unlocked Samsung phones on Tmobile, as their Google Messages client uses Googles RCS services and not T-mobiles.  ATT just moved all their users from ATT RCS services back to Google Jibe for these performance reasons.

When is T-Mobile going to move Samsung Galaxy users off the unstable Tmobile RCS services and onto Google Jibe RCS services?  If any Tmobile reps are listening, please open a case with backend engineering to fix this.  Tmobile Samsung phone users have been dealing with for a year now.  This issue is enough to lose a substantial amount of subscribers over.

Need proof?

 


41 replies

I and my wife have this same issue. We are using Galaxy S23 ultras with T-mobile ROMs. If we use Google messages for RCS messaging each other, the messages frequently fail to send until we click on the message and select the option to send it as an SMS/MMS instead. When we do this, the message will send immediately.  

I have reached out to T-mobile support a few times for this. Each time I was told tech support would follow up with me, but I never receive a follow up. Their service in this regard has been awful. 

 

I read on a reddit post that switching to the Samsung messages app resolves the issue. I'll do that for now until T-mobile resolves the RCS messaging issue by switching to the stable Google Jibe RCS services instead.

T-mobile RCS sucks. I had to switch to SMS.

The issue is on Google's end.  T-Mobile has no control over Google Messages.  The issue also affects some Samsung Messages users that update from the PlayStore versus the Galaxy Store.  Personally, I use Pulse which doesn't use RCS.  No issues at all.

I disagree. I have 2 galaxy s21 ultras being used on my tmobile account. The Google messages app on these devices use the Jibe network for RCS and don't have any issues with sending or receiving RCS messages. 

The google messages app on my T-mobile ROM S23 ultras are forced to use the T-mobile RCS servers instead of Google Jibe RCS servers. If I switch my messaging app to Samsung messages, which apparently doesnt use the T-mobile RCS servers, RCS messages send and receive with no problem. The issues lies with T-mobile and not Google since the issue only occurs when RCS messages are managed by T-mobile's RCS servers. 

My wife and I, both on tmo, are having constant issue with RCS even with each other both using the Google Messages app.  I have issues with other users not on tmo as well.  Basically, tmo’s implementation appears to suck.
Not happy...

After updating my Galaxy S22 Ultra (T-Mobile variant) from One UI 5 to One UI 6, I am no longer able to send RCS text messages via the Google Messages app; SMS and MMS works fine. And yes, RCS is enabled in the Google Messages settings.

 

I've tried clearing the app and cache data for Google Messages, Carrier Services, Google Play Store, and Google Play Services. I've uninstalled and reinstalled Google Messages and Carrier Services (both production and beta versions). And I've even wiped the cache partition.

 

Lastly, I factory reset my phone and even with a fresh install of the OS, the issue persists.

 

Since I didn't experience this issue prior to updating to One UI 6, I have concluded that this is an issue with One UI 6.

 

Is anyone else experiencing this issue? 

I have been having issues with RCS working on my phone since I've gotten it. The issue rears its head mostly in group chats where I do not receive about 2/3 of messages sent to me. This has resulted in me being inadvertently excluded from social events because people didn't know I wasn't receiving messages and obviously I didn't know either. I have had to disable RCS to reliably receive messages from my friends. I am also no longer part of a friend group chat and have to rely on my wife to convey information to me about social outings.

Feels like using T-Mobile makes me a second-class citizen. Perhaps T-Mobile wants us to change carriers?

Userlevel 6
Badge +12

I have been having issues with RCS working on my phone since I've gotten it. The issue rears its head mostly in group chats where I do not receive about 2/3 of messages sent to me. This has resulted in me being inadvertently excluded from social events because people didn't know I wasn't receiving messages and obviously I didn't know either. I have had to disable RCS to reliably receive messages from my friends. I am also no longer part of a friend group chat and have to rely on my wife to convey information to me about social outings.

Feels like using T-Mobile makes me a second-class citizen. Perhaps T-Mobile wants us to change carriers?

Your issue is a Samsung issue. Google messages and Samsung devices been having issue. Doesn’t matter the carrier and which RCS server around the world. 

https://www.sammobile.com/news/rcs-messages-not-working-properly-for-some-galaxy-phone-users/

 

I have been having issues with RCS working on my phone since I've gotten it. The issue rears its head mostly in group chats where I do not receive about 2/3 of messages sent to me. This has resulted in me being inadvertently excluded from social events because people didn't know I wasn't receiving messages and obviously I didn't know either. I have had to disable RCS to reliably receive messages from my friends. I am also no longer part of a friend group chat and have to rely on my wife to convey information to me about social outings.

Feels like using T-Mobile makes me a second-class citizen. Perhaps T-Mobile wants us to change carriers?

Your issue is a Samsung issue. Google messages and Samsung devices been having issue. Doesn’t matter the carrier and which RCS server around the world. 

https://www.sammobile.com/news/rcs-messages-not-working-properly-for-some-galaxy-phone-users/

 

I have seen this happen but is not actually the problem I'm experiencing, since the message will get delivered in some form. The issue I'm having is that I'm just straight up not getting a significant portion of messages from people when I have RCS enabled. Not as sms or rcs, they just go off into the ether. And that is a Jibe/T-Mobile server issue.

 

The reason I know is that the people I'm having this issue with have the same exact phone as me, or same-generation Samsung devices but are on different carriers. I have checked their RCS settings and they have Jibe as their RCS provider, while I'm over here on the pathetic T-Mobile servers playing by myself.

Userlevel 7
Badge +16

@syaoran . you have a 23 dont you? issues on your end with RCS?

Userlevel 7
Badge +15

@syaoran. you have a 23 dont you? issues on your end with RCS?

I don't use RCS.  The more secure is basically a myth because Google sells your data.  I have zero issues with SMS and MMS using Pulse.  Samsung Messages is full of issues.  Especially if you accidentally update it from the ay Store and not the Samsung Store.  The versions are different!  

Userlevel 7
Badge +16

theyre using Google Messages this go around it would seem. i dont have any issues with RCS using G-M but im also on a V60.

Userlevel 7
Badge +15

Google Messages should have the latest updates for RCS.  However, when Google makes changes to the back end.  it can sometimes take carriers a little while to catch up.  Personally, Google's dual-SIM implementation drove me away.  For single SIM, Android Messages isn't that bad.

Userlevel 7
Badge +16

im single sim. has always worked for me perfectly fine.

Badge +1

There is this one cell tower that once I connect to it, almost 100 percent the time RCS messages will hang. I have no data problems. I have to either toggle airplane mode or drive away from the cell tower and connect to another one. It happened on the S20 I had even when it was connected to Jibe. It was always on the same cell towers I use my S23 on. Explain that. And yes, all troubleshooting has been done. I think it goes without saying I had the issue on two phones who connected to two different RCS networks. My wife will experience the same thing. I shouldn’t have to troubleshoot it all the time. It should just work.

Badge +1

I’ve recently removed the carrier services from my wife’s and my phone as were both on S23. Haven’t really seen a difference. Still experience issues. Mainly it is when I connect to another cell tower. Specifically, an area I frequently travel too where the messages will just hang. It’s also common that it states it's waiting for the person to be online even when Google Messages open and my wife is looking at the app. Who knows for certain who’s issue it is. It for sure happens more with those using Google Messages with T-Mobile at the backend. It's a joint effort. I will say I would experience some of the same issues when I was on a S20 when it would use Jibe. Because I experience it more when connected to specific cell towers I can see why some people just don’t experience the issue. And it is a little annoying that I have to send pictures and videos as files so they stay untouched.

Userlevel 7
Badge +16

its gotta be more of a specific devices/texting app issue. im still running my V60 with GM with no issues. i dont call people..90% of my contact to and from is via text with no issues.

@syaoran. you have a 23 dont you? issues on your end with RCS?

I don't use RCS.  The more secure is basically a myth because Google sells your data.  I have zero issues with SMS and MMS using Pulse.  Samsung Messages is full of issues.  Especially if you accidentally update it from the ay Store and not the Samsung Store.  The versions are different!  

Nonsense. Encryption > no encryption. 

Thanks. Now if only someone will listen. This is complete garbage. There is absolutely no valid reason for the failure to support encrypted messaging in 2023. It has even sent messages by SMS without my OK despite NOT having that selected. It also is completely unacceptable that it takes it 5 minutes to decide it's failed. This is completely inexcusable. 

Userlevel 7
Badge +15

@syaoran. you have a 23 dont you? issues on your end with RCS?

I don't use RCS.  The more secure is basically a myth because Google sells your data.  I have zero issues with SMS and MMS using Pulse.  Samsung Messages is full of issues.  Especially if you accidentally update it from the ay Store and not the Samsung Store.  The versions are different!  

Nonsense. Encryption > no encryption. 

What good is that encryption when Google will sell the key to anyone interested?  Google would gladly decrypt any texts at the request of the government without a second thought.  

Userlevel 6
Badge +12

Have to wait for Google to switch you over. 

My daughter on the S23U T-Mobile variant is on T-Mobile until recently and she hasn't had a problem. She is now on Jibe.  I just got the S24U T-Mobile and it's on Jibe. Usually I buy unlocked phones but I ordered late and didn't want to wait for this phone this year. 

 

Wife - S22+ TRCS no trouble

Me - S24U JRCS no trouble

Son - Moto TRCS no trouble

Daughter S23U TRCS and now JRCS No trouble. 

 

I had a coworker who had trouble and got a new sim and that fixed his issue. 

Userlevel 7
Badge +16

It's official. T-Mobile is reverting Google Messages back to Jibe off their own servers. So it just proves this whole time that any T-Mobile employee on here hasn't been listening. Just regurgitating the same troubleshooting steps that everyone will comment back that they've done every step before. This has been an issue since it was implemented on Google Messages to use T-Mobile servers. There is no effort to help customers when so many of us are saying the same thing. I'm curious how many of us called T-Mobile about this for it to be sent up to someone else and never get a call back. It's frustrating. It's easier for support to respond back saying they don't know and to be honest, not going to get an answer for you. I posted a link since support is just as clueless.

 

https://9to5google.com/2023/09/21/t-mobile-rcs-google-jibe/#:~:text=In%20addition%20to%20Get%20the,or%20use%20their%20own%20infrastructure.

mind pointing out which “TMO employee” in here wasnt listening?

Userlevel 1
Badge

Update: https://9to5google.com/2023/09/21/t-mobile-rcs-google-jibe/

We will have to see how long it takes Samsung to upgrade their version of Google Messages.

Userlevel 7
Badge +15

Using ADB to reinstall Google Messages directly from the on-device firmware.  I see Jobe from Google in mine.  This crap still doesn't work properly with dual-SIM, even after updating.  I checked before and after updating.  It shows the same connection to RCS on my s23 Ultra.

 

Badge +1

It's official. T-Mobile is reverting Google Messages back to Jibe off their own servers. So it just proves this whole time that any T-Mobile employee on here hasn't been listening. Just regurgitating the same troubleshooting steps that everyone will comment back that they've done every step before. This has been an issue since it was implemented on Google Messages to use T-Mobile servers. There is no effort to help customers when so many of us are saying the same thing. I'm curious how many of us called T-Mobile about this for it to be sent up to someone else and never get a call back. It's frustrating. It's easier for support to respond back saying they don't know and to be honest, not going to get an answer for you. I posted a link since support is just as clueless.

 

https://9to5google.com/2023/09/21/t-mobile-rcs-google-jibe/#:~:text=In%20addition%20to%20Get%20the,or%20use%20their%20own%20infrastructure.

After updating my Galaxy S22 Ultra (T-Mobile variant) from One UI 5 to One UI 6, I am no longer able to send RCS text messages via the Google Messages app; SMS and MMS works fine. And yes, RCS is enabled in the Google Messages settings.

 

I've tried clearing the app and cache data for Google Messages, Carrier Services, Google Play Store, and Google Play Services. I've uninstalled and reinstalled Google Messages and Carrier Services (both production and beta versions). And I've even wiped the cache partition.

 

Lastly, I factory reset my phone and even with a fresh install of the OS, the issue persists.

 

Since I didn't experience this issue prior to updating to One UI 6, I have concluded that this is an issue with One UI 6.

 

Is anyone else experiencing this issue? 

This happened to us when we moved to T-Mobile in Dec and got new S23+ phones. Nothing fixes it because T-Mobile is using their own servers in the Google messages RCS process, instead of using the established Google Jibe server. They said they're fixing that but apparently instead of only affecting new phones they're switching everyone to their servers worth updates, thus breaking more and more people. We finally gave up and went straight SMS because we were missing so many messages. 

Reply