+1
My wife and I just got new phones from T-Mobile: a Moto G 5g, and a Samsung Galaxy A54 5G. Both were set to send messages by RCS by default. No such messages are ever sent. If I check the status, I always get “waiting to connect.” I tried setting “Switch from RCS chats if a message can’t send,” but after a few minutes it still shows “waiting to connect.” I had to turn off RCS entirely to send a text message. What’s the problem?
Best answer by SteveG-23
View original
+14
My Pixel 6 works fine.
+15
My s23 Ultra works fine as well. I don't use RCS normally but turning it on, it connects almost instantly and I am able to send and receive messages like normal.
+1
Maybe we need to go back to the store and have them troubleshoot.
+15
Flagship devices are updated faster. There have been some changes to RCS over the past few months that might not have been updated in the devices mentioned as of yet. Are your messaging apps up to date? For those using Samsung devices. Are you updating your apps, including Samsung Messages from the Galaxy Store? The app versions are different between the PlayStore in comparison to the Galaxy Store and the Galaxy Store apps for Ssung devices are updated more frequently.
+12
Try this.
Turn off RCS
Turn off 5G
Restart your phone
Wait a few minutes
Turn on RCS
Turn on 5G
I also noticed using ESIM causes problems regardless if the device is unlocked, and if the device doesn’t use the carriers RCS servers.
+1
Thanks, but (a) I just got the phone from the T-mobile store a few days ago, and (b) everything is current and automatically updated. However, I just discovered that the default messaging app was set to the Google version, not the Samsung (they are both just called Messages). So now I will have to experiment with the Samsung version.
+12
either should work fine. If it is having trouble you may need to do above. A lot of people on reddit, twitter, and other places have had good results with above.
+1
tidbits: Will try. My previous “Thanks, but” reply was to Syaoran’s comment.
+1
tidbits -
Thanks for the details. I tried it, and . . .
First I had to learn about eSIMs. This is my first phone with one, and I had been wondering why each of my communications apps was showing options for SIM 1 and eSIM 1. After researching it, I realized the store had not transferred the (very recently updated) SIM card from my old phone, yet some apps on the new one (or at least their Settings screens) were acting as if one were there. I went ahead and transferred the card, then went into the SIM Management and turned off the eSIM.
I then followed your directions above. I found that the default Samsung Messages app would not show me an option to turn on RCS, so I went back to the Google one, and it does. But when I “Turn on RCS chats,” the Status was shown as “Setting up...” “Trying to verify your phone number,” ans it just hung there interminably. . . .
That is, *until I reactivated the eSIM and set it as Primary.* Now RCS shows Status: Connected. And I can send messages properly, with RCS as default and “covert to SMS - only using the eSIM. Interesting. So I guess I will reserve the SIM card option for overseas use, if needed.
Thanks again!
+1
Correcting an editing error in the last paragraph above:
And I can send messages properly, with RCS as default and “Automatically resend as text . . . if a message can’t send” turned on - *only* using the eSIM.
No. It was working fine with Verizon but when I changed to T-Mobile it CONSTANTLY has issues. It either acts like it sends then errors out 5 minutes later or it automatically switches to SMS despite the option being set to NOT do so. I have tried everything in this forum and it either doesn't apply or it doesn't fix it. It's absolutely inexcusable, especially when it sends messages unencrypted without express permission to do so.
+1
Havok970 - I agree. After the steps I described above, I gave up. Both my wife’s and my new phones (one Samsung, one Motorola) had the same problems I described above, similar to yours, and nothing resolved them. I disabled RCS on both, and now our text messages *usually* - but not reliably - go through. Even with everything else working (good phone/data signal, good WiFi, etc.) messages sometimes hang interminably, sometimes in the middle of a conversation - a series of messages go through with no trouble and then they just stop sending. Often one seems to send but really doesn’t, but a follow-up comment goes through, so the people at the other end are wondering what in the world I’m referring to, and I can’t explain. “Resend” doesn’t work. Copying to a new message and trying again doesn’t work. If it’s at all important, I have to call. (I try to explain the glitch by email, but too many people rarely check their email.) The messages eventually send, for the most part, but as much as 20-30 minutes later. Text messaging just seems to be something T-Mobile does badly.
It works sometimes. Other times it's absolutely HORRIBLE. The WORST part is that sometimes it will send your message via plain SMS without any permission or notification. It says the recipient is offline, yet they can send RCS to me and have full connectivity. The bottom line is that it's a horribly insecure joke that is more likely to cause you a false sense of privacy.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
