[Desire Q&A, Help & Troubleshooting] psych0t1c:
I am pretty new to Android and still trying to get all the grips on I need. As of now, there is one thing that really bugs me badly.

I use the device for Sat-Nav driving a lot, I have a semipermanent installetion in my car from my previous smartphones. Basically just a power feed and a 3,5mm Jack that come out of the dash panel where the device holder is mounted. I recharge plug in for recharge as needed. The audio jack goes into the device, from there to a so-called Fastmute box behind the dash which is connected to the stereo head unit (the loudspeaker output cables running away from the head unit to be specific. The Speaker lines are interrupted by the box and just pass through whatever audio is being played back by the stereo. However, once there is current on the 3,5 audio jack (i.e. speech from the SatNav) the music immediately goes mute and you can hear the turn instructions in perfect quality through the car speakers. Once the signal fromthe satnav dies down stereo music comes back.

For my taste this beats most commercial, fixed systems.

Now, since I am on Android weird stuff happens.

On a first testrun shortly after I gut the Desire (which was o2 branded stock 2.1 at that point) I noticed that I do not get any announcements through the fastmute. Checked the jack, opened the dash to check internal wiring, retried a mp3 player. It's all good on that side. The accouncements come through the device speaker, hard to hear, easy to miss a turn etc. I do not why or how, but it seems that the audio routing takes a route different from other audio. This had me pretty much meh!

Well few days later, now with a ModaCo R8 custom ROM and Froyo I was hoping for good luck and gave it another whirl. Of course, no dice. When I plug in the jack of the supplied headset (which I assume doubles as a handsfree) I get the symbol for that in the upper symbol bar. When I exchange that headset jack with the regular 3,5mm jack the symbol looks different, but still vaguel like a set of speakers.

But now here comes the completion of the mindfaq... I had the SatNav volume at about medium (so barely hearble with driving ambient noise) when the phone went and I took the call through the Bluetooth Handsfree instaalled in my car and was distracted by the call (the car came euipped with the BT Handsfree from factory, so the stereo goes to "pause" and the conversation is routed into the vehicle speakers.. A few minutes into the call I suddenly hear a perfectly well understandable, clear turn instruction hopping into the phone conservation. I was extremely intrigued and was hoping that I discovered that CoPilot can route instructions either into A2DP or more likely emulate a "call event" that results in routing the audio into the according BT profile.

However, after that singularity I tried reproducing this for a god part of an hour, driving a route that forces many instructions from the SatNav, all the while calling my own answering machine fo have an connection established.

Sorry for the lengty explanation. Questions:

1 Has anyone ran into this before? What was your solution? Bear with it, switch SatNav software, avoid listening to music in oder to not miss any turn directions?

2. Is there a hack, hidden configuration that would enable me to _force_ this audio routint into the direction of the BT Handsfree, making it think it is an incoming call?