Thread: Voice Command?

Commands work fine on the handset. It will announce appointments and messages through the speaker. I have not been able to get it to announce incoming callers in my contact list which is a big disappointment after turning off my old Treo 700w. I figure, anything you can't get it do on the handset, probably won't work under BT either.

I just got the new Plantronics Discovery 975 BT yesterday and couldn't get it to voice dial which caused me to start searching all the forums. I turned on all the obvious settings on Voice Command as well as BT. The forums led me to believe that it wasn't going to work. For this specific BT, on the call button, 1 sec is a tap, 2 sec turns it on, 4 secs turns it off. I discovered that pressing the BT call button for 3 secs causes it to issue a long low tone, followed by low-low-hi beeps will wake the Pro2 and it will issue the Voice Command low-hi prompt. You can then dial by name, number, ask time, next appt. etc. It takes a little time --> 3 secs to get tone + 5 to 7 secs to wake the phone + 1 to 2 secs to get the VC prompt....but it does work (probably 10 secs total). Right now functionality is more important than speed. Announcements play through the BT just like they are supposed to. It still doesn't announce callers or play distinctive rings in the BT. When a call comes in, it plays the distinctive ring through the handset speaker -- which although disruptive, at least lets me know who is calling.

If anyone has been able to get incoming caller announced through the handset or BT, I would like to know how you did it.

ROM 1.21.651.3
ROM Date 07/17/09
Voice Command v1.6.21052

To recap, currently the TP2 is unable to deliver Voice Command announcements thru a bluetooth headset due to an incompatible bluetooth stack.

I note that there was a TP2 ROM update in mid-October but the HTC site doesn't given any details about what was fixed.
So how do we hold HTC's feet to the fire on this crucial feature that doesn't work at all???

Can anyone provide some historical perspective on how responsive or non-responsive HTC has been to this kind of problem in the past? (My impression is that it's been years since HTC last produced a phone that worked properly with Voice Command
over bluetooth. For example, I don't think Voice Command worked properly over bluetooth on the Fuze or the Tilt or the
8525. If I'm mistaken about that, please let me know.)

Voice command worked perfectly on my Touch Pro, VZW. It does not work however on the TP2. Odd, but true.

Anyone managed to get this working on a TP2 with the official WinMo 6.5 upgrade from HTC?

Ta

Andy

I just got the phone - and have used other WM/HTC phones in the past. The VC works just fine for me - but had to find the menu in the TP2 to turn it on. I pair to a BlueAnt speaker which hangs on my visor which one of the best investments I've made to date. When I pair the device - it loads up all of my contacts (over 1200), and works great for dialing as well as receiving. When a call comes in, it announces the caller by name (unless it's an unknown phone #). This feature was in earlier WM phones and also worked great with my BlueAnt.

Best of luck.

R.

Rich,

You're right that the Blueant Supertooth 3 that hangs on the visor is a great gadget.
But this is way off topic: The Supertooth 3 is doing the caller name announcement,
not Microsoft Voice Command in the phone.

What we want is for Microsoft Voice Command to perform caller name announcement
through a bluetooth headset, not by using a device like the Supertooth 3 which is only
useful when you are in your car.

So far no one claims to have gotten this to work properly on the TP2 because the
bluetooth stack is incompatible with most of the features of Microsoft Voice Command.
I'm not holding my breath waiting for HTC to fix this. They really don't seem interested
at all.

Robert

Got it - and that explains why today (trying to successfully do the same with my Jawbone heaset), I got absolutely nothing out of it. Pretty much useless.

What's funny (sad) about this, is I just upgraded from the Fuze, where it worked fine. Didn't try THAT in the store.

Sorry about the confusion.

R.