I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue
Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either
I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.
hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts
I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.
Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.
I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.
Are any of you using task-killers that may somehow be interrupting an important background service?
I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102
Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?
a quick history of what I've done so far
Sumsung I897 captivate from ATT unlock and being used on Telus network was working great for about 4 days, then all kinds of problem started cropping up.
Phone came unlocked, I rooted using update.zip from xda, installed rom manager and started removing ATT bloatware, entered SMS and APN info which worked fine.
Yesterday I noticed that where I once got good reception I was now getting nothing and would have to drive down the street before I would get something descent. I thought maybe I'd put it back to stock with rom manager and see if that would help which it did not. It actually made it worse, decided to go all out and use the Odin3 one click downloader just to make sure I was back to stock firmware. This didn't work either but now I can enter the SMS and change the preferred network type but it doesn't save. Preferred network type is grayed out and even though I can change it it never save same as SMS.
Now I can't hold connecting in my living room where my wifes Milestone gets full bars. I tried taking the phone to where I had the best signal and change the preferred network, SMS, and set the network operator but it doesn't save any info, can't find on operator half the time on manual or auto and gave me an error and logged it to #*9900#
I've been at this for 2 days straight and can't figure out how to get it right back to stock, it seems to keep hanging onto the same preferred network and not saving anything I enter.
What can I do to get back to stock, and it has to be something that wipes everything clean, clean, clean, because even the GSM disconnects stay logged under *#*#4636#*#*
***I desperately even tried pulling the batt and SIM card for the night in hopes that would do something.
So, if I'm understand what happened correctly, you bought an unlocked Captivate, rooted it, deleted some bloatware, entered your Telus APN info and everything worked awesome for about four days. Now everything has gone down the hole. Is that right?
If that is the case, then we need to figure out what changed. Using Odin3 would have definitely put you back to stock/unrooted your phone, I don't think you could go back any further than that. If I were you, I would act like I first got the phone. As in, I would do everything you did to it, as if was day one. At one point, everything worked fine. Try to recreate that. You can always look into exchanging it or perhaps Samsung customer support can give you a little more insight to what's going on. Here's the number if you want to try them out.
Samsung customer service - 1.800.726.7864
Thanks, I've gone through the process a few times today from start to finish trying to figure it out ... maybe some of the problems aren't real problems and just limitations that I didn't know where their. I've since flash with odin3+re-partion to the bone stock i897UCJF6 as in not the one click method. It loaded fine but still have the same issue, I can't set preferred network type or get it to keep the number entered into SMSC. I think if I can get passed that I'll be be one the up side of winning. I keep noticing that the log of GSM disconnects never clears or the usage statistics under *#*#4636#*# , I'm thinking its in the same area that other bad data is being held onto instead of being cleared when flash firmware or factory reset.
Is anyone able to change preferred network type? maybe I was never able to change it but I think I should be able too.
I may be wrong in assuming this but I don't think ATT is going to be interested helping me connect one of their handset that I'm trying to use on foreign network, but I could be wrong and is an open option.
*#*#197328640#*#*
debug screen
phone control
network control
band selection
wcdma band
wcdma all
menu->end
used this to lock my phone to WCDMA only so that problem is solved
*** never mind posted to soon it still didn't stick after rebooting
be carefull using the service menu as I have no idea what most of this stuff does
I got the SMS service number issue fix by taking out my sim, swapping in another known working sim from the same network, setting the service number, pressing update and then swapping back. Before every time I tried to update the service number it spit out an "update error" can anybody tell where the SMS config data is stored? on the phone or sim.
The only problem I'm having now is with reception which maybe fixable if I can set the preferred network to WCDMA only. But the button for that option is a light blue colour vs other phones that I can change this setting on. Does the blue mean anything like a locked function or something that set by the firmware as unchangeable?
Hello, after leaving a earlier post, I really am at the end of my tether with my wifes phone, basically, her sim works in my galaxy s (VodafoneUK) and so does mine (3UK), but put either sim in her phone, it shows a few bars in the signal bar with both sims, but still says 'Emergency Calls only' I/she cannot make any calls on her phone, I previously rooted before, added custom rom, to try and mend problem, also used odin/samifimware to put stock JVQ rom back on her phone, but to no avail (her firmware/modem/etc all ends in JVQ, my phone has nv_data.bin files etc but hers doesnt have these, what can I do to solve this, tried everything and anything so far!
EDIT * DID A CHECK WITH CHECKMEND TO SEE IF PHONE HAS BEEN BLOCKED,IT HAS* currently *UNKNOWN* network has imei blocked the phone
Hi, i hope someone can help,
When i am in a call (eg. ANZ phone banking) and i am asked to enter my rego number and pin, they dont recognise the numbers i have entered, the same happens to other calls when i am asked to enter numbers.
This happens about 75% of the time, the very odd time it will work, i have tried both 2degrees & vodafone SIM, 2g and 3g, i have tried all different roms & basebands, froyo & GB etc, i have even loaded a stock KDZ rom, still the same result, WEIRD!!
Please help,
Cheers
Hello everybody,
I have a Lumia 820 dev and I want to activate Visual VoiceMail that is already activated by my operator (B&You - Bouygues Telecom) but the toggle switches is not present.
I don't want to flash my device that is developper unlocked.
I want to know if it is possible to enable this feature on my phone or if you know a way to edit the registry.
Thanks in advance,
Best regards
Believe me, we'd all love a way to edit the registry...
Odd that the switch wouldn't be present. Have you tried rebooting the phone? On mine, it showed up (and worked) as soon as I put the SIM in (which the phone was shut down during).
GoodDayToDie said:
Believe me, we'd all love a way to edit the registry...
Odd that the switch wouldn't be present. Have you tried rebooting the phone? On mine, it showed up (and worked) as soon as I put the SIM in (which the phone was shut down during).
Click to expand...
Click to collapse
I have my WP8 for 2 months so it have rebooted many times but never appear.
I contacted my operator to desactivate, reactivate the VVM but even after several reboots, the option never appear
victorc2 said:
I contacted my operator to desactivate, reactivate the VVM but even after several reboots, the option never appear
Click to expand...
Click to collapse
Did you make sure to dial into your voicemail after? It may be missing from some carriers' ROMs, but if it's there you usually need to dial into your voicemail after VVM is provisioned for the phone to try to set it up.