ACURA MDX . ORG
www.acuramdx.org ACURA MDX . ORG Archive > General > General Discussions
 
Blue Tooth Help - Click HERE for Original Thread
Advertisement
telstar
What am I doing wrong?? Every time I get into my X, I cannot find the connection with my phone. If I go back into setup and "pair" my phone again, it workd great.

Any idea why I have to "repair" my bluetooth every time I get into my car?

Thanks
Danger Mouse
What phone are you using? My (and my wifes) Moto V551 work perfectly with both our X and our TL. There are a bunch of threads on this over on the TL site (http://tl.acurazine.com/forums/forumdisplay.php?f=2) that might be of some help.
dstrimple
I've had my Bluetooth phone--Motorol v710--for three months now and it lost connectivity just once. I powered the phone off and on again and the connection was restored. I never ran a repair.
telstar
I have a V710 and Verizon service.
Advertisement
dstrimple
Service is Verizon also. It has happened just once in three months. Recylcling the phone on/off did the trick.
dstrimple
One other possible variable--I never turn my phone off. It's on 24/7. So it's either your phone or the vehicle itself. Good luck...
Jim03MDX
Have you gone into bluetooth settings on your phone? Does it list Hands Free Link under paired devices? Look at properties for Hands Free Link and check to see what the options are to recognize/trust this device. Maybe this setting is off.
denm316
I have a v710 as well. By any chance have you taken it in to Verizon and had the firmware upgraded in the past month or so. I am not saying this is the problem, however when I got the new firmware it fixed issues I was having with numerous other Bluetooth devices.

It is a free upgrade and will make the phone more stable overall.
Advertisement
myu
Telstar, try to do a master reset with your V710 and see if that helps with the problem. I have the same phone and a while back I had a problem with incoming calls not ringing in the MDX. Originially I thought it was the MDX that was causing the problem but it turns out that resetting the phone actually corrected the problem. Hope this helps.

Powered by: Search Engine Indexer and vBulletin v2.2.9
Copyright © 2000 - 2002, Jelsoft Enterprises Limited
Copyright 2000 Acuramdx.org. All Rights Reserved.