I have a Mio A701 with WM5, the latest official ROM.
Whenever you write more than 160 characters (or 80 in Unicode, I've disabled the Unicode option anyway), that message will be sent in multiple sms.
The thing is, whenever I pass that limit (160 characters), aka need to send a multiple sms message, I just can't send it. I always get the error "Your text message cannot be sent".
So, is this a bug, an option that can be checked/unchecked? The logical thing would be windows sending it automatically, wouldn't it?
yeah it should auto split it into 2 and send them both it works for me
so it could be an issue with the rom you are using or the operator but then
people with other phones would get the same prob
I also thought that maybe was some kind of configuration I had to do because of the operator, because with other cellphones I could always send text messages like that without any problem. I've asked this in many places but never got a reply
No one really knows a solution to this? Or at least that it happened to someone here? I'm still stuck with splitting the messages manually I've changed my rom to WM6.1, but it's still the same! With generic cellphones this never happened, so I don't really know where the problem is coming from.
I've thought that maybe it's because the sending timeout is too short... Can that be changed in the registry?
I'm back again! And still with the problem
I've found out that with SMS Chat v1.05, I can send messages normally. With any more recent version, or any other program, the same problem occurs. Any idea on why?
Related
Hi,
I got my Raphael 2 days now and I've got a problem that I also had on my wizard with Windows Mobile 6.1.
When I send a text-message that is longer then 1 message (more then 160 characters), the receiver gets a scrambled text-message.
The scrambled message contains text from the new message and text from messages send earlier to that person!
I did a hard reset on my device, but even then the problem exists.
Anyone that can confirm this bug? Can it be fixed?
Thanks in advance!
The bug is probably not in your phone, but in the receivers phone that is not able to receive messages that are that long.
WDawn said:
The bug is probably not in your phone, but in the receivers phone that is not able to receive messages that are that long.
Click to expand...
Click to collapse
Thanks! But the strangest thing is:
Sometimes she receives long messages (more then 160 characters) from other people, and then it works fine! None of the other people has a phone with windows mobile.
Any other solutions??
Are you texting in English or some other language? If so, have you messed with unicode support? Try enabling unicode support if it is disabled and see what happens.
Hi,
Today I found an SMS message stuck in the outbox on my "HTC touch pro", (O2 network).
The message was resending itself regularly, (upsetting the recipient obviously).
I was unable to just delete the message from the outbox and found that it only dissappeared after deleting it from the deleted items folder.
Is this a common problem - has anyone found a way of stopping this happening.
I've only been using this phone for about 1 month but this has not happened previously.
Thanks in advance,
Dave.
Can anyone help with this one??????
PLEEEEEASE!!!!
Never seen this before. Are you using the stock ROM?
Yep- everything as purchased.
No tweaks or upgrades.
D.
Davebrown135 said:
Yep- everything as purchased.
No tweaks or upgrades.
D.
Click to expand...
Click to collapse
Strange problem.
What (precise) ROM & WWE version does your touch pro run?
Does it show multiple copies of the same textmessage in "sent items"?
did the message contain other than simple text?
Like #34 or #*34 and alike sort of formating (34 used as example for any range of numbers)
What I could think of is that the cell provider or phone has some kind of error in which the text sending wasn't completed eg. the cell tower didn't send/ the phone didn't receive the propper "message sent" signal, and the phone simply resend the message.
Did it happen with only one receipient?
Hi,
ROM version is 1.90.206.4 WWE
Text msg was straight forward text - no numbers/characters.
Error only occured to one recipient.
Only one copy of the msg was held in the outbox.
Cheers
D.
Davebrown135 said:
Hi,
ROM version is 1.90.206.4 WWE
Text msg was straight forward text - no numbers/characters.
Error only occured to one recipient.
Only one copy of the msg was held in the outbox.
Cheers
D.
Click to expand...
Click to collapse
I would say it was a fluke, never heard of this before, and I really think it has to do with cell<->phone communication.
Keep us posted if it happens again.
Regards,
EqX
Hi,
I've got exectly the same problem, however the thing I discovered is that my text messages stay in the outbox when I have the regulare GSM netwerkcoverage, as soon as I've got 3G or HSPDA receive they are being transferred, my textmessage settings however say they have to be transfered by GSM.
I've got a SE X1 on stock WINMO 6.1 build 19608.1.2.60
Nobody formiliare with this problem? (excue me for my bad English)
Me too. Can't edit the message, can't delete it, can't move it. Keeps sending to the same recipient everytime I open messaging. I've pulled the battery, no change
WM 6.1 pro
CE OS 5.2.19214 Build 19214.1.0.4
ATT tilt (HTC 8925)
Bad form to reply to my own message, but found a tolerable fix
I did a MENU TOOLS Clear Messages
And the second time it got rid of it.
First time hung for several minutes, second time that was the only message left to delete.
This happened to me too today, I was chatting with a friend and she was like why the hell do you keep sending the same message over and over again.
I restarted the phone and no change then I looked in the outbox it is there cant delete cant edit cant move.
However the message is in the deleted items too.
if its not just click delete in the outbox then go to the deleted items and click delete from there it will be gone.
The message somehow links it to both folders like a shadow copy.
Simply that process fixed it.
--------
PS : I was using Wm 6.5 and threaded texting.
Same Issue
Yeah mine are just sitting in Outbox too. I can reply to a message without an issue but when I compose a new message it just goes to the outbox and there isn't a way to send it. Just simple text so no clue why. Any advice?
Hi everyone, I'm new here, and to the HTC Touch Pro, and I tried searching for a solution to this problem but I couldn't find it.
I have Verizon as I said, and I used to have the LG Voyager phone. I just upgraded to the HTC Touch Pro, and have noticed an annoying problem with my text messages.
With the Voyager, when I'd text over 160 characters, as long as I was sending to another Verizon customer, it would send one long text message, it wouldn't break it up or anything. Also I could receive messages over 160 characters from anyone who could send them to me.
With the HTC Touch Pro, if I send over 160, it breaks it into multiple messages, which is annoying to the person I text. Also and more importantly, I can't receive messages over 160 characters. I get the text cut off at the 160 point, followed by a message saying something to the effect of the previous message was edited to remove extra features, or something similar to that.
Other than the change to my data plan necessary for a PDA/Smart phone, I made no other changes to the account when I switched phones.
Does anyone know how to resolve this?
I've looked around a lot and have found 1 or 2 peoplethat have the same problem but nobody has any answers. Anyone have any ideas?
The thing is, that this isn't a problem... it's a default feature which.. unfortunately, I doubt can be changed.
Of course, i might be wrong..
Well thanks for clearing it up anyway. I didnt realize the voyager was actually doing somethingout of the norm to allow those messages to send. Thanks for the reply.
I have the same problem, and its very annoying.
There has to be a way to fix it, maybe flashing a new radio eh?
I'm not sure cause im new to the whole smartphone thing, i just barely got this tp a couple weeks ago.
that is what the phone company allows it's not something that can be changed.
Hi there,
Each hour, the system ( custom tom JACxROM [v1.3] ) send a message to the number 00453 ( Denmark ), but I don't see anything in my sms box, but on my provider statics, they said me I send much sms to 00453, is this an error in the system?
I think yes, but I flashed the rom again, and with the first boot, the system has send 10 messages to 00453, an unknown number for me, and as told, I don't see the messages in my sms app.
Somebody knows how this happens?
i wouldnt have thought that would be the rom.Try putting the sim card in another phone for a day, Look at your next bill for the certain day and heck if the other phone has sent it.
Does this ROM come with any T-mobile apps like Myfaves?
Your problem seems to be similar to the T-mobile Myfaves problem we used to have on imported G1's in the past => see here
Take a log with ddms and check if something is happening with SMSStatusReceiver, it should tell you which application is sending those messages.
I hope that Proximus number is not your girlfriend
you can also try flashing a different rom and see if it happens again. might not be rom related, but as AMON said, app related.
I found the problem, it was the MyFaves apps that sends automaticly sms messages to their server. So I deleted this app and my problem is solved now!
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.