[HELP] Problem sending and recieving text messages - Touch Pro, Fuze ROM Development

I have a huge problem sending text messages.
After typing a messages and trying to send the message it sometimes takes about 30 min. before it is gone. The same problem is with receiving if someone types a message to me and sends it away it sometime takes up to 2h. before i'm receiving.
I already tried serveral radios, changing settings in phone under Services but nothing worked.
Other people with the same Mobile provider don't experience this problem...
Anybody know a solution for this?
Thanks in advanced

I recall reading some posts from other members with similar issues on different carrier networks.
One member ended up contacting the carrier to have them reset his profile.
Another member had to contact the carrier and have them send a new SIM card.
HTH,

i had a problem where I couldn't send or receive them at all.... it occured after I reverted the phone back to stock for warranty... i loaded the latest fuze update, then reverted the spl to 1.90.... wouldnt do sms.... i fixed it by loading the update again, letting it override the spl 1.90 for the newer one 5.10, or whatever it said, i can't remember....
doubt anything i just said has any relevance to ur issue, disregard it all if it doesnt....

Thnx for helping I tried an other sim from an other provider and no problems at all. After searching the forum for a bit I red a lot about changing the sim because it is too old... (1/2 year )

Related

Missing SMS messages?

Hi. I am asking this question for my partner who has an iMate Smartflip and she always roasts me for not sending here texts when I know I have. (I have a TyTnII with delivery noti on).
It appears she sends an SMS to me and I answer immediately, her Smartfilp does not pick it up but if she receives one 'out of the blue' it's OK. This is also very hit and miss in the way it fails.
Just wondering if anyone else has seen this. Checked the Forum and can't seem to see anything.
Cheers.
BTW, tried the obvious and put the SIM card in a different phone and it works fine....
Doesn't she use any data connection (GPRS)? The SMS should be delivered even when are connected but I have experienced delays of messages (I recieved SMS's few hours after the sending even my phone was turned on).
No GPRS in use as it's a PAYG SIM. Just the standard service center number.
It's really strange, the messages are not delayed, just don't appear on the phone even if I send them and get back a delivery notification as if its getting certain data it can't handle.
It's probably been fixed in a HTC firmware update but you know how iMate are slow to follow...
You can install any firmware you want to. If it's not a problem for you/her I hope update (which wipe out all user data as well) helps you. The newest firmware from Cingular would be probably the best one. (I dont have phone from Cingular but Im using their fw so it must be the same with iMate)

Text messages keep resending

