Database Info

Microsoft Voice Command

Anyone have any luck getting MC VC 1.6 to work on the Touch Cruise via bluetooth? I can get it to work via the buttons on the TC itself, but not via any of the bluetooth headsets I have. I also have an AT&T Tilt and 8125, and I don't have any issues using MC VC 1.6 and bluetooth headsets with either of those phone.
I've tried all the fixes I've found so far, but none of them have worked so far. If anyone's got any ideas how to get this working, I could use some help.
Stumped,
Dave

Hi Dave. I have MS VC 1.6 up and running on my TC via bluetooth on my Jawbone no problem. Know it doesn't help to answer you questions, but it does work.
Dan

Dan, thanks for the reply. I got it working, but had to jump through some hoops to get it working, and I'm not sure which step was the one that finally got it working. Seems to be working OK, but I no longer have a flashing blue LED light on the TC to show that Bluetooth is turned on.
Did you have to do anything special to get it working? Can you tell me what build of MSVC you're using?
Thanks,
Dave

MS VoiceCommand v1.60.4622.0
Hi and sorry for my pour english,
I installed MS VoiceCommand 1.6 Fr on my HTC Cruise.
Everything works fine except that the blue LED does not flash when I turn "On" the BT.
If I remove MS VC with the BT "On", the blue LED restart to flash. And if I reinstall MSVC, it stops blinking.
I still have a look at this forum and the other ones, but I didn't found the solution.
Maybe someone can help me ?
Bemi

How could i get this to work on the S9's on the Tilt and 8525 instead of the voice recognition app?

MSVC Broke my BT,could not connect to my Moto S9 with it installed. Had to uninstall VC to get BT back. Anyone else have this prblem?

bemi said:
Hi and sorry for my pour english,
I installed MS VoiceCommand 1.6 Fr on my HTC Cruise.
Everything works fine except that the blue LED does not flash when I turn "On" the BT.
If I remove MS VC with the BT "On", the blue LED restart to flash. And if I reinstall MSVC, it stops blinking.
I still have a look at this forum and the other ones, but I didn't found the solution.
Maybe someone can help me ?
Bemi
Click to expand...
Click to collapse
Bemi, exactly the same thing for me, with MVC 1.6 fr on my TC french SFR opérator
waiting for some trick to fix that blue led

I have the same problem with the blue light (it is really a very strange bug...)
An other question, with BT on: I try to use the vocal command with the head set and the phone on stand by nothing happens if I turn it on the phone (but the phone is still locked) nothing happens. I have to unlock the TC to be able to use the MSVC with a bluetooth headset.
is it normal???
Hope my question is clear...
Thank for any help/info

dfields said:
Dan, thanks for the reply. I got it working, but had to jump through some hoops to get it working, and I'm not sure which step was the one that finally got it working. Seems to be working OK, but I no longer have a flashing blue LED light on the TC to show that Bluetooth is turned on.
Did you have to do anything special to get it working? Can you tell me what build of MSVC you're using?
Thanks,
Dave
Click to expand...
Click to collapse
@dfields,
Could you please explain what you did to get VC to work? does your BT work after instaling VC? Not just the flashing LED but are you able to connect to a BT headset?

XDA Orbit 2 and Voice Command does not announce incomeing calls
Hi,
my device: XDA orbit 2 = Touch Cruise = Polaris
OS: WM6 GER
VC 1.6 GER
I know that there are problems, but i also do know, that it can be solved. there are some files to be replaced on the phone. i tried the ones that are offered in another thread for another wm6 phone, but the dont work. i guess, because they are for the english version of VC 1.6, but i have the german version.
does anybody know, wher i can get these files? or how can i make VC 1.6 to announce incomming calls on my xda orbit 2?
Thanks

8925 Tilt ms voice Command 1.6 over bluetooth

I have just upgraded to the tilt .
I have installed ms voice Command 1.6 and also the bt voice Command hack to allow voice Command to come over my bluetooth . Well it's not working . even if I edit the reg. I also tried the vc16btfix , still didn't work. is there something i'm missing ?

criddle said:
I have just upgraded to the tilt .
I have installed ms voice Command 1.6 and also the bt voice Command hack to allow voice Command to come over my bluetooth . Well it's not working . even if I edit the reg. I also tried the vc16btfix , still didn't work. is there something i'm missing ?
Click to expand...
Click to collapse
I have 8925 with Custel ROM. I've read here and there that people upgrade and install the BT Hack...
But I never had to. I had the 8525 and I remember I had to add the BT Hack (and give it like 15 seconds or whatever...) to transfer all audio to BT. But at least on my 8925, right out of hard reset, VC 1.6 works fine with my BT Headset (Jabra, Jawbone, few Motorolas, etc...all of them works fine).

