Fix RCS

Masso435 wrote:

I’ve uninstalled carrier services before as well. It still is touch and go. I recently did it again and going to test that out a little further. Whether it’s Google or T-Mobile, it’s still T-Mobile who decided who to configure Google Messages on new phones to be the RCS backend and not touch older phones or unlocked phones. So really, it’s on T-Mobile to make the changes to make this work no matter who the RCS provider is. Also, I’ve noticed that photos and videos are compressed if sent as a photo or video. If I send it as a file under the 100 MB limit, it usually doesn’t touch it. For instance, it drops the photo down to about a 3 megapixal photo. If a video is over 30 MB it will compress that. I don’t understand why. It use to send them untouched. Samsung messages actually compresses photos a little too which just confirms it’s T-Mobile. It doesn’t make sense to do that if it’s under the RCS size limit. And yes, the send photos faster is turned off.

No Google unloaded it. They themselves chose to pass it off to carriers at their convenience. As I pointed out Google SHOULD have waited until interloping was tested and good to go before handing it off. Also Jibe to Jibe or even Just Jibe itself still has issues with itself on Google own forums. 

Google MO is to push the standard and dump it on carriers as soon as possible. They do not want to maintain it. They've done this for years with various projects.  Never heard of people call Google Forever Beta?