Hi all,
I've been having this rather baffling problem for a while now where various people have reported that they keep receiving copies of text messages I've sent them. This appears to be happening with no rhyme or reason - Sometimes they re-send, and sometimes they don't. It happens to some people I send text messages to, but not others. The only thing I have observed is that these repeat messages do appear in my sent items and I noticed that one repeating text message was stuck in my outbox and I was unable to delete it.
I'm using DCD 3.2.0 with radio version 3.42.30. I don't think this has anything to do with DCDs rom or the new radio as I've had this problem for several months. The only additional software I had installed was HTC Home - I did a hard reset for now and didn't install HTC Home just to see if that was the culprit - No problems yet.
I've searched the forums and found some people having this issue in the past, but no solution as far as I can see. Has anyone else had this particular issue? Any help will be greatly appreciated.
this is most likely a carrier (network) issue and has nothing to do with your phone. if you're on verizon, try dialing *28899
kflipproductions said:
this is most likely a carrier (network) issue and has nothing to do with your phone. if you're on verizon, try dialing *28899
Click to expand...
Click to collapse
Sorry - Forgot to mention I'm on Sprint. I've already contacted them and they supposedly reprovisioned my account, but that hasn't appeared to help anything. Thanks for your response.
i guess you could try reflashing, but like i said it sounds like a network issue so you'd probably be wasting your time. did sprint recognize a problem?
Yep, already tried reflashing. And no, Sprint said everything looks peachy on their end.
are you getting any kind of notification that your text wasnt sent? are they queing up at all? are you using SMS software?
kflipproductions said:
are you getting any kind of notification that your text wasnt sent? are they queing up at all? are you using SMS software?
Click to expand...
Click to collapse
Well, I occasionally get a notification that it wasn't sent if I tried to send a text message at the exact time I received a text, but I'm not sure that those are the times my texts would start repeating. No additional software - Just using the standard threaded text messaging that comes with wm 6.1.
i dunno man i would just call Sprint and ask them to reset/refresh things on their end regardless of how it looks to them. i'm not familiar with how Sprint works or how their tech support is. sorry i couldnt help more
That's alright, man. Thanks for your help. Much appreciated!
well I have experienced this problem with before. This problems occurs when your texts messages are not send thru the first time...next time when access the conversation thread all of the unsend draft messages will be resent, thus creating a double message so to speak. what I found to fix the problem is to reflash and rerun the sprint cab. Generally this should fix the problem. If you are continuing to experience this problem I believe you might have a radio incompatiblity problem. I suggest to flash with different radio.
FHK
johnkoong said:
well I have experienced this problem with before. This problems occurs when your texts messages are not send thru the first time...next time when access the conversation thread all of the unsend draft messages will be resent, thus creating a double message so to speak. what I found to fix the problem is to reflash and rerun the sprint cab. Generally this should fix the problem. If you are continuing to experience this problem I believe you might have a radio incompatiblity problem. I suggest to flash with different radio.
FHK
Click to expand...
Click to collapse
Interesting point. However, I've had this problem with several different roms and radios so I'm not sure that's the culprit. Also, I've reflashed several times and the problem keeps coming back.
reflash the newest official sprint rom and test it out for a bit. if you still have the issue then its obviously on the network and don't let them tell you otherwise.
Well, I've already done that as well.
I tried the newest sprint rom before moving to DCD. Well, I guess I'll go and harass Sprint. Again, thanks for your help.
Well unfortunately you are going to have to live with this unless Sprint steps up.......it is a Sprint issue and it happens to everyone.....but I can say it has not happened to me in a little while....I have ran many radios and roms and it still happens....every time you talk to Sprint everything is peachy on their end.....LMAO....

Radio 1.14.25.35 from official FUZE ROM Breaking MMS

