PDA

View Full Version : Quick app request: Enabling BT Voice Command for all


mobilehavoc
21st March 2006, 04:15 PM
I'm familiar with developing Windows apps (Win32/MFC) but I haven't worked with that stuff for years and I also am not familiar with Windows CE.

I'm looking for someone to help try and put together an app to do the following:

* Call the app BTAudioOff.exe
* Call the app BTAudioOn.exe
* Call the app VoiceCmd.exe

The BTAudio apps are the ones posted by someone on here and VoiceCMD is the executable from Microsoft's VC.

I did some testing and if I run these apps in this order Voice Command over BT works every single time with no issues and with excellent clarity since you are manually opening the BT audio gateway and calling VC.

I was looking to create a batch or script file but couldn't find if Windows CE supports it. By having one .exe or script that runs them in this order, we can have the BT button launch that app (registry change) which in turn would allow MS VC to be used over BT on all BT headsets repeatedly.

I'm doing this for myself and others in the community who are looking for this solution. I'd really appreciate any help people could provide on this.

Thanks.

vijay555
21st March 2006, 04:58 PM
Check out VJVolubilis.

It will be updated to script in the Voice Command registry hack, but if you do the voice command registry hack yourself, just opening the Audio gateway (-AGon) works for most of us.

V

mobilehavoc
21st March 2006, 05:27 PM
Check out VJVolubilis.

It will be updated to script in the Voice Command registry hack, but if you do the voice command registry hack yourself, just opening the Audio gateway (-AGon) works for most of us.

V

Hey Vijay, nice website and tools. Looks nice.

AGON would work but how do I execute VoiceCMD.exe from the same line.

i.e. I want to have a single executable or command that will both turn on the audio gateway AND run Voicecommand.

Can your application accept a parameter for an executable to run???

i.e.
vjvolubilis.exe -agon voicecmd.exe

This would turn on the audio gateway and then execute voicecommand.

Not sure if it's coming across clearly what I want to do.

J Crew
21st March 2006, 05:27 PM
hopfully someone will know how to get this idea rolling.

- Jason

vijay555
21st March 2006, 05:30 PM
I'm pledged to a round of new updates to VJVolubilis that will hopefully address some of the VC stuff; if you read through the VJVolubilis thread you'll see what they're on about.

However, for now, use MortScript. It's excellent for scripting anything.

V

mobilehavoc
21st March 2006, 05:56 PM
AWESOME. I have a solution working using MortScript. Need to test it a little bit and then I'll post it..as easy as pie!! :)

mobilehavoc
21st March 2006, 06:24 PM
Crap...ran across a problem. When I run the MortScript manually through either Resco Explorer/File Manager it opens the BT audio and brings up VoiceCommand every single time.

However when I changed the registery so that instead of pointing to voicecmd.exe it points to my .mscr script it doesn't seem to work and I can't understand why.

I think it probably has to do with the Cyberon software opening closing the BT channel before launching the exe.

Hmmmmm....working on it still...any tips would be appreciated.

mobilehavoc
21st March 2006, 07:20 PM
Well I give up for now. It seems hitting the BT headset button launches a mini Cyberon invisible app that sets up the BT audio gateway and then launches what's referred to in the registry

For whatever reason no matter what I tried, I couldn't get it to run a .mscr script either by directly pointing to the script or pointing to MortScript.exe and passing the script as a command line parameter.

All in all, it works 100% when you run the .mscr manually but getting it to execute through the BT headset button thing is much more difficult than I had anticipated.

Hopefully somoene can help resolve this on here and/or this will be resolved with MS Voice Command 2.0 if it ever comes out.

Vladimyr
21st March 2006, 07:35 PM
However when I changed the registery so that instead of pointing to voicecmd.exe it points to my .mscr script it doesn't seem to work and I can't understand why.

The Registry might not point to something except an ".exe"...
You may use the "autorun" function (http://www.sto-helit.de/modules/edito/content.php?id=39) of MortScript
(copy "Autorun.exe" from the "Windows" folder to the folder where your script is located and rename it the same as the script, e.c. "myscript.mscr" and "myscript.exe")

mobilehavoc
21st March 2006, 08:01 PM
Thanks Vlad! It worked...need to do some more testing with a BT headset that was having trouble with it tonight.

Thanks though.

boogaboo
22nd March 2006, 12:04 AM
Can't wait to see if you can fix this mobilehavoc!

See you on the forums!

This will make lives easier, guranteed!

Cheers! If you were closer I'd buy you a beer, heck a case!

boogaboo
22nd March 2006, 12:05 AM
Can't wait to see if you can fix this mobilehavoc!

See you on the forums!

This will make lives easier, guranteed!

Cheers! If you were closer I'd buy you a beer, heck a case!

edsub
22nd March 2006, 12:11 AM
this sounds promising.
I do not have any issues with triggering VC via my BT headset
I DO have issues with triggering VC via my Nokia BT carkit (after a while VC just does not react anymore)

mobilehavoc
22nd March 2006, 12:34 AM
Well after much testing and whatnot, it is not currently possible to do...it's a problem with voice command as everyone knows...specifically that since it wasn't designed for BT, it does NOT close the audio gateway so the next time you press the button on your BT headset, it does not respond.

This works with certain headsets like the HS850 because for whatever reason, a subsequent press of the BT headset button turns the audio gateway off and then the next one turns it on. This is why certain headsets work but require 2 presses to work.

The ONLY way to get this to work currently is to have an app (MortScript almost did it) that can wait until VoiceCmd has executed and completed, then close the audio gateway. Problem with that is VoiceCmd may lead to a phone call or god knows what else so it's tricky.

I'm sure there's a way to do it...in the end, again...ALL THAT IS NEEDED is for some way to close the BT audio gateway once VoiceCmd finishes...then all will be right with the world. I give up because I don't have the expertise or time and my HS850 works fine with it...

Hopefully someone else can give it a shot sometime.