maybe they just dont wanna talk to you and hanging up....
I spoke with Live chat motorola support about the same issue and here is the copy:
Here is the copy of my Live support chat:
Valeria: Hi, my name is Valeria. How may I help you?
Me: I have a motorola droid and just wanted to see if you are aware of a call issue
Me: When I dial a number to call, press send and bring phone to ear...the bottom buttons (back, menu, home and search) light up and whole screen comes back on...and this ends the call.
Me: at first the screen dims, but then above happens
Me: Will there be a fix for this? I have lost many important call because of this.
Valeria: It seems to be that the prioximity sensor is not working properly.
Valeria: Have you tried to remove the battery from the phone?
Me: I have rebooted the phone a few times. Once I reboot it, it works fine for a little, then the bug comes back. I have researched and seen many people with same issue.
Me: or I should say, the battery pull/restart is the only temporary fix, unless I use speakerphone. But in most cases it's a confidentiality thing.
Me: so I need to use my phone properly.
Valeria: Motorola stands behind our products by offering a one-year warranty issued from the date of purchase. This warranty does not cover physical or liquid damage and is applicable to all the phones that were manufactured for the US market.
Valeria: You may prefer to check with your carrier for insurance, replacement or exchange programs available with your plan or monthly fee. You may also send the unit directly to Motorola where our technicians will make any necessary repair to ensure a properly functioning unit. Our turnaround time at our National Service Center is 5-7 business days since we receive the unit at our facility. If the phone is determined to have suffered physical or liquid damage, it will be shipped back to you unrepaired.
Me: Is this a software issue or hardware? I have heard many reports of this. If it's software (ie OS code, etc), then a software update would most likely take care of it.
Me: If it's hardware and many people have the same issue, then it's pointless to replace the phone, as all of them will have it. (they were from mass production, correct?)
Me: In case that it's hardware, motorola needs to redo the handsets???
Valeria: Please note that this issue is handled like a problem with the phone. The option from Motorola is to offer a free repair since it's covered under warranty.
Me: But what my point is, if it's a know software issue, then may be it has already been taken care of with the Android update that may come?
Me: Instead of me going thru hassle of replacement and Me: you know what I mean?
Valeria: No, I'm sorry. The update do not solve this issue.
Valeria: The device will be examined by a technician and will be repaired. It won't be replaced.
Valeria: This is the only option available from Motorola.
Me: Ok. What is my option? Will I be without a device?
Me: Should I send it to motorola or go to vzw?
Me: I am sure vzw will offer a replacement and that is not what I would prefer.
Me: I love the phone and just want it to work.
Valeria: The option from Motorola, as I explained previously, would be to send it to be repaired. I can send you the instuctions via email.
Valeria: Motorola do not offer loaner phones, I recommend you to check with your carrier for this.
Me: Ok, let me call vzw and find out what I should do. As far as instructions, yes, please send them to firstname.lastname@example.org. Thank you for your assistance.
Me: Do you know if the newer units (like the 2nd/3rd batch) have same issue?
Valeria: This is not considered as a "known issue", so the newest phones shouldn't have this issue as you have.
Me: Ok. Thank you. Again, please don't forget to send support info to my email.
Valeria: No, I won't.
Valeria: If you need any more information get in touch. Thanks from Motorola, bye!
Me: Have a great day.
So, all I can say is DARN!!!
tats, are you saying you pressed 1 to program your phone ... and then when that was finished, called back and pressed 2 to update your roaming? And this helped with the disconnect issues?
I just received a voicemail from VZW and there is not an update on the horizon for this fix ... so I assume nothing will be done until they hear enough complaints to warrant an update or upgrade or fix. I guess it's just not a priority to Moto/Google/Verizon ... ugh!
Motorola said they would pass the feedback along blah blah blah ... not sure how far that will get us.
I'm still trying to find a 'work-around' for this ... covering the sensor with my 'unique skin' doesn't seem to be helping ... I wonder if a developer would be able to come up with an app for this issue ... maybe something where we had to press the power button to blacken the screen and then press again to bring it back if we need to press the dial pad buttons. Hmmm... if only I was a cool developer... LOL!
My wife was having a similar problem. I started looking into what it would take for me to write an app to address this problem and during my research I found an app called Screen Suite. It is an iPhone lock screen clone but it has an option to lock the screen when a call connects. It has solved the problem for her.
This might be slightly off topic but I've been talking on the phone with my gf a few times and my face will move far enough away from the screen that it will likely come back on and the mute button gets pressed. Next thing I know she's like, "Hey....hey! Hello?" and I keep going "Yeah...yeah! What?!" and then she hangs up and calls back. This happened three times or so until I finally caught onto it. The sensor is cool and all but I wish you could simply turn the screen off so that it wouldn't come back on until you pressed the power button. Of course if you use an earpiece on your lengthier conversations, or live alone and thus use speakerphone, this isn't really a big deal.
I had a Droid a couple weeks ago and this was one of the reasons I returned it. I was on phone #2 and it still kept doing the same thing.. number beeping, hanging up, muting calls. I liked the phone alot, right now I'm holding out for the Nexus One. I'm hoping I dont run into the same problem with it.
I'm glad to see I'm not the only one this is happening to.