Solved! Go to Solution.
Hello Community,
This has been determined to be a known issue. Thanks so much to the community for bringing this to our attention. We have engaged the proper groups, and will hopefully have a resolution soon. This is affecting iOS and Android devices.
Thanks so much
Tim, AT&T Community Specialist

Remove any emotes and emoticons and try to send the message.
Remove any emotes and emoticons and try to send the message.

Hi David,
Thanks, I did also notice that the issue was with emoticons. Would you happen to know whether this issue is known to AT&T technicians or w/e and is being worked on?
Hi David,
Thanks, I did also notice that the issue was with emoticons. Would you happen to know whether this issue is known to AT&T technicians or w/e and is being worked on?
Apparently some kind of software bug or whatnot causing this. Probably will be an update.
Apparently some kind of software bug or whatnot causing this. Probably will be an update.

I'm having this issue on two different unlocked, non-ATT devices, and there's been no software updates in the last many months on either.
Emoticons were working for me last week. Now I get corrupted SMS messages that are half-english half-non-ascii.
Really hoping this gets addressed ASAP. I've seen so many people posting about this issue all around the net and they all are within the last few days.
Edit:
Well, to be fair, it could truly be a software issue, just not on my end. I'm only having this issue when someone with an iPhone sends me an SMS with emoticons.
I'm having this issue on two different unlocked, non-ATT devices, and there's been no software updates in the last many months on either.
Emoticons were working for me last week. Now I get corrupted SMS messages that are half-english half-non-ascii.
Really hoping this gets addressed ASAP. I've seen so many people posting about this issue all around the net and they all are within the last few days.
Edit:
Well, to be fair, it could truly be a software issue, just not on my end. I'm only having this issue when someone with an iPhone sends me an SMS with emoticons.
The same thing is happening to my recipients with texts sent from my Samsung Android phone. However, it is intermittent, and I just checked and the problem does appear to be linked to the use of emoticons. So obviously the short-term solution is to not use them. But ATT needs to fix this.
I saw chatter on another (not ATT board) from 2014 which identified a similar problem, and in that case it was linked to an attack on the phone. If so, and if there is any indication that this is the case now, ATT should put out an alert until the problem is resolved!
The same thing is happening to my recipients with texts sent from my Samsung Android phone. However, it is intermittent, and I just checked and the problem does appear to be linked to the use of emoticons. So obviously the short-term solution is to not use them. But ATT needs to fix this.
I saw chatter on another (not ATT board) from 2014 which identified a similar problem, and in that case it was linked to an attack on the phone. If so, and if there is any indication that this is the case now, ATT should put out an alert until the problem is resolved!
Still possible that this is an attack on our phones, so definitely avoid until ATT resolves the issue.
Still possible that this is an attack on our phones, so definitely avoid until ATT resolves the issue.
I appeciatel everyone's info. I'm receiving short messages just fine, with or without emoticons. It's hard to tell all my friends and family not to use them when texting me and only me, that's not going to work. It's the longer messages that are converted to Chinese characters, and both the folks I have received these corrupted message do have iPhones. I hope that a fix is found soon; it is really annoying.
I appeciatel everyone's info. I'm receiving short messages just fine, with or without emoticons. It's hard to tell all my friends and family not to use them when texting me and only me, that's not going to work. It's the longer messages that are converted to Chinese characters, and both the folks I have received these corrupted message do have iPhones. I hope that a fix is found soon; it is really annoying.
This wouldn't likely be an update on phones/devices, but on the server side.
I guess it could depend on where the tranformation is going bad, but it would seem to be some sort of server parser or XML transform or similar is more likely the culprit.
Yeah, @OneToughCookie, you could definitely "inject" some bad code, particularly depending on how the transofrmations are being done, but my guess is that the most likely "target" would be the AT&T servers, although I suppose it could be devices too.
It's hard to say, but I'd be willing to bet there are numerous people looking at this, given the possibilities ;-]
*If this (or another post in this thread) fixes your problem/issue, please mark it as "accept-solution", and I'll tag it, to make it easier for others to find the answer(s). FYI: I'm an AT&T end-user, just like most of us in the forum. Thanks.
This wouldn't likely be an update on phones/devices, but on the server side.
I guess it could depend on where the tranformation is going bad, but it would seem to be some sort of server parser or XML transform or similar is more likely the culprit.
Yeah, @OneToughCookie, you could definitely "inject" some bad code, particularly depending on how the transofrmations are being done, but my guess is that the most likely "target" would be the AT&T servers, although I suppose it could be devices too.
It's hard to say, but I'd be willing to bet there are numerous people looking at this, given the possibilities ;-]
*If this (or another post in this thread) fixes your problem/issue, please mark it as "accept-solution", and I'll tag it, to make it easier for others to find the answer(s). FYI: I'm an AT&T end-user, just like most of us in the forum. Thanks.
*If this (or another post in this thread) fixes your problem/issue, please mark it as "accept-solution", and I'll tag it, to make it easier for others to find the answer(s). FYI: I'm an AT&T end-user, just like most of us in the forum. Thanks.

