Database Develop

Voice Commands Over Bluetooth Works on TuMa v1.3 - WM5 ROM

I have posted This thread to assist anyone like me, who is not a programming whiz. Got to Install this mainly through trial and error and I am not an expert in this. So If anyone can make my steps easier please do!
This is a Variation Installation For a thread a while back in October 2005 Author Ncruz and effjay. Ncruz Posted a wm5 cab. This cab does not install directly due to permissions. However I have extracted the files using windows cab manager.
First are the files are required in windows. If it asks about permissions copy to PDA root folder then copy with Resco File Explorer and overwrite. Next are the registry files. You can import them with a registry program such as tre or regedit.
If you want Microsoft Voice commands to be the default program overwrite SSDialer.exe in windows folder with Voicecmd.exe from Program files/Voice command/ otherwise Cyberon Voice is initiated when you press headset.
I will post the cab in its entirity although it will not install, incase someone knows an easier method to get voice commands working Please contibute to this thread. However this method worked for me. Below in the zip are the files Extracted with Win Cab manager in zip format so you can copy zip to your pda then extract them to the correct folders, along with the registry files you need to import to registry.
N.B..sound of Voice commands is through PDA and not headset. Pressing headset connect button opens Cyberon or active voice command depending on what you have

Can not seem to be able to import the reg files....

OKay, got the files to import and the files copied - no go for me. Darn-it.

Installation
did you do a soft reset with the software built with the rom and repair the bluetooth headset

I might have reset without using the software reset....
However, got it working with this cab file that I found on my storage card. I even got MS Voice Command to work when I hit my BT Headset button.
Heck, it did not even change the record button to SSDialer! I would have thought it would but it did not. So, I am happy!

glad its working for you

now how can i do?
download odie3 's cab file and install? that's right?
Then, when device auto turn off, bt still go off as before?

I can't download files..... Where can I get them?

Re: now how can i do?
kriengkrai said:
download odie3 's cab file and install? that's right?
Then, when device auto turn off, bt still go off as before?
Click to expand...
Click to collapse
The only way I know how to keep BT on is by plugging in my Device to a power source and doing a soft-reset. As long as I do not turn it off with the power button or have it set to auto-power off while plug in, BT will stay on. I do this everytime I get into my car - since it takes me a hour [sometimes more] to get home, so my BT Headset always works.
Hopefully I explained that correctly for you to understand....

Odie
Your query confirmed. The Wlan manager icon from the today screen goes as a side effect of installing the cab. Wifi still works but the Icon in today is not there. Not a big deal for me, as I have skinned my Pda with Wisbar, which has a wifi icon.

Re: Odie
MOHDWADEA said:
Your query confirmed. The Wlan manager icon from the today screen goes as a side effect of installing the cab. Wifi still works but the Icon in today is not there. Not a big deal for me, as I have skinned my Pda with Wisbar, which has a wifi icon.
Click to expand...
Click to collapse
Yes it happened to me as well, but i prefer BT Voice Command Activation than WLAN icon
Thanks for the info

BT activation doesn't work for me...
For some reason the activation through BT headset doesn not work for me.
I'm using WM5 TuMa 1.3 ROM.
The BA_WM5_Voice_Dialer_2.cab doesn't install on my device (permission violation), so I copied the files manually to the Windows folder.
The reg files also don't import to my registry when double-clicking, so I made the changes manually.
It still doesn't work.
Now, when I hit the button of my BT headset (Moto HS-810), the standard dialer is activated (instead of the voice command app) and I hear hissing sounds in the headset.
I tried it both with Cyberon and MS apps. Both don't work.
Did anyone encounter this problem? Anyone solved it?
Thanks.

anyone knpow how to do this with voice command on 2003se?

Just upgraded to TuMa 1.3 and have found a MUCH more simple way of doing it.
1) Install Microsoft Voice Command
2) Download Total Commander (http://www.ghisler.com/ce.htm)
3) Using Total Commander change the read only tickbox for \windows\sddialer.exe so that there is no tick (1 press just greys it out, i needed to press twice) <- browse to \windows in TC and right cick (hold down) on sddialer.exe, and click properties.
4) (you don't need TC for this) Copy %install dir%\voicecmd.exe (where %install dir% is the directory you installed voice command to) to a temporary location and rename it to sddialer.exe.
5) (using TC) 'Right click' on your new sddialer.exe (previoult voicecmd.exe) and select 'cut to clipboard' then navigate to \windows\ and 'right click' and select 'paste from clipboard', when propted overwrite the origional file.
6) press the button on your headset and test it!
the only thing we need now is for some clever person to work out how to route the voicecmd audio through to the headset instead of the load speaker (to my knowledge it uses the microphone on the headset allready (at least it works when i speak quietly from the next room )

it works like a charm
cheers

Do what Midlet says?
If I do what Midlet says- will I still need the 2 files that mohdwadea has posted? Is Midlet's process a complete stand-alone process... or is if preceded by more steps?

Re: Do what Midlet says?
sgrbhtngr said:
If I do what Midlet says- will I still need the 2 files that mohdwadea has posted? Is Midlet's process a complete stand-alone process... or is if preceded by more steps?
Click to expand...
Click to collapse
Have not investigated midlets way of installing as Mine is working. However i suggest that if you check your registry and see if the reg keys i posted within the zip are there. If his way works fine, if it does not i suggest you import the keys into registry and see if that helps. I also strongly suggest you make a note of the keys and where they are imported too, as if it does not work you can remove them.

It worked
Mohdwadea,
Your method worked! This time I performed a soft-reset after the installation and also re-connected the headset. I did not have to go he registry-entry route because the cab-file installed on my device.
This will help me a lot on the road in business. God bless you.

Just glad its working for you!

voice not sending
MOHDWADEA,
I am using this fix a lot on the road. It works very well... expect for in one situation! I can initiate voice dialing by the record button on my device and it accepts voice dialing commands through the bluetooth headset and teh call goes fine.
However, if I initiate the voice dialing using the button on my blueooth headset (Cardo Scala 500), it initiates the voice dial app just fine, accepts commands and conencts the call.... but the other party cannot get my outgoing voice through my bluetooth headset, rather it gets the voice from the mic on my phone. Also, the incoming sound can be heard in my bletooth headset but ALSO on the phone.
Any suggestions?
Thanks!
Sagar
I-mate PDA 2K
WM5 TuMav1.3

BT Audio Streaming + Voice Command

Just sorted BT voice dialing on my TRINITY witha Jabra BT250 all working fine
using the infor here:
http://forum.xda-developers.com/showthread.php?t=281977
I've also mastered using BTAudioOn.exe in the registry in place of the voice dialer to give me Audio Streaming
Only problem is, as the article in the forun suggest it disables the voice commands!! I can live with this as I only want to stean the TOMTOM voice when using the satnav while walking or on my bike.
What I had in mind was a a couple of icons, one to make the registry changes for the BT Audio streaming and the other icon to toggle back (ie change the registry back to voice comand via the BT headset). As far as I can see (once BTaudioOn.exe is copied to my Trinity) the only difference between turning my Jabra BT250v into an audio streaming headset and a phone headset are the two registry changes; and then change them back to give me a Phone headset again.
Can anyone tell me if this is possible to use a .REG file?
Can it be written on a PC and then copied to the Trinity so that it runs?
Will reg files run the same on a PDA and they do on a PC?
Thanks in advance

Try to use SKSchema software, it can put any values in registry depends of any window or process runing on the device. It watch & if you made a rule to put in registry key voicecommand with launcheAppEnable zero as window of TomTom appears u can get a continiusly sound in handsfree if also it put long value in Duration option.

Where do I fond the software please

Also... could you please explain a little better a I don't understand what you have written...sorry!

http://pocketgear.com/software_detail.asp?id=20385
& read help in windows directory after install

Microsoft Voice Command

Hi, has anyone managed to install this, and get it to work? It doesn't install properly on my Diamond and I can only see settings for it, nothing under programmes.
I get an error along the lines of "programme not installed correctly" or something like that ... can't stand Voice Commander pre-installed.
Thanks, M.

same happend to me, but just ignore the mesage. it is installed anyway. afaik the icon for voice command always was under settings it never had one in programs.
i just installed it and it works fine, allthough it seems that the recognition is not as good as it was on my tytn. will see if it improves over time...
cheers
chaos42

Interesting. I set the button to be key 1 (same as where voice commander normally resides) and yet when I press it I just get a single tone beep response, not the normal multi-tone initiating voice command one.
Haven't tried it with my bluetooth headset yet as the charge has run out on it!
Also, has anyone figured out how to remove the installed Voice Commander?
Thanks, M.

works for me!
vc1.6 i installed it 5 times and did not work after i assigned my only f))king button it just one beep not like used to 3 beeps so i create a icon in programs dir and then link button to that it works perfect. perfect recognition if anything better and faster than any of my previos pda's

