[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
Wrong..

Nope. Turning bluetooth on does not do this.

Connecting a bluetooth A2DP sink does this. Now, when you turn on bluetooth, if your car supports A2DP, it probably auto-connects, and does this to you. However, in the bluetooth menu in android, under the settings for the paired device, you can disable 'media audio' for that device in the phone. Now, if you connect a bluetooth device that supports both Headset audio and media audio.. the phone only actually connects to the headset audio profile, leaving your media audio routing as if there was nothing connected to bluetooth. (My bluetooth earpiece 'supports' a2dp - but it's poor quality and mono, why would I want to use it?)

Why wouldn't it? Bluetooth media audio (A2DP) is a completely different bluetooth service from bluetooth handsfree profile or headset profile. Your car stereo probably supports both A2DP and Handsfree Profile. If it didn't support Handsfree profile, you wouldn't be able to take calls through it. Handsfree profile allows the phone to indicate that there is an incoming call, and to activate the handsfree device when the call is answered. So.. bluetooth would tell your car stereo, as it is supposed to.

Well, hope you learned something with your subscription. :)

This is for the samsung OEM docks (And work-alikes) that use a 619 kOhm resistor between MicroUSB pins 4 and 5 to trigger 'car dock' mode, and have the data pins of the MicroUSB connector connected to the right/left channels of the audio jack/cable.

This does not hook up to a USB data port - the data pins are re-purposed to carry analogue audio instead of a digital signal. So you would use an OEM dock that lets you plug an 'aux cable' from the dock to your car stereo.. or you could make yourself soemething like this and plug the usb plug into your charger, and the 3.5mm jack into your aux-in.

Bluetooth call audio is working still - with our patches, bluetooth devices still take priority for call audio, so those of you using it that way are still fine.

However, we're trying to get this in CM10 proper, which means we are trying not to make anything work worse than it does currently. IE, if we made it so you couldn't use speakerphone in the dock, it'd be a regression, and I bet there are those who would see that as an issue. It should be fully fixable, but you gotta give us time to figure out how. :)

On an aside, this thread educated me about the downsides to A2DP streaming from CM10. I'm really disappointed that the quality is so bad - I thought it passed 16bit/44.1khz PCM over bt, not some horribly lossy mess. I want to start looking into that next - I don't really like having a dock in the way in my car, so I've been looking into an A2DP-capable receiver, but I don't want the quality to be horrible.. but I am curious, does anyone know if CM supports the mid-level codecs bluez supports? Apt-X is one high-quality codec, but A2DP defines MP3 or AAC coding is allowed as well, both of which it looks like BlueZ supports (Howerver, no Bluetooth A2DP device is required to support MP3, AAC, or Apt-X, just "SBC", which is the ****ty codec) - I wonder if it's really just up to what codecs your device supports?