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!