MS VC 1.7 freezes Daimond to hard reset
I Posted in another thread, but it should indeed belong here :
Hope to see a working solution for MSVC soon , an official fix from MS would even do fine.
http://forum.xda-developers.com/showpost.php?p=2323586&postcount=109
I flashed to Eslite 1.0, so i might give it another try now

I have MSVC 1.6 OK on my Diamond. It is true, that the installation tells me error when I install, but now it is OK. You can configure MSVC in Settings/Voice Command. Then:
1) you have to create link to voicecmd.exe (for example voicebtn.lnk), copy this link into \windows\star menu\programs
2) in settings/button assignment, you have to reassign long press of phone button to this new link voicebtn.lnk and now is MSVC functional

vphk said:
I have MSVC 1.6 OK on my Diamond. It is true, that the installation tells me error when I install, but now it is OK. You can configure MSVC in Settings/Voice Command. Then:
1) you have to create link to voicecmd.exe (for example voicebtn.lnk), copy this link into \windows\star menu\programs
2) in settings/button assignment, you have to reassign long press of phone button to this new link voicebtn.lnk and now is MSVC functional
Click to expand...
Click to collapse
i even did not get so far.
I tried to install 1.6 build 17913 on TLR Rom, though it gave this "unrecoverable error" again.
Rebooting resulted in a brick when tapping "settings" which forced a hard reset again damned
Will stick a while to Cyberon Voice command, though I liked MSVC better.

I have used MSVC_US_PPC 1.6.19209.bengalih.cab from pda4x.
No problem after setting Button1 to MSVC.

@ vphk
How did you make that link? Sorry neub

ceevee369 said:
i even did not get so far.
I tried to install 1.6 build 17913 on TLR Rom, though it gave this "unrecoverable error" again.
Rebooting resulted in a brick when tapping "settings" which forced a hard reset again damned
Will stick a while to Cyberon Voice command, though I liked MSVC better.
Click to expand...
Click to collapse
I suppose I am not the only one with this exact problem......I hope someone can solve this...

How to open websites in opera using voice command
I'm running a german version of MSVC v1.60.46220 and it's running very smooth. I read the tutorials and configured it to meet my needs. Now I want to open websites with opera using a simple command like "Start xda-developers". To do this I created a link (.url) in a subfolder of programs. This works with Pocket IE. To open the site in opera I changed the file association for the extension .url to \windows\OperaL.exe "%1%. Now opera starts but the home screen appears instead of the site that is linked. help appreciated

I cant get the talking ringtone to work on my diamond.
I adjusted the settings so it should work without an headset.
Do you have to adjust the ringtone somewhere?

Officer21 said:
@ vphk
How did you make that link? Sorry neub
Click to expand...
Click to collapse
to create the link mentionned by rxdoctor in post #4 :
1 - from your PC, go to \program files\voice comand on your pda (via Active Sync connection), create a shortcut here (like you would do for a file on your PC)
2- move this shortcut to \Windows\start menu\Programs on the pda
Then the name of this shortcut appears in the drop down list of programs you can assign to the button.
Now I have MS voice command working fine

The Definitive Guide for Microsoft Voice Command (MSVC) on the Kaiser/Tilt 2.0

This is a repost as requested (original thread was closed because the original author apparently left the site because he felt he was being treated unfairly)... I TAKE NO CREDIT
here is the discussion confirming that
and here
and here is the archive of the original thread
The Definitive Guide to Microsoft Voice Command (MSVC) for the Kaiser/Tilt - 2.0
*** UPDATED 9/16/2008 ***​
PLEASE READ THIS FIRST POST (AND ANY REFERENCED SECTIONS) BEFORE ASKING ANY QUESTIONS!​
Hello and welcome to the Definitive Guide for Microsoft Voice Command (MSVC) on the Kaiser/Tilt. I hope that this resource is effective in getting MSVC working to a satisfactory level on your device. As you go through this guide, please remember the following:
I am not a programmer or Windows Mobile engineer. I am just a tech-savvy user with an IT background. All the information I have discovered on this product was by reading what was available from all over the web and doing many tests on my own.
I am not affiliated with Microsoft in any way. I have no special insight as to why Microsoft doesn’t offer better support on this product.
I maintain this guide on my own time. Therefore I can only update it and answer questions when I have the time, which will most likely be less and less as time goes on…
THIS GUIDE IS FOR THE HTC KAISER and AT&T TILT! While it is quite possible much of the information in this guide will help you on other devices, I wrote this with the Kaiser/Tilt in mind. This is because I own a Tilt and so that is what I can perform tests on. If you own a device other than the Kaiser/Tilt then by all means read the guide and absorb its information. More likely than not if the answer isn’t in the guide I won’t be able to help with it. Look to a device specific forum for help.
How to post your issues with MSVC:​
BEFORE POSTING:
READ THE ENTIRE GUIDE - There is a lot of information here and 85%+ of the time you will find what you need herein.
FOLLOW THE TROUBLESHOOTING SECTION – Make sure you read and re-read the troubleshooting section and try ALL remedies before posting.
If after the above you are still having issues with MSVC on your device, please post your information in the following format to allow myself and other members to easily assist. Please keep in mind all the above information before posting:
ROM: Version of ROM you are using (be specific!)
MSVC Version: Version of MSVC. (You can find this under Start > Settings > Voice Command)
Bluetooth: Your bluetooth headset model
Description: Provide a detailed description of what problem you are having, how to recreate it, as well as what you have attempted to do to remedy it.​On to the Guide...!

