Related
Hi Guys,
I'm running Cyanogenmod 6.1 (Android 2.2.1) on my G1.
I received a text message but the notification then said;
"Text message rejected due to storage full"
(or something along those lines)
My questions are;
1. Is there anyway to get that text message resent by the network? If the phone says it 'rejected it' then presumably this means it has a not-delivered status on the mobile providers SMS system?
2. Can text messages be saved to the memory card?
Thanks,
Mark.
Not as far as I know. I had something similiar happens to me and I could never re-receive it.
This happened to me once and it never, ever came through. I gave up on it. Though a few weeks later it had happened again for a different reason. I done a manual search roam, tried to join a different network, it failed, put me back to my original network and the latest message came through. It worked a good couple of times for me.
Chocolate Columbo said:
This happened to me once and it never, ever came through. I gave up on it. Though a few weeks later it had happened again for a different reason. I done a manual search roam, tried to join a different network, it failed, put me back to my original network and the latest message came through. It worked a good couple of times for me.
Click to expand...
Click to collapse
I too thought this would work but it didn't...
Which network did it work on?
It worked for me on giffgaff. Though when it didn't work, I had left the phone for like 2 days before actually trying anything like that to retrieve rejected ones. When I got the reject message the last few times, I cleared space then done the roam thing straight away and it came through.
I don't need to be clearing space anymore really though. I just keep an eye on it even though I'm now flashing ROMs all the time. That roam change thing was when my a2ext wasn't configured/working properly and I was in the middle of conversations.
Arghh, this just happened to me with being on a magpieless Froyo rom and just being on a market binge.
Who's fault is this, the rom/phone not sending the correct response to the network, or the network being a ****?
I'm sure it should work, it used to be fine back in the day when texts went on the sim and you could have 10 so it happened all the time.
Its pants. The phone is supposed to send a confirmation back to the network of successful receipt. So either something isn't working with that or the networks aren't processing as they should.
Hi,
I have had the HD7 for a few weeks now... before the nodo update i never had a problem with it but ever since then, i keep getting a lot of error messages for text messages saying the message wasn't sent. This usually happens when the signal is 1 bar or no bars (but signal is still there) and sometimes even happened with full bars.
Anyone else have this problem? I am with Bell in Canada
same also with hd7 in tmo usa
same problem 02 UK
However ive found that if i go into the settings and into the carrier options and switch off 3g, everything works fine , texts are sent and received and i have no issues
this problem seems to come and go for me so im presuming its the same deal that you have - when the 3g signal is low its unable to connect correctly - and since it has a 3g signal it dosent auto downgrade to the lower speed connection - so manually disabling 3g forces it to connect at the slower speed
hope this helps a little
feel free to tell me im talking bollocks tho - this is just my experience of the problem
No message errors here on O2 UK. I've had the HD7 since release & use messaging a lot. I don't get a 3g signal in my area, so that might be a factor.
Sent from my HD7 using XDA Windows Phone 7 App
Hey mate...Bell in Toronto area here. I've been getting the same thing, rather often tiotoo A few times I think it was due to receiving a text the same time or very shortly after trying to send one..it's weird though, pretty much every time I click to resend it goes no problem. You're not alone with that issue mate lol
phew ok awesome then... it hasnt been doing that for me ever since i started this thread lol, so i am a little happy for now... i am going to send off emails to bell and HTC and see what they say regarding this issue.
As per the 3G connection trick, as soon as i turn mine off, i lose all signal from the phone... the dialer just says "emergency only".
Thanks
saketh321 said:
phew ok awesome then... it hasnt been doing that for me ever since i started this thread lol, so i am a little happy for now... i am going to send off emails to bell and HTC and see what they say regarding this issue.
As per the 3G connection trick, as soon as i turn mine off, i lose all signal from the phone... the dialer just says "emergency only".
Thanks
Click to expand...
Click to collapse
I think it is a network issue. I'm on Telus (sharing towers with bell) and I have this problem on my HD7 and Galaxy S. Only in the last couple weeks.
I have to keep resending texts
Blue1k said:
I think it is a network issue. I'm on Telus (sharing towers with bell) and I have this problem on my HD7 and Galaxy S. Only in the last couple weeks.
I have to keep resending texts
Click to expand...
Click to collapse
Oh yeah that's right... i forgot Bell and Telus dont have edge bands. Hopefully the text messaging thing can be fixed soon... its getting annoying now.
I've been having the same problem. I used to send text messages in the loo's on my break, but now if I go there the signal is weaker and it fails alot. never used to before nodo.
This has been an issue for me since Day 1. My college is in a low coverage area and anytime im here, i sometimes get the error message.
I dont pay it much mind because if my phone is showing 1 bar or no bars, then it is obviously not the phone's fault(in my case) but the fact that I am just in a low coverage are and it struggles to get the message out.
This happens more so with my pic message than text message.
Sometimes people have also told me they have text me and I never received it or I'll text them and they never receive it.
carmeng4evr said:
This has been an issue for me since Day 1. My college is in a low coverage area and anytime im here, i sometimes get the error message.
I dont pay it much mind because if my phone is showing 1 bar or no bars, then it is obviously not the phone's fault(in my case) but the fact that I am just in a low coverage are and it struggles to get the message out.
This happens more so with my pic message than text message.
Sometimes people have also told me they have text me and I never received it or I'll text them and they never receive it.
Click to expand...
Click to collapse
did you check with anyone else in t-mobile that goes to your college? I do remember reading where people are complaining the hd7 has a weak antenna.
But even then so, 1 bar is no excuse for a text message to not go through.
I have the same problem. my phone will have full bars one moment then the next it will be down to one and "cant send: text message error" its annoying because i will reply and then look at my phone a hour later and see why they havent replied and the message didnt even send >_<
Some other times my phone get NO signal at all for a couple minutes then randomly has full bars again, its really irritating. I live in a college town where everyone here gets good signal.. no reason for this. I dont really remember it happening when i had the February update.
Ok so i sent HTC an email and this is the reply I got.
I understand that since performing the nodo update on your HTC HD7, you have been having issues sending text messages. I checked around with several of my coworkers and tried to find other instances of this issue occurring from other forums, but it appears to be a fairly uncommon issue. I took a look at the forum thread that you started and obtained more details such as this usually tends to happen when there is low signal. I see that some of the other posters recommended reverting to 2G in such a situation and that is not a bad idea. You can enable 2G only by going to Settings> Cellular. Additionally, the way you hold the phone can affect the signal as well. You may want to try holding around the sides so that your palm does not come in contact with the back of the phone, which can block the signal. Aside from that, you can also try a factory reset in case an issue occurred during the update and did not install properly or caused corruption in some of the files in the phone’s software. Please be sure to back up the information on your phone and the go to Settings> About Phone> Factory Reset.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number 11CACW17ENA000115.
Sincerely,
Lydia
HTC
I'm glad I am not the only one having this issue. (T-Mo USA) Mine started acting up last night with my 3G being EXTREMELY slow loading web pages and then ultimately not being able to load anything. Then this morning I am unable to send text messages, but randomly I will receive many emails and texts (like I only have a connection for a few seconds), then when I try to reply I am unable to send. Very frustrating.
i too have experienced this so here are some tips. For me i only get this problem when pressing send and right away press the home key or back key which interrupts the sending process result of fail sending. Enabling 3g if you dont have it is another problem so disable it. I also get this problem when locking the phone right after i press send so wait till it finish and then lock .
i hope this helps, if not restart the phone, and if that doesnt help take it to tmo and exchange =)
I've had this problem on my Omnia 7 since day one. Always have to disable my damn data.
And the ***** of it is when I go to re-enable data afterwards I have wait a few minutes to get it working again. Sometimes I have to turn the phone off and on in order to get data.
It's not a cell carrier problem since on my Diamond 2 I never had a problem, and the same thing with the x10.
Same problem with Samsung Focus on Bell. After NoDo update, SMS has been useless. I will get SMS, although often late. Sending is worst, I get the dreaded 'cannot send' message. I will occasionally be able to send some. Wondering if it's a signal issue. However, I can send just fine putting my SIM in another phone.
I've had T-mobile HD7 since last november, my girlfriend and I exchange about 30 messages every day, never had this problem before the NoDo update, not even once, no matter how bad the signals were. Im 99% sure its NoDo update causing this not t-mobile network. It's so annoying when you text somebody then go do something else, 20 minutes later you check back and see this un-happy face and can't send message.
BTW, Factory Reset won't help, tried that.
seantan2001 said:
I've had T-mobile HD7 since last november, my girlfriend and I exchange about 30 messages every day, never had this problem before the NoDo update, not even once, no matter how bad the signals were. Im 99% sure its NoDo update causing this not t-mobile network. It's so annoying when you text somebody then go do something else, 20 minutes later you check back and see this un-happy face and can't send message.
BTW, Factory Reset won't help, tried that.
Click to expand...
Click to collapse
yeah tried that too man... WPcentral wrote an article asking other people if they are having that issue and it seems some are and some arent.
http://www.wpcentral.com/sms-issue-hd7-Nodo
It will happen occasionally if I'm on Edge network. If I have a solid 3g signal it never happens.
I got an HTC One international unlocked edition phone 5 days ago. unfortunately for the last couple of days i have been experiencing an annoying problem where my network connection gets dropped every few hours or so. When this happens the phone displays the message "No signal", "limited service". The issue gets resolved by either restarting the phone, or by turning Air plane mode on and then off again. When the no Services message is on it seems like the radio off for all intents and purposes as not network gets detected.
I've looked around online and implemented the popular 'tape solution' whereby u apply some tape on the top of the micro-sim to give it better contact with the phone. But doesn't seems too successful.
Can someone tell whether this is an effective solution to the problem. it seems more like a software problem as turning Air plane on & off fixes it, if so can i expect a patch form HTC or Android in the near future. I've heard that there is a patch coming out this Friday I hope that this will solve the problem.
i've also attached images of the error
thanks in advance
dantoddd
So, as the title states, I did the entire "Install PwnMyMoto, install the OTA update, get rooted-updated-phone" as soon as I got it. However, I never activated by calling Verizon. Fast-forward 30 minutes, I get off of Wi-fi, and I realize that I'm not getting data or anything. So I turn off my phone, call their number, push all the correct numbers, and I'm told that my phone should activate once I turn it on again. Except... I turn it on, get the message that it'll start activating, and then am immediately presented with an error message saying that it couldn't activate, and that I should call the activation number again.
Was I supposed to activate before rooting? Am I completely screwed for now?
meant2live218 said:
So, as the title states, I did the entire "Install PwnMyMoto, install the OTA update, get rooted-updated-phone" as soon as I got it. However, I never activated by calling Verizon. Fast-forward 30 minutes, I get off of Wi-fi, and I realize that I'm not getting data or anything. So I turn off my phone, call their number, push all the correct numbers, and I'm told that my phone should activate once I turn it on again. Except... I turn it on, get the message that it'll start activating, and then am immediately presented with an error message saying that it couldn't activate, and that I should call the activation number again.
Was I supposed to activate before rooting? Am I completely screwed for now?
Click to expand...
Click to collapse
before you attempt to start diagnosing everything and figuring out what you can do. Call the hotline. I have had many problems activating phones in the past where it does things like what you are saying. Then you call customer services and they do their thing and they eventually get it working. Their automated services can get screwy and do things incorrectly. Calling them can be a PITA but it often gets fixed that way.
jayboyyyy said:
before you attempt to start diagnosing everything and figuring out what you can do. Call the hotline. I have had many problems activating phones in the past where it does things like what you are saying. Then you call customer services and they do their thing and they eventually get it working. Their automated services can get screwy and do things incorrectly. Calling them can be a PITA but it often gets fixed that way.
Click to expand...
Click to collapse
Cool, will do when I get back home. Should I do things like unroot it or anything? Or will they not care?
Alright! I went in to Verizon, the guy there couldn't help me, his call couldn't help me, but they directed me to Customer Support. Then I was redirected to Tech Support. But eventually, they got it. I have no clue how or what was wrong, but it involved me reading off the SIM number and IMEI number.
Anyways, thanks for the help, could I get this closed?
sorry if this has been answered but I have searched all over and cant find it.
So I took the spint OTA the other day and now every one in awhile i recieve Assisted dialing error / Invalid Mobile country code. I have turned off assisted dialing but I'm still getting this error. It takes me off 4g and says its on 3g but yet no connection seems to be there at all. anyone else have this problem?
david.herh said:
sorry if this has been answered but I have searched all over and cant find it.
So I took the spint OTA the other day and now every one in awhile i recieve Assisted dialing error / Invalid Mobile country code. I have turned off assisted dialing but I'm still getting this error. It takes me off 4g and says its on 3g but yet no connection seems to be there at all. anyone else have this problem?
Click to expand...
Click to collapse
Did you do a factory reset, I know you lose everything but in my past experience, factory reset after taking an ota is a must.
Sent on my Moto X
I've been intermittently getting this error for the past couple of days too. And yes, I did a factory reset after the KitKat OTA.
I am also getting this notification a few times a day. Both my "current country" and "reference country" are correctly set to USA, and it doesn't matter if I have assisted dialing turned on or off. Fortunately, it doesn't seem to affect the cell signal.
Just got my Sprint Moto X two days ago and did the KitKat update immediately on receiving.
Doing a search on it, it seems to have been infrequently reported going back several years, and always on Motorola devices. And sometimes has been reported as causing loss of the cell signal until you reboot.
fwald said:
I am also getting this notification a few times a day. Both my "current country" and "reference country" are correctly set to USA, and it doesn't matter if I have assisted dialing turned on or off. Fortunately, it doesn't seem to affect the cell signal.
Just got my Sprint Moto X two days ago and did the KitKat update immediately on receiving.
Doing a search on it, it seems to have been infrequently reported going back several years, and always on Motorola devices. And sometimes has been reported as causing loss of the cell signal until you reboot.
Click to expand...
Click to collapse
It's not a huge deal but kind of annoying. And it only started happening to me a few days ago.
clankfu said:
It's not a huge deal but kind of annoying. And it only started happening to me a few days ago.
Click to expand...
Click to collapse
Agreed. If it ever starts resulting in loss of cell signal, however, it will be a huge pain.
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
My phone would not self activate either but that's the only thing in common on those grounds.
dshiznit00 said:
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
Click to expand...
Click to collapse
Wasn't it already on USA?
I also have my number integrated with Google Voice via Sprint.
I seem to get this error whenever it switches from wifi to mobile data.
[
dshiznit00 said:
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
Click to expand...
Click to collapse
I'm integrated with Sprint/Google Voice, but was getting it right off the bat before I even set up GV.
Mine is a new phone.
My phone also would not self-activate, I went to the Sprint web site and entered the MEID and UCC but still had to call them.
However, I only experienced the problem 1-2 more times since my post. I only had the phone in my house, which I suppose doesn't eliminate tower switching but makes it less likely.
I've since unlocked the bootloader and rooted and haven't had it once after that.
It does seem to be a Sprint-only issue with the Moto X this time, but if you do a Google search it was a rare issue with other Moto phones.