This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Reboot by holding down the power button on top and hitting (power off) when it comes on the screen. Wait a few seconds and hold down the power button. The phone takes a minute or so to reboot. It's solved the problem twice for me.
I rebooted, *228 1 and 2, took out the battery and threw away the cover that came with it. Something made the echo go away. Took the private off, didn't work, so I put that back on. I'm doing great now. wooo hooo!!
Since this appears to be a widespread problem, I would think Verizon would put something on their support page explaining the problem, work around, and final solution. It doesn't make sense for everyone to have to try different solutions until something works.
The problem has nothing to do with cell vs landline. If you use a bluethooth device, there is no echo, cell or landline. It is some type of software or combination of software and hardware that requires a fix.
I emailed Verizon support about the echo problem. This was the response:
"At this time, I have not heard any concerns regarding the Droid having any issues. I wanted to provide this information over the phone but due to the industry regulations, it was too early to contact you. "
I called tech support and they said to remove the battery while the droid was up and running and then replace it after ten seconds. Pretty harsh reboot..... The echo went away.
I'd also had the problem that my email wasn't downloading and the reboot cured that also. I'm hoping we don't have to reboot every couple days...
Bob
Isnt this echo, reverb, 'tones' issue supposed to be addressed in the 12/11 update? My issue with this 'whistle' and 'tone' noise seems to come and go right now.
I made a phone call while still in bed this morning and my bed has steel bars around and above and I got the echo back on the other end.... but the interesting thing is when I walked away and got out of the steel cage of my bed it went away.
I don't know if I was getting standing waves reflecting back or if it was causing a marginal signal to the towers.....
My phone did the echo thing again today.. this time i did a *228 and picked option 1 and it didn't reboot my phone and without trying to go back in and try option two, I tested it and that seemed to fix it. "again"
So since there was no reboot involved, that makes me think its related to interaction with the cell sites as doing a reprogram or a reboot either one would cause the camera to release connection with the cell site it was locked onto and come up on another.
Found this over in the crackberry android forums...anyone tried it yet:
Saw this tip over at HoFo:
Get into the programming menu, from the call screen, enter ##PROGRAM and press send. Enter code 000000.
In option 04, you can change the vocode option to EVRC-B, it made my in-call audio sound better. Your phone will reset after you exit and apply the new setting.
Warning: Be careful what options you change in the programming menu, you could potentially brick your phone.