[Tilt, TyTN II, MDA Vario III Themes and Apps] joel2009:
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!