Documenting Microsoft Voice Command (MSVC) functionality has proved to be a lengthy (and tricky!) proposition. There are many scattered posts out there as to how to install and configure it. I hope to bring as much information as I can to this central location. I will also offer some custom tools to overcome some of the current limitations of MSVC. For information on what MSVC is, or basic information on how to use it, please refer to the official Microsoft site for MSVC here
There are several steps to get MSVC working; generally they fall into the following categories:
Obtaining MSVC (or locating an installed copy)
Installing/Upgrading MSVC
Testing Basic MSVC functionality
Mapping a button to MSVC
Configuring the BT headset
Configuring Incoming Call Announcements
Obtaining MSVC:
Use a ROM with MSVC already installed – This is probably the best way to do it. In many cases if you have ROM with MSVC already installed you hopefully won’t need most of this guide. Official ROMS with MSVC should work out of the box. In addition, most cooks who include MSVC spend some time ensuring that it works. You may still want to refer to the guide to tweak or optimize your MSVC installation.
Purchase a copy of MSVC – If you don’t have a ROM with MSVC installed, you can purchase a copy from various online vendors. Be aware that the retail versions of MSVC currently for sale may not function fully on newer Windows Mobile devices.
Download a copy of MSVC – You can download a copy of MSVC from this guide or another location. The legality of downloading copies of MSVC has been much disputed and more information on that below.
MSVC Versions
RETAIL VERSIONS:
1.5 – There are retails version of MSVC 1.5. These are very outdated, and will not work on Windows Mobile 6.0+ devices. I will not discuss them here
1.6.4622 - Retail localized versions (available in US, UK, and French versions). Should work on WM 6.0 but WITHOUT incoming announcements.
1.6.17913 - Updated retail US version. Should work with some WM 6.0 and 6.1 builds.
EMBEDDED VERSIONS:
1.6.19209 - Embedded WM 6.0 US version, not available for retail. Should work with most WM 6.0 and 6.1 builds. RECOMMENDED FOR 6.0 devices.
1.6.19213 – Updated WM 6.1 US version. Should work with newest 6.1 builds. RECOMMENDED FOR 6.1 devices.
1.6.19214 – Latest WM 6.1 US version. Should work with newest 6.1 builds. RECOMMENDED FOR 6.1 devices.
You will note that the Microsoft has not release a retail version since 1.6.17913. Unfortunately most 6.0 and 6.1 device will not work without at least version 1.6.19209 or newer. This has left the user community in a difficult position: User’s cannot buy a working version, but the legality of obtaining an updated version has been put into question.
With the latest HTC official ROM release for the Kaiser, MSVC is included. Because of this many accept that MSVC is now in the public domain for usage, since anyone can download this ROM. In reality, you should probably be an AT&T customer or own a retail version of MSVC in order to use the newer non-retail versions.
Below are downloadable copies of non-retail MSVC versions below. These CABs were created by packaging the appropriate embedded files and registry entries from the various test and official ROMs that HTC/AT&T has released and that are available for download elsewhere on this forum.
NOTE: I have not been able to find any discernable differences between the functionality of .19209, .19213, and .19214. In fact, I continue to use .19209 because of this. This guide was written with 1.6.19209 in mind.
Download MSVC 1.6.19209​
Download MSVC 1.6.19213​
Download MSVC 1.6.19214​
Notes on Older Versions, Methods, and Hacks
This information is provided for informational purposes only. It is not recommended that you use these older methods, but rather run one of the newer MSVC versions.
Version 1.60.4622 (Localized versions) has been tested to work but WITHOUT incoming announcements (either to phone or BT). To get incoming announcements to work you can replace the voicecmd.exe with the version from 1.6.17913 or 1.6.19209.
The file voicecommandreplacementfiles.zip that is circulating is simply a set of 4 files from version 1.6.17913. Copying these over your current installation in effect upgrades it to that version. There should be no need to apply those files if you are running 1.6.17913 or above.
The older methods of updating the audio gateway and using xcsdm's BTVoiceCommand (the 0.9f hack) do not seem to be valid for the Kaiser. Covering these methods is out of scope of this guide, but you can find more information by searching xda-developers and looking at info for other devices like the Hermes. Check out the section on MSVC here
How to Determine MSVC Version
To determine which version of MSVC is running on a device, do the following:
Go to Start > Settings > Personal Tab > Voice Command
This is the Voice Command settings applet. Open the applet to see the version number you are running.
Installing/Upgrading MSVC
Installing MSVC is as simple as running the CAB to install.
NOTE: Always install MSVC to your device's internal system memory, not to an external storage card.
In general MSVC will be installed in one of two locations:
\Windows – This is common on devices using ROMS with MSVC already built-in.
\Program Files\Voice Command – This is common on devices where MSVC has been installed separately from a .CAB file. Most retail versions will install in this method, as well as the embedded CABs offered for download from this guide. This method is preferred, as it isolates the MSVC files and allows for easier upgrading.
Once MSVC is installed, you should reboot your device and then follow the instructions above for determining MSVC version to see if it installed.
To upgrade MSVC you should first uninstall the old version and reboot before attempting to install the newer version.
Unfortunately, if you have a ROM with MSVC built-in it may impossible to upgrade. This is because ROMs with MSVC built-in have files which cannot be overwritten, as they are burned into the ROM. All of MSVC can be placed in alternate locations except for the Voice Command applet in Settings. This must always be placed in the \Windows directory. As most ROMs place their MSVC files in the \Windows directory, you can attempt to install one of the non-retail versions offered in this guide. This would mean that you would be using the old applet file, and MSVC may function improperly, or not at all. For more information, see the additional information section.

