User Profile
Masso435
Newbie Caller
Joined 2 years ago
User Widgets
Contribuciones
Re: Monthly credit for RCS issues
So what do you say to the users on this community forum who do realize the issue and spoke out? It is strange that they used Jibe as the RCS provider then became middle man for delivery and is now switching back. Didn't use Smart Switch. RCS was turned off on the old phones before activating the new ones. Both S23 phones purchased at the same time have the same issues and there are others I know who are in the same situation in my area. Majority of the time by toggling airplane mode to re-register my connection will start sending and receiving messages. I noticed with my phone is handed off to another tower it starts to happen. It will hang for 30 minutes if I let it. Doesn't matter if I have Carrier Service installed or not. Samsung messages only operates on T-Mobile towers. Google Messages is sending to both. It doesn't affect everyone and I can't say why because there are too many variables. I usually have this issue when I connect to specific towers and will only start working the 90 percent of the time it fails by toggling airplane mode or even killing the app and clearing the cache. It's consistently inconsistent and every bit of troubleshooting does not fix it.Re: Monthly credit for RCS issues
It's not the app. I can replicate it at anytime. It always sends to Jibe as a well as the T-Mobile RCS servers. Jibe uses a protocol that stays active. I'm not saying it's everyone but it's enough people I see have the issue. My wife and I both had S20 before, that operated on Jibe, and then we switch to S23 with T-Mobile and we started having issues. It's frustrating to be told to troubleshoot when there is others out there that have issues. Samsung Messages works fine. I can pin point specific cell towers I switch to and have to toggle airplane mode to start work. It says I'm connected the whole time. That's something I would like explanation on. This is an issue and there hasn't been any follow up since the announcement. There is a reason all carriers are switch back to Jibe. I've tried both official and beta builds for just over a year of having this phone. My wife again has the same phone. I can only say my experience is 100 percent consistent in my area with phone that operate on T-Mobile RCS servers in the Kansas City area.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.Re: When will T-Mobile convert their RCS platform to the Jibe Platform (Google) for RCS?
syaoran wrote: Anyone still having T-Mobile for the RCS. Try disabling RCS for a day and then re-emabling it to see if that helps. Just turning it off and right back on doesn't allow the connection for RCS to refresh. I had Google Messages removed from my device for most of the time I have had my s23 Ultra and Samsung Messages is also not installed either. I usually use Pulse but recently installed Google Messages again from the Play Store to test and troubleshoot some Android 14/One UI 6 issues people were reporting on Samsung Members. It's a hardcoded IMS setting. It points at T-Mobile RCS path and connects to Jibe as well. When you send a RCS message it's sending to both.RCS change over to Jibe
T-Mobile has yet to move those whose RCS backend is T-Mobile over to Jibe. They told me once they're still testing it. What's to test? There are multiple phones out there where Jibe is the RCS provider. When you send a RCS message it goes to both Jibe and T-Mobile RCS servers which sends double the data. I've verified by running a packet capture. Not to mention that it still compresses pictures and videos. I verified the resolution of the picture. You can see in the debug options what the max resolution is set in the app.Re: T-Mobile RCS Messaging Stability Issues
There is this one cell tower that once I connect to it, almost 100 percent the time RCS messages will hang. I have no data problems. I have to either toggle airplane mode or drive away from the cell tower and connect to another one. It happened on the S20 I had even when it was connected to Jibe. It was always on the same cell towers I use my S23 on. Explain that. And yes, all troubleshooting has been done. I think it goes without saying I had the issue on two phones who connected to two different RCS networks. My wife will experience the same thing. I shouldn't have to troubleshoot it all the time. It should just work.Switch to Jibe
So T-Mobile supposedly says they're switching RCS over to Jibe for those who have T-Mobile as the RCS but still hasn't. I don't think they are though. One would think they would test it out first and when they're ready to roll out, make the announcement. If any rep can respond with an actually roll out ETA that would be great. If the answer is it's on the works then we know it's not happening for at least current models. I have the S23.
