Child Item

Site Totals

61410 Questions Answered 270 Categories

Droid won't answer calls, won't notify on new VM

At some point during the day, my Droid will refuse to take calls. People who call my number will be forwarded directly to voicemail. Also, the phone doesn't notify me that either (a) I missed a call or (b) I have a new voicemail until I refresh the display in my Visual Voicemail app. I can make calls during this time, but I can't receive them. I generally have three or four bars for most of the day, and my 3G connection seems OK. While calls won't ring the phone, email and other notifications appear to work fine.

Turning the phone off and on again seems to solve the problem. Is this happening to anyone else? Any help is appreciated.

Comments

seriouscat

When I call my phone from my office phone, it rings and rings on my office phone, but the call doesn't pick up on the Droid. Sometimes the Droid will pick up the call and start ringing halfway into the call, other times it works just fine. I don't get it. It makes me wonder how many other calls I'm going to miss out on just because my Droid isn't ringing when someone calls. I'm wondering if it has something to do with signal strength, but it seems like I have 2-3 bars when I do the test calls from my office phone.

I also had an issue two days in a row where it wouldn't let me slide unlock it when there was an incoming call. I had to press the power button to get it to unfreeze (I'm assuming that's what the problem was). Other calls throughout the day didn't give me that problem.

I feel like it's pointless to bring it into the Verizon store because I know when they test it, it's going to work just fine.

robertpalmer

One more data point in tracking down this problem. I discovered this morning that the Droid wasn't receiving calls. The phone uptime was around 41 hours, and the time since the last call was about 16 hours. The phone's status said "In Service" and was not roaming.

I made a call from the Droid, and it went through fine. Then, I tried calling the Droid back, which worked.

So, in addition to restarting the phone, making a call seems to correct this issue as well.

Child Item