Database Users

MS Voice Command and Jabra BT200 Headset

Are they compatible?
I've changed the registry to use the voicecmd.exe file instead of the inbuilt Voice Dialer (which I must admit, I never tested with the Jabra!)
But when I press the Jabra button, I hear a noise in my ear but it doesn't seem to activate anything on the MDA Pro itself...
What am I doing wrong?

Have you got the lid closed? If the screen is closed it doesn't work.

This is mad.
If I press the button on my Jabra, I now hear that the voice path is activated but saying "help" into the Jabra mike doesn't do anything. No "mike" icon on the device (lid is open) and nothing happens.
However, with this voice path open, if I then press the voice command button on the device, everything works through BT. I hear the woman and can speak to her.
However, pressing buttons on each device seems a very silly way of doing it.
I should be able to press JUST the headset button, right?

I use the same hardware without issue
I find some commands dont work so well over bluetooth - but call seems to work OK!
I find the built-in mike is better to practice with first THEN try with the headset
I use DIAL <name> at HOME or on mobile etc and this seems OK
My only ***** is than on both BT and the device the VC voice is too low!!
While I remember to 200 Headset supports two profiles - I find the basic one works better with VC (that way you dont accidentally redial if you double tap the button!)

Found the problem. I reinstalled the VC software with no joy, so checked the reg entry. I was missing the space between "Voice" and "Command", so no wonder it wasn't working...
I would have expected an error of some kind instead, maybe... but at least it is solved now.

Activate Voice Command by Bluetooth headset

I got a Bluetrek G2 Bluetooth headset, and i paired it up and when i presss the button i work but after that it not working anymore no matter how many time i press the button
Any advise?

when using VC from MS via BT the Audiogateway stays open.
You have to close it (by pressing the BT button once) before you can give an new command (by pressing the BT button once again)

New application: Talk Button Detector 0.3

I've written a basic application that detects when you press the talk button on the wired headsets and runs Microsoft Voice Command (if installed) or Voice Speed Dialing (otherwise).
To ease the button press detection when you are listening music, you should slide down the hardware volume control to the minimum.
It can take up to 2 seconds to detect the button press, and doesn't work when the device is sleeping.
If you run the application twice, it shows a window with the energy readings and you will be able to stop it. If the application doesn't work, please, report you energy readings when the button is pressed and released and the environment type (noisy, quiet, ...)
CHANGES IN VERSION 0.2
----------------------
- Prevent the audio subsystem to be suspendend by the power manager.
- Suspend the button state polling when the headset is unplugged.
- Suspend the button state polling when Microsoft Voice Command is listening.

New release 0.3
New release 0.3:
- Prevents the system from suspending
- Powers on the system before launching the voice recognition program
To save energy, I recommend to enable the UserIdle power state (which turns off the screen and several other periphicals), changing in the registry key [\HKLM\System\CurrentControlSet\Control\Power\Timeouts] the value of "BattUserIdle" to "120" (seconds).
I'm waiting feedback.

Thanks, I have been looking for an application like this since I got my Wizard. (not everyone has a bluetooth headset) Seems to work well. Will do more testing over the next few days in different environments.

will dis work on the mini-magician..if not cud u make it possible really wud love that
cheers

http://rinkworks.com/dialect/
V

Vijay wats wit da URL?

It's a Windows Mobile 2003 application because it's developed with Microsoft Embeed Visual C++ 4, and I can't find a way to install the Windows Mobile 2005 SDK (it needs Visual Studio 2005; a bunch of pounds).
But it actually needs Windows Mobile 5 to run properly, since it uses state notifications to know when the headset is plugged/unplugged and if the voice recognizer is running. Last is very important; otherwise the recording is distorted and doesn't recognize anything.
Otherwise, it should be pretty easy to adapt to any hardware. I just need to know where the headset state is stored in the registry. In Wizard, it's in [HKLM\System\State\Hardware], in the value "Headset".

