Database Users

Microsoft Voice Command

Hi,
I am thinking of buying this software to run on my qtek 9100.
It is running a T-Mobile 1.6 rom with the blackberry connect.
Will it work OK?
Is it worth buying?
Would you recommend it?
Thanks,
Dave

i use it and love it. only wish it would work with bluetooth headsets. it's nice to hear who is calling by a nice female voice rather than ringtones. the voice recognition is great as well.

I would recommend it.
The voice dialing works much better than the standard built in voice dialing (even though it has actually sampled your voice FFS).

bl117 said:
i use it and love it. only wish it would work with bluetooth headsets. it's nice to hear who is calling by a nice female voice rather than ringtones. the voice recognition is great as well.
Click to expand...
Click to collapse
It works great with bluetooth headsets. There's a couple of tweaks you need to do though. You can probably find it with a search.

bl117 said:
i use it and love it. only wish it would work with bluetooth headsets. it's nice to hear who is calling by a nice female voice rather than ringtones. the voice recognition is great as well.
Click to expand...
Click to collapse
if only she didnt sound like a chinese robot!

gregski said:
It works great with bluetooth headsets. There's a couple of tweaks you need to do though. You can probably find it with a search.
Click to expand...
Click to collapse
Unfortunatly, the reg hack tweak for BT VC only works once. It stops working after you end a call.

dangerous_dom said:
Unfortunatly, the reg hack tweak for BT VC only works once. It stops working after you end a call.
Click to expand...
Click to collapse
Huh? I've never experienced this. Every time I push the button on my headset, Voice Command activates. No matter how many calls I've had. It might be a matter of the headset as well. I could never get my Jabra BT500 to work reliably...sold it. But my Tekkeon ET3000 works flawlessly.

dangerous_dom said:
gregski said:
It works great with bluetooth headsets. There's a couple of tweaks you need to do though. You can probably find it with a search.
Click to expand...
Click to collapse
Unfortunatly, the reg hack tweak for BT VC only works once. It stops working after you end a call.
Click to expand...
Click to collapse
I never had this problem. Here is the tweak I use:
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe. Reset device.
When it stops working, does that registry value still show the right value?

works fine here
VC works great with my Cardo Scala 500. Sounds better too since they gave me free silicone caps. I can hear ringtones, notifications, etc. all through the headset.

Re: works fine here
j007w said:
VC works great with my Cardo Scala 500. Sounds better too since they gave me free silicone caps. I can hear ringtones, notifications, etc. all through the headset.
Click to expand...
Click to collapse
How did you enable ring tones? Mine doesn't do that by default and I haven't figured out how to enable it.

I don't think that anyone can say that Voice Command works flawlessly over bluetooth.
The fact that pressing the button on the headset opens the audio gateway and it has to be closed before it can be opened again is a bug, not a feature. The audio gateway should close itself and doesn't.
The software has been out since January '05, I believe, so some bugs with Windows Mobile 5.0 are expected.
That being said, I love Voice Command despite its issues. Once Microsoft decides to release a new version that works better over bluetooth, I'll love it even more. It's presently still worth buying, definitely.

it's a great program, but needs to be updated for WM5. It should support activation from Bluetooth headset out of the box.
Some people seem to have it working, but with my Sony Ericsson HBH-662 it only works once after each reboot.

Mine also works only once through bluetooth - i got the latest Rom/Radio Rom (the Mr Clean one) installed, perhaps that has got something to do with it?

Deep DooDoo
Hey Guys,
I installed voice command on my Tmo Wizard and the midst of uninstalling it, it gave me a message that it wasnt uninstalled correctly. It left a shortcut in the settings section. Ever since then when i try reinstalling it, it gives me a msg that another version is already installed. How do i remove the already installed one short of hard resettin my phone? Any help will be deeply appreciated. Any role for removing it via reg edit?
Thanks in advance.
:?:

