RCS Issues, Google Messages Glitch, Group Message Issues
Hi, This is a multifaceted problem that I've seen all over various forums, so I am not quite sure if the issue is specifically T-mobile, Google Messages, or something else. I have a Samsung Galaxy S22 running One UI V6.0, Android V14. The last software update was 22Mar2024 and these issues have been occurring for months. Frequently, in individual message threads or group threads, I will not be able to send or receive messages at all. I will get a single balloon of death that never converts to two balloons, and will not be given the option to send the message as SMS instead. I am connected to RCS, have 5G signal, and available WiFi. In a group chat with two other Android users (on two other carriers), random numbers join the group, and then leave the group. The other two users do not see this activity. I am the original owner of this phone and have had this specific phone number for about 20y so it is highly unlikely that this is a carryover from a previous owner. In the same group chat as in #2, I am frequently booted from the group. Sometimes I am notified of this on my side of the group chat and sometimes I am not. Someone has to manually add me back in. This happens at random times, and has been occurring for multiple weeks, so it's not like one of us got a new version of a messaging app suddenly and it broke the chat. In other forums, I have seen the following as a "solution" of sorts: turn on airplane mode, force stop Google Messages, delete cache, delete data, restart phone in airplane mode, exercise patience, turn off airplane mode. I have performed this action many, many times. It seems to fix it, sometimes, but doesn't last very long. This is not a solution. I've also seen performing a factory reset as a "solution." I have not done this yet because I find it absurdly excessive. I know I am not the only one in the T-Mobile community to experience this type of behavior. I prefer using Google Messages to Samsung Messages so switching messaging apps is not my favorite solution either. Please advise on appropriate next steps to rectify this situation.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?
iOS 18 updated but seeing IMS Status "Voice & SMS" only
I've checked a few articles, and most people are saying this update is an Apple issue. The common thread in all the articles is IMS status and mine is showing only 'voice & 'sms'. Are there settings I have to change in order to gain RCS capabilities?Google Chat FeaturesRCS status stuck at: Setting Up, Trying to Verify my phone number
Hello All. I have great news. My Google Messages RCS is finally working. Here is how I did it, please read this very carefully. Read my original post in Recommemded Answer green color above link. You must disable chat on all previous devices by going here and (on bottom of this site) follow directions:https://messages.google.com/disable-chat Then you must TURN RCS CHAT FEATURES OFF in GM and wait exactly 10 days. If you turn RCS ON before 10 days are gone, the clock starts all over again for 10 days. You literally have to be patient and wait 10 days with the RCS OFF for 10 days. After 10 days, turn RCS ON and you will see CONNECTED !!!! I repeat to you again, STEP 1 is: You must deactivate all prior devices' GM phone number associations by following the bottom instructions on this site:https://messages.google.com/disable-chatand if you get error message like: contact your carrier or you requested code too many times, disregard it. Then STEP 2, TURN RCS OFF FOR 10 DAYS in GM and wait 10 days. If you potz around and turn on RCS in GM BEFORE 10 days are gone, you must start 10-days clock all over again! Just be patgient for 10 days. STEP 3: On day #10, Clear Cache in GM and turn on RCS and you will see that you are GREEN LIGHT in RCS as CONNECTED. The best thing to do for this step 3 is to: completely uninstall Google messages and completely uninstall Carrier Services and then reinstall Google messages and reinstall Carrier Services. If you do this in this step, your cash and Data will be cleared. I am an expert in this now as I have triued everything: Contacted carrier, contacted device manufacturer, uninstalled Carrier Services and Reinstalled Carrier services. This has nothing with the carrier nor device manufacturer nor Samsung nor Motorola nor OnePlus. This RCS trying to verify.... occurs because when you switched your device, or when you switched SIM, or when u ported a number, or when you activated Google account email on another device, you DID NOT turn OFF RCS in GM or did not turn OFF RCS in the native Messages App, and now Google's RCS sees that you have RCS active in multiple devices/accounts/phone numbers, in which RCS remained TURNED ON, and Google RCS Server gets confused. What you need to do is STEP 1, STEP 2 and Step 3. Step 1 will deactivate ALL the shmootz you created and Step 1 will DEACTIVATE ALL devices' and all phone numbers' and all accounts' RCS GM once and for all. Step 2 does the "reset with google". Step 2 takes you OFF of "blacklist" at google. I see some people waited 8 days-not good. You absolutely must wait 10 days (not business days) - 10 CALENDAR DAYS and the day you do step 1, and step 2 is day #1. And by the way: Please make sure you have CARRIER SERVICES INSTALLED AND UPDATED from Google Play Store as well as latest updates of GM, and please update your device firmware by checking for update in SOftware Update in Settings. Basically please update your device firmware and all device apps in Google Play Store all aroung before proceeding with Steps 1,2,3. Let me know, but dont tell me that it doesnt work because you did not wait 10 full days. You must wait 10 days and then reply here and let me know. If you are unable to send or receive messages on Google messages app, this post does not apply to you. What I recommend you do is to: completely uninstall Google messages and completely uninstall Carrier Services. Then reinstall Google messages and reinstall Carrier Services. Then contact your cell phone carrier and ask them to refresh your connection and make sure that your messages and data features are turned on on the carrier side and make sure that Short Code Programming is also turned on, on the carrier side. So make sure messaging, data and short code programming is also turned on, on the carrier side. And meanwhile do not touch the toggle for full 10 days. In 10 days toggle ON and u will be set. I wrote 3 steps: make sure you read this twice to fully understand and follow my directions. From now on, you need to understand the concept, to make sure that this RCS feature not turning on again never happens to you again, you FIRST must make sure that before you change your devices, or change SIM cards in devices, or change Google accounts in devices, you absolutely must make sure that the first thing you do is: TOGGLE RCS CHAT OFF in GM FIRST before changing devices, sims or accnts! Otherwise, the Google server will be very confused and will Blacklist Your account, your device and your phone number by yourhaving too many RCS features toggled on in GM everywhere. To get UNblacklisted and turning RCS back to ON, you must read the steps 1,2 and 3. When i say 10 days, i mean 10 calendar days, not 10 business days. Day #1 starts the moment you toggle OFF rcs and keep it OFFfor 10 calendar days. You absolutely must respect the 10-DAY TOGGLE OFF, as i explained to you in Step 2. This step 2 is the only step that will UN-blacklist your phone number, you GM, and your GM account from the Google server. Please respect the 10day toggle off. If you potz around with toggle, you will not have RCS, and your 10day clock will start all over again with every time u potz around with Toggle. ALSO: ON DAY # 10, WHEN YOU TOGGLE THE RCS ON, IN THE GOOGLE MESSAGES APP, THE GOOGLE MESSAGES WILL ASK YOU TO RE-TYPE YOUR CELL PHONE NUMBER TO VERIFY IT WITH GOOGLE (THAT SAME DAY 10), PLEASE RETYPE THE PHONE NUMBER VERY SLOWLY AND CORRECTLY-BECAUSE: IF YOU TYPE YOUR NUMBER INCORRECTLY, EVEN BY 1 DIDIGT, YOUR STEPS 1,2 AND 3 (WITH 10-DAYS TOGGLE OFF) MAY START AGAIN. PLEASE SLOW DOWN AND BE VERY CAREFUL WHEN YOU RE-TYPE YOUR CELL NUMBER INTO GM APP WHEN IT RE-ASKS YOU TO VERIFY YOUR CELL NUMBER ON THAT DAY #10. PLEASE SLOW DOWN AND BREATH SLOWLY WHEN TYPING YOUR CELL ON DAY 10 (AFTER YOU TOGGLE RCS on ON SAME DAY #10.)MMS Group MMS Corruption: members dropped in replies, Phone numbers changed, New Groups started
Two phones on our TMobile plans experiencing this issue. Group MMS threads keep getting corrupted. When receiving messages, all group members are present, but replying in that group message, messages is randomly leaving out people, and a NEW message thread is created, with one or more recipients removed. This happens on both the sender's phone and the recipient's phone. Sometimes replying to the new corrupted thread is not possible, even though messages come in to that corrupted thread. You have to hunt for the right message thread to reply to. Sometimes Phone numbers are getting corrupted, and digits in the numbers are off. We get a message from a contact, and their number is wrong. We cannot reply to that number, we have to go to the thread with their CORRECT number and reply to that. This is totally frustrating for everyone, as you can imagine. Tried uninstalling Messages, deleting most messages, rebooting, reinstalling messages, etc. The problem disappears then comes back. Samsung phones, with latest updates.
Samsung Messages - receiving RCS messages, but not RCS media across T-Mobile devices
I have an S24+ and my brother has an A54 - we are both on T-Mobile and both on the same plan. I only very recently got the S24+ and I came from a Pixel 7 Pro, where I was using the default Google Messages app. My brother seems to prefer the Samsung Messages app and has been using it primarily. With my Pixel, RCS communication between us has been fine, both in terms of text messages as well as multimedia. After getting the S24, I initially tried using Samsung Messages, as I prefer the aesthetic and cohesion of the app with all the other Samsung native apps, which I've generally quickly grown to like. My issue is this: It does seem like RCS text chats come through just fine between the two of us (the message details will say "Chat" as opposed to "Text Message"), but I've noticed that a lot of images that he tried to send me through RCS come through as an empty "Cancelled" image. Sometimes his images do come through, but only because it seems to randomly fallback to sending those as an MMS (and not RCS). I also determined that if I change my default messenger app on the S24+ to Google, then the RCS images come through just fine. I would prefer using Samsung's messages app overall, although I'm also aware that even Samsung themselves are trying to discourage people from using it in favor of Google's. I'm also aware that there seems to be a bit of a discontinuity between RCS servers originally maintained by T-Mobile, and those that Google/Jibe maintain. I checked my settings in Google Messages and it says I'm using services maintined by "my carrier", although by turning on debugging information, I find it's actually rcs-acs-tmo-us.jibe.google.com. Is there any possible solution to ensure RCS chats *and* multimedia messages (not necessarily MMS's) come through just fine on the Samsung messages app? Or should I just grin and accept the fact that Samsung's messages app is basically deprecated, and that I really ought to use Google? Because as much as I prefer the cohesion of Samsung's app with the rest of OneUI, I feel the broken functionality is a deal-breaker, and I'm reasonably confident the answer is gonna be "just use Google Messages".
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.
Monthly credit for RCS issues
My wife and I have carrier locked S23 phones. We, like thousands of people where Google Messages is using T-Mobile's RCS backend, continue to have issues sending and receiving RCS messages. They have to fix it regardless of the announcement back in September. They really didn't even layout if it makes those changes on current models over to Jibe or irs only future models. There is nothing to test. It already works for T-Mobile phones that already has Jibe set. Why I've been told they testing doesn't make sense. I pay for a service that doesn't work. I shouldn't have to turn off RCS or use a other messaging app if you offer it. Why can't any T-Mobile rep give any timeline, explanation, or anything? When. Sending messages, it literally sends double the data. One through T-Mobile servers and Jibe servers so it literally is already working that way.
