Last edit by: IB Advertising
Issue: Cannot default the My Ford Sync system (without Navigation) to Bluetooth audio
Some users are having an issue with when they turn the ignition on their My Ford Sync system reverts to Line-In even though they were using Bluetooth audio when they turn their vehicle off. They would like to have the system revert back to Bluetooth audio instead of having to go through the menus to be able to get to Bluetooth audio or use the voice commands. A Ford customer service representative FordIVTteam actually joined in the conversation and gave the reason why Ford made this change (as it would previously revert to Bluetooth) and the best method to get back to the source they wanted.
Read the full discussion below.
Some users are having an issue with when they turn the ignition on their My Ford Sync system reverts to Line-In even though they were using Bluetooth audio when they turn their vehicle off. They would like to have the system revert back to Bluetooth audio instead of having to go through the menus to be able to get to Bluetooth audio or use the voice commands. A Ford customer service representative FordIVTteam actually joined in the conversation and gave the reason why Ford made this change (as it would previously revert to Bluetooth) and the best method to get back to the source they wanted.
Read the full discussion below.
Can Sync default to Bluetooth Audio?
Thank you Mr. Knowitall. We can no more stop posters from going off topic than we can stop you from trolling this thread with information that is not related nor helpful.
Spoken like a person who just finished bragging on his own creds...

I have gone beyond this forum... Ford is not going to fix this. Someone from Ford Customer Care for the Great Lakes Region called me to discuss the problem and offered me some free oil changes as a goodwill gesture. Why not just fix the issue instead of 'handling' me? The woman who offered me the oil changes had spoken to someone in engineering who confirmed this is a known issue and not one of simple phone connectivity. (Thank you anyway, Mr. Badass69) She also made it clear the fact they are aware of it doesn't mean they will fix it. Nevertheless, it has been put into a pile of complaints which nobody at Ford will read.

Ditching the truck is what I plan to do. As stated, after driving Fords for most of my adult life, I am now a former Ford customer who is also a walking/talking billboard advertisement as to what a ****ty experience it is to deal with Ford and their dealers. As stated earlier, Mike Rowe is a liar.I will be making some videos which show the nonsense that is Sync and compare it to technology available in other vehicles.
I have already convinced three people to purchase non-Ford vehicles; two shiny new GMCs and a Toyota Tundra have been purchased instead of F-Series trucks thanks largely to me. I even referred the guy who bought the Tundra to the salesman who sold us our Toyota mini-van/kid-hauler. I hope all you people who are dissatisfied with Ford vehicles will likewise tell everyone you know that you are unhappy. Tell EVERYONE!!!
My next truck will likely be a Toyota Tundra. My neighbor's Tundra is a sweet ride and the bluetooth media interface works properly. Woulda, shoulda, coulda... I'm still looking for a car for my kid but a Ford is not being considered.
All this over the
radio and the inept handling of customer complaints by Ford and the dealer.Hey Ford!

Good.... now you can stop you incessant whining on here and go whine about the next thing you don't like on a Tundra forum. Lol. I like that even through the banter CP3 is going to try and make a solution for this.... versus you that can do nothing but complain... Because yes Ford should fix it... but won't so get over it. Good riddance.
Should be starting all that in the summer if everything goes as planned.
My idea should work. My end game is to have my in dash ipad control the ac, heater, etc by sending messages over the trucks can bus. It's just a matter of sniffing out the protocol and making a list of commands, which is going to be very time consuming. Then you just send the desired sequence using ipad, android, arduino ...whatever really.
Should be starting all that in the summer if everything goes as planned.
Good.... now you can stop you incessant whining on here and go whine about the next thing you don't like on a Tundra forum. Lol. I like that even through the banter CP3 is going to try and make a solution for this.... versus you that can do nothing but complain... Because yes Ford should fix it... but won't so get over it. Good riddance.

