I've got the same problem with my 7130e on VZW. When it first happened, tech support (in typical VZW fashion) said they had never had the problem before and it must be the phone. Swapped it out, and still have the problem. When others receive calls from me they can hear themselves in a really bad echo!
I just purchased the 7130e and am having echo issues. I took the phone back yesterday and now my new one is doing the same thing. I have no control over the volume when speaking on the phone either.
After reading on this forum.. I am going to change out the phone for another model. Does anyone have suggestions?
Thanks so much.. this forum is a great tool. I only have so many days to trade the phone out and I'm sure they would have kept swapping me with new ones had I not read about everyone's issues.
I find that my callers experience an echo not while I'm using a Bluetooth headset, but AFTER it. And disabling Bluetooth is not enough to rectify the problem. I have to remove the battery for my callers not to experience the echo anymore.
RIM really blew this one! It really sounds like a software problem, which begs the question: why hasn't a firmware update with a fix been released?
Last edited by ndirish2001; 08-01-2006 at 12:32 PM..
Try the following to stop the echo with Bluetooth Headset.
Remove the battery from 7130e.
Replace battery
Select OPTIONS icon
Select Bluetooth
Select the Bluetooth accessory for which the 7130e is paired to
Select DEVICE PROPERTIES
Select ECHO CONTROL
Select CHANGE OPTION
Set to 'ON'
Select SAVE
I have used this setting for many different Bluetooth headsets and it works great. Good luck
Try the following to stop the echo with Bluetooth Headset.
Remove the battery from 7130e.
Replace battery
Select OPTIONS icon
Select Bluetooth
Select the Bluetooth accessory for which the 7130e is paired to
Select DEVICE PROPERTIES
Select ECHO CONTROL
Select CHANGE OPTION
Set to 'ON'
Select SAVE
I have used this setting for many different Bluetooth headsets and it works great. Good luck
That would be a 7130e
I have the same phone and yes, that option exists. Mine is set to "automatic" and I haven't had any problems with my Plantronics 320.
I just performed bajan's advice. Hopefully it will work.
OT: Had a discussion with Verizon rep. He got to play with the new 8705 coming out. If I'm still having problems with the 7130e I will replace it for the full keyboard IF IF IF the 8700 Verizon series has EVDO with tethering capabilities.
PS - I see the forum community is calling it a 8703e but the tech rep indeed called it an 8705 twice, although he could have been twice mistaken.
Last edited by $tockmarket; 08-05-2006 at 07:36 PM..
I've taken the advice and changed the Echo setting from automatic to on. However, I don't think it is a Bluetooth issue (at least in my case) because the people I am talking to hear their echo when I am using the handset, so Bluetooth cannot be the problem.
It is interesting that other have commented on this problem having started about 2 months ago. This seem like a Verizon problem. I dont think that everyone's phone has started doing this simultaneously due to a hardware problem.
I almost always get complaints about the person on the other end hearing an obnoxious echo that makes it hard for them to hold a conversation. I feel this is affecting my everyday business. A reboot fixes the problem for about a day, and occasionally my blue tooth will help the problem also. Verizon needs to figure this out. This is a business phone. They are affecting a very important part of their business. rebooting is not a solution as my phone rings constantly all day and a reboot can take nearly 20 minutes. I wonder what kind of solution is out there? Are they going to have to issue a new model or can they create a firmware? Either way that have to face the facts that something needs to be done. I agree that Verizon is very good about sending you a new phone, but the new phones seem to have the same old problems
Same problem here with Sprint. I am now on phone 3, 20 hours of t-shooting into it, they offered me a $5 credit. Phopne 3 seems okay 2 days into it.
Quite embarassing problem in a professional setting, quite inconvenient...network people say it's the phone, phone people say it's the network. How do they go months without detecting a problem?
I just found this post doing a yahoo search since I don't know if Verizon will solve this problem.
I started having the echo problem about 2 months ago myself. I called Verizon they sent me out a replacement phone and it does the same thing. They are going to be sending me out another one and I should have it in a few days.
Only thing that seems to temporarily fix it is taking the battery out and putting it back in or muting the phone or switching it to a bluetooh device, seems to fix it for like 2 days. Mine does it where ever I am after about 2-3 days.
I hope Verizon can fix this bug. I wonder if it is anything to do with the firmware 4.1.0.268 update that fixed the bluetooh reboot issue and the getting stuck in 1x. I noticed this issue after I upgraded the firmware. which was also about 2 months ago. It does seem software oriented on the phone itself, too buggy to be the network. Of course my friend updated his bberry as well to 4.1.0.268 and his doesn't echo here at my house.
