Voice Command 1.6 BT confirmation not working on 6800
 

Hello,

I have VC 1.6 installed and the default for VC is confirmation. If you leave it as the default and you dial a person by name - e.g. call mary at work, it will try to confirm you want to dial mary but it doesn't listen or can't make out the confirmation so it never places the call. You can turn off confirmation and it will place the call but I'd like to get the confirmation working.

i also don't receive any announcements. when i get a call the sound is still routed to my bluetooth headset, but it's just the phone ring sounds, not my lovely MS lady like I'm used to!

I was hoping that some of the sprint cabs that install when you first boot up the phone cause this problem, but i have no idea as i haven't rebooted without installing them because i'm waiting to hear which cabs are definitely needed and which are not.

the stock VC works for me over BT without a problem

I am a little unclear as to whether VC works...

Can you initiate voice commands from the headset? If so, does this open the audio gateway to allow you to speak the command via the headset?

Do any voice notifications work either through the BT or internal speaker?

This will decide whether I want to trade me 6700 in for the 6800.

thanks for the help!

Ron

Mine did not work, added the following to my reg:

HKLM\Software\Microsoft\Bluetooth\AudioGateway

(DWORD)
LaunchAPEnable = 1

VoiceCmdEnable = 1

BlueTooth on Headset now works fine.

-Sonny

Mine is finally working after making some minor changes from above as well as tweaking the notifications and options settings in Voice command 1.6

Not sure how it happened, but I change the notifications preferences and it has worked ever since.

The solution Sonny listed is for VC 1.5. You will not need to make those changes for VC 1.6 - it is BT enabled by default. If you make those changes with 1.6 on you 6800, after you reboot your BT will not work properly with VC 1.6.

RJB - you can use VC to make calls - however you have to turn the confirmation off as that feature doesn't work so it will never place the call. Turn it off and trust the VC to get it right 100% is your only option currently short of not using VC.

Or I just say "show contact name" and when it pop it up, I press the dpad in. That way I am sure I get the right person.

I am using VC 1.6 as well. Works fine.

-Sonny

exactly. Mines working fines as well. I tried both 1.5 and 1.6. 1.6 is the only one that is working on my end.

So are either of you saying that confirmation works for you? I can dial through vc however if VC confirmation is turned on it will not verify and complete the dial sequence.

Mine is confirming like it used to. It is only through the headset which is the way I actually always use it anyways.

Did you have to make any registry changes - I'm wondering why it doesn't work for so many of us - there is a large number of posts in MS's newsgroup about this same issue.

It's not working for me either.

I think I'm having the same problems as some... voice command doesn't appear to be hearing my confirmations... only over the bluetooth headset... just performed my second hard reset of the night I'll have to re-pair my devices and try again.

NOTE: It was working on a cheap Mustek headset I bought off woot. But once I paired my new one it no longer works using either. Even after the hard reset.

Did you read the title of the thread? And some of the posts? This is a known issue, if you have confirmation on VC will not hear it, hence will not finalize placing the call.

Some users have e-mailed MS and are looking for a fix. It also seems to work for other users although they have not replied as whether they were using confirmation or not.

Is anybody having the issue of where if you are on the phone over BT and then have any type of notification (i.e. text message) the BT drops? I had this happening and then once I uninstalled VC it stopped happening. Is there a fix?

-JAE

It is still working, but I only hear it through the bluetooth. I did install BTToggle and I'm not sure if that may have something to do with it. The confirmation is working, but all of the voice confirmations sound like crap through the headset (it used to sound better on my old 6700 and my 750WX)

I'm not sure if its a fluke, but I'm at least happy it is working for now.

I've been messing with it for a while now and I think I will review what I have done to make mine work OK.

1) make sure that the Voice Speed Dial that comes with the Phone is disabled. This can be accomplished by going to programs and selecting Voice Speed Dial switch and hitting disable.

