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?
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?
