I can receive text messages written in Russian, and translate them with Google Translate with no problem.
However, when I try to send a text message in Russian - it appears to be sent correctly on my screen in the native HTC SMS app, but when the receiver gets the message it only displays "**********".
The receiver is using an HTC EVO (2.3.3) and I am using the Sensation. I had no problem doing with with my old Samsung Vibrant. The only thing that has changed is my device. Anyone have any ideas?
I've seen a similar issue on my friend's Samsung I9000. When sending messages in Hebrew they appeared fine on the device, however they were printed as "squares" on the recipient device.
I can't remember the exact way we did it, however I know for sure there's a setting under messaging for choosing the Charset, what fixed it for us was choosing Unicode instead of Auto.
Another direction - can you please try using a different keyboard? Or if you're not using the stock, may I suggest testing it with AnySoftKeyboard?
This is t-mobile's network. Use MMS (add subject) and it will go through fine.
Trekest said:
I've seen a similar issue on my friend's Samsung I9000. When sending messages in Hebrew they appeared fine on the device, however they were printed as "squares" on the recipient device.
I can't remember the exact way we did it, however I know for sure there's a setting under messaging for choosing the Charset, what fixed it for us was choosing Unicode instead of Auto.
Another direction - can you please try using a different keyboard? Or if you're not using the stock, may I suggest testing it with AnySoftKeyboard?
Click to expand...
Click to collapse
I have spoken to HTC tech support and they are at a loss.
I have looked in the messaging settings and there is no option to choose charset. I have also tried this with SmartKeyboard Pro and gotten the same result.
borodin1 said:
This is t-mobile's network. Use MMS (add subject) and it will go through fine.
Click to expand...
Click to collapse
OK, how do I force it to compose MMS instead of SMS?
Related
I just got the Triumph, rooted it, Installed CWM, and loaded the latest MIUI.
I can send regular (english) SMS messages with no problem. When I try sending Chinese, the receiver doesn't get the Pinyin characters. The receiver gets a line of garbage (question marks, commas, etc). The same happens in reverse. When someone sens me a message in Chinese, I just get garbage instead of Pinyin.
I read somewhere there is a fix for this... a hack, if you will. I can't remember exactly, but it has something to do with the stock message app forcing 7-bit characters? Any ideas on how to fix this?
A friend of mine has this exact problem.
The only difference is that he uses CM7 and tries to send messages in Cyrillic (the alphabet, that is used in Russian and some other Slavonic languages)
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
Hello there. At&t user here. I have been using at&t for a while and can't switch carriers, and was wondering if anyone could solve this dilemma for me. Using a nexus s, cyanogenmod.
I need long messages to get merged to one message for the recipient, which would probably best be suited by having them converted to mms.
I was wondering if anyone knows an app that can do this.
Handcent for example, merges them into one and converts to mms, but it needs the sms to be at least 3 sms's long before it does that, so that ones that are between 160-320 characters still get split. I know that gosms doesn't allow this either. This is work-related, so if anyone could help me I would be forever thankful.
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. Just got my first Xiaomi (Mix 2S). Based in UK. Using the default SMS messaging app, several times (different contacts) have messaged me. When I reply it shows 'Message not sent. Tap to review the message then try again'. When I inspect the displayed number, the leading 0 appears to have been stripped (all UK mobile numbers start '07'). Even if I click the contact icon in the messaging app and add the country code, the reply message still fails. The only way to get a message to be sent back is to create a new message thread using the stored contact so that it uses the leading zero. Clearly this is frustrating. Anyone else experienced this or know of a resolution? Thanks in advance.
I'm using the default sms app and I don't have any problem. I'm from Belgium.
No problem in Finland.
Also no problem in Germany...
I'm from Slovenia and noticed this problem, but as it looks, it's an issue of individual contacts. Got it fixed by manually entering number with country code (for that contact) Maybe it has something to do with the region, set in the Settings. Dunno.
also no problem in VietNam
Thanks for your replies. opica - glad I'm not the only one then. I did as you did and updated contacts with country code each time. A bit time-consuming and I found SMS replies used the original (stripped zero) number so failed. I has to start a new text thread to the new contact. each time My current workaround is to use an alternative SMS app. Currently testing both Textra and PulseSMS. Both seem really good and no issue (yet) with stripping leading zeros and failing messages. My guess is that this is specific to MIUI SMS default app and specific to numbers starting with zero, although the issue seems intermittent.
opica - reading your post again, maybe you are right. I originally had my country set as 'UK' (my actual location) but changed this to 'India' and maybe this is the root cause. It seems that several features such as face unlock and even MIUI themes are not available when country set to anywehre in the EU (i think) hence setting this to India in the settings as I know that allows these features. Odd that one has to do this - unless there is a better workaround I don't know of to get these features.
I've had this problem with only one contact so far and it works now with changed number, even with the region set to India (yes, I also set it, because I don't have Themes options if I set it to my country, but I'm not using face unlock, so I don't know any alternatives). If I'm not mistaken, this is because of the GDPR and there is no info about Xiaomi's compliance with this regulation.
Well, I didn't dig deeper... For now. If the problem raises again, then I will
P.S. The best alternative SMS app for me is YAATA - it's fully customizable.
Im from philippines, and i set my region to india too. Ive had this problem for so long now, and its irritating