Forum Discussion

apexdestroyer's avatar
apexdestroyer
Network Novice
Hace 8 años

Native Messenger 1MB text limitations

I like using the native Samsung messaging app on my Galaxy S8 but I always get a notice, when sending gifs and such, that the max size is 1MB. Is there a fix for this? Do I have a setting wrong? ...
  • tmo_amanda's avatar
    tmo_amanda
    Hace 8 años

    Thanks for giving those steps that Marissa recommended a shot. From doing some digging, at this time, there is no way to have the native messaging app auto-compress files before sending. The best recommendation would be to utilize a 3rd party app such as the one you mentioned above.

tidbits's avatar
tidbits
Spectrum Specialist
Hace 8 años
hartbjh@gmail.com wrote:
What is RCS Messaging, and How Does It Work? | Digital Trends 
In the U.S., T-Mobile and AT&T have implemented versions of RCS that only work on their respective networks; they don't conform to the Universal Profile. Sprint's does, but it isn't available on all devices.
"A big question mark is whether carriers will move at a reasonable speed to create interoperability," Shirey said. "We haven't seen much activity here."
https://www.androidcentral.com/google-making-it-easier-carriers-communicate-over-rcs 
GSMA Announces Version 2 of the RCS Universal Profile Standard

Look at the dates. July 2017 that was printed and there still no available APIs which makes it harder to work with and have to work with proprietary 3rd party applications.  So that is a moot argument right now.  Also T-Mobile pushed their own version out sometime in 2013-2014 I don't remember exactly when.  Also like I said T-Mobile open sourced there's and OFFERED it to the world which no one took and T-Mobile was the first carrier to push out RCS even if it was their own.

I also further explained Google's Jibe uses a lot of T-Mobiles own code, and even T-Mobile is working on pushing out Jibe support on their network by end of 2017 including Samsungs version.  T-Mobile is doing this because there isn't a finished standard and that's all they can do to offer better interloping support.  I believe the rest of the world still hasn't even adopted any standard to date because well just look at how many are out there.

Current implementations of RCS goes through the IMS protocol with allows any data to not count towards data buckets.  With limitations to maximum bandwidth for "network" optimizations, and data caps this should matter to people.  The previous baby versions which you may try to elude to went through data channels and counted towards your data, and I have used them before and you had to find people and convince them to install them and that's why they don't catch on.  Much like Allo/Duo, Hangouts, and such only catch the techies and not normal users.

So it's coming to T-Mobile and T-Mobile will use whatever is available until one standard wins the world at the end.  So just some more information on it.  Now pay attention to some of your articles talking about late 2017 API's will be finalized.  Then look at the response.  Sems like T-Mobile is waiting for things to be finalized before implementing it.  That's just my opinion.  https://twitter.com/TMobileHelp/status/902574344970186752

Discusiones recientes