2) I also made these changes to my registry (not sure if they made a difference or not.

HKEY_LOCAL_MACHINE\Security\Policies\Policies\0000 1001 = 2
-> Change the value data from 2 to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\0000 1005 = 16
-> Change the value data from 16 to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\0000 1017 = 128
-> Change the value data from 128 to 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> Add new value "0000101b": Dword = 1
Close registry editor and soft reboot.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2 DP\Settings
UseJointStereo: change the DWORD from “1” TO “0” no quotes.

HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd
Add "Priority256 "= dword:60 (Use Dword Value)

HKLM/SOFTWARE/Microsoft/Bluetooth/AudioGateway/Capability
(Dword:69)(Default is 37)

HKLM/SOFTWARE/Microsoft/Bluetooth/AD2P/Settings/BitPool
(Dword: 60)(Default is 30)

I Think these probably didn't do it.

I also installed BTAUDIO (which I think is the key somehow) and details of that can be found in the thread "How to open Audio Gateway over BT?"

I then installed VC 1.5 which didn't work worth a damn, and then I removed it. I then installed VC 1.6 and within voice command 1.6, I unchecked calender, media, messaging, start menu and then made the following changes to the phone options: I Checked confirm calling by name (works fine) and confirm when dialing by number (also works fine). Only thing that doesn't seem to work is the beep notification to start the "Dial (###) ###-###" Other than that it is working fine. That isn't a critical thing for me at least.

Thats all I did. If I can find a way to film it working, I will post the video. Like I said before, this was a major annoyance with the Treo 700WX that you couldn't voice dial over BT. I am just thrilled that it is working on the Mogul.

Here is the video hosted by Photobucket.

CALL SPRINT
http://s192.photobucket.com/albums/z...t=ed5fa9c0.flv

CALL RETENTIONS BY NUMBER
http://s192.photobucket.com/albums/z...t=2380ecdc.flv

It kinda surprised me when I did the call sprint. It was the first time it gave me the button press notification beep.

biglee - it appears in both videos that you are using the handset, not BT headset to make the calls.

Confirmation works for all of using our handsets - the issue is confirmation does not work when we initiate VC using our BT headsets.

I am. It works the same with BT, but I used the handset so everyone could hear the confirmations, etc. When I press the BT on my headset, it beeps and then does the same as it used to.

Earlier this week, when BT audio was set to open the Audio Gateway, I could only use the headset. Once I switched it back to voice speed dial, it works like it did before!

What ringer do you guys have set in Notifications so that VC will announce the caller upon receiving a phone call?

Text Messages and Emails are being announced just fine. Just phone calls are not.

I can't seem to get text or emails announced. what ringer do you use to have them announced?

thanks

A - I can't complete calls using my BT
B - I am not getting any announcements over my BT (i.e. text and emails)

Both of these things were working fine on my 6700.

Please I need help. I specifically signed on tonight to find a solution to this very issue.

There are some files on XDA that I got to get Voice Command working on Windows Mobile 6. This isn't the only handset that has issues.

There was an internal build of WM6 with a slightly newer version of Voice Command inside it that they took the files out of. It consists of a replacement executable, and a few DLL files. Overwrite them as necessary (Wherever they are at - in \Windows or \Program Files\Voice Command) - and do the INITVOL registry tweak for the software that we all know and love, and you'll be all set.

Mine allows me to give commands via Bluetooth, and announces incoming calls (as well as calendar reminders and corporate email) over my ring tone on my Mogul.

It's file "voicecommandreplacementfiles.zip" in the thread "can someone extract VC 1.6 from faria's rom?" on the third page.

Hope that helps.

Oh... and USE THE DEVICE TO UNZIP THE FILES!!! (To save yourself a LOT of trouble.) Actually use the "ZIP" utility on the handset, or else may you fare misery from the "converted to mobile" format of each file inside the zip file.

Also, VoiceCommand has to be NOT "Enabled" to copy over it's executable. If it is "Enabled", you'll get a sharing violation message saying you cannot overwrite the file. Reenable it after all four files are overwritten.

Are Registry Tweaks the only way to get this work the way it did on the 6700? I am not comfortable messing around with the phones registry not to mention I don't have any software installed that would enable my accessing it.

The registry shouldn't be feared, a lot of changes you make with software just make the necessary registry changes with you. If they are well documented on here you will have less to worry about. If adverse effects come from a registry change made and you are unable to change it back, it's easy to solve, with a hard reset. Just remember to backup often! I have pretty much given up on this software package working well in its current state. My question is more for Microsoft, when will we see WM6 support in the app itself!

I did the INITVOL hack to modify the registry to allow louder volume. I didn't have this software on my 6700 so I don't know how it functioned out of the box.

At a minimum, those four files need replaced with the ones I referenced. After that, it seems that VoiceCommand 1.6 not only works, but it works 100% on the HTC Mogul

I was wondering the same thing. How is it announcements and voice recognition worked fine on the 6700 but doesn't on the 6800. I went to MS site and they didn't have any stuff on the WM6. They still have stuff about WM5. They need to update their site pronto.

Tested with a BT headset? And what about the problems with Call Announce?

confirmation over bluetooth still doesn't work for me after adding the files

My handset announces calls aloud after the update in the little computer narrator voice. I have it set to play announcements through the handset, not the headset.

I can also dial out using voice commands with Bluetooth. I simply hold the headset "answer" button in and speak into it like I would the handset. I have tested this with a Nokia HS-26W and my new Plantronics 665.

Confirmation over Bluetooth is also somewhat working for me, if I'm understanding the question right.

Me (through the headset): "Call John Smith"
Handset (through the headset): Two known numbers (or whatever it says)
Handset (through the headset): Call John Smith at Work or Mobile?
-----------
Now, if I say "At Mobile", it doesn't work. But, if I respond "John Smith at Mobile", it works sometimes. The best thing to do when you're calling out is to leave the confirmation feature off and dial out with "Call John Smith at Mobile" in your initial voice command (the headset will still say "Calling John Smith at Mobile". I think it has to do with how it's looking at the voice spectrum through the headset during confirmation. It doesn't seem to work as well during confirmation as it does during "dial out" mode.

Ok I put the four files in there, which made it so I now when I press the button on my headset and say "Call John" it will come back and say, "Call John?" no matter what I say after that nothing happens.

Is there something else I have to change? I saw something about having to change the registry to tweak InitVol for voice mcommand, I put it to 7, but it still is a very faint voice.

Is there something else I have to do so that I can get it to recognize that I say yes and dial the number? I'm using Voice command 1.6 I wasn't sure how to turn notifications off, since I heard that was a problem with it still isn't it?

Any help would be great, I'm trying out my friends Mogul right now, if I can get this to work on it, Ill be buying one tomorrow myself!

Thanks,

!J

what do I put to turn off notifications which I guess is the only way to get this to work. I am on the Voice Command Notification Options screen but am not sure which to check as none of them seem to be to turn notifications off.

Can someone help me out?


There are 3 options

Announce notifications using Bluetooth hands free only

Announe notifications using Bluetooh hands free if available

or Announce notifications through device speaker or wired headset only.


Also should I check off Only during free time or uncheck it.

~J

I don't know what is up with my Mogul but my voice speed dial has to be set up. Everytime I press the voice speed dial button on the phone or bluetooth it tells me there are no trained voice tags. I literally have to go and record my voice for each option like calculator, audio, activesync, contacts and such. That is crazy.

BTW the voice speed dial software is
Cyberon Voice Speed Dial Settings Version 1.2 Build 070129

I hate the included Cyberon program.
I am using Microsoft Voice Command 1.6 with the included wired headset and it is a lot better, though it is still far from perfect.
One word simple names stink on it, like Mom.

I am using "Announce Notifications through Device Speaker or Wired Headset Only" and I have "Only During Free Time" unchecked.

I am using VC 1.60.4622.0 on my new HTC 6800 and have seen many suggestions to turn off the confirmation. Unfortunately, I cannot find this option. I might add that this is the purchased and installed VC, not bundled. Am I overlooking something in the VC options?

I installed VC 1.6 on my Mogul. The Confirmation DID not work so I uninstalled. Now, my standard Voice Speed Dial no longer works through the BT headset. It works when I use it on phone, but not through the BT headset. I had previously tested it Out of box and it worked fine with stock voice software and BT headset. After the VC uninstall I press the talk button and say a name in the BT and nothing happens.

Any ideas?