Is it just me or is anyone experiencing a "Forbidden" error when sending/receiving MMS after updating to AT&T's new ROM with 1.14.25.35 Radio?
I've reflashed the updated AT&T ROM and then flashed NRG's latest 6.5 ROM with the correct Rilphone.dll and still have the Error. I even tried sending from the new stock ROM and got the error. I did this multiple times to make sure it wasn't a bad flash and still have the "Forbidden" error. Did I do something wrong when I flashed the new ROM and Radio? The settings in MMS are correct and I didn't load anything else prior to testing MMS.
At first I thought it was AT&T and wasted over 30 minutes with a rep that knew next to nothing. Then it dawned on me that this all started after I updated to the new ROM/Radio release for AT&T on HTC's website. So, I reverted back to the original shipped ROM with 1.02.25.32 Radio, flashed NRG's latest 6.5 ROM and can now send/receive MMS.
I had the same forbidden error and had to talk to tech support from att.. apparently it's because i had placed my sim into an iphone and we all know iphones can't send mms so it registered into their system that i was using an iphone thereby causing the iphones imei to register to my number hence why it's forbidden to send/receive a mms. did you perhaps do something similar?
ATT0001 file can't open it
Hey Guys... sorry than I can't help to solve your problem.. But i have a problem too with the MMS... what happens is that every time I send or receive a mms to a windows mobile phone comes as ATT0001 file and I can not open .. I need help with this thanks
Loner2DEnd: I did but only to unlock one. I've done this before and have never had that problem up. I only noticed that I wasn't able to send/receive MMS after I had the official update from HTC for the FUZE. I was on the phone with the tech and they told me that using my SIM in an iPhone wouldn't have updated my account. You can log onto your online account with AT&T and see what phone/IMEI is registered with your account. Mine still has my FUZE and correct IMEI. Everything is working now that I reflashed the original shipped ROM with the 1.02.25.32 Radio.
I downloaded another copy of the ROM update from HTC for the FUZE and ran the same tests to see if maybe it was a corrupted file/bad flash and I still had the same issues with MMS. My internet still worked but I got the same Forbidden Error. For now, I'm going to just stay with my current (original shipped) Radio since everything's working.
Dannyedilber: I'm not familiar with that Error. Sorry man. I don't know much about MMS and had to do some homework and some trial and error to finally find this solution. Maybe one of the seniors can answer your question.
I've had this problem a few times but usually fixes itself after a reset or a quick disconnect/reconnect of the radio.
I find that if I leave my data on for an extended period of time, it seems to happen. Almost like AT&T is seeing the high traffic and cutting me off.
Also check to make sure you guys don't have Data disabled in your accounts.
@Dannyedilber: I don't even know what an "ATT0001" file is?
@Loner2DEnd: My wife just returned her iPhone because she said it sucks compared to Windows Mobile (smart girl eh?) and went back to her old Samsung Blackjack. We did this yesterday, after her having the iPhone for a little under 30 days. I just sent her a picture and she got it.
From AT&T
The data network works for all of our devices and the Windows Mobile devices are the only ones that seem to have had some issues with the way the data network is configured. Rather than trying to re-configure and potentially break the network for other users, we have been working on a fix for the Windows Mobile issue. We have a fix that will be implemented by the end of this quarter and we should have the problem resolved at that time.
Click to expand...
Click to collapse
From AT&T
Just wanted to let you know that I did get an update. The project to "fix" the 403 error is moving forward. Right now we plan to have the implementation complete in June with Project closure in Early July. I will follow up again in about a month to see the status and provide closure information.
Just for clarification: This project hasn't slipped a month, we keep the project open during a "soak" period to ensure that everything is going as expected. Also, as we apply the fix to the elements in the network the fix will be applied to certain markets and complaints should drop for that market dramatically. I haven't seen this issue in a while here so I believe that the patch has been applied for the Minneapolis market.
Click to expand...
Click to collapse
An easy temporary fix is to put your phone into flight mode and then take it out. A new data connection almost always works. Worst case scenario soft reset the phone.
so its by market then?
I flashed the new rom about last week, had no issues receiving and sending MMS on it and on NATF's 4.7 rom.
Still No MMS
nmbr6 said:
...An easy temporary fix is to put your phone into flight mode and then take it out. A new data connection almost always works. Worst case scenario soft reset the phone.
Click to expand...
Click to collapse
My MMS is not working incoming or outgoing. I have tried it from TF3D2, Titanium, after reset, after airplane mode and reset with no success. I put my SIM card in my backup phone and MMS send and receive worked flawlessly. I do not get the forbidden error message some of you have gotten; it just does not work. I have reset the RegEdit keys several times and they are currently set at 1.2mb. I know that 6oo K is at&t max, but the two test MMS messages are 77K and 317k. Thanks - David.
Black C5 said:
My MMS is not working incoming or outgoing. I have tried it from TF3D2, Titanium, after reset, after airplane mode and reset with no success. I put my SIM card in my backup phone and MMS send and receive worked flawlessly. I do not get the forbidden error message some of you have gotten; it just does not work. I have reset the RegEdit keys several times and they are currently set at 1.2mb. I know that 6oo K is at&t max, but the two test MMS messages are 77K and 317k. Thanks - David.
Click to expand...
Click to collapse
It sounds like you have a different issue altogether. My posts were answers from AT&T strictly for the 403 forbidden issue.
Player911 sorry that I was not very specific...whats happening is when I send a ATT MMS to someone who have a HTC touch pro to her hotmail account.. she can't open it because the picture come as ATT0001.. even when I send att MMS to myself at my email account I receive as a ATT0001
Need help with this guys.. please
Sorry my english
Hi All:
First off thank you for the info in resolving this issue. Since swithing back to the original shipped ROM with radio 1.02.25.32 then flashing EnergyROM 3.0 Phoenix 6/12, I've had no problems with MMS Forbidden Error. It's been a week now and I've had no data/network issues either. I'll try again with the new Radio/ROM this weekend when I have some free time and will report back. Thanks everyone!
Tru using a registry editor and go in and change the registry in Arcsoft under HKLM>Software>Arcsoft>Arcsoft MMS UA>Config>MM1>MMSCSetting>SampleMMSC>Wap1SendDefault and Wap2SendDefault and change to a desired number. For instance, I have 102400 set to send up to 1MB.
See if that allows you to send.
try enabling ATT's proxy. This always works for me.
1. Enable the proxy
2. Kill the data connection
3. Reconnect data
4. Try sending or receiving.
This has worked countless times for me.

[Q] Unable to send text message...retrying

