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 usersoff the unstable Tmobile RCS services and onto Google Jibe RCS services? If any Tmobile reps are listening, please open a casewith backend engineering to fix this. Tmobile Samsung phone usershave been dealing with for a year now. This issue is enough to lose a substantial amount of subscribers over. Need proof?
When will T-Mobile convert their RCS platform to the Jibe Platform (Google) for RCS?
I've noticed that Samsung S21-S23 are on T-Mobile's servers for RCS messaging (AKA Google Messages). But there is an update from T-Mobile'stwitter account posted on 9/21/23 that they will be migrating to Jibe. Any idea or ETA that these devices will migrate.
