Have just downloaded build 23047 and have build a rom but have experienced something strange.
SMS texting does not work? Then I open text and click new text. No text windows appears.
Am I the only one who gets that error??
Did you include "Webview" That could be the problem. It's necessairy for sms messages.
i have same problem
i have the same problem, also i have checked my setting, i have included the webview.
Anyone can help?
Is there anyone who get the same problem?
Did you include Riched20 package from SYS?
Related
Hey guys, I like the new threaded style messaging in WM6.1, though whenever I send or receive a MMS message the contact name disappears and only gives me the phone number throughout the thread. I am guessing its because of the plus sign that is added in front of the phone number when you send a MMS message and it is not recognized. Does anybody know how to fix this? If possible, other than just disabling the threaded style? Thanks would appreciate the help.
New Rom?
You could flash a new rom. I use Dutty's April 29th rom and it works for me. Something you could do if your willing to try a different rom.
Hey there
I recently upgraded to the official WWE 6.1 of HTC. Now I know that there's seems to be a lot of issues with it according to several threads.
I just wanted to know if anyone experienced this weird behavior...
When I try to send an SMS, OFTEN and it doesn't seems to happen when I do something in particular, my message CAN'T be sent, I have to retry a LEAST 3 times so that it's being sent successfully. I never experienced that with 6.0.
Would it be due to something special that I haven't checked or thought of? I've check my SMS service center number and it's fine.
Any ideas?
When you mean sending a SMS, do you mean that this happens when creating a new SMS or responding to a SMS message?
If it's the latter, then I'm in the same boat. I've had this issue with my earlier Qtek 8310 aswell. (http://forum.xda-developers.com/showthread.php?t=370674).
The only solution I've found so far is to create a new SMS message when "responding" to these contacts.
khals said:
When you mean sending a SMS, do you mean that this happens when creating a new SMS or responding to a SMS message?
If it's the latter, then I'm in the same boat. I've had this issue with my earlier Qtek 8310 aswell. (http://forum.xda-developers.com/showthread.php?t=370674).
The only solution I've found so far is to create a new SMS message when "responding" to these contacts.
Click to expand...
Click to collapse
Well it's kinda hard to say
I remember, yesterday, creating a new one and it did the same. It's really weird. I'm still trying to find a "pattern" to this, as I doubt someone coded something random to prevent the thing from working properly.
i get this when trying tosend out mms of pics i took.. the pics are downsized.. so i dont understand whats wrong..
anyone plsss?
anyone can help?
I'm also now experiencing this problem. Seems to happen when you take a picture and use the on screen option to create an MMS message and send the picture immediately.
The message sends and a response comes back after a few seconds saying that the message format is corrupt... anyone got any ideas what may be causing this? I'm still stock ROM since Nov 4. 08.
Cheers,
DrSpain
since 09 no one has come up with an answer for this?
Having the same issue.
WhiT3Kr0w said:
Having the same issue.
Click to expand...
Click to collapse
For the lost souls that find this thread I leave here the solution that fixed my problem (on HTC Desire). I also had the corrupt message being displayed each time sending an MMS. Nothing was resolving my issue. I tried a lot of stuff from deleting and adding APN settings manually to installing APN apps to create the settings for me.
What worked for me:
I created a second entry on the APN settings with the same data as the normal APN for MMS. So instead of having an APN for MMS I now have 2 (with different names). And it started to send and receive MMS. Not sure why this works, but it does.
Also, I've also read somewhere that selecting a different network to lose the connection with the current one and going back again that would fix this issue. It didn't work for me though.
HTC Aria / Android MMS Fix
I recently experienced what I believe is your issue. "message format corrupt" I could send/receive SMS, could receive MMS, but could not send MMS. What I discovered is that there is an error (for lack of a better term) when you import your contacts into Android or Google Contacts where the device, (for MMS messages, but seems to work fine for phone calls) does not recognize telephone numbers with parentheses. In the contacts you have as (505) 555-1212 you'll need to edit to 505-555-1212. This will fix the issue. As a quick test, instead of selecting the contact you wish to MMS and manually enter the number; it should go through just fine.
This is in the rom section because it is a rom related issue.
using both dutty's 3.4 and 6.5 R1, and also topix with manila 2.1 I get an immediate response with an "InvalidPduContent" error when i try to respond to a message via the manila threaded sms. i can send messages from standard winmo sms.
I have AT&T. I get the same error on both the Telstra T8285 and the T8282. I looked into the error futher and it seems it can be a problem with the following:
"to" field is being interpreted wrong. when i send a message to someone via manila, i check the "sent items" folder and the to field looks like this:
"Last, First" <14405551212>
the above is the only format that fails.
if i send a new message via manila (no existing conversation), it only shows the person's number in the To field like this:
(440) 555-1212
using default winmo sms it looks like this:
Last, First
has anyone found a solution to this issue other than disabling the manila sms portion? Hopefully this sheds some new light on the situation
I have the same issue. I dont know what is causing it but hopefully someone will fix it. I prefer using the manila for sms as it's alot nicer but for now it's back to the old, ah well...
I see what you mean as well with the incorrect format issue. It is appearing, on face value, to be interpreted as an email address not a phone number. If you get on e of the failed messages and click on the name that's what it's coming back with but the messages that went through ok when the number is clicked it goes straight to the Manila contact.
its a bug in the manila,newer versions works perfect,bud if someone know a solution,i have the same issue...
I had this problem also, then flashed Lost In Asia, v4 (v5 now) and had no problems. The fact that when you clicked to reply to a message, by default goes to the new manila sms system meant that these roms weren't an option for me. Try Lost In Asia if you have time, see if it solves your problem.
I had a Italian ROM (NextGen 1.7) and I no have this problem.
does nobody have a solution for this please
Some User Set Their SMS Sending Option To GSM , And The SMS Bug FIX For Them , Try This .
This is also being discussed in Dutty 3.6 thread. He gathered some information about provider, country etc.
It seems that T-Mobile and Orange suffer the most from this problem.
One solution could be that you add +AREACODE to the contact.
Dutty's V3.7 will be online soon and contain a small updated Manila. Have to see if this still has the same problem.
i work with topix 2.0 rc1 and have the sms issue,yesterday i have unlocked my hd with olipro tool,with the sms issue i can't send whitin manila and can't send to special numbers like the radio etc...
today i tryed again and the sms issue is completly gone!i dont understand bud maybe someone does?
is it because of the radio?the sim unlock or security,cid,i dont know.
maybe this info will help to solve the issue.
Been discussed in great detail on Duttys thread and it appears to be a mixture of unicode, location and carrier. However it has also been fixed on Duttys latest rom V3.7
I've seen a couple of threads on this across the web but theres nothing i've found that can fix it.
So,
I have a contact saved with 07... or +44...., i send an sms to them fine. They then reply and when i click to reply at the top i can see the number has automatically changed to 44 (no +), therefore the sms cant be sent and i get an error message. I have to close that conversation, go to the origional conversation and then retype and send.
Recieved sms, upon reply drops + and message failed.
This has only happened on a couple of contacts and others work fine. I have tried standard sms, Go Sms and hancent. None of them can resolve the issue.
I have tried 2.1, 2.2 JP5, JPU and 2.2.1 JPY (standard and custom ROMS) and all give the same problems with the same contacts.
There is literally nothing i can do to sort this.
I have tried deleting their contact and adding a new one, sync with facebook (get them to remove their number and add it in manually). Literally nothing i can do has got around this problem.
Please please someone help me. For a perminant solution i would be willing to donate via paypal.
Edit:
Is there any way to REPLACE the standard sms apk with a different one as Go sms and Handcent run off the standard sms app. Therefore, maybe a replacement (rather than an addon) would fix this bug??
Somethimes it hapened to me too.
When I tried to send it again for once or twice usualy it works.
Would be happy if someone can fix this.
please someone help!!? I will donate £10 (like $15,16ish dunno exchange rate)
Could it be a problem with the person who replies phone or network? As it only happens to a few it sounds like their phone or network is not enclosing the correct reply number with their text. Is that possible?
I'm experiencing the same problem. It only happens to one contact in my list. I've tried many things but cant solve the problem...
jimmy_zeropm said:
I'm experiencing the same problem. It only happens to one contact in my list. I've tried many things but cant solve the problem...
Click to expand...
Click to collapse
Sorry for late response,
finally i have got this sorted. i think it is a samsung rom issue either that or possibly go sms (although stock mms did it too). I am now running cm7 and have not had this issue once, if you aren't running cm7, i would highly recommend it, it is very fast and reliable, there are some bugs but it brings new features too. check it out
If deleting the whole thread fixes it, there's an app in the market that can fix it.