It's a great piece of software. It has a few quirks which annoy me a little but hopefully they'll be sorted in the update if it ever comes.
When voice dialing a number e.g. dial 282 456... it insists on putting a zero infront of the number i.e. it will dial 0282 456.... I'm using the UK version BTW. I tried the US version up it didn't recognise my voice as well.
Also, the volume of the voice when annoucing this could be louder. there is no way to increace the volume.
It wold be nice if they expanded the command library to include more functions.

Re: Deep DooDoo
I finally fixed it a couple of soft resets later and trying to install the updated version 1.5 before installing version 1.0 and then uninstalling both and installing 1.0 and 1.5 together it finally worked!! Its a nice piece of software.
Email me if anyone wants detailed info.
XNG
nice_xtremely said:
Hey Guys,
I installed voice command on my Tmo Wizard and the midst of uninstalling it, it gave me a message that it wasnt uninstalled correctly. It left a shortcut in the settings section. Ever since then when i try reinstalling it, it gives me a msg that another version is already installed. How do i remove the already installed one short of hard resettin my phone? Any help will be deeply appreciated. Any role for removing it via reg edit?
Thanks in advance.
:?:
Click to expand...
Click to collapse

Summary: Voicecommand via Bluetooth [STILL UNDONE]

After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht

Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?

Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.

Changed over to Tytn... works perfectly without any hacks

here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.

Microsoft Voice Command 1.6 - ISSUES!

I just got the Microsoft Voice Command 1.6 (refer to as VC from here on) this morning and so far it has been quite disappointing.
I am using it on a Cingular 8525 with a Sony Ericsson HBH-GV435 headset (both are BT 2.0).
Right after the installation I noticed that the talk button on the headset did not trigger the VC so I did a power cycling.
After the power cycling the button will now trigger the VC as if I pushed the VC button on the phone but the problem is that it is not picking up my voice command via the headset but it is still listening from the phone's mic.
Any thoughts on this?

hjkl;' why no delete?

skygear said:
did you try to go under your d\settingd to chsnge the buttons? i think you have to reg edit the files for ear pice mic
Click to expand...
Click to collapse
I didn't know that.....I'm going to try and search for it. Can you maybe post a linky for the info on how to do that?
thx!

Version 1.6 at present time DOES NOT WORK properly with the TyTN. You should go back to V1.5 and wait for a patch...

goestoeleven said:
Version 1.6 at present time DOES NOT WORK properly with the TyTN. You should go back to V1.5 and wait for a patch...
Click to expand...
Click to collapse
I see. Thanks for the info. Hope the patch will be available soon!

What is the probelm with the ver 1.6 and the TyTn? Is it just the TyTN rom or does it not function with the JasJam or the 8525 either?
Dp you guys know this by experience or is it posted somewhere?
PocketPCThoughts list the 8525 as a "compatible device".

The problem will affect all Hermes devices, and it will probably require a patch / a new dll and/or a registry hack to make things work properly. It should work, but it doesn't, and this goes to show you what a poor job of testing was done before product release.
If the single biggest additional feature/function (ie, bluetooth support) doesn't work properly, why was it shipped?

goestoeleven said:
The problem will affect all Hermes devices, and it will probably require a patch / a new dll and/or a registry hack to make things work properly. It should work, but it doesn't, and this goes to show you what a poor job of testing was done before product release.
If the single biggest additional feature/function (ie, bluetooth support) doesn't work properly, why was it shipped?
Click to expand...
Click to collapse
Come on folks... This is MS we are talking about...
If it had been a software package with a little penguin or a devil on it we would be just fine

mrderby said:
Come on folks... This is MS we are talking about...
If it had been a software package with a little penguin or a devil on it we would be just fine
Click to expand...
Click to collapse
Or maybe we should start to look at HTC... Their implementation of the whole bluetooth "feature" is crap too... AD2P anybody? well let's hack the crap out of the register, and than try to be happy with songs that hickup every 30 secs or so... neah great!

