Related
Is 1.6.17913 the latest revision? If there's a newer one, I'd like to get a hold of it...Yes, I do own 1.6 legally...
Mine says v1.60.4622.0, which I think is an OEM version that is part of Helmi's Apache Kitchen.
JimSmith94 said:
Mine says v1.60.4622.0, which I think is an OEM version that is part of Helmi's Apache Kitchen.
Click to expand...
Click to collapse
I have the same version, but I have spotty trouble with it on my Tilt. I can't get it to announce incoming calls. (I better do more research. I am sure someone has solved this.)
Mark
Incoming announcements work on the Tilt, but not the Hermes. Pretty sure it's just a registry edit, or you can install ZaJules BTFix - enable it, power down, disable it, power down.
I'd be interested to know about this as well.
Also, i recently rom'd my wizard to WM6 and now when i press the button on my BT Headset, voice command is not fired. If I remember correctly, wasn't there a reg hack for this to get VC to launch on button press?
Thanks
pkley said:
Is 1.6.17913 the latest revision? If there's a newer one, I'd like to get a hold of it...Yes, I do own 1.6 legally...
Click to expand...
Click to collapse
That's the latest one I've heard of.
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...
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
I posted a couple of days ago but didnt really explain properly so starting again.
I have a touch pro, with romeos2 rom installed. I have tried the 1.51 and 1.60.1 builds.
the device pairs find, picks up phonebook etc fine. but i cant dial from the headunit. its driving me insane. I havent tried with other roms apart from romeos2.
Sometimes it will dial but only if you dial on the headunit then turn phone off and on. it seemed to work slightly better with romeos1.51 but still useless.
Does anyone have any ideas? meh... getting annoyed with this
p.s. i tried my friends touch HD and works perfectly, 100%. he has windows build 20757
UPDATE: incase anyone else is having issues
Monx (romeos2 legend) has asvised to try installing the BTSAP profile when using his rom. I havent tested yet but will try tonight.
What i did find is that I tried the windows build my friend had and that didnt help, issue was the same. I tried another radio 1.02.25.31, same problem only worse. then tried flashing RRE 3.1 fuze rom and at the same time 1.08.25.20M1 radio. Now the phone works in the car, responds to headunit dial requests.
New problem is that it doesnt download phonebook to the headunit.
will keep posted on progress if anyone is having this problem
same here, im running Romeos 1.5x final touch pro rom on my fuze.
paired fine, cant make phone call, the car shows no connection
i tried install BTSAP, BTSAP, BTBPP, doesnt work...
please help, i really like romeos rom
Its working!!! i reflashed romeos 1.60.2 and installed the btsap profile and its working.
I dont think its the btsap that did it as from what i gather the btsap is to access the sim card of your phone to use it remotely in another phone devide in a car stereo and i dont have that.
I think the think that fixed it was flashin the australia radio 1.08.25.20M1.
It responded instantly to dial requests and pairs fine!
teddyonair said:
same here, im running Romeos 1.5x final touch pro rom on my fuze.
paired fine, cant make phone call, the car shows no connection
i tried install BTSAP, BTSAP, BTBPP, doesnt work...
please help, i really like romeos rom
Click to expand...
Click to collapse
Try flashing the australia 1.08.25.20M1 Raphael radio and see if that works.
Also have you tried Jetware handsfree extensions? Some head units need this to work properly, and i think pioneer has issues if its not used.
1.08.25.20M1 ? I've been using this radio since they first posted it here.
so i dont think its the radio thats blocking it
any other suggestion?
btw i have a kenwood navigation with bluetooth add-on. works fine with my tilt and all the other phones.
thanks in advance...
teddyonair said:
1.08.25.20M1 ? I've been using this radio since they first posted it here.
so i dont think its the radio thats blocking it
any other suggestion?
btw i have a kenwood navigation with bluetooth add-on. works fine with my tilt and all the other phones.
thanks in advance...
Click to expand...
Click to collapse
did you try the Jetware handsfree extensions? http://www.jetwaremobile.com/index.htm
well after all that, i hard resetted my device again to setup up from scratch, tested with new radio and it didnt work.
Sooo... installed the BTSAP profile and working fine so looks like that was the cause of my problems all along
thanks for testing that for us...
i installed BTSAP in my fuze still no luck...hopefully more people will come in and share with us how their setup works
well after all that mine isnt actually working properly arrrrrrgh
I just did few tests as have been messing with phone at work then quickly testing on breaks. anyway basically if the phone is on it seems to work fine and connects/dials calls perfectly since installing btsap....
however.... if the phone goes in to standby for a length of time it doesnt wake up when i try and dial from the headunit. If it then turn the phone on again it will start dialing.
This is totally 100% doing my head in as just spend bloody 90 quid on the bluetooth thing for my car
Anyone got any ideas why it wont wake up when dialing from bluetooth handsfree? The dial command obviously got to the phone as it starts dialling when you take it out of standby.
HELP! lol
Glad to see I am not alone in this. What a pain! Can someone tell me where to download the BTSAP cab? I will try that and jetware to see if it helps. I have a Kenwood head unit that also allows for SMS via the head unit but it doesn't work with my Fuze. Anyone else have that feature working?
Thanks
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