Search button is a good friend on this forum it helped me find my solution for this exact same problem
Try this:
Edvard_Greig said:
Hallelujah! I finally figured it out- so it did have to do with the XCSDM setting I believe... so here is what I did for anyone else that is wondering:
1. Installed MSVC 1.6 (from the link in the TNT ROM posted earlier)
2. Soft Reset
3a. Made registry change to set Path = \Program Files\Voice Command\voicecmd.exe (no quotes)
3b. Change button assignment (assigned to Button 6/PTT in my case)
4. Soft Reset
5. Enable XCSDM
6. Soft Reset
7. Disable XCSDM
8. Soft Reset
9. Pair Bluetooth Headset
It seems to be working...the best I can figure is that when it initially gets installed the XCSDM doesn't have any value at all, but by enabling it, and then disabling it, it actually turns it off as opposed to having a null value. Also note that since I am using Alex's 'UltraClean' ROM, there were never any Cyberon installation traces, and therefore I ignored those sections.
In any case it seems to be working great and I'm very happy.
Thank you everyone for all your help, and hopefully what I listed above will help someone else.
Click to expand...
Click to collapse
found in this thread over here: http://forum.xda-developers.com/showthread.php?t=333260&highlight=Microsoft+Voice+Command&page=16

i'm using the original wm6 that came with th tilt. when I do push the button on my headset it's like all the handset volume is transferred to the headset

i had same issues then i tried the steps above and solved my problem i'm not on the original att rom anymore though i'm using dutty's dualtouch v3 rom. You should try those steps mentioned above should solve your problem if not then dunno sorry i went crazy my self trying to fix this problem then when i tried this solution it worked i was so happy all the headaches and times searching forums finally paid off LOL. Anyhow good luck.

Running Dutty's v2K fixed and . . .
no issues with MSVC 1.6 without hack. sometimes stops responding but either turning my BT off and on again, or SR fixes it. Using a Jawbone if that makes a difference.

Problem after updating to new ATT Tilt Rom
I cant use voice command through the headset anymore after upgrading the rom from HTC. What happens now is when I press the Bluetooth button it transfers any sound to the headset (Music playing from MP or in call voice) but will not allow me to use any Voice command functions.
Please HELP!!

Redundant...
Another dead thread that wouldn't have to be killed if the search function was used...

WM6.1 and MS Voice Command

Did anyone get it to work on wm6.1? i install it and it installs, but when i try to go to settings it will not go any farther. I like to have in say whos calling. Its a feature i can't live without! any help would be appreciated!
wolfskin

I think this is a problem when using the "official" 6.1 base. When I load it, it freezes after the install (like when it tries to load the "Help" file) and I must SR the phone. The next boot will be fine until it seems to start the Voice Command program, at which point will freeze the device. I had to hard reset to recover.
Others have reported Dutty's and other 6.1 releases not based on the "official" ROMs work with Voice Command.

i have it installed, haven't noticed any problems or than it needs to be tweaked to anounce calls. all other features, buttons, menus work.

i cant resist this one
READ THE FORUMS
http://forum.xda-developers.com/showthread.php?t=365118&page=6

1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)

Mine works with Schaps...
I am the same way, i must have MSVC for my blutooth carkit...Schaps is the only one i could get it to work well on; however, I din't try it on Dutty's

Just Tested on Alex's WM6.1 Home BETA 2
Works Great.

No problems...works on WM6.1

OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.

Same Here, no issues (Except the caller id anouncement)

Works fine for wm6.1 and its fine with my parrot carkit actually bluetooth audio much much better now

WM6.1 VoiceCommand 1.6 US
Works fine here - in fact BETTER than with original TYTN release where it would often hang just after hoing the lookup till you hit the Red Phone Key.

Now that it sounds like BT volume is better with 6.1, has anyone taken the time to compare registry settings between WM6 and WM6.1 to see what the differences are?

asking it to play music, and than anything works for me, no issues.

Laubscherc said:
Same Here, no issues (Except the caller id anouncement)
Click to expand...
Click to collapse
Did you go into Settings-Personal-VC and check "announce incoming callers"?
Mine is working completely without any hacks.

In the official 3.03 used in Alex's 6.1 Beta 1, MSVC didn't work for me, crashed the settings.
Now with Alex's Beta 2 he used official 3.02 and MSVC works perfectly.

asfoor said:
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Click to expand...
Click to collapse
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!

MELPHBOY said:
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
Click to expand...
Click to collapse
Use Kaiser Tweak in disable the trusted certification.