Can someone please help me with my long going problem?
Intermittently, when replying to a text message (either in stock messaging or handcent, etc) the phone does not send the text message, and refuses to send for up to a minute after retrying, then the message will eventually send.
This has been happening for MONTHS, and I have had my HTC hero replaced through orange several times regarding the issue, as they had identified it as a handset fault. I then got a replacement SIM from orange aswell to try and rectify the issue, but shortly after registering my new SIM, the issue still occurs.
It seems someone in this thread has the same problem:
http://forum.xda-developers.com/showthread.php?t=665932
I tried the "fix", ie. making sure all numbers were in international number format (+44...) but this made no difference.
As I said, this issue is intermittent and RANDOM, but happens around 3 times a day. It is very frustrating especially when trying to reply to a text urgently.
Is anyone else having the same issue?
Before anyone asks, yes my message centre number is correct (+447973100973).
It only seems to be when replying to a text message, well that is when i notice it anyway.
Any help is much appreciated!
Thanks
I started to get this when I rooted to VR12, it did it alot the first couple of days then didn't do it much. I've now unrooted to orange 2.1, its done it twice in a week. It didn't do it at all on 1.5, maybe a coincidence. Location doesn't matter either.
I noticed this issue. I updated to 2.1 and found im having the same problem. Its intermittent so i cant tell what is forcing it to "retry". Only noticed this since going from 1.5 ---> 2.1.
I installed Darkstone's Froyo Sense v1 and just today gave me the error. Friend of mine actually mentioned it earlier today. We tested it a few times. When I sent him an mms, I got the error, but he still got it. The little envelope icon remained on my message. Tried it again with another friend and same thing, but after 2min the message was sent.
I had the same problem.
I fixed it by entering the service number in the service-menu of the radio. DIAL *#*#4636#*#* and you will see the menu comming up. Take the upper option. Scroll down and update your servicenumber there. While you are there check if the prefferd network is " gsm auto prl" instead of "wcdma". It can save some power.
Goodluck.
Sent from my Hero using XDA App
Hi mcall_r
just wondering if any of these suggestions fixed your problem as I'm having the same issue. mach2005 where do you get the service number from to enter?
Me too!
Hi,
I've been having this issue too. Along with all the other bugs introduced with 2.1 it's been driving me nuts.
The issue seems to occur intermittently and with a variety of numbers. Normally I get the notification sound, a text icon with an exclamation mark in the notification bar and the text 'unable to send text message'. After a while it normally resolves itself and the message is sent however with one number, my mum's, the problem always persists.
Initially I tried checking the message centre number, ultimately I tried a master reset, without any joy. Then I got a new SIM from Orange, which still hasn't resolved the issue. I can pop the SIM into another phone and send messages to her number so it's definitely the phone.
Just today I noticed that I had an unread text from 'Anon' deep in my message thread, which apparently had come from nowhere (I have observed this before). After deleting the thread I was again able to text my mum, is this just a coincidence? Seriously pissed off with this issue but hoping it is now finally resolved. The messaging in Android/Sense seems fubar, I've also had issues with it resolving to the wrong contact when selecting 'Send message' from another contact. Anyone had these same issues in combination with the 'cannot send text message' error?

com.android.phone...

com.android.phone has stopped unexpectedly
ok i have done a search none of which are helping me at all....
i haven't edited anything at all, but yet i'm getting this new error and i can't seem to fix it, i send the odd message and i receive the odd message thanks to go SMS
but other than that my whole network doesn't work
i'm on 02 UK
everytime i receive a phone call i get the error, everytime i send or receive a message i get the error, the notifications aren't displaying i'm out of my whits end here like wth... help
Try this:
http://www.google.com/support/forum/p/Google Mobile/thread?tid=53d875e70942e732&hl=en
If no one has any other answers you can always repair it through PC Companion.
i understand what you are going thru. I am not sure if its the same , but i had this issue with mini pro and had tried all the things in the world to see if that gets solved. My issue only cropped up with INCOMING CALLs and that too randomly. i tried reset , repair multiple times but not solved. Then finally when SE updated to the last build (which is unfortunately not rootable so far) my problem got solved.
i am sure its a bug , but mostly you can try and rename or delete your contacts (like some people reportedly had issues due to contacts photo , or something in the contact name - maybe special characters etc). If you have not yet tried the factory reset , please try that at the first place.

Categories

Resources