I have a Verizon Droid 3 phone and it's now unlocked and I am using Rogers/Fido service in Canada. Most of my calls I receive show up as Payphone or Unknown caller. I am dual booting between the default image(5.6.xx) and ICS Alpha #5 and no matter what ROM image I use, it doesn't get fixed. I heard something about downloading true callerid but I can't find it in the Market. Any ideas to fix this? (Especially anyone using the ICS version). Thank you in advance.
Are you using CDMA or GSM? If GSM try changing your apn info.
Sent from my DROID3 using XDA App
Same problem with me ..
Sent from my A15 using XDA Premium 4 mobile app
I remember having similar problems (I think, was a long time ago), and I think simply turning OFF Assisted dialing under settings -> Call settings helped for me...
Edit:
Thinking about it, I recall that all incoming calls showed up with american +01 in front of every number, thus not linking them to my contacts. So my problem was not exactly the same as yours but i guess you could try disabling assisted dialing anyways to see if it solves your problem.
Sent from my DROID3 using xda app-developers app
Related
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
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 a problem using the Nexus 6 on my carrier, "Bluegrass Cellular" which is a regional cdma/lte carrier partnered with Verizon Wireless under their "LRA" (LTE in rural America) program. This issue happens with other carriers under the same agreement, and a few other carriers per Google search but I couldn't find any solutions. Issue doesn't seem to be ROM dependant either. If more carrier specific info is needed I can provide it.
Before a wonky work around mentioned next, this is the issue. Problem is if connected to LTE, everything works, calls in and out, mms in and out, and receiving sms. But you cannot send sms. If you are connected to LTE, when you send a sms it will fail with the message message, "cant send message (insert carrier name) error -1. But you could downgrade network to 3g and you can send fine. But back to LTE no sms.
Only fix/work around my friend found is to flash the android m preview radio. With that, sms sends, but it takes 30-45 seconds to send per text.
Does anyone have any ideas? Android m radio with delay is better than nothing, but it's still rather frustrating. Thanks in advance for any inputs.
Sent from my Nexus 6 using XDA Premium 4 mobile app
I'm in the same boat here, tried multiple different things and no luck. Only fix is m radio that's takes up to 40 seconds to send which I feel is wasting precious battery life. Anybody have any idea?
fantasy2c said:
I'm in the same boat here, tried multiple different things and no luck. Only fix is m radio that's takes up to 40 seconds to send which I feel is wasting precious battery life. Anybody have any idea?
Click to expand...
Click to collapse
Yeah it is. Hopefully someone has suggestions on how to fix it or have any info on what's making it hold up when it sends. No idea why it sends instantly on 3g, 40 seconds on LTE on m radio, but no sending at all on lte any lp radio. Would it be a radio problem maybe I'm not sure... With all the proper apns set (not that it should matter for sms) I don't know what else it could be.
Sent from my Nexus 6 using XDA Premium 4 mobile app
Anyone got any ideas?
Sent from my Nexus 6 using XDA Premium 4 mobile app
Bump. Still looking for advice regarding this issue. Any insight is appreciated.
Sent from my Shamu
Go to the info dialer menu (*#*#INFO#*#*). Go to the phone info. Scroll to the bottom and turn off SMS over IMS.
Done already doesn't change anything. Same delay on LTE
Sent from my Shamu
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)
Hi guys. Been having issues receiving calls lately. The phone doesn't ring and the caller says it goes straight to voicemail. I read through some support forums on Verizon's website and it looked like other people were having the same issue. Verizon suggested making sure Advanced Calling was on. However, it DOES work for me when Advanced Calling is OFF. Has anyone experienced this? It's pretty frustrating. I'm on Computerfreek's 1.5 build. Thanks in advance.
Sent from my XT1254 using XDA Free mobile app
I too have been having this issue; it does not occur consistently but every few days I am told by people trying to contact me that their calls are going straight to voicemail. I do have Advanced Calling on but I noticed the last time it happened (last Friday afternoon 10-23 at my office where I always have service) that when I made a phone call, I could not access data / internet simultaneously also. After a reboot, everything was back to normal though; I too am on Computerfreek's 1.5B Pon-3 Base w. IOS Emoji build.
met the same issue in China, everyday received several SMS says somebody called you but not answered...
Are either of you using Google voice as your voicemail by any chance?
Sent from my XT1254 using XDA Free mobile app
papstar said:
Are either of you using Google voice as your voicemail by any chance?
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I use Google Voice strictly for voicemail (no calling), but I do not have the app installed on my phone. I just receive vm notifications via gmail.
I ask because after this issue I went back to using Verizon voicemail and everything is working as expected.
Sent from my XT1254 using XDA Free mobile app
papstar said:
I ask because after this issue I went back to using Verizon voicemail and everything is working as expected.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I have used google voice since its inception on other phones but have been having issues with it since advanced calling was added to this phone; at first with kitkat, I would get calls and see if I missed calls, but if someone left me a voicemail, I would not receive it. On rooted lollipop roms, I have tried using GV with and without the app installed but it never seems to work perfectly. On a positive note, I haven't noticed the issue occurring since the last time I posted about it but I will most likely make the switch to vzw if it does.