Hi all!
When i switch-off the airplane mode, my nexus one ( stock 2.3.3 ) doesn't reconnect to the normal network ( gsm/umts,2g/3g ) for calls and messages.
The airplane symbol disappears and appears a little rectangle with a ! on it and the message "Emergency call only".
If i switch the phone off and then on, it connects correctly as usual and i can call and send sms as usual.
How can i solve this boring problem?
Thank you so much!
Sounds like it's a defect with the radio. You may want to call HTC for a repair/replacement if you're still in warranty.
Thanks for the answer!
I am still on warranty, but that would be annoying i think..
May it be a software problem?
Sent from my Nexus One using XDA App
If you think its software your could try doing a factory restore. I'm sure others can chime in with how to do this... or how to downgrade and upgrade again. See if that resolves it.
Sent from my Nexus One using Tapatalk
Its most likely software like it might not have updated to gingerbread right because in the process of updating there was several updates from 2.2 to 2.3.3 that includes a radio upgrade but it might not have receved that one update before it reveved gingerbread
I know cause i have a nexus one as well as a g2
Its worth a look at
Sent from my T-Mobile G2 using XDA App
Thank you for the answer
So i think i will try to downgrade and then update again to ginger..
I'll let you know...
Sent from my Nexus One using XDA App
Problem was dued to NoLock App.
When the lock was disabled, the sim card ( i must unlock it with the pin code) couldn 't reconnect.
I suddenly discovered it this morning .
With lock on, airplane mode works perfectly
Thank you all for helping, i love my nexus!
Sent from my Nexus One using XDA App
Related
Let me prefix my post with: please don't call 911 just to "test" your phone if this post title has worried you. There is no reason to believe you have a 911 calling problem (more explained below) and you will take up valuable resources from others who actually have an emergency and need immediate help.
I am the owner of a Samsung SGH-i896 Captivate. Today I had to call 911. The call failed. It acted like it was placing the call to 911, it said "Emergency number" on the screen as it acted like it was dialing, and then in half a second the call failed. Other calls worked fine. I had service. Thankfully I was able to use the phone of a friend that was with me to successfully dial 911.
I know this is really really horrible, especially since my little warning at the top of this thread... but when I came home I removed the SIM from my phone and tried to dial 911 to see if it would ring. It didn't work. The lock screen says "No SIM card." and "Emergency calls only". The phone shows full reception bars. When I dial 911 the screen flashes "Out of service area" at the top with a phone picture underneath and then the text"Emergency number". This comes up for 1 second then the dialer exits to my home screen.
I'd like your help to track down this problem.
Dial 112 (911 is only for us phones)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
911 is used in Canada. And the SGH-I896 is a Canadian phone.
Have you thought of it more as a network issue, and not a phone issue? I have unfortunately had to dial 911 from my Captivate before, and it worked fine. I'm using an i9000 ROM with an i9000 modem in non-3G service areas.
cgi101 said:
911 is used in Canada. And the SGH-I896 is a Canadian phone.
Click to expand...
Click to collapse
I'm not sure then does 112 work? Don't call just to test it but it should work I had this problem on an early i9000 rom 112 worked for me... this should be moved to Q&A though it is a bit of an issue... I guess no one realty tests the emergency call features...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
metalmansam said:
I'm not sure then does 112 work? Don't call just to test it but it should work I had this problem on an early i9000 rom 112 worked for me... this should be moved to Q&A though it is a bit of an issue... I guess no one realty tests the emergency call features...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Perhaps the issue warrants the attention of developement.
I had to dial 911 on my phone. live in us using cognition 4 and it would not work.
Hmm perhaps this does does need more attention if it still doesn't work on cog 4... I had this problem when the first froyo cog rom came out... I do believe it was brought up then & 112 was the temporary fix but I can't believe 911 still doesn't work...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
112 gives me the same "Out of service area" like when I dial 911 without a SIM.
Alright, so I installed Rogers stock 2.2. I tried with both SIM in and SIM out. I'm not able to dial 911 in either case. Call fails with SIM in, and I get the "Out of service" message when SIM is out.
Sounds like there is definitely something wrong with my phone.
Ok so I can confirm that 911 does work on cog 4.3 on the i897 on att in us so I think it does have something to do with the missing nvdata but why would you still be able to make regular calls & not emergency calls that seems backwards hmm?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Who needs 911 anyway!
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to help figure this out for evetyone but how the hell do we test this one out??? I guess I could go out looking for trouble.
ridethelight said:
Perhaps the issue warrants the attention of developement.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
If you give me an idea on how to fix it, I will test it out...
I have an i897 and have have used it on phoenix (not sure the version), and andromeda 2.1. Not sure how to test, but that does seem like an network problem. Phone not connecting properly.
I tried putting in a SIM from another carrier. 911 emergency calls don't go through.
I tried putting in a SIM from another carrier. All calls work, not 911. Tested on Rogers and Bell Canada.
Thought I herd on android central podcast that the problem was known?
Sent from my SGH-I897 using XDA Premium App
I just checked. Looks like that's a problem for the Vibrant and only when calling from the lock screen. Seems unrelated to this issue, since those people can still call from the dialer once they unlock their phone.
For anyone who has this problem in the future: I'm pretty sure it was related to having lost the phone's original /efs/ folder including nv_data.bin. You have to have a backup nv_data to restore from to fix the problem, or else it needs to go to samsung for servicing to be re-flashed. This fixed my phone. (well, got a replacement...)
For anyone who has this problem in the future: I'm pretty sure it was related to a bad upgrade to 2.2 via Samsung Kies... Replacement phone is working fine for now.
I have had this phone close to two months now
In the last two weeks or so, I have been unable to make/receive calls or text messages while im in roaming
My provider allows me to do so, and have called and been told that my account is able to
Is there some app not allowing me to do so? I have uninstalled the apps that can make calls that I had but still no luck (Skype, Tango, Kakao Talk and Text)
Please help!!! Maybe something in the hidden menus perhaps, just need help where to look...
Thanks
slide down the statusbar. Hold on the data toggle. Settings should appear. Make sure roaming is ticked
Sent from my LG-P880 using xda app-developers app
Unfortunately, "Data roaming" has always been ticked
More info into my situation:
LG P880G
Android 4.0.3 (V10F)
did you tried to contact LG costumer support ?
Sent from my LG-P880 using xda app-developers app
not yet, guess i have to
Anyone know if the RemoteCall service is any good?
Would factory resetting the phone make any difference? Could an app have really done this sort of disabling?
well, p880g is canadian model - you're from canada i guess?
first off, did it work before? if it did, then factory reset is 98% sure to help. if you re-flash kdz, i think you have 99% chance of making it work. that 1% is for some obscure problem that came up, and is exclusive with p880g, which not many of people here have.
I can only make phonecalls through my bluetooth headset. If I switch bluetooth of and try to make a phonecall with the receiver, speakerphone or cable headset there is no sound. The cable headset and speaker plays all other sounds ok and when testing the receiver with *#0*# it produces sound. I do not have any obscure call recording software or like installed. Running stock rom.
Any suggestions?
Hi,
I am having the same problem.did you find any solution to this bug?
Thanx
Sent from my GT-I9295 using xda app-developers app
Related thread
This seems to be exactly the same issue that I am having and that was described on this older thread: http://forum.xda-developers.com/showthread.php?t=2544300 [In call sound problem]
did you guys had this problem when the device was not rooted? becasue untill I rooted mine everything was OK. after root probelm occured. I am going to stock original rom and unroot mine a I wonder if it makes any sense.. I hope it does because I am getting desperate... If that will not work I will returnt go on warranty.
I did a repair through KIES and that fixed it for a few weeks but then it returned. My device wasn't rooted. Now I'm waiting for a good stock ROM without Samsung's bloatware to flash to.
Sent from my GT-I9295 using Tapatalk
did you try to contact samsung support ? or warranty? This phone is otherwise useless for me without its basic functionality.. if it has this bug also on stock ROM that its Samsung problem hm?
I've had my S4A since July, rooted it within a week and have not had a single problem with it. I'm on MF3 if that makes a difference.
strange.. I cannot find such ROM here.. http://samsung-updates.com/device/?id=GT-I9295
matelko said:
did you guys had this problem when the device was not rooted? ...
Click to expand...
Click to collapse
I have had the problem both unrooted and rooted. Although it sometimes disappeared after a hard reset, it soon came back after installing a few apps and changing some settings, none of which have in principle anything to do with phone functionality. One option would be to make a call after each change but it would be a very long process...
sorry matelko was signed by accident my computer under my account.
Hi,
so now running on stock ROM and still the same problem. I can make only make bluetooth calls. This phone is driving me crazy... can you please share with me the MF3 ROm so that I can test it?
Thank you
Yesterday upgraded ro Cyanogenmod 4.3... The phone worked perfect..a nd in the morning again the same ****... Phone is quiet.. It is possible to make bt headseat calls only.... I do no know what to do...anybody any idea before I finally decide to solve this as warranty claim?
Thanx
So, yesterday I have tried to put sim card from another provider to check if it is not a provider fault...and guess what.. the phone works normally with another providers sim card. I contacted my procider and reported this problem and now I am waiting for their feedback... hopefully they will find out something to make it work..
Sent from my GT-I9295 using xda app-developers app
So the provider made a check of signal and sim card and confirmed that everything is ok.. today i got a phone replaced.. so now i wonder if this problem will dissaper with new device...
Sent from my GT-I9295 using xda app-developers app
yokomcperez said:
I have had the problem both unrooted and rooted. Although it sometimes disappeared after a hard reset, it soon came back after installing a few apps and changing some settings, none of which have in principle anything to do with phone functionality. One option would be to make a call after each change but it would be a very long process...
Click to expand...
Click to collapse
Exact same problem here, is there a fix?
I just installed the new stock 4.4.2 and same thing, worked for a couple of calls and then bye.
Geonerd said:
Exact same problem here, is there a fix?
I just installed the new stock 4.4.2 and same thing, worked for a couple of calls and then bye.
Click to expand...
Click to collapse
Hi, does anybody has a Fix for this issue? It is getting really annoying and happening to a bunch of people in active S4 and the normal S4. After a new flash or sometimes randomly it works perfectly and then suddenly it goes silent on calls again.
Please help
Exactly the same problem. No problem until I started using my helmet's bluetooth. Only thing that works is to switch off bluetooth after using, restart phone and then about the 3rd 4th call, sound comes back on again. Comes and goes after that.
Sent from my GT-I9295 using XDA Free mobile app
The same problem after ~3-4 weeks from flashing Kitkat. Still no fix?
dark.angel said:
The same problem after ~3-4 weeks from flashing Kitkat. Still no fix?
Click to expand...
Click to collapse
Same problem with sound. Was from the very beginning with stock rom, also now with CM 10.2.
It's kinda annoying to have a phone without a proper call functionality..
Same problem
Has anyone found a fix to this?
I've been having this for about two weeks. and I've looked in almost every forum and could not a solution that works.
I've done everything from hard reset, factory reset, not installing viber/skype, tried using soundabout, change the network settings, and probably a few more suggested solutions that just doesn't seem to work.
any help is much appreciated.
Every time I call I get a message that I'm roaming and I can't make a call. Text messages don't go through either. At least I still have a data connection... Right
tommason1968 said:
Every time I call I get a message that I'm roaming and I can't make a call. Text messages don't go through either. At least I still have a data connection... Right
Click to expand...
Click to collapse
I have the same issue, did you find any sort of fix?
Yes I updated my profile and prl. Not sure why or how it got to that point though
Sent from my 831C using xda app-developers app
Same thing
I'm having the same problem. It seems like it started when I updated to the newest software. When I'm right next to a tower, it seems to work normal, but when I get anywhere else...not so much. It will show signal, but disconnect right after I dial. After multiple attempts at provisioning, and manual reprogramming, they determined that it was an antenna problem and that I should take it into a store to get it replaced.
I'm having the same issue before and after updating. Sounds like a tower upgrade issue Imo
Sent from my awesome HTC M8
I thought that I had fixed it through a profile and prl update, but yesterday afternoon I lost everything. Took it back to the sprint store and was told that the connection issues are because of people buying or switching to the new S5 causing provisioning issues. The only time my phone works is over wifi. It's going back today
Sent from my 831C using xda app-developers app
Fux the s5. Fux Sprint for not running the numbers on making sure it's network doesn't crash. The network is a nightmare in Chicago.
Sent from my 831C using Tapatalk
Pretty sure the network crap is just an excuse .... Just hope they realize and update their crap . I'll be hanging on awhile longer it not I'm just gonna call up htc and get it replaced after the 14 days
I was having the same problem and it turned out to be my Air rave. Called Air Rave direct 866-556-7310 and they reset my system. Everything fine now. Seems my air rave was stuck trying to connect my old phone. Maybe it'll help someone.
Hi, I've noticed recently that sometimes when I try to call a number, it does not call; instead the dialpad goes blank. This occurs especially trying to dial numbers from Google maps or from contacts. Does anyone know a solution to this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
incisivekeith said:
Hi, I've noticed recently that sometimes when I try to call a number, it does not call; instead the dialpad goes blank. This occurs especially trying to dial numbers from Google maps or from contacts. Does anyone know a solution to this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
No one with that issue?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
I have an issue like that, but the dial pad doesn't go blank. the call just sits there in silence and never connects. I have to toggle Airplane mode to fix it.
I have a similar issue! WHen calling someone it says dialing for like 10 seconds. Sometimes i miss calls because when someone calls me it says the netwrk is busy or something like that,
Not sure why this is happening. The only "system" change I've made is installing themes.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Has anyone come across a fix for this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Yes and unfortunately it is that the 3 or 4 of us have defective phones. We need new ones
stu5797 said:
Yes and unfortunately it is that the 3 or 4 of us have defective phones. We need new ones
Click to expand...
Click to collapse
Not sure that's the solution. The issue wasn't present since the day I bought the phone.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
if i recall, i having this problem on galaxy s5 or note4 edge, cant remember.
when i make a call, i always turn off wifi, it fixed the problem for me.
Did you swap the SIM from your previous phone to this phone without activating the new one? I did this and had issues. I called AT&T, and they said my IMEI from my old phone was showing and not the new one. You might try giving them a call and make sure the IMEI showing on their side is that of your new phone.
I notice that this frequently occurs if I start a call while connected to Wifi and then walk/drive outside the Wifi range. Toggling Airplane mode always fixes it for me.
eventer289 said:
I have an issue like that, but the dial pad doesn't go blank. the call just sits there in silence and never connects. I have to toggle Airplane mode to fix it.
Click to expand...
Click to collapse
I have this exact issue and the airplane mode toggle fixes it. I would like to know what is going on , whether my device is defective or if there is a better fix.
Same issue (not connecting calls, not the screen blank issue)