Native Messenger 1MB text limitations

Textra does not limit size but carriers do. Textra, and most other 3rd party sms apps have an unrestricted size limit but since it is still SMS carriers have to have size limits. Data messengers do not.

Not edited to soften language  :-)

Ok, I found out via the T-Mobile website self-help section that mms can not exceed 1MB. So how am I able to send mms through Textra that are greater than 1MB?

¡Hola, @apexdestroyer​! I'm glad you were able to answer your basic question using the info in the Problemas con mensajes de foto y video (MSM) document. My basic understanding here is that a third party messaging app would be bound to the same basic network rules in place for native/stock messaging -- so I don't think that a third party app is going to be able to send an MMS file over 1MB, either. Have you had a chance to give it a shot? If I'm wrong here, I'd love to know!

- Marissa

You are correct. I sent a few pictures through Textra and they were all over 2MB. They were sent with no problems. On the receiveing end, the pictures were compressed and/or reduced to about 300kb-500kb each.

So, I am assuming that Textra auto-converts these (even when the max file size allowed in Textra is set to "none")

Is there a way to have the stock Samsung app auto-compress as well instead of giving me a 1MB limit notice while trying to send?

So, firstly -- I apologize for using the word "basic" three times in my original reply, because I just reread it and it made my skin crawl!

I don't know of a way to force the native app to auto-compress, though that would definitely be useful functionality. When the error message pops up for you, are there any next step options, or only the ability to dismiss it? In Messaging > Settings, do you see an Mensajería avanzada: Samsung Galaxy S8​ menu? If so, can you check that your image size option is set to send images as Best Available?

- Marissa

Basically,😀 I can only dismiss the notification. There is not an advanced messaging setting but I can adjust the multimedia limit to either "Automatically accept all" or "Automatically accept files less than 9765 MB in size"

I have "all" selected.

Also setting for image size is set to "best available"

I gotta tell you this is the latest surprise with tmobile service and makes the "unlimited" such a fallacy. I moved from V +iphone to Tmobile+Samsung on Android and there is no question in my mind after 3 weeks of usage that it is a far inferior product and service. Iphones are costly but there is a CLEAR advantage. Omg who would think unlimited would limit the size of pictures or video text or otherwise in the year 2017!!!   I'm pretty sure Android is worse then Tmobile in this stack of inferiority. As soon as the iphone 8 comes out I'm dropping this android/samsung duo. To everyone out there thinking android is a good thing.... absolutely not!!!  that return button makes for the worse user interface too.

This, for the most part, has nothing to do with T Mobile.

First, you came from an Iphone, Iphone has imessage. A very good and complete messenger service that we do not have on android, once you realize that you either need to move back to apple or get over it and find a better way, like the rest of us.

As to why. The built in app we use for text messaging is a basic sms app. Go back fifteen years to a flip phone and it is the same basic method of sending messages. Imessage on the other hand works like whatsapp or allo (data) but uses sms as a backup. that is why it is so complete. Android has nothing like this, for the most part. If you use imessage and see a green bubble you know they are either not using imessage or have no data. So when you try to send a picture it has to compress the pic to be able to send it.

Googles messaging is a giant cluster frak. They have google messages, basic SMS, google allo/duo, which are messengers with video phone calling like whatsapp, only better. Even though everyone is screaming for google to merge the two to create basically imessages for android they have not, and might not.

Google came out with RMS, rich message service, that works nearly identical to imessage. The issue is the carriers. The program is totally open source (or whatever the correct terminology is) Only sprint in the US and a couple of canadian carriers use the actual google system. Verizon will not use it because they have verizon messages, a good but only if you have verizon app. Don't know what ATT does with it. T-Mobile uses it but they use their own variation so it only works tmobile to tmobile, if you have the correct phone, and not if you bought a non tmobile phone.

Basically, carriers are trying to do their own thing, google is drunk, and we have a choice of a lot of good message services that no one can agree on, whatsapp is the most popular, or seems to be. The carriers in the US hamstring everything. Iphone users will not use a separate messenger then complain about green bubbles. So SMS is the standart, very outdated standard, in the US and since google will not build an imessage clone and make it the built in app we have a headache.

hartbjh@gmail.com wrote:
This, for the most part, has nothing to do with T Mobile. 
First, you came from an Iphone, Iphone has imessage. A very good and complete messenger service that we do not have on android, once you realize that you either need to move back to apple or get over it and find a better way, like the rest of us. 
As to why. The built in app we use for text messaging is a basic sms app. Go back fifteen years to a flip phone and it is the same basic method of sending messages. Imessage on the other hand works like whatsapp or allo (data) but uses sms as a backup. that is why it is so complete. Android has nothing like this, for the most part. If you use imessage and see a green bubble you know they are either not using imessage or have no data. So when you try to send a picture it has to compress the pic to be able to send it. 
Googles messaging is a giant cluster frak. They have google messages, basic SMS, google allo/duo, which are messengers with video phone calling like whatsapp, only better. Even though everyone is screaming for google to merge the two to create basically imessages for android they have not, and might not. 
Google came out with RMS, rich message service, that works nearly identical to imessage. The issue is the carriers. The program is totally open source (or whatever the correct terminology is) Only sprint in the US and a couple of canadian carriers use the actual google system. Verizon will not use it because they have verizon messages, a good but only if you have verizon app. Don't know what ATT does with it. T-Mobile uses it but they use their own variation so it only works tmobile to tmobile, if you have the correct phone, and not if you bought a non tmobile phone.
Basically, carriers are trying to do their own thing, google is drunk, and we have a choice of a lot of good message services that no one can agree on, whatsapp is the most popular, or seems to be. The carriers in the US hamstring everything. Iphone users will not use a separate messenger then complain about green bubbles. So SMS is the standart, very outdated standard, in the US and since google will not build an imessage clone and make it the built in app we have a headache. 

Carriers already pushed out their RCS services roughly 2 year prior to Google making Jibe.  T-Mobile even open sourced the baseline for all the communications called IMS which gave way to things like VoLTE, WiFi calling, and RCS all of which goes over the IMS protocol, and IS a standard.  They open sourced theirs and offered it to carriers around the world just for better interloping between carriers.  So Google makes a standard based off T-Moibles standard.  Even Samsung is pushing out their own.  Anyway T-Mobile DECIDED to work with ALL standards on their network not just their own.  With that in mind it'll take time to complete support every single one of them without messing up their network.  Projection Jibe support is end of this year as well as Samsung version.  Sprint because they don't have the money nor willing to spend the resources always takes what others are willing to give them so they don't have to spend higher developmental costs.

Google Code Archive - Long-term storage for Google Code Project Hosting.

iMessages has a 10MB limit just like T-Mobiles RCS(technically RCS supports up to 10GB, but carrier restrictions.  Just think of all the pirating lol) last I remember.  iMessages uses data, and eats into you data pool which RCS uses data but does not eat data but counts as SMS and with SMS dying for IMS soon Apple messenger has to support IMS messaging in order to keep it's backup and actually starts to devalue iMessages hence why they added games, stickers, and doing a redesign.  The only thing that would have going for it is end to end encryption, but once Android goes full IMS if you want end to end you can use a 3rd party app and have that, but I believe manufacturers are adopting it on their own.  I haven't tested the new beta for iOS but I have a feeling they may be implementing IMS/RCS support (may not be fully turned on) just in case.

T-Mobile will let any manufacturer put their stuff in the base code, with the only thing they wish is to test it out against their security and network to ensure there is no chance the carrier can be affected by possible compromises or network strain due to bad code.  Remember T-Mobile Open sources their code.