Related
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Atra said:
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Click to expand...
Click to collapse
What else do you have loaded on your phone(s) that have this issue. I use VC on all WM6 and WM5 roms that I've run (and ones I've cooked, like the Crossbow Reloaded ones you mentioned) and have never had this error and I've never tweaked around registry settings. I just install the cab and it works...
Are you installing VC 1.6 US?
With all the WM6 roms i've used (not as many as some but i'm new here) I haven't had an issue with VC 1.6 US either.
don't think it's a definite answer, but i did have this problem in the past when i installed voice command on my memory card rather than on phone memory. sometimes during loadup after a soft reset i would get that error...think it's because it takes longer to load from the card and voice command is setup to run right away (always in the background)...
if it's installed on the phone memory...dunno...sorry
I run VC 1.6 US and have never had a problem with it. I always install it in main memory.
I give..
Going back to WM5 Molski. To answer some of the post..
It's VC 1.6
No other software loaded..Fresh flash.
Installed to device, not storage *only option offered for install location*.
Get a message during device install: (...recommend installing to main memory. Do you still want to install to "."...) I answer Yes because it just aborts install to say No.
Thanks for the replies guys..
<--[Totally Screwed]
OK, now I have no sound from the speakers and Mic not working. While in Phone mode, the speaker button stays in the On position and won't turn off. Got the old Voice Command registry settings in place but it seems the new problem is the culprit. Going to start a new thread with new problem unless someone has any ideas..
Closing out
Back up and functioning on Molski 3.3 Crossbow. From what I can tell, during the WM 6 load, the speaker phone option became stuck in the On position but the speakers and Mic were not functioning. Voice Command seemed to know there was a problem and gave the "..restart VC.." message. After re-flashing Molski (a few times, still no joy), I flashed with the wired earbud/Mic connected. After flash and phone restart, I removed the headset while in phone mode. Speaker button reset to normal, phone speakers/mic started working again. Reloaded Voice Command and all worked.
aaahh the joys of PDAdome.. Where else can you get the thrill of accomplishment by getting back to the same friggin place
Thanks again for the replies all..
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Give Molski a try..
Avatar28 said:
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Click to expand...
Click to collapse
I didn't have any problems with his roms (..and went back to it with no probs). Only started having problems after I tried the Faria WM6. If the Molski works for you let me know. We'll give Faria a nudge.. Good Luck!
VC issues I've run across
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
At one point I had a strange issue with the bluetooth microphone.... VC would work fine (I'd ask "what time is it" and it would tell me the time) but when I was in a call, no one could here me.... I ended up enabling and then disabling auto gain control... wallah, mic works again.... weirdness.... (don't think this was rom related)
Anyway... the roms that I've had this problem with was XDA Mobile 6 (release 1... relase 2 is kicking a$$) and I think NBD 7.1... never had a problem with a ny Pandora cooked roms.....
Anyway... my $.02... (I'll probably get change)
kudo's to the rom wizards that be...
never had a problem. Installed in a few different roms. works fine
installed to main memory.
wolverine9827 said:
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
Click to expand...
Click to collapse
Voice Command Bluetooth Fix
View attachment 43147
I can't take credit for this and I can't give credit but Thank you...!
I've used this and has worked when VC w/n initiate via earpiece.
There's several threads on the specifics of this cab.
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
sorry if this has been covered, but ever since i swithed to the 6.1 roms
i can not seem to get my bluetooth headset working. I can pair the device
but when i press the button on my headset nothing happens. If i hold the button in it dials the last number.
Anyone else experiencing this? Was working fine prior to 6.1 for me and
have done the process 100 times so i know i doing everything right.
6.1 does not prompt me for the device password "0000" ...
lancevs said:
sorry if this has been covered, but ever since i swithed to the 6.1 roms
i can not seem to get my bluetooth headset working. I can pair the device
but when i press the button on my headset nothing happens. If i hold the button in it dials the last number.
Anyone else experiencing this? Was working fine prior to 6.1 for me and
have done the process 100 times so i know i doing everything right.
6.1 does not prompt me for the device password "0000" ...
Click to expand...
Click to collapse
Funny you should say that. I have been trying DCS1.3 and the bluetooth works fine (both headset and a2dp profiles) and in Dutty's 6.1 rom (WHICH IS SUPERB I MUST SAY !!!) the headset profile works fine but the a2dp stereo occasionally cuts out. Done it a few times and it wasn't a range issue or anything. Anyone else had this !!
It's a shame because dutty's 6.1 rom is amazing. Love the speed of the cube and the beautiful icons !
Is it just me or has anyone else experienced this ?
maybe its just me!
am i the only one with this issue?
bluetooth
Mine works fine- I have three headsets and a Bluetooth GPS synced up.
pairing is no issue for me. I cant get the BT working with Voice Dialer.
Few ppl including myself have ask for solution in Dutty's thread, but no luck. I am currently using 3.03 leak version and it works great.
Did you HARD RESET after flashing the 6.1 rom at the "tap here" screen?
Yes.
Hard reset anf reflash few times... no go...
P1Tater said:
Did you HARD RESET after flashing the 6.1 rom at the "tap here" screen?
Click to expand...
Click to collapse
Penske MB said:
Yes.
Hard reset anf reflash few times... no go...
Click to expand...
Click to collapse
I remember there being a bluetooth fix with something.
Do any of these work?
tried both..... still no go
when BT botton was press, it went to dial pad instead voice dialer..
alltheway said:
I remember there being a bluetooth fix with something.
Do any of these work?
Click to expand...
Click to collapse
Penske MB said:
tried both..... still no go
when BT botton was press, it went to dial pad instead voice dialer..
Click to expand...
Click to collapse
do you map the keys correctly?
There is no setting to map the BT earpiece's botton.....
If any, plz let me know.
alltheway said:
do you map the keys correctly?
Click to expand...
Click to collapse
I have only just installed the new ROM and ran a few quick tests with the parrot minikit. It paired okay but then I had a few intermittent problems. Sometimes dialling from the phone would not automatically transfer to the minikit and sometimes I could not transfer a conversation from the phone to the minikit. Other times these worked okay. I did not try answering from the minikit as no-one called me while I was testing.
Only tried this once so will try again tonight and then try the bluetooth fixes and report back.
Using Radio 1.64.08.21 on Orange TyTN II and did the hard reset after installation.
Penske MB said:
There is no setting to map the BT earpiece's botton.....
If any, plz let me know.
Click to expand...
Click to collapse
Start > Setting > Buttons.
Again...tried... map the botton..... i have try everything I can think of, but... no solution....
BTW, the botton 6 "PTT" map will start the voice dialer. BUT... what I need is press the botton on BT device to start voice dialer and I will heard a "beep" to start voice dialer while I am driving or doing oter thing without touch my phone. When I press the botton on BT device, it goes to dial pad or I can't heard the "beep" again, and it start the voice dial in "mute" mode... I have never experience in any other ROM I tried before. So far I have not yet found any solution. I need the BT device, because I am always on phone while doing other things.
alltheway said:
Start > Setting > Buttons.
Click to expand...
Click to collapse
Penske MB said:
Again...tried... map the botton..... i have try everything I can think of, but... no solution....
BTW, the botton 6 "PTT" map will start the voice dialer. BUT... what I need is press the botton on BT device to start voice dialer and I will heard a "beep" to start voice dialer while I am driving or doing oter thing without touch my phone. When I press the botton on BT device, it goes to dial pad or I can't heard the "beep" again, and it start the voice dial in "mute" mode... I have never experience in any other ROM I tried before. So far I have not yet found any solution. I need the BT device, because I am always on phone while doing other things.
Click to expand...
Click to collapse
same problem here, was working great on all the 6.0 roms but since 6.1 not working for me.. i hear no sound in the headset. i do see the headset icon on the dialer screen, but the button on the headset does nothing for me.. I am using the motorola h700 i believe.
UK TYTN II with Dutty's 6.1 rom works fine for me. Holding the BT button on headset launches voice dialler ( Schaps cyberon version) Double pressing the BT headset button dials last number. Single press on BT headest answers call when the phone rings.
Can you attack the CAb you use? I might have the older version of Cyberon.
Thanks
c.b said:
UK TYTN II with Dutty's 6.1 rom works fine for me. Holding the BT button on headset launches voice dialler ( Schaps cyberon version) Double pressing the BT headset button dials last number. Single press on BT headest answers call when the phone rings.
Click to expand...
Click to collapse
Penske MB said:
Can you attack the CAb you use? I might have the older version of Cyberon.
Thanks
Click to expand...
Click to collapse
do u mean this one.
The one I am using from Schaps can be found here http://forum.xda-developers.com/attachment.php?attachmentid=63977
Thanks guys,
Those are the 2 files I found last night, but did not have the chance to try them yet.
Cyberon voice command is almost 2MB and compare with Cyberon Voice Dialer 617k. What are the difference between these two??
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
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