Testing Basic MSVC Functionality
The purpose of this guide is not to walk step-by-step on how to use MSVC, suffice it to say that once you have installed the application, or located your installation, you should be able to use it to a basic degree. To test basic functionality, do the following:
Locate the voicecmd.exe file. This will be in the MSVC installation directory or \Windows. Usually a shortcut is also created in the Startup folder.
Click to run the file (sometimes you may need to click it 2 or three times to initialize).
When launched, you should hear a beep and a microphone icon appear at the top of the screen.
You should now be able to speak into your phone (not BT at this point) and get MSVC to respond. You can try saying “help” and MSVC should respond with some options. You can also try “dial 555-1212” (or some other number) to make sure it begins to dial.
To my knowledge, there are no issues with getting MSVC to work through the local speakers (assuming you are using a version appropriate to your Windows Mobile version). If you can click the “voicecmd” executable in the proper directory, hear the beep, and get the microphone icon to appear then you should be able to speak to MSVC to get it to dial, etc.
Mapping a button to MSVC
We obviously don’t want to have to manually run the voicecmd.exe every time we want to issue a voice command. The easy solution is to map a button.
In most cases you only need to map a button to MVC if you want to launch if from your phone. By this I mean if you only plan on initiating MSVC via your BT headset then you do not necessarily need to do this. However, for purposes of testing, I recommend you map a button and then you can remove the mapping once your BT works.
*In some instances it appears that the Bluetooth headset device may not trigger MSVC if a button is not mapped. If you are having problems initiating MSVC from your headset, I recommend you try and map a button.
Mapping a button to MSVC is as simple as going into Start > Settings > Buttons and changing any button to launch Voice Command.
The challenge is that most peoplewant to keep their buttons how they are and instead remap the PTT button (the one on the top-left side of the phone) to launch MSVC.
If you would like to remap your PTT button to MSVC, do the following:
Download and install on your phone one of the popular registry editors (PHM RegEdit, Resco, etc…).
Goto HKLM\Software\ Microsoft\Shell\Keys
- Add a new key named "40C6"
- Add a new string value under the key called "Name" with a value of "Button 6" (or anything else you may want to call it, like “PTT”)
You can test that this is created properly by going back to Start > Settings > Buttons and you should now see the button listed. Choose to change this button to “Voice Command.”
You have now mapped the button to MSVC! There are two issues however: The first is that this won’t work until after a soft reset. The second is that a soft reset will cause the PTT service to overwrite the change you just did! Therefore, our only option is to remove the PTT service.
To remove the PTT service do the following:
Goto HKLM\Services\PTT
Delete the entire “PTT” Key. (NOTE: You may wish to backup/export this key first with your registry editor.)
Soft-reset your device. You should now be able to launch MSVC from the PTT button!
Remember, if you have another application handling your device’s buttons (like AE Button Plus), you may not need to do any of this. In addition, if you prefer to use a button other than PTT, simply map the button without the above tasks.
Configuring the BT Headset
This is probably one of the more problematic issues that people encounter. Various results have been reported with trying to get your BT headset to launch MSVC. Sometimes it does nothing, other times it redials the last number or, if you’re lucky, it will actually just work!
The key configuration point appears to be a registry key named BTAGExtModule. I believe this stands for: BlueTooth Audio Gateway Extension Module. As its name suggests it is an extension to Bluetooth which controls what application to launch and thus establish an audio gateway between your BT headset and your phone.
NOTE: In some cases this is the critical and only step you need to get MSVC working. On some devices the BTAGExtModule is set to OEMAGW.DLL. Setting it to VCBTHAG.DLL and resetting is all that is need to get MSVC working!
There are several options you can enter here and you may need to do some experimentation. The important thing is that whatever file you enter for the value of the BTAGExtModule must actually exist on your phone! Be sure to use File Explorer and browse to whatever directory you are specifying any make sure the file exits (be sure to turn on “Show All Files in Explorer options!”).
In all my tests, I am using the 1.6.19209 build of MSVC and therefore the proper gateway to use is “vcbthag.dll” (Voice Command Blue Tooth Audio Gateway). This is true of all later versions as well.
For informational purposes, here are all the audio gateways that are known to exist:
VCBTHAG.DLL – This is the audio gateway included in all of the versions of MSVC I have tested. It always appears to work in all my tests and I suggest you use this one.
OEMAGW.DLL – This is the OEM Audio Gateway. I assume it can be customized by the OEM, or rather the OEM renames whatever gateway they want to use to this filename. It may not exist on your phone, or may not do anything at all.
BTAGTEXT.DLL – This is another audio gateway. It may be generic, but I think it may have also been the default in earlier versions of MSVC. I don’t think you should ever need to use this one, but I mention it because I believe it was used in previous solutions.
To check your audio gateway:
Goto HKLM\Software\Microsoft\Bluetooth\AudioGateway
Ensure BTAGExtModule is set to “\Windows\vcbthag.dll” or “\Program Files\Voice Command\vcbthag.dll” (or another location depending on where your MSVC files are located).
SOFT RESET the phone
Wait about 60 seconds after restart to ensure all services are started
You should now be able to use your BT headset to initiate the audio gateway and initialize Voice Command.
Be sure you pair your BT headset with a “hands-free” profile!
Click your BT button and you should hear the MSVC “beep” and see the microphone icon. You should now be able to speak MSVC commands to initialize a call, etc.
TIP: You may want to walk about 10 feet away from your phone to test this. This will make sure that your voice commands are being send through your headset and aren’t just being picked up by your phone microphone. I have not seen this problem recently, although some people have claimed this issue previously.

