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?
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...RCS is totally unusable on my wife's S23U. When will it be switched over to use Jibe?
There's been issues with General Samsung devices across the world. Doesn't matter if on carrier or Google servers.
https://www.sammobile.com/news/rcs-messages-not-working-properly-for-some-galaxy-phone-users/
xstahsie wrote:
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 just started having this issue in the last couple of weeks. I am sure I was updated to One UI 6. I've noticed though it's always the contacts who have Apple phones where I get the error message "Trouble Sending. Check Options" (as well as "Waiting for connection" When I AM already connected to WiFi!. It's pretty much every day several times a day. The only contact that I see the messages sent as RCS has an android.
Time to see if I can find another Texting app.
Continues to be an issue with my wife's S22U and she just got it replaced. Surprisingly all the techs seem to not be aware of this issue.
My S21 purchased via Samsung has no issues (on Jibe).
Grounds for a class action are building.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.
I have zero issues with RCS still….but dont have a Sammy phone..
T-mobile RCS sucks. I had to switch to SMS.
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?
Masso435 wrote:
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?
