4.2.2 BT won't auto connect with Ford Sync

[Lukewarm]

My Verizon Galaxy nexus is unrooted and stock. Since the 4.2.2 update my phone won't automatically connect with the Ford Sync system in my car. I don't use it for audio, just phone. The phone shows it as connected but the car doesn't see it until I disconnect and reconnect on my phone. If I attempt to voice dial through the car's system it tells me there is no phone connected.

Prior to the update, whenever I started my car, the BT symbol illuminated in the message center and the phone would work through the steering wheel controls or voice commands. I never needed to pull my phone out of my pocket.

I've searched and scanned the first half dozen pages. Most BT problems talk about it turning off or audio problems. This update made a good working system a complete hassle.

 

[mruno]

try "forgetting" it on your phone and then add it again.

 

[jj14x]

I have the sprint version of the phone, and 4.2 screwed up bluetooth for me too (though in my case, it is even worse - it disconnects from my car's BT system very frequently. Restarting BT on my phone will usually reconnect, but only for a little time - it disconnects again).

It was perfectly stable with 4.1

Hopefully, google will get this basic feature working again

 

[Lukewarm]

I have deleted the phone from the car and "forgot" the car from the phone numerous times and then resynced both. Still, no dice.

 

[Demache]

Bizarre. BT still works perfectly on my Kenwood unit. Is this exclusively a Ford Sync issue?

 

[jj14x]

nope - I've seen this issue (with my phone) on Toyota's OEM system, on Chevy's OEM system, and on Audi's OEM system

I suspect it is device specific...

 

[CharlzO]

nope - I've seen this issue (with my phone) on Toyota's OEM system, on Chevy's OEM system, and on Audi's OEM system

I suspect it is device specific...

It's more a 4.2 update specific thing, actually. Google changed the Bluetooth stacks or something technical, and it really caused havoc for a lot of people. I know on the Sourcery ROM, there is a backup to the old version, I rarely have disconnects, maybe once a week if that, now. I've been on that a while though, so I can't say as I've paid much attention to what's going on with it on stock.

 

[iron_city]

I have deleted the phone from the car and "forgot" the car from the phone numerous times and then resynced both. Still, no dice.

I have a VZW stock SGN, and my connection with Ford SYNC is working perfectly fine with 4.2.2.

But there was a hiccup ... it didn't automatically connect after the update. I noticed was that my phone was renamed after the 4.2.2 update. In "Settings...Bluetooth", my phone changed from "Galaxy Nexus" to something like "Galaxy Nexus463829". (I don't recall the exact numbers.)

I deleted the phone from SYNC (and forgot SYNC from the phone), changed the name back to "Galaxy Nexus", then re-added it. No problems since.

I have the basic SYNC, though. Is this what you have, or do you have the MFT? When asking questions about SYNC, you should state which system you have.

 

[mgdeftones]

I have MFT and since the update it has been hit or miss. It doesn't happen often, but there are times when it won't pair with the car. I had to pair it several times to get the car to actually download the phone book so I could make voice calls.

My main issue is that most of the time my phone won't turn off blue tooth sharing after I get out of the car and if I don't turn my blue tooth off and on it drains my battery pretty quickly.

 

[jbarhorst2]

Mine is terrible too. I have a Lexus LS and since the update my Bluetooth in the car constantly mutes and unmutes the radio. Sometimes BT works for calls and sometimes not. PITA. WiFi at home drops in and out too.