Configuring Incoming Call Announcments
Incoming call announcements are another major hurdle with MSVC. Even on an otherwise functioning Voice Command, the incoming announcements won’t always function properly. One of three behaviors occurs:
No incoming announcements at all
Incoming announcements come only from the phone, and not from the BT headset.
Incoming announcements work properly…which is of course what we want!
I believe the issues with incoming announcements not working are due to one of two reasons:
An older version of MSVC (pre 1.6.17913) - In actuality, the file voicecmd.exe is solely responsible for incoming announcements. Whether or not they work for you is dependent on your version of that file. See the beginning of this article for information about proper MSVC versions and how to obtain them.
Incorrect MSVC settings – In some cases, MSVC simply isn’t set up properly. This is what I would like to detail here.
To ensure your MSVC is properly set up for incoming announcements, do the following:
Go to Start > Settings > Personal Tab > Voice Command
Ensure “Enabled” is checked (you probably wouldn’t have gotten this far if it wasn’t!).
Scroll down to “Phone” and make sure it is checked.
With “Phone” highlighted click “Options”
Check “Announce Incoming Calls”
Click OK to go back to the main Voice Command screen
Click “Notifications” and set your notification options.
Now place a call to your phone and you should have the incoming call announced. If the number is in your phone book it should speak the name, otherwise it will speak the phone number.
Where the announcement comes from (device speaker BT headset will depend on your Notification options.
Please read the following sections for more information on this!
Important Notes regarding Incoming Announcements
Location of incoming call announcements are a function of the “Notifications” settings in the MSVC applet. There are 3 setting in this dialog:
“Announce notifications using Bluetooth hands free only” - Use this if you want incoming announcement ONLY to come in over your BT headset and not your phone.
“Announce notifications using Bluetooth hands free if available” – Use this if you want incoming announcements to come in over both BT when BT device is available (and BT is on) or on your phone’s speakers (when not using BT).
“Announce notifications through device speaker or wired headset only.” – Use this if you want to have incoming announcements ONLY come through your speakerphone under any circumstances.
ISSUE #1:
Incoming announcements (and ring tone) don't come through BOTH the BT headset AND the speakerphone simultaneously.
The problem here lies in the fact that if you have option #1 or #2 set AND BT is on, announcements/rings will only go to your BT headset. This may be inconvenient if your headset is not in your ear. Here is a summary of what will happen when using option #1 or #2:
If MSVC is DISABLED and BT is DISABLED then an incoming call will ring normally on your phone.
If MSVC is DISABLED and BT is ENABLED then an incoming call will ring normally on the phone AND your BT headset will ring with its built-in ring tone.
If MSVC is ENABLED and BT is DISABLED then an incoming call will ring ONLY on the phone. If incoming announcements are on, these will also play only through the phone.
If MSVC is ENABLED and BT is ENABLED and INCOMING NOTIFICATIONS are ON then an incoming call will announce/ring on ONLY the BT headset. (NOTE: you will actually hear the phone’s ring tone coming through your BT headset along with the incoming notification).
If MSVC is ENABLED and BT is ENABLED and INCOMING NOTIFICATIONS are OFF then an incoming call will ring on both the phone (normal ring) and the BT headset (built-in ring). No announcements will be heard.
SOLUTIONS:
If you aren’t happy with any of the scenarios presented above by choosing notification options #1 and #2 then you have the option to use notification option #3, "Announce notifications through device speaker or wired headset only." Of course this will allow you to hear notifications over the device speaker, but not over BT.
One other option which appears to work, but is not fully tested is to set your phone to also vibrate for calls. It seems from my limited testing that the phone will vibrate even if incoming announcements are directed to the BT headset.
Again, these are not the best of all possible worlds, but there are some other options. For more information, see the next post.
ISSUE #2:
Calls from PRIVATE or UNKNOWN numbers do not seem to always (most of the time) properly announce. In fact, they will cut the ring off when using incoming announcements. As of current, I am not aware of any fix for this. This happens with incoming announcements over the phone AND the BT headset.
This issue seem to be coded into the Voice Command files themselves. When MSVC is enabled it installs some sort of proxy between the phone’s hardware to intercept incoming calls. It does this whether or not you turn on incoming announcements. This IS NOT related to the audio issues. In fact, if you put in a false value for the BTAGExtModule value then you will not be able to initiate MSVC from your BT however all the ringing issues still exist!
SOLUTIONS:
None

Additional Information Regarding MSVC
List of File and Registry Entries for Voice Command
Attached is a .ZIP with 4 files. 2 .REG files (one for 1.6.17913 and one for 1.6.19209) and 2 .CSV files (one for 1.6.17913 and one for 1.6.19209) listing files.
The information for 1.6.17913 is gathered from an official .CAB file and should be everything you would expect if you installed a retail copy of MSVC.
Since there exists no official version of 1.6.19209 I pulled the information from a recent decompiled AT&T 6.1 ROM. Since this is a built-in version of Voice Command, all files would be installed in the \Windows directory (apart from shortcuts in StartUp).
The .CAB for 1.6.19209 that I offer above is actually a conglomeration of these two. It uses all the updated 1.6.19209 files while maintaining a proper directory structure (In this case using Program Files\MS Voice Command instead of dumping everything in \Windows). It also maintains those files that were not present in the ROM's 1.6.19209 files, namely those dealing with WMP skins. I attempted to make it as close as to what an "official" version might look like from Microsoft.
Built-in versions and manual installs
MSVC, like all applications installs files and registry entries onto your device. The problem with using a Stock or Cooked ROM with MSVC pre-installed is that it may not have been installed correctly (with all the correct files or registry entries). Additionally, because pre-installed applications are often embedded in the ROM and you cannot always move or update files with working versions (because ROM files are read-only). Because of this, it may be easiest to use a ROM that doesn’t have MSVC pre-installed. However by modifying files, locations, and registry entries you may be able to get MSVC working.
Because of these limitationsit is necessary to understand a few things about how MSVC files work.
As I have already covered, MSVC files are generally installed in one of two locations:
\Windows
\Program Files\Voice Command
Generally, if you are in the built-in boat, your files will be installed in \Windows
How does MSVC know where to look for your files?
Well, the first thing to know is where and how is MSVC usually initiated:
The answer is one of three ways:
From your \Windows\StartUp folder when WM first boots
When manually launched from the shortcut or a button
When called from the BT audio gateway to receive a voice command
For #1 and #2 you will generally want to ensure that the version of MSVC being launched is the one you want. There will generally be a shortcut to your copy of MSVC (specifically the voicecmd.exe file) that launches the application in the \Windows\StartUp folder. Therefore, if you want to install a different version of this exe (and if you can’t overwrite it and need to install it to a different location) make a NEW shortcut in \Windows\StartUp to launch your new copy.
Once voicecmd.exe is launched it will want to look for the rest of its files. It knows where to look by accessing the registry at this location:
HKLM\Software\Microsoft\Voice Command
The two keys to pay close attention to are:
AppInstallPath and ResourcePath
The value of AppInstallPath should be the full path to the copy of voicecmd.exe that you want to use, for example:
"\Program Files\Voice Command\VoiceCmd.exe"
Or
“\Windows\VoiceCmd.exe”
The value of ResourcePath should be the full path to the directory that the supporting files are stored in, for example:
“\Program Files\Voice Command”
Or
“\Windows”
Changing these two keys, along with the shortcuts should effectively allow you to bypass a built-in version of VC in lieu of file versions that you want to use. If the keys don’t exist in the root of HKLM\Software\Microsoft\Voice Command you can create them as string values.
You will also want to update your BT Audio Gateway so that the proper gateway is launched from your BT headset. Find it at the following location:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
Set BTAGExtModule to the full path to the copy of the audio gateway dll being used, for example:
“\Windows\vcbthag.dll”
Or
“\Program Files\Voice Command\vcbthag.dll”
EXAMPLE:
If I have a built-in version of MSVC with all files in \Windows, and I wanted to update to a different build I would do the following:
Install all files into a new location, e.g. “\Program Files\NewVC”
Update AppInstallPath to “\Program Files\NewVC\VoiceCmd.exe”
Update ResourcePath to “\Program Files\NewVC”
Update BTAGExtModule to “\Program Files\NewVC\vcbthag.dll”
Delete shortcuts that point to “\Windows\VoiceCmd.exe” and create new ones that point to “\Program Files\NewVC\VoiceCmd.exe”
NOTE: The VoiceCommand_PPC.cpl file may pose an issue becuase as a control applet, it always needs to remain in the \Windows directory. If you can't overwrite this file you may still be ok since you should be able to use a copy of VoiceCommand_PPC.cpl that is different from the other file versions.
NOW AVAILABLE - Manual install for 1.6.19209 to help assist in this process. It is available here. Additional instructions enclosed.
How Incoming Announcements Work (Under the Hood)
Incoming Announcements are the function of the voicecmd.exe and the following registry key:
Code:
HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce
"Script" = "as5p"
"Category" = "VoiceCommand1"
"Sound" = "Application Data\Volatile\TTSCallerID.wav"
When a call comes in and MSVC is enabled it checks itself to see if it should be performing incoming announcements. If it is configured to play announcements it uses the above settings. The “Script” section is similar to the scripts used for normal ring profiles, it basically is telling it to play the file listed in “Sound”
The file in “Sound” is dynamically generated for each call and then played over your ringtone as your announcement.
On versions where Incoming Announcements don’t work (like UK version 1.60.4622.0) the settings are the same, but the voicecmd.exe file does not properly generate the TTSCallerID.wav and thus no announcements are made.
The Private/Unknown caller issue is also related, as voicecmd.exe doesn’t seem to properly generate the file. It actually appears to leave the .wav file open since it doesn’t know how to properly output “private” or “unknown” this locking of the file appears to be why no ringtone plays at all.
This also appears to be why occasionally you will get an announcement of the last caller's ID when you get a Private call. It hasn't properly cleared out the old TTSCallerID.wav and is replaying the last one in queue.

Troubleshooting, Tweaks, and Tips
TROUBLESHOOTING
Remember that an app alone is not responsible for how it functions. Cooked ROMs and 3rd party software can all interfere with the operation of not just another application, but the OS itself. There are quite a few fantastic cooked ROMs out there that incorporate MSVC successfully, and many other individuals are running it. Chances are it can work for you, but you may be forced to try a different ROM.
INSTALLATION/UPGRADING:
Always use a current version of MSVC
Always install to main device memory (no storage card!)
Always remove previous versions first (when possible).
Soft-reset after any install/uninstall of previous versions.
Soft-reset after making any change to files or registy
Always read and re-read this guide to ensure that your problem isn't already listed
APPLICATION HANG/NON-RESPONSIVENESS
Disable and then enable it in Start > Settings > Voice Command
BLUETOOTH:
Delete and re-pair your Bluetooth headset
Try a different bluetooth headset
Ensure it works through the device speakers (without a bluetooth headset)
Talk loudly and clearly
Use a non-A2DP BT headset (or disable A2DP)
If using a car-kit, or another BT device with voice recognition, it may be best to disable MSVC and use the car-kit's built-in voice recognition abilities.
RECOGNITION:
Ensure that you are not using a localized version (for example trying to dial UK formatted numbers with an EU version).
CONFIRMATIONS:
By default, when you say "Call contact" MSVC will speak a confirmation and wait for you to say "Yes/No" or "Correct/Incorrect." Some devices (and older versions of MSVC) will cut off before accepting the confirmation. The only solution is to upgrade and if that doesn't work, turn off confirmations. This will cause the call to initiate immediately after speaking "Call contact." The downside is that you will not have the option to cancel the call via MSVC. However, MSVC will still repeat the name/number back to you so you can cancel it via your BT headset buttons.
ANNOUNCEMENTS:
Please see the appropriate sections on incoming announcements and see my MSVC tools for more information.
BUTTON MAPPING:
If your button mapping stops launching MSVC, try to remap the button to another application, save the changes, then remap back to MSVC.
OTHER:
See Tweaks and Tips for more!
MORE BELOW!

TWEAKS
There aren't too many additional tweaks you can do with MSVC. If you have information on additional tweaks, please advise:
Change Speech Speed - If your friendly MSVC assistanct Michelle is talking too slow or too fast for you, you can change her speed.
Go to HKEY_CURRENT_USER\Software\Microsoft\Speech\Voices
Change the value of "DefaultTTSRate" from between 1 (slowest) and 10 (fastest). Default if 4. I prefer 0 as it is not that slow and makes her a little clearer to understand.
Change MSVC to another voice - Can't be done! At least not any way that has been discovered. The various localized versions (US vs. UK, etc.) use different voices, but part of this configuration appears to be hard-coded into the application.
Change the sounds MSVC uses - Can't be done! The following registry keys exist dealing with sounds for MSVC:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech\Earcons]
"SRDirectedEarcon"="SRDirected.wav"
"TimeoutEarcon"="SRAsleep.wav"
"PTTEarcon"="SRAwake.wav"
If you remove or change these values the sounds go away, so they are definitely linked to these keys. But the issue is these files don't exist! So the sounds are apparently built into the program code. I have played around with changing these values to redirect to other sounds with no success.
Change Bluetooth PTT Delay - When you press the button on your BT headset to initiate MSVC two things happen: Your audio gateway opens to pass your voice to the phone AND MSVC initiates on the phone to accept your command. Some BT headsets take a while to establish their audio gateway. Because of this MSVC may open before the audio gateway is established. This can cause your voice to get cut off or decrease your recognition. To increase or decrease the delay from when you push your BT headset to when MSVC "picks up" do the following:
Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech
Add/Change a DWORD value "BluetoothPTTDelay"
Add a value in milliseconds (ms) - I believe the default is about 400ms. I'm not sure how high a value it will accept, but I think it maxes out at somewhere between 2-4000 (2-4 seconds). A value of "2000" should be good if you need a longer delay. Alternatively, you can try setting this to 0 if your BT gateway establishes quickly...this may make MSVC pick up quicker.
SOFT RESET!
Change Recognizer Timeout - When the MSVC Microphone appears at the top of your screen, you have 4 seconds to start talking before it closes. If you want to increase or decrease this interval do the following:
Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech
Add/Change a DWORD value "SRTimeout"
Add a value in milliseconds (ms) - The default is "4000" (4 seconds). I'm not sure how high a value it will accept, but I have tested it between 0 and 8000. 8000 is an 8 second timeout and 0 causes it to not listen to a word you say!
SOFT RESET!
Change Rejection and Ignore Threshholds - When you speak a voice command, MSVC attempts to understand what you say. It assigns your speech a confidence level based on its interpretation on a scale from 1 to 100. It compares the confidence level to the IgnoreThreshold (default 10). If the confidence level is less than the IgnoreThreshold it discards the command. This would happen if you said something that MSVC doesn't understand at all like "cook me breakfast." It would assign a very low confidence level based on it's matching techniques. It would then most likely discard this and do nothing further. If what you say is somewhat recognizable to MSVC, meaning it is above the IgnoreThreshold it will attempt to interpret it. It will compare the confidence level to the RejectionThreshold (default 36). If the confidence level is less than the RejectionThreshold, but GREATER than the IgnoreThreshold that means that it won't reject you, but it isn't 100% sure. In this case you will be asked to "Try again" or "Please Repeat." Otherwise, if your confidence level is above the RejectionThreshold that means MSVS thinks it understood you and will do its best to interpret your command to one in its set. To change the values of these thresholds to better tune MSVC to your vocal tones, you can modify the following:
Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech
Change DWORD value "IgnoreThreshold" or "RejectionThreshold"
Soft-reset
Adjusting Volume of Announcements - There are two values that seem to influence the volume of announcements. They are stored within the following key:
HKCU\Control Panel\Sound Categories\Voice Command1
The values are:
AttenutationCategory
InitVol
There are apparently different default setting based on your device. In general the values are generally around 1-4 for AttenuationCategory and 1-5 for InitVol. Some research shows that setting InitVol to 40 and AttenuationCategory to 1 provide the best results. In my testing I have found the InitVol to do nothing. The AttenuationCategory definitely does something, it seems the lower the number the lower the voice. When set it to 0 the announcements were very faint. Setting it higher made them higher, although I can't say that anything over 4 or 5 got any louder.
In my findings I would say set both of these to 5 (I have read some other posts that lead me to believe setting InitVol over 5 is pointless, in addition, the posts that recommend setting it to 40 don't specify if that is decimal or hex).
Adjusting Incoming announcements while on a call - Incoming announcements will come in if they are enabled...even when you are on a call. The only time they will not is if your time is marked as "busy" in your calendar. See my MSVC tools for ways around this and other announcement issues.
TIPS
Windows Media Player Voice Commands:
Apparently MSVC doesn't properly read ID3v2 tags. If you want it to understand you properly you should use ID3v1. Find out more info here. (courtesy nonsequitir).
Problems using "Dial":
Some people have issues with the "Dial" command in MSVC. This often occurs when trying to dial numbers that are different than the standard dialing system for the country that the version of MSVC supports. The workaround for this would be to create a contact and use the "Call" command instead.
Use the nickname field to improve recognition accuracy:
From Microsoft: "You can name contacts with nicknames such as Home, Mom, or Dentist. After doing this, you can call by simply saying Call Home, etc. If you have a contact that you consistently cannot access, try adding a nick name that looks the way that you might pronounce it."
To add a nickname to a user, edit the contact. Click the arrow to the right of the contact's name to bring down an advanced dialog box that allows you to specify a nickname.
Jawbone 2 Users:
In order to initiate MSVC from this headset, you do not press the talk button. Instead you hold the Noise Assassin button for 2 seconds. (courtesy Mario23)

Additional MSVC Tools - For Incoming Announcment Issues
Microsoft Voice Command Toggle Script
This tool presents my solution to the above issues with incoming announcements coming to both the BT headset and the phone. Others, like myself would prefer MSVC to deliver incoming announcements to the BT headset AND speakerphone simultaneously. The main reason for this is that ideally, we want the announcement coming to our BT, but out BT might not always be in our ear. Therefore it would be nice to for the announcement to come to the phone as well so we don’t miss a call.
Unfortunately, this doesn’t seem possible with the current version of MSVC. But I have written a simple script to give the next best thing.
The basic idea the script uses is this:
When the BT headset is in the ear, Notification option #2 is chosen (“Announce notifications using Bluetooth hands free if available”).
When we want to remove out BT headset, the script quickly toggles to option #3 (“Announce notifications through device speaker or wired headset only.”)
This allows the BT channel to remain in its default state and simply redirects through a toggle of the notification option where you want the announcement to come out. By mapping this script to a button (like PTT) you can quickly toggle your phone when you remove or replace the headset from your ear.
The below file is a .CAB file that will install MortScript onto your phone as well as my MSVC Toggle Script. It will place the script into your Start\Programs\Tools so that you can then map it to a button of your choosing. I will also post the separate .mscr file for those that already have MortScript installed. (Warning: Installing and then removing the CAB file may also remove MortScript).
Basically MortScript is a application that allows the creation of advanced scripts to control the device and applications.
The MSVC Toggle script works in the following way:
When you initiate the MSVC Toggle either by a button or clicking, it first attempts to determine where your MSVC is installed. The application only supports MSVC installations to \Program Files\Voice Command or \Windows. You will get 3 warning buzzes and the application will quit if it is installed elsewhere. (Specifically it is looking for the location of the VoiceCommand_PPC.cpl file, which should almost always be in \Windows).
Once the application is located, the script simply toggles between notification option #2 (BT headset announcements) and #3 (speakerphone announcements).
However, changing the registry key isn’t enough as the changes aren't loaded into MSVC running memory. So, the next thing the script does is reload MSVC settings by opening and closing the MSVC applet. You will see the MSVC applet briefly flash on the screen and then close.
You will then feel a quick vibration to let you know the toggle has completed There will be a short (250ms) vibration when switching to option #2 (BT announcement) and a longer (500ms) vibration when switching to option #3 (Phone announcement).
It’s that simple!
Free/Busy Toggle Script
Another issue with incoming announcements is that they often "announce" at inopportune times, like when you are already on a call, or in a meeting. One way to prevent this is to se the notification option "only during free time". Free/Busy time is normally determined if you have an appointment in your calendar that sets your disposition to Free/Busy. So, if you have a meeting scheduled in your calendar and the time is set to "busy" you won't get announcments if this option is selected. However this is inconvinient to have to go in and create an appointment everytime you want to be marked as "busy". Luckily, I have found a location in the registry which records that information and have used it in the following tool.
FreeBusyToggle Script works like the MSVCToggle Script from above. It installs into the same \Programs\Tools folder and uses MortScript. For easy use you should map it to a key.
When you run the script it will make one short beep indicating your time is set to free, or two short beeps indicating your time has been set to busy.
So, if you are going to be taking calls or in a meeting, press to toggle till you get the two beeps and then your time is set to busy and you won't get announcments. After the meeting, press again and your time will be set back to free.
Not a perfect solution...but That's It!

reserved*************

reserved************

Awesome thank you

Thanks for keeping this alive

Pumpiron579 said:
Thanks for keeping this alive
Click to expand...
Click to collapse
excuse me, but can we give advice/link to Bengalih's formes files???
such as if some one want to flash their rom they should use sashimi afterwards... is such discussion allowed??? and files can't be uploaded? (even to rapidshare, etc???)
sorry but this is the first time I've sen this kind of thing in forum...
yes sometimes noobs and also oldies can be annoying when come to words picking, but just to make someone like him to go is no one intention of course
so does it mean we cant post files uploaded by bengalih or????
so confused here

rajmagi said:
excuse me, but can we give advice/link to Bengalih's formes files???
such as if some one want to flash their rom they should use sashimi afterwards... is such discussion allowed??? and files can't be uploaded? (even to rapidshare, etc???)
sorry but this is the first time I've sen this kind of thing in forum...
yes sometimes noobs and also oldies can be annoying when come to words picking, but just to make someone like him to go is no one intention of course
so does it mean we cant post files uploaded by bengalih or????
so confused here
Click to expand...
Click to collapse
He deleted all his stuff, but i provided a link to the snap shot that google took of it before he did so, if you would like to access it it is at the top of the page.
as for posting his stuff i think that as long as you do not claim it as your own you should be able to post it
if you have anything you would like to add i can put it in the original posts (sorry if i missed anything i was just trying to get it up)
edit: Yes discussion is allowed but he deleted most of his stuff or his forums are closed. This repost was approved by a mod(thats why i can say reposting his stuff should be fine.)

brynwall said:
Awesome thank you
Click to expand...
Click to collapse
Pumpiron579 said:
Thanks for keeping this alive
Click to expand...
Click to collapse
no problem

Refresh, move up list to find.

Version 1.60.4622 (Localized versions) has been tested to work but WITHOUT incoming announcements (either to phone or BT). To get incoming announcements to work you can replace the voicecmd.exe with the version from 1.6.17913 or 1.6.19209.
The file voicecommandreplacementfiles.zip that is circulating is simply a set of 4 files from version 1.6.17913. Copying these over your current installation in effect upgrades it to that version. There should be no need to apply those files if you are running 1.6.17913 or above.
Click to expand...
Click to collapse
But so, is it enough, to copy the new voicecmd.exe over them, or should we need to add the other three files from voicecommandreplacementfiles.zip as well ?
Thanks !

Hi all -- I do not know any of the specifics, and I really don't care, of exactly why bengalih left, but since this thread represents his work, I do not think it inappropriate to provide you a link where you can interact with him directly.
http://www.winmo-experts.com/viewtopic.php?f=11&t=2

Hey,
I checked out all the settings mentioned in the first page ... but the announce voice is not working at all with receiving proceedure (sms, phone called ...etc); however VC is working normally when I give/say a command!
My MSCV v1.6.19971
My Radio version: 1.02.25.19
Any suggestions?

Read subject of email
When I was using msvoice in wm6.0 I could have msvoice anounce the name of sender and the subject of the email. I can't seem to get it to work in wm6.1 with msvoice .209.
Any thoughts?

software issue with MS Voice command

I have the Fuze. Has there been a fix for the following issue?
If you enable "announce incoming caller" my phone will say the name if it's in my address book, or the number. When I answer the phone via BT headset, I cannot hear the caller, but the caller can hear me. If I transfer to my phone, I can now hear the caller. If I turn off the announce, then everything is working again.
Just a heads up, my phone when I first got it, would work fine, then it stopped announcing the caller. All you would hear is a "beep" in the headset. Then I was shown a regedit that got the voice to com back, but can't hear the caller.
I know this was a ongoing issue months ago, but was there ever a solve for this?
Oh my Fuze is stock.
ms voicecommand version: 1.6.19971
rom version: 1.95.502.5 wwe
rom date:10/20/08
proto version:52.39c.25.22h

@starstreak:
I'm latching on some additional URL's to help us troubleshoot the issue.
MS Voice Command on the Fuze
http://forum.xda-developers.com/showthread.php?t=445204
The Definitive Guide to Microsoft Voice Command (MSVC) 2.1
http://www.winmo-experts.com/viewtopic.php?f=11&t=2
Da_G's Simple ROM Kitchen Solutions (Fixes)
http://forum.xda-developers.com/showpost.php?p=3467110&postcount=503
http://forum.xda-developers.com/showpost.php?p=3462813&postcount=489
http://forum.xda-developers.com/showpost.php?p=3592035&postcount=644
Da_G's Simple ROM Kitchen Reports
http://forum.xda-developers.com/showpost.php?p=3455841&postcount=470
http://forum.xda-developers.com/showpost.php?p=3457239&postcount=471
http://forum.xda-developers.com/showpost.php?p=3460626&postcount=480
http://forum.xda-developers.com/showpost.php?p=3460665&postcount=481
http://forum.xda-developers.com/showpost.php?p=3460972&postcount=483
http://forum.xda-developers.com/showpost.php?p=3462787&postcount=488
http://forum.xda-developers.com/showpost.php?p=3617314&postcount=709

Few questions:
1) What file is the BT Audio Gateway pointing to:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
BTAGExtModule =
2) Is there a BT Headset Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\InCallPoliteBeep
3) Is there a Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\TTSAnnounce

