Regardless of the sig block, this isn't a paid endorsement. My copy of VC
1.6 works just fine with VC over BT. I use it with my K-Jam (an HTC device),
and have used it with an SP5 (another HTC gizmo). Primarily my use is with
a Cardo Scala Rider BT headset (mono) while on a motorcycle. The phone stays
in the saddle bag. My routine is to turn on the headset unit and then ask
for the time or battery life to verify operation. I have made calls by
pressing the button on the headset, waiting for the VC beep and stating the
name. After responding to the home, work, mobile question, the call is made.
I can answer calls on the Scala, which are announced by Contact name, by
saying 'answer', or pushing the button. (The answer via voice is a Scala
function, not a VC one). Hang up is automatic whether initiating or
answering.

I will comment that the Scala is not a cheap headset, with very good sound
and apparently great pickup and fidelity. My wife says I sound clearer on
the Scala on a bike going 50, than I do on the installed car handsfree in my
Jeep. So there may be some headset quality involved. Initially VC didn't
support BT because the fidelity of BT voice wasn't sufficient to ensure
voice recognition. I don't think BT got better, I think MS voice recognition
got better enough that they were willing to offer support. Doesn't mean
every headset provides sufficient fidelity.

I can of course not listen to music on the headset. I can request it, but
once the system initiates the media player it would expect to broadcast that
sound over a Stereo A2DP profile, which neither the K-Jam or the Scala
support. It just comes out of the K-Jam speakers. Not very satisfying when
the phone is in the saddle bags. ;) I have actually turned some of those
options off in VC support as each feature takes memory and processor effort.

I can't dispute that you can likely find lots of folks with issues on the
net, but for me it works as advertised and acceptably, within it's
constraints. Note that the units I use them on are official ROMs with the MS
BT stack.

--
Sven
MS MVP Mobile Devices
"Joe V" <JoeV@discussions.microsoft.com> wrote in message
news:ECEE3F61-0D5C-4C51-91B2-F9EEFD1D4466@microsoft.com...
>
> This is more of a rant then a question in regards to Voice Command 1.6 not
> functioning properly with mono bluetooth headset on my HTC Trinity and for
> the most part pretty much all new generation WM5/6 devices. Search Voice
> Command 1.6 in google and you'll find hundreds of posts from people upset
> at
> the fact that Voice Commands Bluetooth functionality doesn't work.
>
> Now yes I know some devices just aren't capable and I've also read that
> the
> problem with HTC devices is their implementaton of Bluetooth on newer
> devices
> isn't according to spec. As seems to be the case with other manufactures
> too!
> Will you think that two companies that are partnered so closely together
> when
> it comes to developing/promoting Windows Mobile devices would have seen
> this
> before the release of Voice Command 1.6 or at least came up with some kind
> of
> solution by now. HTC doesn't seem to care about fixing it, Microsoft is
> very
> quiet about it, even their website is inaccurate as to Voice Command
> outputting sound on WM5 revisions prior to a certain version.
>
> I'm sure it may not be an easy fix or maybe it is but in either case it's
> a
> real shame because Voice Command is an amazing application. It's one of
> those
> killer apps that once you start using it you can't live without it. I was
> using it on my old HTC Wizard without any problems and it was awesome,
> being
> able to dial without having to pre-record voice tags, hearing incoming
> callers, emails, appointments ect without having to look at your phone.
> Most
> devices can't touch this ease of use, not even the hyped up IPhone and
> you'd
> think Microsoft would realize this enough to get some kind of fix out.
>
> I saw an interview with someone at Microsoft showing how they were opening
> up Voice Command API so other applications could incorporate the voice
> recognition into their devices, this was awesome and I look forward to it.
> Of
> course this is still in the early stage. At least there is some
> development
> going on with Voice Command but how about releasing a working Voice
> Command
> patch for mono bluetooth headsets instead making us wait for a whole new
> version which will require a new device!
>
> Anyway I hope eventually Micrisoft or HTC or both will come up with some
> kind of solution as well other vendors!
>