When will T-Mobile convert their RCS platform to the Jibe Platform (Google) for RCS?

tidbits wrote:

Actually US forums...  If you go to other forums including Google own forums There are examples outside of just T-Mobile. You have a case of confirmation bias due to the limited date given to you. 

 

Fun fact it's an interloping issue which T-Mobile and Google are in charge of. People blame T-Mobile for it.

 

How do we know this is an issue?

T-Mobile to T-Mobile no issues using RCS to each other Perceived using Samsung Messages.

Jibe to Jibe no issues. (Perceived though, Google own forums alone shows it's not all roses).

To and from each other there are issues. 

There are issues with any RCS withing Samsung Devices. Some people notice this from time to time with Pixel devices. 

 

There are a lot of testing done in various places not just T-Mobile on other carrier forums. It's one of the reasons carriers are dropping their own servers for Jibe because they all have interloping issues and they got blamed for it alone. For all we know carriers interloping are good, but Google is what is actually causing the issues. 

When I am in front of a computer and I will track that rabbit hole and share links. You will need a translator because they will be in Korean, Mandarin, and French. 

I have seen threads on the AT&T boards and various Canadian carrier forums as well. 

There is one thing that I don't think some realize is, that when a person shuts off their device or has no data or WiFi for whatever reason.  The RCS message will not send to them because they are offline.  That is just how the system works regardless of who the RCS provider is.  If you send it as an SMS or MMS, it will still send and the person will receive it unless their device is powered off or has no cell coverage or WiFi Calling at all until they reconnect to the network.  It makes me wonder if this us what a lot of people are misinterpreting as an issue.