1) What file is the BT Audio Gateway pointing to:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
BTAGExtModule = oemagw.dll
2) Is there a BT Headset Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\InCallPoliteBeep
catagory incall
script as5p
sound application data\volatile\\ttscallerid.exe
3) Is there a Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\TTSAnnounce
catagory voicecommand1
script as5p
sound application data\volatile\\ttscallerid

That happened to me with the stock 6.1 & MSVC, but, since I flashed to RRE's 6.5 V4, which uses MSVC 1.6.21234, that problem disappeared.
It would do the same thing yours did, you'd answer your BT, they could hear you but you couldn't hear them. I tried it with several different BT headsets, made no difference.

@p51d007:
If you can spare a moment, would it be possible for you to post up the registry for the BT Audio Gateway?
@startstreak:
Those registry entries don't look right (ex: point to ttscallerid.exe, extra back slashes, etc). Here are my entries:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
REG_SZ: BTAGExtModule = \windows\VCBTHAG.DLL
[HKEY_CURRENT_USER\ControlPanel\Sounds\InCallPoliteBeep]
REG_SZ: Script = as5p
REG_SZ: Category = InCall
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
[HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce]
REG_SZ: Script = as5p
REG_SZ: Category = VoiceCommand1
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
Cheers,

hilaireg- I remember where those extra "//" came from. It was from another regedit that was on this board.
I redid your settings on mine. Wow. I can now hear my caller. I tried it around 8 times with different phones. 2 times, my phone vibrated (I have it set to vibrate&ring at the same time) but nothing sounded on my headset untill the phone killed the call to goto voicemail. At that split second, I heard my ring tone in my ear for like less than a second. So I'm not sure if that is a new issue.
I am happy for your help. Since I got the fuze when it first came out, I never had my MSVC working this well. Thanks!