Okay then it shud work for the Mini cause it runs 2003se right? i installed it nothing happens..wat do i do? really love the concept...

It doesn't seem to work with the 8125. I thought the 8125 was really a Wizzard? It detects the button in about 1.5 seconds, but an error window pops up. It doesn't seem to be able to initiate the Voice Command aplication.

Could this be..
what i've been looking for?
I'll let you know.

Wow
WOW!!!:shock: this stuff is really working!!!.. Wired headset is much better than that bluetooth headset coz it's stereo! I have a question tho, is there anyway to automaticly start the exe (program) after softreset or shutdown?
Thanks

Wow
WOW!!!:shock: this stuff is really working!!!.. Wired headset is much better than that bluetooth headset coz it's stereo! I have a question tho, is there anyway to automaticly start the exe (program) after softreset or shutdown?
Thanks

This looks excellent. I will check back once I install voice command!

Tried this on Prophet
Finally someone came up with a solution for this HTC error in construction!
THANK YOU!
I tried this out on my Prophet, in a quiet environment (sitting in bed).
Energy readings when idle are around 250-350 (averaging 310) and exactely 27 when the button is pressed (no matter where the manual volume slider is at that time).
Are those numbers about the same on the Wizard? How can the button-is-now-pressed-threshold be adapted to the Prophet?
Thanks!
P.S.: It obviously doesn't work so far...otherwise I would not have posted these numbers...I press the button and nothing happens.

Talk Button Detector 0.3 is not working on QTek 9100
Hi there,
I have cimply copied the Talk Button Detector on my device and launched it. But when I press the "Talk" button on my headset. It says: "unable to launch talk application".
The "Speed Deal Application" is installed and workng fine when I press the button on the device.
Thank you for your help in advance.

Does not work on T-mobile SDA. But, it detects the button! But give me an error - "Unable to launch speech application"
Please, let us know, what could be done to make it working.
Thanks.

Tried it on my 6700- I only get a -1 reading regardless if I am hitting the bottom or not. I really hope this gets ported to work- people would pay for this functionality.

nice work. but i dun use voice dial myself except with bluetooth headset. i was wondering if you can make use of the wired headset button to launch other application for example say windows media player and play the next song on it when u press it while inside windows media player. that would be useful as i dont like taking out the fone that much to change song when im listening to music.

I would LOVE for this to work on a T-Mobile MDA Vario with a dutch (NL) windows mobile 5
somehow the program works, it even boots out of standby, but it keeps giving me the error "unable to launch talk application"
i do not have windows voice command installed (i tried it, hated it) and use the standard voice control (dutch name: "Gesproken Snelkeuze")
perhaps the translation is the problem here.. could you or anyone else modify the program to enable it to use different application names
i would give you my first unborn child in return

Anyone, Please ? or anyone that could adapt it to make it so you can choose the program yourself ?
the program DOES respond to me pressing the button, it just doesnt load the right program (prob due to language)

Voice Commands - Make It Even More Awesome?

I've recently been having a play with the Voice Tag function on my Wizard. I can call any of my contacts by voice, and I can perform a plethora of functions on my phone by voice (helped by the added hardware button functions that Pocket+ provides). Now i'm wondering if I can do even MORE by voice, i.e. a spoken password, dialing by saying each number, that kind of thing?

Yeah,
Dump the cheezy Cyberon Voice Dial and get Microsoft Voice Command or Cyberon Voice Commander.
Both allow you to access PDA functions such as launch programs, access calander etc.
Additionally they allow "Dial 444 555-1234"
In my opinion MS Voice Command is better.
I've played with Cyberon Voice Commander because it will read e-mail and text messages but I've found it to be useless. Also Cyberon has too much of a delay from activation to ready for voice input for my tastes.
Oh yeah, neither of these requires "Voice Tags", they work by recgonizing your spoken voice!
Cyberon Voice Commander costs about $20,
MS Voice Command is about $40.
Both can be purchased at Handango.com

Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?

