S22 Ulra RCS Not Working Properly

Everything is up to date. I work in IT, I worked known to unknown in a logical sequence. I'm just sending it back and getting the T-Mobile model and will have them send me the unlock code. Pain but stuff just seems to work better which is ridiculous. 

Carrier services, tried rolling back, tried everything. The only thing I'm thinking is happening is something is wrong with universal profile. Like the T-Mobile users connect and we show as encrypted but when the data is sent it sends to the old profile that's on the T-Mobile servers and even though I've confirmed my number on new devices it's still trying to hit the cached profile but it's just a guess. 

Only reason it disconnects is because we gave up and sent as sms/mms 

It's bizarre for sure.. I'm hoping it clears after me being on jibe servers for a few more days.

Came across The doc on how it works and user stories and such.

https://www.gsma.com/newsroom/wp-content/uploads//RCC.71-v2.6-1.pdf

So I got it working after forcing my buddy to go to the website to confirm his number. We both had to. I'm 90% sure it was because we had stale entries and it wasn't replicating properly. I actually went to the site for him as he's not super technical and was tired of me trying to troubleshoot so he just gave me the otp and blammo it worked about 2 mins later. 

I knew I had to do all the same troubleshooting on his end to reset his connection because there was nothing else for me to try. I had done it all on my so many times lol. I was able to get other t-mobile user too. I had already started the return process too and was about to send it back and to get the network locked version. Which I don't mind either because T-mobile unlocks it for me when I have if you reach out to the right customer service reps. Glad I didn't have to though. I liked the blue color and I wouldn't have lost about $50 from the pre-order and discount programs I'm part of not to mention my screen protectors. 

There are issues when using Message with T-Mobile as the backend for RCS. It is sending pictures and videos as text. Even now it displays SMS or MMS on the send button when sending to another person running Google Messages with T-Mobile as the back end. If I send to someone using Samsung Messages on T-Moible it's fine. If I send to someone using Messages with Jibe as the backend it seems ok. When I first got my S23 Ultra it would not compress the videos so long as they were under 30 MB. I noticed that it was compressing photos before when I was recently on the T-Mobile S20. RCS was provided by a Jibe. Again, I've tried all troubleshoot steps. Disabled RCS and deregistered my number from Google Messages and waited 10 days before enabling. There is so much inconsistency with Google Messages over T-Mobile RCS servers. There is something implemented wrong. Anyone who has a S22 or S23 look at the photo or video size of one you sent or received. Specifically those using Google Messages over T-Mobile RCS servers. See if it's the original size. 

Well the t-mobile chat servers on google messages default allowed is unlimited size. For unlocked devices it's only 100mb… kinda sucks. Not sure I'll buy an unlocked device again. So many gotchas and they just don't work the same way as the network locked devices.. not to mention my esim is broken.. tried different carriers and everything. I mean t-mobile unlocks it for me me anyways. So will never go the unlocked route again. ( I did this to myself I believe on the s20 ultra and had the similar drama and said I wouldn't do it either but of course I did and now I hate it.. 

It's 100 MB for RCS Universal Profile 1.0. Ignore what it says in the settings of the Google Messages app. That just means it will receive a file of over a gig. The protocol doesn't support over 100 MB. What's crazy is I can send pictures through Samsung Messages over RCS to someone on Android Messages. There is still slight compression with photos. The resolution is smaller. 

Google Messages is compressing photos down to 768 x 1024.