I'll post ONLY the ones that vary from yours...
Hope this helps.
[HKEY_CURRENT_USER\ControlPanel\Sounds\InCallPoliteBeep]
REG_SZ: Script = p <<<<<THIS IS DIFFERENT
REG_SZ: Sound = Alarm1.wma <<<<THIS IS DIFFERENT
[HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce]
REG_SZ: Category = InCall2 <<<<<THIS IS DIFFERENT
hilaireg said:
@p51d007:
If you can spare a moment, would it be possible for you to post up the registry for the BT Audio Gateway?
@startstreak:
Those registry entries don't look right (ex: point to ttscallerid.exe, extra back slashes, etc). Here are my entries:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
REG_SZ: BTAGExtModule = \windows\VCBTHAG.DLL
[HKEY_CURRENT_USER\ControlPanel\Sounds\InCallPoliteBeep]
REG_SZ: Script = as5p
REG_SZ: Category = InCall
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
[HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce]
REG_SZ: Script = as5p
REG_SZ: Category = VoiceCommand1
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
Cheers,
Click to expand...
Click to collapse

starstreak said:
hilaireg- I remember where those extra "//" came from. It was from another regedit that was on this board.
I redid your settings on mine. Wow. I can now hear my caller. I tried it around 8 times with different phones. 2 times, my phone vibrated (I have it set to vibrate&ring at the same time) but nothing sounded on my headset untill the phone killed the call to goto voicemail. At that split second, I heard my ring tone in my ear for like less than a second. So I'm not sure if that is a new issue.
I am happy for your help. Since I got the fuze when it first came out, I never had my MSVC working this well. Thanks!
Click to expand...
Click to collapse
As I see it, you have a few options:
1) Continue to debug the issues
I've a feeling that the MSVC install on the ROM has been messed up. I'm not sure if it's only the registry part or if some of the exe/dll are impacted as well. If it turns out exe/dll's are also a problem, we will quickly run out of options.
In the interim, I can post up the MSVC registry file so that you can compare the settings against those in your device registry.
2) Follow p51d007's recommendation
IMHO, I recommend this approach. Drop the ROM you are using and flash a working ROM.
Alternatively, make an inventory of the applications on your device, and then look at the 6.1 Kitchen in the Raphael ROM Development thread - there's text files listing the applications in the kitchen/pack. Compare it against your list to make sure that all the applications you use/have are present and cook your own ... provides *way* more control.
* EDIT *
Posted registry and post-MSVC configuration.

I was thinking about upgrading to 6.5 if it was stable. If I had to cook.

I wouldn't call it an upgrade; it's still pretty much unreleased code.
That said, Da_G (and others) have done a fantastic job with the 6.5 code they've managed to locate.
If you need to rely on device functionality, you may want to look trying a 6.1 ROM - or cooking your own. That way, you can try WinMO 6.5 on the weekends ...

Text Messages
Voice Command on my tilt read messages and I could hear them. I realize the Fuze has had issues with Voice Command. Has anyone gotten this feature to work? Saved time from having to pick device up from desk.

try flashing back to stock and then going back to a ROM. Try out NRGZ28's Energy ROM. Working great very little bugs. on an older version but i'm sure the new one is just as stable.

It Works...
If you go to the voice command icon in settings, highlight messaging (don't just put the check mark in the box, highlight the word messaging) then push the options button. You will go to the Voice Cammand: Messaging Options and take the check out of the High priority messages only box. This should work. I have had Energy Roms anda few others, like right now I have RRE's and my messages read after doing this. Everytime I flash a new rom I have to go and do this. But it works afterwards.

Muchas Gracias
I did as you suggested, unchecked High priority massages only. Works like a charm, thanx