First: Hermes generally does not work with BT2.0, I guess, especially my MDAvario2 does not...
I'm using a BT Headset HBH608, which was perfectly working with every phone I've ever tried...
Second: VC1.6 could not be installed on Vario2' and Hermes Devices at all, getting an error message...
VC1.5 (engl.) works, not perfect, but it usually works...

MickKnatterton said:
First: Hermes generally does not work with BT2.0, I guess, especially my MDAvario2 does not...
I'm using a BT Headset HBH608, which was perfectly working with every phone I've ever tried...
Second: VC1.6 could not be installed on Vario2' and Hermes Devices at all, getting an error message...
VC1.5 (engl.) works, not perfect, but it usually works...
Click to expand...
Click to collapse
What do you mean it cant be installed. I have it installed on a TyTn and it works perfectly. I am not using a BT headset, so cant comment on that.

I've got v1.6 on an 8525 and it seems to working fine.
what exactly are the problems others are having with Hermes devices?

@DigitalFX: Hermes does support Bluetooth 2.0, but not Enhanced Data Rate.
@JCrompton: MSVC 1.6 does not route sounds/commands properly through a Bluetooth headset on the Hermes. You may be able to initiate a call with your headset button, but you'll be using the mic/speaker on the Hermes to complete it. Also, sounds/announcements are not working as advertised. HTC and M$ are working on a patch.

VC 1.6 works fine on my MDA with Motorola BT headset.

Mark (NL) said:
Or maybe we should start to look at HTC... Their implementation of the whole bluetooth "feature" is crap too... AD2P anybody? well let's hack the crap out of the register, and than try to be happy with songs that hickup every 30 secs or so... neah great!
Click to expand...
Click to collapse
Seriously, why dind't any OEM use the Widcomm stack instead of the crappy MS one ?!
If only there was a way to hack the Widcomm stack and replace the MS one like they did with the Dell axims..
Adi

goestoeleven said:
@DigitalFX: Hermes does support Bluetooth 2.0, but not Enhanced Data Rate.
@JCrompton: MSVC 1.6 does not route sounds/commands properly through a Bluetooth headset on the Hermes. You may be able to initiate a call with your headset button, but you'll be using the mic/speaker on the Hermes to complete it. Also, sounds/announcements are not working as advertised. HTC and M$ are working on a patch.
Click to expand...
Click to collapse
Has anyone tried this... (look for the cab)
http://forum.xda-developers.com/showthread.php?t=283412&page=5

My 8525 works fine with 1.6 and my SE662 BT headset. Calls can be activated over BT using headset button, and audio routes to my headset throughout my call.

URPREY said:
My 8525 works fine with 1.6 and my SE662 BT headset. Calls can be activated over BT using headset button, and audio routes to my headset throughout my call.
Click to expand...
Click to collapse
Wow! Have you done any registry hacks? I'd love to see what your Voice Command keys look like....
TIA,
Richard

I have an 8525 also, and 1.6 works as MS says it does.
The headset button activates voice command, the Beep occurs on the 8525, and the mike on the 8525 listens for input. If I say, Dial ... or Call... then the call works fine on the BT headset like expected.
I know a patch is in the works to fix this issue, and when they do, 1.6 is superior to 1.5 for voice interpretation.
However, for now, I have 1.5 working perfectly fine. All features work, and all I had to do was enter/change 2 registry keys (only 1 was necessary)