This is happening to me also and can't seem to find a fix. It started on Oct 13th for me. It does not happen on short texts, only on somewhat longer ones. For me it has nothing to do with emoji's.
help
This is happening to me also and can't seem to find a fix. It started on Oct 13th for me. It does not happen on short texts, only on somewhat longer ones. For me it has nothing to do with emoji's.
help
Thought I'd just chime in. Using a Nexus 6P on At&t and receiving the weird Chinese messages from a specific friend that has an At&t iPhone on iOS 10. Always happens when he texts with emojis.
Thought I'd just chime in. Using a Nexus 6P on At&t and receiving the weird Chinese messages from a specific friend that has an At&t iPhone on iOS 10. Always happens when he texts with emojis.
Yes, my husband got my texts today in Chinese as well. I have an iphone6 plus. I removed the emoticons, and told him to check for an update for his S4. And to download an anti-virus? Is this exclusive to AT&T? or is it all of the samsung s4's that are experiencing this problem?
Yes, my husband got my texts today in Chinese as well. I have an iphone6 plus. I removed the emoticons, and told him to check for an update for his S4. And to download an anti-virus? Is this exclusive to AT&T? or is it all of the samsung s4's that are experiencing this problem?
No one should have to "remove" emoticons from their device, this is more about just not using them.
The likely scenario (not based, but from previous parsing experience when coding for years) is something like this:
- I send a "squiggly-faced smiley", and it uses a "code" to tell the server (on the AT&T side) that you want to send it, something like "<esc>12345".
- Another person uses a "trigger" to send a message in Mandarin, and it's something like "<esc>1234"
- In theory, the parser should differentiate from these, but maybe something got hosed, a buffer got shortened, or the value is getting truncated, and both are coming through as "<esc>1234".
If this is the case, all the characters after that sequence will be interpreted as Mandarin, even though one person intended to send an emoticon, and antother a message, in Mandrin, or at least part of the message.
I would talk to a CSR, everyone who's seeing this should, the more "reports" they have from the field, the more weight this will likely get, and hopefully someone will debug it and fix things.
This can hose the server, in other ways too (not going into that tech detail here), so ultimately, it's in the best-interest of the MMS/SMS server team to look at this, sooner rather than later...
The chance that it's infecting phones/devices is low. I suppose it's possible, that someone is "injecting" code into one of those buffers, probably through an overrrun, but it's pretty unlikely, as long as you're using built-in texting apps, or known-well-tested ones.
*If this (or another post in this thread) fixes your problem/issue, please mark it as "accept-solution", and I'll tag it, to make it easier for others to find the answer(s). FYI: I'm an AT&T end-user, just like most of us in the forum. Thanks.
No one should have to "remove" emoticons from their device, this is more about just not using them.
The likely scenario (not based, but from previous parsing experience when coding for years) is something like this:
- I send a "squiggly-faced smiley", and it uses a "code" to tell the server (on the AT&T side) that you want to send it, something like "<esc>12345".
- Another person uses a "trigger" to send a message in Mandarin, and it's something like "<esc>1234"
- In theory, the parser should differentiate from these, but maybe something got hosed, a buffer got shortened, or the value is getting truncated, and both are coming through as "<esc>1234".
If this is the case, all the characters after that sequence will be interpreted as Mandarin, even though one person intended to send an emoticon, and antother a message, in Mandrin, or at least part of the message.
I would talk to a CSR, everyone who's seeing this should, the more "reports" they have from the field, the more weight this will likely get, and hopefully someone will debug it and fix things.
This can hose the server, in other ways too (not going into that tech detail here), so ultimately, it's in the best-interest of the MMS/SMS server team to look at this, sooner rather than later...
The chance that it's infecting phones/devices is low. I suppose it's possible, that someone is "injecting" code into one of those buffers, probably through an overrrun, but it's pretty unlikely, as long as you're using built-in texting apps, or known-well-tested ones.
*If this (or another post in this thread) fixes your problem/issue, please mark it as "accept-solution", and I'll tag it, to make it easier for others to find the answer(s). FYI: I'm an AT&T end-user, just like most of us in the forum. Thanks.
*If this (or another post in this thread) fixes your problem/issue, please mark it as "accept-solution", and I'll tag it, to make it easier for others to find the answer(s). FYI: I'm an AT&T end-user, just like most of us in the forum. Thanks.

Pretty much the same thing here.....using an iphone 7, but the interesting thing is that is is also happening when I send texts through my computer as the two are synched
Pretty much the same thing here.....using an iphone 7, but the interesting thing is that is is also happening when I send texts through my computer as the two are synched
Hello Community,
This has been determined to be a known issue. Thanks so much to the community for bringing this to our attention. We have engaged the proper groups, and will hopefully have a resolution soon. This is affecting iOS and Android devices.
Thanks so much
Tim, AT&T Community Specialist
Hello Community,
This has been determined to be a known issue. Thanks so much to the community for bringing this to our attention. We have engaged the proper groups, and will hopefully have a resolution soon. This is affecting iOS and Android devices.
Thanks so much
Tim, AT&T Community Specialist

Receiving text messages from friends started last week on 10/13. Is it a hack? Called AT&T Chat tech support and ended up resetting to factory default settings, after backing up data. Hope you determine the cause of this soon.
Receiving text messages from friends started last week on 10/13. Is it a hack? Called AT&T Chat tech support and ended up resetting to factory default settings, after backing up data. Hope you determine the cause of this soon.
Sign up now to post, reply, and join the conversation.
© 2016 AT&T Intellectual Property.© 2016 AT&T Intellectual Property. link. This link will open a new window All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners.
link. The first nationwide carrier to be awarded the Seal of Wireless Quality. For details, visit www.ctia.org.This link will open a new window
link. Click to verify BBB accreditation and to see a BBB report.This link will open a new window
link. This site is certified by TRUSTeThis link will open a new window
link. USA Proud Sponsor of the U.S. Olympic TeamThis link will open a new window