alltheway said:
Use Kaiser Tweak in disable the trusted certification.
Click to expand...
Click to collapse
Not true....
The Voice Command.asx is NOT part of Kaiser Tweak Menu. There are only two certificates to disable or enable. Even if you were to disable both the WiFi certificate announcement or the BT Certificate announcement, the VC.asx certificate right violation still shows when you request or command the VC, and will not respond to the command.
Did you locate the certificate disable/enable on your phone Kaiser Tweak before you decided to post your response?
Unless you can prove me wrong, I AM WAITING.........

pkley said:
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Click to expand...
Click to collapse
What radio did you upgrade to ? just tried all 3 and still doesnt work for me

Which MS Voice Command version works

Anyone know which one works properly with bluetooth and announcements?
thanks

MS Voice Command
I use MS Voice Command v1.60.4622.0; it works fine . I've made an update from the older Version v1.5, which didn't work on the TD1 either.
I have to admitted, my TD2 arrived only 3 days ago, so I couldn't use voice command for hours, but making a call ist very easy, the speaker of the TD2 is of good quality.

and what about announcing incoming calls by dictating the caller ID name or incoming phone number? I was trying it with MS VC 1.6.19971 without success :-/

Hi,
which button is VC using?
Regards,
Rodik
Drobix said:
I use MS Voice Command v1.60.4622.0; it works fine . I've made an update from the older Version v1.5, which didn't work on the TD1 either.
I have to admitted, my TD2 arrived only 3 days ago, so I couldn't use voice command for hours, but making a call ist very easy, the speaker of the TD2 is of good quality.
Click to expand...
Click to collapse

is it possible to use the button of ear-phone?
in the setting i found only button 1....
thx

try http://ae.inc.ru/aebplus.php it is working

neveceral said:
try http://ae.inc.ru/aebplus.php it is working
Click to expand...
Click to collapse
Can you tell me which button you remaped?

no one knows? i tried every button in the list and also its not possible to set it up as a new one.... damn i need this!!!

You can map it in settings, personal, buttons. Select MS voice command from the list on the right. This will then also work with bluetooth headset button.
I can't get incoming caller announce to work on any UK version.

no, there is only button 1 shown!
also i need this for a wired headset, no bluetooth crap

I'm using MS Voice Command v1.60.4622.0 and everything works as it should. I have mapped the long press call button and it works with a bluetooth button as well. It works with both hands free units I have in our two cars and also with the Garmin Zumo on my motorbike. Caller id announcements work also as long as your bluetooth unit supports that function.

ok, it works for me with bluetooth as well, but i want to use the button og my ear phones! i love music and there is not good solution for bluetooth. so in the next days i get an adapter to use my high performace era pohnes and i would like zo use vc with the button on this adapter! the problem is it doesnt work with the one includet!! so please dont tell me it works with the blue one!!

ok, got it!
go to:
hklm\software\oem\voicecommand\
create string key "Path" value "\program files\voice command\voicecmd.exe" or whatever
gl
incubus

Did you fix call announcements?
This registry edit gets announcements to work:
Edit this registry key:
HKCU\ControlPanel\Sounds\TTSAnnounce\Category
Change from VoiceCommand1 to Ring
It should now work, but sounds level is low. To increase the sound level, I did this edit:
HKCU\Control Panel\Sound Categories\Voice Command1\AttenutationCategory
I set it to 4 which is decent, you can go to 5, but I see no difference going louder. Using 0 or 1 will make it whisper quiet.
If that does not make it louder, then edit:
HKCU\Control Panel\Sound Categories\Ring\AttenutationCategory
Same thing, set to 4 or 5.

damn, doesnt work for me...!

Did you restart?
Edit:
This fixed it on my TD2 with MSVC UK1.6, the same version loaded on a Touch Diamond this fix didn't work. This program really is so odd.

sure, not only once, i also spend some time waintig, thought it could take a while but nothing! using vc1.60.4622uk... i think i will wait for wm 6.5 and the new integrated vc

I had problems with starting via Key 1.
I made a shortcut of voicecmd.exe und assigned the shortcut to key 1.
Works now via key 1.
Bluetooth headset key worked before.
Path in registry didn't help
v 1.60.4622 de