Danny-B- said:
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Click to expand...
Click to collapse
Maybe that's why none of these products supports it!!

I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.

jimmyhauser said:
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
Click to expand...
Click to collapse
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.

JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.

JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Same for me. Sometimes the recgonition isn't the same over bluetooth, but I never have to try more than twice. I use my VC for everything.

jimmyhauser said:
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
Click to expand...
Click to collapse
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.

VC Usage Vs. VS VC Memory Usage
I've had VC on and off of my 8125 since I bought it in April.
The main problem I have with MSVC is whether its use (or lack there of) validates the amount of memory it uses.
For someone that makes calls primarily off of his recent call list, I find that the usability benefit does not outweigh the memory usage.
Wish there was a way to disable / enable the functionality, as to release that memory for other applications.

JNGold said:
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
Click to expand...
Click to collapse
Believe me, I am not an expert on this, I am just trying to figure things logically. But I would bet it has to do with the fact that you are probably using a different bluetooth handsfree device than I am. Maybe that was what you were referring to when you said it was a bluetooth issue. Or maybe it is the fact that you have a different model of phone.
What I am saying is that it cant be the bluetooth software on my phone, because the cyberon voice dial works fine over bluetooth, where the MS voice command does not.
And I have voice command on the phone also. All my programs are. I only keep music and videos on the storage card.
And voice command works great when using on the phone itself. I am amazed at how well and how quickly the recognition works. It just doesnt respond well to my Nokia car kit. And maybe that is the problem.
My wife's car has the same bluetooth kit as my car, I am going to try it in her car one of these days to see if I have the same problems there. She has a Nokia 6682, and her bluetooth voice dialling works great.
And also, does VC really use that much memory? If so, I think may take it off the phone. (I use it a little when not in the car) But if it is considerable, then I agree that it is not worth it.

the problem is that without any BT headset i can't get the microsoft voice command to work.
i installed it, dedicate the button. the problem is that when i press it the mic sign appers, i hear the bip and if i say "HELP " it does absolutly nothing.
NOTHING
it just stands there, then another bip comes and the mic sign disappears .
what should i do?

did you turn your mic auto-gain off like the instructions said?

problem solved.
don't know how ...soft reset and bam ! it worked.
the problem is that it hardly recognizes 0 ( zero )
well...i think the old voice dial would do the trick for me...

Keys to success:
1. Load in main memory. (Yes, it's a hog, but to me it's worth it.)
2. Be patient. Sometimes it takes a moment or two to activate.
3. Make sure your volume is not muted. (I admit it, I often walk out of a meeting and get frustrated with why it isn't working... oh, volume is off.)
4. Experiment. Watch the phone while you are playing.
Here are my results with Motorla hs850 .
1. Usually I push once to open the gateway and a second time to activate VC. (Note, I only wear my headset when I need it.)
2. Sometimes the gateway is open for whatever reason and I'll get an immediate bong. So after the first press, I give it a second to see if it will come up.
3. Otherwise, I may get into three presses. One which I think is opening the gateway but is actually opening VC before the bong sounds. A second which I think is activating VC but apparently is closing it. The third press usually then does the trick, but sometimes I'll even have to go to number 4.
So my strategy is:
1. Push button.
2. Wait a slow count for response.
3. Go back to #1 until success is achieved.

Headset connect button voice command activate time

Has anyone any idea on how I can adjust the time required to hold the headset connect button in order to activate the voice command? Currently I need to hold this for far to long in order to activate it.

Maybe there's something in the manual, but I can't even anwer calls with that button. I think it's supposed to be short press to answer calls, and long press for voice command. Still not figured it out.

That's odd, I press the button for a brief moment , and voice-command is activated.....BT headset btw, but it works like a charm...

The handsfree wired headset that came with the Dopod is the one that takes quite a few seconds of holding to respond. I imagine that a bluetooth headset would work differentially as the time is probably controlled by the device itself rather than the HTC 3600.