I've tried with "search" but I cannot match the keyword ....
So, there was a time when restoring your contacts from pimbackup was harmful to the sms app, I cannot send text message longer than 160 chars (I can send them, no errors, but they are not received)
Anyone knows how to solve this issue? I've this bug on my HD2 from various roms, so, I think that it's related with the stored contacts
Maybe there's something with the tags that HTC Sense stores in the "notes" tab of each contact, in this case, there is a way to wipe all the notes of each contact automatically?
Oh yes you can!!!
As far as I know, it's nothing to do with you having imported contacts etc. from PIMbackup......it's just the way it goes....
By default, the messaging application is set to "use Unicode when necessary" which results in long messages being broken into several chunks of 160 characters or less. The messages are delivered (eventually) to the recipient, but their order is not guaranteed.
To "fix" the problem, go to the Messaging tab, tap All Messages, then Menu, then Settings, then Options and un-tick the "Use Unicode when necessary" option, tap Done.....and that's it - problem "fixed"!!
Now, when you send a long message, it is sent as a whole message to your network where it is broken up into 160 char chunks before being sent. The recipient, assuming their network supports long SMS messages, receives your message just as you sent it.
Hope that helps,
Mark.
PS. There is some sort of history to this "feature"; back in days of the HTC Hermes (and others), having Unicode switched on meant that you could only send 70 characters even though the messaging app thought you'd used 160 characters. People were sending a 150 char message and getting charged for three messages - two of 70 chars and one of 10 chars....
Thanks man;
My network supports long sms, but I can't seem to be able to send them anyway :/
I'll make another test
Edit: Nope, no luck, they are not received, and the target can receive sms longer than 160chars, for sure
I am SURE that there was a bug with restoring contacts with some sense/manila bug, I've read about it right here, on XDA
Sorry for the double post, but I've foud out that it's an issue with stored contacts;
I've tried to send an sms to myself, and I received it with no problems...
I too am facing the this issue (HTC HD2 TMOUS) with sending sms more than 160 characters. this is not related to stored contacts in my case.
I did a hard reset and tried to send a sms more than 160 characters still facing same issue. I tried with 3 different Network Operators, still the same persists. However I have no problem with sending sms lesser than 160 characters. Anyone found a fix for this ?
P.S.: I know its a old thread, but... no fix yet.
Hi! I'm using the stock sms app. I have had zero trouble before with messages, but a couple of days ago my messages wouldn't just get sent. I can receive fine, but afted sending an error only pops up saying message not sent. I believe this is some sort of problem with my smsc number, because when I use Go SMS and type in my smsc number manually, I can send messages fine. Calls and internet are working.
When I call *#*#4636#*#* and go to phone information, the smsc box is empty and if I hit update, it just comes up with an error.
I think I accidently pressed update before this problem came up and the box said 00. Any help would be very much appreciated because I prefer the stock sms app to 3rd party ones.
Lookinen said:
Hi! I'm using the stock sms app. I have had zero trouble before with messages, but a couple of days ago my messages wouldn't just get sent. I can receive fine, but afted sending an error only pops up saying message not sent. I believe this is some sort of problem with my smsc number, because when I use Go SMS and type in my smsc number manually, I can send messages fine. Calls and internet are working.
When I call *#*#4636#*#* and go to phone information, the smsc box is empty and if I hit update, it just comes up with an error.
I think I accidently pressed update before this problem came up and the box said 00. Any help would be very much appreciated because I prefer the stock sms app to 3rd party ones.
Click to expand...
Click to collapse
I'm not sure if that is the problem, as my smsc field is empty and I'm not experiencing the same issue. What is your preferred network type?
WCDMA Only, but it seems I got it fixed. I didn't reaize that I had to encode the sms centers number. Working now
Hi. I'm using with my N5 with t-mo in the US. I have a rule in Outlook (on my PC) that sends an SMS to my phone in the event that I get an email from a specific individual. So, the message is sent to [email protected]. This message arrives to my phone as an SMS.
With my prior phone (which was using a CM-based 4.2.2 ROM) this message would appear in my SMS client (Slide Messaging Pro; but prior to that was Handcent) identified by the email address, which would then map correctly into Contacts and bring up the correct contact picture (me).
With my N5 running KitKat, the message shows up as from a four digit code ( e.g., 3823, which varies from message to message), and the SMS client can't map it into Contacts to get the picture. Instead, the first part of the message is my email address.
This is hardly mission-critical, but I am wondering if there is some way to strip out the 4 digit code so that the SMS maps to Contacts correctly? I'm currently rooted but using stock recovery, if that matters.
Does anyone know how to remove the call back number on every single sms message I receive? Even if the person has it turned off on their phone it still shows up on mine when they send me a message. I would just use another messaging app because that fixes the problem but then I can send mms messages. I'm on a local carrier and can't find the settings to put in to fix this either. Any help is appreciated thanks.
*can't send mms I meant to say.
The Samsung Messaging application has a serious error that causes other people not to receive certain sms. From what I was able to find out has to do with the division of very long sms in 2 sms having these sms emojis in the zone of division.
Examples of sms where the error occurs and people do not receive (iPhone) or receive but deformed with invalid characters (Android):???????????????????????????????????a
Other:??????????????????????????????????a?
If you send these sms through the application of Google Messages for example this error is no longer happening so the error is in my view of the Samsung Messaging application.
Anyone knows how to fix this bug? Does anyone else have this bug?
Thank you