Forum Discussion
T-Mobile RCS Messaging Stability Issues
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?
Matt_76 wrote:
First my OP N300, then my son's TCL X30 and now my wife's Moto Edge 2022 all have this problem. TM support told me it was because I was on a 4G plan. Upgraded to the Magenta plan last night, but so far I'm not seeing an improvement. I was going to switch to an S24 for performance issues with the N300, too bad it won't fix this problem.
So instead of T-Mobile moving new phones back to Google Jibe Servers it sounds like they're doubling down on using their own broken system for all their customers? Maybe they want to keep people from using encrypted communation and force us all to SMS with crappy RCS service?
This issue still persists. I have it on my S23 Ultra, and my wife's brand new S24+ has the same issue. We have eight lines and have been with T-Mobile for over 20 years. If they don't fix this soon, we'll be forced to switch carriers. I kept getting in hot water with my wife until we figured out what was going on. She thought I simply wasn't reading her messages.
How is this still an issue? I am frequently having to jump through hoops just to get my RCS messages to work again. When functional, it's quite nice, but the repeated issues are obnoxious. It seems anytime there is a system update, I have to jump through hoops just to get my device to "verify" my number and re-enable RCS. Am I the only one who feels like the company gives zero F***s regarding this problem? If I wanted fancy features that only worked half of the time, I'd have bought an iPhone.
I switch to T-Mobile in March, and have the Flip5. I have had the same issues as everyone else in the thread with RCS messaged. The latest update made it even worse, to the point that I am not getting over half of my texts. The only "solution" that T-Mobile tech support gave me was to turn off RCS on my phone, and they placed the blame on Google and Samsung. Absolutely ridiculous.
Is there any way to get our phones to use the Jibe RCS server instead of T-Mobile’s crappy RCS servers?