Hi,
What i did, to get MS Voice Command v1.60.4622.0 French version
retail, working with bluetooth Callerid's announcement:
i installed it (ps: dont forget to activate the notification via bluetooth, obvious but i forgot that before trying many manipulations ;-) )
All worked except notification via bluetooth
(i eared the ringtone instead of callerid)
i tried to replace some V.C files by the 1.6.192.13, because that was working with my Kaiser stock rom 6.1(but noway with the Topaz)
http://forum.xda-developers.com/showpost.php?p=2186001&postcount=254
(also tried with 192.14, 199.71,199.65,19209 but be careful some of the VoiceCommand_PPC.cpl versions made my topaz always rebooting the key to solve that worry was to replace via activesync the cpl file before the pin prompt, via explorer from desktop in the topaz/windows folder )
finally i uninstalled all, reinstalled retail 1.60.4622, Desactivated voice command (step quoted below perhaps not necessary, up to you)
And replaced the three files
VoiceCommand_PPC.cpl in /windows
VoiceCommandWMP.dll in \program files\voice command\
voicecmd.exe in \program files\voice command\
by those version 1.6.192.13
(ps: replacing VoiceCmdRes_PPC.dll with v1.6.192.13 as said in the link above made voicecommand crash when activating it)
Click to expand...
Click to collapse
All was working except the bluetooth announcement:
After i tried the regedit (backup first !!) given at the begining of that thread
hklm\software\oem\voicecommand\
created string key "Path" value "\program files\voice command\voicecmd.exe"
Edited this registry key:
HKCU\ControlPanel\Sounds\TTSAnnounce\Category
i renamed the DATA of the string "category" from:
"VoiceCommand1" to "Ring"
to increase the volume i set to 4 the AttenutationCategory in
HKCU\Control Panel\Sound Categories\Voice Command1\
After a reset, announcements via bt are working
greetings

wm 6.5
Does MSVC work with the newer Sakajati ROMs based on 6.5 or not. I have a tad of ADD and can't keep up

Microsoft Voice Commander Not Working

When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?

I'm using 1.6.21040.
Gave an error during installation, but seems to be working as far as announcing calls and reading texts.

I have tried to installed version 1.6.21725 and it seems to work fine, but I tried to link to the key virtually using AE Buttons, everything collapsed. The lnk file just got deleted: any suggestion.
How did you guys use to assign to a key?

Was asking the same question. Install worked with one error message. The program works when I start it manually, but I cannot find a way to assign execution to a specific button press. Looking for ideas here.
Toby

i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way

I've switched to 21725 and used aebutton plus to assign it to long press windows key, all works perfectly now.

I dont want to use aebutton plus, so I tried to use the old Long_Send.lnk and had no luck, am I doing something wrong?
or is it a diffrent name in 6.5

MSVC
I got that error too but it has stopped for some reason and now works well.
Version is v1.6.21040
I tried to upload a cab for you but it wouldn't upload.
I use MSVC for text to speech, to announce calls, read emails to me and announce calendar reminders.
This version won't read text msgs.
I don't use it for voice commands, Cyberon Voice Speed Dialer is much better for that.
mallman said:
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
Click to expand...
Click to collapse

mallman said:
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
Click to expand...
Click to collapse
WHICH LINK DID YOU USE, THE SHORT OR LONG ONE??
Thanks!

I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.

MSVC cab
Oops!
Got it.
NotATreoFan said:
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
Click to expand...
Click to collapse

So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.

bill340 said:
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
Click to expand...
Click to collapse
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.

I Think I've Found An Answer
If you go into the registry and go to:
\\HKLM\Software\OEM\VoiceCommand
and edit the value for VoiceCmdEnable to 1 (it was set to 0 on my HD2), then soft reset.
Now you should be able to get Voice Command working through BT, at least it's working for me at the moment.

It does not help fo rme at all...
No change!
Which version of MSVC do you use?

I'm not entirely sure, but in the Voice Command settings it shows v1.60.4622.0

weepatc said:
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
Click to expand...
Click to collapse
In my case it is very similar, but when i activate voice command with the assigned button on my HD2 and not via the headset, everthing works as it should. Maby thats a indication how to get it worki`n the right way.

VoiceCommander Working
Hi,
Initially I couldnt get the BT to connect to VC (just got a BT disconnect beep in my ear).
Tried installing 2nd time (over the top), and seemed to 1/2 work but sometimes I would have to say name I wanting to dial through handset - then it would put call through BT - strange.
Finally, I noticed that if the BT headset was on when the phone was switched on (fluke that happened), it worked fine.
If the BT headset is switched on after the phone, it still plays up. Not tried turning BT on handset off and on whilst BT headset turned on yet - something to try tonight I guess.
Note : this only started working a day or so ago so not tested throughly yet.
My VC version is 1.6.4622.0.
I also noticed that on handango - a new VC version is available (updated 20/11/2009) which says works with Touch HD2 - but only USA voice at the mo so I'm waiting for the UK (hopefully released soon).
Hope the above helps.

Looks like I have an old version of Voice Command MSVC1.6.19214. How do I get a later version? Don't see why I should have to pay for it again when it is still 1.6.

Sorry, my bad - not working anymore. Worked for one day, then I get the same as everyone else