Hi Everyone,
I'm encountering problems on the stock SMS of LiquidSmooth. When I'm sending longer than 160 characters, the message is automatically converted to MMS and I don't like that. I already tried checking the Split SMS but what It did is that is split the message into 2 separate sms. I'm using rootbox before but didn't encounter this problem. Any solution for this? Maybe, any way on how to remove the 160 limit on sending sms? I like the UI and simplicity of design of the stock SMS that is why I like to use it.
Thanks!
Related
I have a Problem with sending SMS from my Android.
If i send an SMS less than 160 Chars. all is ok.
If the SMS is longer, only the first part of the SMS arrive...and on my android comes an error that SMS could not be send...
I know that there are Codes like *LONG# *LAST# But they don't work... or why the SMS don't arrives???
Help me...
So lately I've been having some annoying SMS/MMS issues that are starting to grind my gears and I'm starting to feel a bit of resentment over the phone.
I've been getting complaints of iPhone users receiving my SMS twice. I'm seeing that when this happens, I get a "message failed" error in other SMS apps other than the stock SMS app, and then it sends right away. This problem can be recreated on both the stock SMS app and Play Store apps.
I'm also getting this extremely annoying problem with MMS where I can't receive files bigger than 600 KB. I get the error "One or more of the message components have been deleted by MMS Adaptation. Either the message was too large or the components were unsuitable for your terminal." This is happening on a message over 800 KB.
Has anyone experienced these issues? Is this carrier related? I refuse to believe that my phone will not receive 1 MB or bigger MMS messages, as I'm sure it's quite capable of doing.
Also, does anyone have the APN for HSPA+ without LTE? I'm thinking maybe the SMS problem has to do with the network I'm operating on. Please advise.
Edit: the MMS limitation is due to the stock SMS application. the limit for files received is 600 KB while other applications can download well over 1.2 MB. My problem is solved, I'll have to find another viable SMS application.
Look at my thread about similar issues with sms. http://forum.xda-developers.com/showthread.php?t=1656203
Sent from my AT&T HTC One X using XDA
dimgl said:
I've been getting complaints of iPhone users receiving my SMS twice. I'm seeing that when this happens, I get a "message failed" error in other SMS apps other than the stock SMS app, and then it sends right away. This problem can be recreated on both the stock SMS app and Play Store apps.
Click to expand...
Click to collapse
Hi,
Did you fix this issue with the recipient received your SMS 2 times?
I am using the stock app and never tried any Play Store app.
For me this happen to an Android Phone too.
Maybe your phone heard you were gonna take her back and now she's mad and is refusing to talk
Sent from my HTC Edge
My phone is send *and* receiving duplicate SMSes from iPhones. Very annoying.
Used to have problems
I used to have mms problems, but ever since i flashed the CleanRom 2.4 on my phone, everything has been peachy keen
coming from a heavily jailbroken iphone, I can say that I do love rooting a whole lot more. I love how android operates and is so similar to linux
OP, not sure which app you were using, but I know ChompSMS was producing the exact results you were reporting.
1) Multiple messages sent / SMS Failed etc. This will show up in both Chomp and the stock app. (FIXED by latest Chomp update!)
2) MMS Adaptation. I have found that this is specifically when iPhone users send you a screengrab of their display. Those are saved in .png instead of .jpg and do not share the same compression rate. Obviously you could just have a really big .jpg, but most likely it is the former.
3) General MMS issues. This will occur if you do not disable "Auto-retrieve" in the stock Messages app.
I know it's a week later, but hopefully this saves you a headache or trips to the AT&T store.
I had completely forgotten about chomp. Thanks for reminding me. I started using it and while I still get messages not sending if I reply to a text from the pop up notification, it doesn't do it nearly as much as go sms. With go sms, the message not sending would happen one after another but not with chomp. And even though I don't like the sound, I've set chomp to make a sound after a successful sent message so at least I can tell if my message has sent without having to open the app.
Thanks again for mentioning chomp
Sent from my AT&T HTC One X using XDA
tekkneke said:
OP, not sure which app you were using, but I know ChompSMS was producing the exact results you were reporting.
1) Multiple messages sent / SMS Failed etc. This will show up in both Chomp and the stock app. (FIXED by latest Chomp update!)
2) MMS Adaptation. I have found that this is specifically when iPhone users send you a screengrab of their display. Those are saved in .png instead of .jpg and do not share the same compression rate. Obviously you could just have a really big .jpg, but most likely it is the former.
3) General MMS issues. This will occur if you do not disable "Auto-retrieve" in the stock Messages app.
I know it's a week later, but hopefully this saves you a headache or trips to the AT&T store.
Click to expand...
Click to collapse
I was using stock messaging.
Sent from my Galaxy Nexus using XDA
Hi,
I'm currently using an ICS rom for my phone that already has the 160 char fix for the sms, the problem is in my country the phone provider supports multiple sms's (like sending up to 4 sms of 160 chars at once), and with gingerbread i would receive those sms fine, they would received together as one, in ICS they get cut off at 160 chars and i don't receive the rest.
Is there any fix for this?
Regards,
Search in play store "Android 4.1 JB Messaging SMS" by Tim Hutt. Try this, is an app based on original JB SMS, but in the moment dont work MMS. Author promess solver in nexts releases, and dont have option for re-notification SMS every 2minutus.
Hey there,
If I send a message that is too long (like it breaks up into 2 messages after the 1st messages character limit is exceeded), the message will not send. I am using a 3rd party, 8sms, because I don't like utilizing Hangouts as my SMS and chat.
I'm sure they will blame it on me using the 3rd party app, because thats what they did last time I had a problem (not related to this)
Anyone else having this problem? Is it Nexus 5 wide, or just Sprint?
Thank you so much.
gsteelx said:
Hey there,
If I send a message that is too long (like it breaks up into 2 messages after the 1st messages character limit is exceeded), the message will not send. I am using a 3rd party, 8sms, because I don't like utilizing Hangouts as my SMS and chat.
I'm sure they will blame it on me using the 3rd party app, because thats what they did last time I had a problem (not related to this)
Anyone else having this problem? Is it Nexus 5 wide, or just Sprint?
Thank you so much.
Click to expand...
Click to collapse
It is doing the same thing when I switch it to Hangouts.
Sprint rep not very helpful. Did a bunch of phone resetting, changing the MSID, etc... to no avail.
gsteelx said:
Hey there,
If I send a message that is too long (like it breaks up into 2 messages after the 1st messages character limit is exceeded), the message will not send. I am using a 3rd party, 8sms, because I don't like utilizing Hangouts as my SMS and chat.
I'm sure they will blame it on me using the 3rd party app, because thats what they did last time I had a problem (not related to this)
Anyone else having this problem? Is it Nexus 5 wide, or just Sprint?
Thank you so much.
Click to expand...
Click to collapse
I haven't tried any third-party SMS apps yet because I'm mostly happy with Hangouts, but it really annoys me that I can't even send a text with more than 160 characters. On previous phones, you could set up the messaging app to let you type to your heart's content and have the app automatically split the message up into 160-character texts. In Hangouts, it actually won't let you type more than 160 characters. You have to send the text and then start another one. There's no way that I can find to change this.
maxpower7 said:
I haven't tried any third-party SMS apps yet because I'm mostly happy with Hangouts, but it really annoys me that I can't even send a text with more than 160 characters. On previous phones, you could set up the messaging app to let you type to your heart's content and have the app automatically split the message up into 160-character texts. In Hangouts, it actually won't let you type more than 160 characters. You have to send the text and then start another one. There's no way that I can find to change this.
Click to expand...
Click to collapse
Yeah, that is what I meant by it not allowing me to do it on Hangouts either. It is truly annoying as ****. 8SMS is really just like the old messaging that we used to have before these updates. I am overall happy with it, just not with not being able to send a message over 160 characters, because it fails.
Does anyone else have a 3rd party SMS app that they like? I tried another one in the Play Store, but it had heaps of ads pop up after sending a text message... I gave that the swift delete quick!
Thanks for everyones help. This forum rocks!
I tried an app called Textra, just to see if it was 8SMS causing the problem.
Textra did the same thing...
I figured out the problem of why it wouldn't send text messages over 160 characters in 8SMS.
In the older versions of Android, on the messenger, it would automatically change the over 160 SMS to an MMS, and you could keep typing. By default, in 8SMS, this wasn't enabled. I had to enable it in settings.
Problem fixed.
Hopefully anyone who uses 8SMS will find this post. I highly recommend this app. I am not a fan of hangouts for SMS.
This is standard for SMS, some phones trick you into thinking there is no limit by not showing you the count or the limit and automatically combining everything or converting the SMS into another protocol (like imessage)
More info here:
http://www.wirelessdevnet.com/channels/sms/features/sms.html
Specifically from the site:
"The messages are limited by size. An SMS message can’t exceed 160 characters. (BTW this limitation is due to the limitation in the MAP protocol in GSM) In case of longer e-mails or information service messages like news, the messages need to broken down into more than one message. The need to break the messages into several smaller segments could make SMS comparatively costlier in comparison to GPRS (for the same kind of service). Also, This doesn’t look very appealing on a mobile device!
However
MMS (talked about later) would remove the limitation of small messages"
Personally I think in the year 2013/2014 and the technologies we have I'm sure it is possible to change this limitation by introducing a new SMS method or protocol/etc but that requires someone to actually spend the time and money to introduce a new standard that replaces one that has been in place for a very long time
I was having the same issue. There are two options to get long text messages to work on Sprint. I'm also using 8sms (great messaging app, really recommend it over Hangouts).
The first, like someone else stated, is to select the option to convert long messages to picture messages. Make sure you select anything over 1 message long to be converted.
The second option that I discovered is to enable "split counter" in the settings. This will split the texts and send them as consecutives SMS messages without converting them to MMS messages. Hope this helps.
Hi!
I just downloaded Textra. I have no problems sending SMS, but I have problems with MMS. Every time I send a MMS, I get a reply with the message:
"One or more of the message components have been deleted by MMS Adaptation. Either the message was too large or the components were unsuitable for your terminal."
I have set the Send Size Limit for photos to 300KB. APN Settings is correct, as when I use the Samsung SMS app, it works.
Is it some setting I need to do? I am not sure if the Textra app is automatically resizing the photos?
I am using a Samsung Galaxy Note 4, running on Android version 4.4.4
Will appreciate if anyone has any solution to this? I am not a mobile user in USA but in Singapore
Thanks!
I think it's a compatibility problem on android 4.4.4.
You should notify to the deverlopers.