xcsdm said:
I have an 8525 also, and 1.6 works as MS says it does.
The headset button activates voice command, the Beep occurs on the 8525, and the mike on the 8525 listens for input. If I say, Dial ... or Call... then the call works fine on the BT headset like expected.
Click to expand...
Click to collapse
So how loud do you have to shout for the mike on the 8525 to hear you if the phone is in the next room, or in your purse or you're driving? It might be the way MS intended it to work, but I doubt it.
[RANT]
I can't believe that MS wouldn't have caught this problem during beta testing. Speaks volumes (pun intended) for the current state of software development and testing at MS. Anyone know if MS Reader works with WM5 yet? How about full multi-user support for ActiveSync? Win XP has been around for years now with this funtionality. And while I am on my rant, how about SP3 for Win XP? Currently we would have to download and install over 70 (!) critical patches to SP2 just to get our computers to the dynamic state they are at today. Come on MS, enough is enough. Get your s#!* together!!
[/RANT]
John

Voice Command 1.6 - can SMS be read through bluetooth?

I am very sorry in advance if this issue has been raised elsewhere on the site, but after spending quite some time searching for an answer by both the forum search and google search, I am going round in circles and haven't found a solution.
I have a UK Tmobile Vario 2 (Hermes) running its original Rom (I have been too scared to flash it in case I break the phone as I don't really know what I am doing) and I have a Motorola S705 A2DP headset. I love the feature on VC 1.6 which reads out new text messages in full but can't find any way of routing the audio for this feature through my bt headset. The incoming call notification works through the headset but every time an SMS comes through it pauses A2DP, reads it via the phones loudspeaker, then diverts sound back to the headset again?!?
I went on the WIKI and found the Voice Command section. I tried installing the patch/program it suggests and did the tweaks it said to the registry , but it didn't make any difference on this problem.
I just wondered if this is an unfixable problem, or if there is anything I can do to get it working because this feature would be incredibly useful to me (I ride a motorbike and to get texts read through my headset when riding would be excellent).
Thanks in advance for any help guys. Sorry again if I am raising a known issue, if I am, if you could point me in the right direction it would be much appreciated.

have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.

bapski said:
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
Click to expand...
Click to collapse
Thanks Bapski, I have just installed it but unfortunately it hasn't helped thank you anyway though, it was definitely worth a try

Well, I have had a good read through the threads on Voice Command and all the fixes for the headset button but it seems nothing yet solves the problem of routing the SMS notification through the headset which is a shame, it would have been so useful.
Well, hopefully, when I get my nice new Kaiser upgrade (whenever that may be ) .. I will have more luck with the bluetooth audio

Don't buy a phone with a MS BT stack because they will never fix the problem..MS has known about this for so long its just sad..The next phone I get will have a widcomm bt stack.

Yeh, got to say that the bluetooth hasn't been particularly great ... especially when trying to get it working on A2DP.
If only I hadn't stumbled across VC 1.6 I would be none the wiser and wouldn't even know it is possible to have SMS messages read out oh well

it doesnt work dont even bother, I loved it on my wizard, but there is a hardware problem with the heremes or whatever the problem is the last revision of the BT stack doesnt fix it and its never worked. all the patches and fixes only work for awhile then just stop and rquire a cryptic series of hacks to make them half work again. your better off buying a thai slave to read your messages to you.

Bluetooth can place calls but not receive them

I have a problem and have't been able to find any information on it. I have a TMoUS HD2. I had an original Jawbone lying around so I paired it and it works perfectly. I decided to pick up a Jawbone 2. I paired it, but it developed a problem. While outgoing calls are no problem, I cannot answer calls with it, nor can I initiate voice dialing with it. Incoming calls are routed through the handset. I deleted the pairing, and re-paired it to no effect. I also tried the original Jawbone again and it again worked fine. What I don't understand is why it initially worked properly, then developed this problem (with no changes to the phone).
Any ideas?

me too
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.

mcc2905 said:
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.
Click to expand...
Click to collapse
well, it was probably me. I was answering with the handset rather than the earpiece. it didn't matter with the old one, but it does with this one. chalk it up to unfamiliarity with the newer unit. either that or the phone woke up in a better mood today.

sorted
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.

mcc2905 said:
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.
Click to expand...
Click to collapse
Glad my fumbling around with this thing was able to help someone.