Yes, Ford should fix this. So how is my complaint about it whining?
YOU said it was a phone connectivity issue. Now, you say CP3 should be able to fix it through reverse engineering? How is this possible if the phone won't even connect as you've concluded, tech genius?
Since portions of the CAN bus messaging are proprietary, we don't even know that all the Sync messages even use CAN messages to control the media functions within Sync. Those functions may be self-contained in the head unit and not subject to external control from CAN. Not everything in the vehicle does. Example... air bags.
The only reason anyone would go to such lengths is they are willing to fiddle with it. It stands to reason, then, since I'm bothered by the fiddling required to get music to play via bluetooth that I would be disinclined to go to such lengths to reverse engineer this by sniffing messages and trying to write my own software which you agree Ford should be fixing themselves.
CP3 may well be able to control the heater, AC, headlights, etc. using an iPad or a microcontroller but may not be able to gain full access to the sync functions which control the entertainment system. Further, since the bluetooth connectivity remains part of the problem, controlling those things via reverse-engineered software is rendered moot if you still have to fiddle with things to get devices to connect. You'd end up with cool software but be no further with regard to the fiddling required to make things work.
It seems like only a troll would make issue of my legitimate complaint and suggest that because I am unwilling to reverse engineer the CAN messages, write my own software and interact with a bluetooth<->CAN interface that my complaint constitutes "incessant whining". Most reasonable people would say my complaint as a consumer is legitimate.
So, insult me all you want, TROLL, I CAN <---(see what I did there?) do more than complain about this. Even though "...its just a matter of interfacing with the truck and of course decoding their signaling for whatever desired output you have. And like you said..." blah blah blah as you try to BS your way to appearing an expert... As a customer with a new truck, I shouldn't have to do ANY of this.
Again, I cannot stop you from trolling this thread and bragging about how tech smart you think you are. Don't assume, however, you are the only one who possesses any technical skill or knowledge. You lost your cred when you stated this problem is caused by people's phones. You sounded just like the
in the dealer's service department who told me to contact my cellular provider to get this working.(You aren't the
from the dealer's service department, are you?)
Seriously I won't even bother to read all that drivel. Go complain about your next purchase on another forum..... I see troll in there..... well personal attacks and never posting beyond to complain about the rest of the worlds hardships against you pretty much is textbook definition. Again.... no loss whatsoever.
Last edited by 1994Vmax; Apr 2, 2014 at 05:25 PM.
Oh I know for a fact the sync commands are sent over the can bus. I've probed and identified nearly every component involved in the sync system. It's just a matter of spending the time to decode the messages, or even identify the protocol it uses at that. There's no standard protocol for the entertainment bus like there is for OBD bus. That's why it will take a long time.
Oh I know for a fact the sync commands are sent over the can bus. I've probed and identified nearly every component involved in the sync system. It's just a matter of spending the time to decode the messages, or even identify the protocol it uses at that. There's no standard protocol for the entertainment bus like there is for OBD bus. That's why it will take a long time.
Yeah that's what I thought. I know it's Canbus too but never researched yet as to whether signalling is standardized or proprietary. That's really gay that it's not standardized..... not impossible but like mentioned..... thousands of commands and line by line. Ugh....
Holy Smokes Batman! We need Therapy for some folks here...
Folks...before freaking out at each other, make sure you've all installed the latest updates to your systems.
I didn't check all the posts to see if you all did this as I'm too lazy (being Indian it comes natural to me).
My sync (or as I called it stync at the time) was always giving me problems too, then I updated the system and voila! (not all) but most of the problems were solved.
So lets all dial it down a notch, crack a Michelob and chill out...while you maybe do a system update.

Folks...before freaking out at each other, make sure you've all installed the latest updates to your systems.
I didn't check all the posts to see if you all did this as I'm too lazy (being Indian it comes natural to me).
My sync (or as I called it stync at the time) was always giving me problems too, then I updated the system and voila! (not all) but most of the problems were solved.
So lets all dial it down a notch, crack a Michelob and chill out...while you maybe do a system update.






