Summarized procedure for getting MSVC 1.6 to work with Kaiser

[goestoeleven]

No attempts to claim credit for inventing this process (the PTT fix is in the Wiki, and the Cyberon bit has been around since the Wizard days), but this could be the first time it's been completely posted in one place.

Cheers!

-------------------


Step 1. Disable Cyberon
- Delete SDDaemon.lnk in \Windows\Startup
- Delete the Voice Dialer shortcut from \Windows\Start Menu\Programs (or whatever submenu folder it might be in)

[NOTE: if you don't delete the shortcut and accidentally click it (or launch the program directly from File Explorer), you may have to repeat the ENTIRE procedure]


- In each of these registry locations:

HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Main_ContextMenu
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Main_Tools
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Summary_Tools

----> Remove this key entirely: {2C0E9904-F32D-4f53-875F-479F5CA81E18}

- In this registry location: HKEY_LOCAL_MACHINE \ ControlPanel

----> Remove this key entirely: VoiceTagCPL


Step 2. Disable PTT and Enable PTT Button
----> Remove this key entirely: HKEY_LOCAL_MACHINE \ Services \ PTT

From HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Keys

- Add a new key called "40C6"
- Add a string under the key called "Name" with the value "Button 6"

- Add a new key called "40C7"
- Add a string under this key called "Name" with the value "Button 6 (hold)"


Step 3. Install MSVC 1.6

- Be sure to use the latest build, which can be found at http://www.sendspace.com/file/f48smf
< File Name: MSVC_US_PPC 1.6.17913.CAB Size: 3MB >
NOTE: this is licensed software; you should only download this update if you already have a licensed copy of MSVC 1.6


Step 4. Remap MSVC to PTT button (optional)


Step 5. Pair your headset

You should now be able to initiate MSVC from your BT headset and receive prompts thru its speaker. Finally, I can leave my phone in the case when I want to!

Enjoy!

[Griffy wiffy]

I have a HTC branded TytnII and there is no PPT reg entry. Also the keys

From HKLM\Software\Microsoft\Shell\Keys

- Add a new key called "40C6"
- Add a string under the key called "Name" with the value "Button 6"

- Add a new key called "40C7"
- Add a string under this key called "Name" with the value "Button 6 (hold)"

already exist. So..

this didnt work for me. If i push the button on my BT headset it redials the last number.

Button 6 is the Voice command button near the wheel so i cant see how the BT headset button is going to work??

any help would be great as this is then only function missing from a great device.

cheers

[goestoeleven]

Should have mentioned that this has been tested by me only on a Tilt with AT&T stock ROM...

You shouldn't have to worry about the PTT-related steps on a TyTN II (nothing there to disable).

[Russ741]

Step 1. Disable Cyberon
[/B]- Delete SDDaemon.lnk in both \Windows\Start Menu and \Windows\Startup

- In these registry locations:

----> Remove this key entirely: {2C0E9904-F32D-4f53-875F-479F5CA81E18}



So this seems to be a very straight forward process, easily followed by anyone that has any right to be mucking about in a registry. However, (;))SDDaemon.lnk does not exist in \Window\Start Menu it does exist in \Windows\Startup

Also, Remove this key entirely... Where the hell is it?

All other steps work fine..

Russ741

[Russ741]

The PTT is now maped to VC, very cool works good.
However VC is still not working properly, I can issue commands, (dial, call, time, etc) but the system will not announce calls or appointments. I used the same CAB I have used on previous installs that worked fine before.

Any ideas anyone?

Russ741

[Russ741]

If anyone else is having issues with call announcements look here for the fix.

http://forum.xda-developers.com/showthread.php?t=333260

Mine is now 100% and I can go back to my real job!

Russ741

[sscholz]

I have a HTC branded TytnII and there is no PPT reg entry. Also the keys

From HKLM\Software\Microsoft\Shell\Keys

- Add a new key called "40C6"
- Add a string under the key called "Name" with the value "Button 6"

- Add a new key called "40C7"
- Add a string under this key called "Name" with the value "Button 6 (hold)"

already exist. So..

this didnt work for me. If i push the button on my BT headset it redials the last number.

Button 6 is the Voice command button near the wheel so i cant see how the BT headset button is going to work??

any help would be great as this is then only function missing from a great device.

cheers

I use a plantronic BT head set. To use VC on the tilt I hold the main button down on the head set until I hear the VC chime in. Takes about 4-5 of holding it down until VC kicks in. I hear about 3 or beeps during that time.

[goestoeleven]

If anyone else is having issues with call announcements look here for the fix.

http://forum.xda-developers.com/showthread.php?t=333260

Mine is now 100% and I can go back to my real job!

Russ741

I can confirm that with the procedure in #1, along with the update CAB from the above link, I'm now getting incoming calls announced, too! :)

Procedure in #1 has been updated accordingly.

[Russ741]

I can confirm that with the procedure in #1, along with the update CAB from the above link, I'm now getting incoming calls announced, too! :)

Procedure in #1 has been updated accordingly.

@goestoeleven: did you not put in the registry change?

4. Lastly, you must modify this registry entry in order to use your Bluetooth headset with Voice Command:
HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand Path = "\Program Files\Voice Command\VoiceCmd.exe

That's from your posting and I am pretty sure that is what really fixed my issue. I was using the older ver of MSVC with my wizard and it worked fine. So, unless there is something really different about the OS build on the Tilt, updating the MSVC may have improved on things but I still believe this reg key is what did it.

BTW: I loaded the updated MSVC before I tried the reg change and this ver of MSVC does NOT make that change for you!

I recommend you update post1 to include this step.

Great job on finding that key by the way! THANKS!!!!!!

Russ741

[goestoeleven]

@goestoeleven: did you not put in the registry change?

4. Lastly, you must modify this registry entry in order to use your Bluetooth headset with Voice Command:
HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand Path = "\Program Files\Voice Command\VoiceCmd.exe



This key is not necessary with MSVC 1.6 (it was with MSVC 1.5). I'm running just fine without it.

[diar]

i still can not initiate voice command from my headset. everything else works fine. i hear announcements, i can answer and hang up phone calls (the voice quality is still horrible), i get reminders, etc. but when i press the button to activate, it just opens the phone app.

is there something missing?

[Russ741]

This key is not necessary with MSVC 1.6 (it was with MSVC 1.5). I'm running just fine without it.

Interesting, I tried a couple different copies of MSVC 1.6, including the CAB I used on my Wizard and didn't get announcements. It wasn't until I loaded the latest ver and put in the reg patch did it start working 100%. I admit I didn't test between the latest ver and the reg change (yeah I know I should have) so I can't say for sure which one did it.

Russ741

[Russ741]

i still can not initiate voice command from my headset. everything else works fine. i hear announcements, i can answer and hang up phone calls (the voice quality is still horrible), i get reminders, etc. but when i press the button to activate, it just opens the phone app.

is there something missing?

That's very odd, normally the part that fails (for me at least) is the announcements or ring tone to the BT.
Can you initiate calls from the MSVC mapped key on the phone? That will narrow down if the prob is with the BT, MSVC or the phone itself.

Russ741

[diar]

yes...i push PTT and VC functions just fine. i'll try that final reg change again and i'll soft reset and see what happens.

EDIT: i still can't initiate calls from the headset, however, this change does seem to have solved the low volume problem for me. just got a call, i heard the caller loud and clear and they heard me no problem.

so one problem down, one to go.

[MELPHBOY]

I followed step in posting 1 to the letter and everything worked perfectly including caller ID voice announcement over bluetooth. But,when I soft reset or turn my phone off, I do not get voice announcement over bluetooth anymore.:confused: HELP!:eek:

[kahibbi]

Thanks! I like this concept ... I'll try it on my AT&T Tilt Rom.

[rsolomon]

Works great on my Jabra BT500.

On my Parrot CK3100 I get the "button only works once" behavior described in another thread - everything is great the first time I initiate VC from the car kit, but after that the phone's speaker and microphone are the only things active.

Next time the phone and car kit connect I get one more button push that works.

Argh. I'll search that other thread again, but I don't recall a fix for the folks that had these probs w/their headsets. (Any pointers are of course welcomed!)

Richard

[gtdRR]

Thanks a lot. This worked perfect for me. I am using an AT&T Tilt with helmi_c's Kaiser AKU.0.7.0 Cooked ROM and a Plantronics Discovery 655 headset.

[lansa]

I have a wired headset (HTC brand) and installed Voice Command, but cant get it to work from the headset button...does anyone know how I can activate from the button on headset?

[austinsnyc]

i guess its safe to say you went into MSVC SETTINGS AND CHANGED the settings to wired headset? there has never been an issue with wired headsets just BT

[lansa]

The only setting that mentions wired headset is under "Notifications", and I have the wired headset option checked, but I dont think that actually maps the headset button to voicecommand...do i need to add a registry key to map the button? The cyberon app worked fine with my wired headset.

[shaolinmastr]

MSVC still does not announce calls through the speaker with no headset. or even with a wired headset for that fact from day one.

[shaolinmastr]

Taken from goestoeleven original post. This i what worked for me on my TILT. Thanks goestoeleven for making this alot easier to do.

Step 1. Disable Cyberon
- Delete SDDaemon.lnk in \Windows\Startup
- Delete the Voice Dialer shortcut from \Windows\Start Menu\Programs (or whatever submenu folder it might be in)

[NOTE: if you don't delete the shortcut and accidentally click it (or launch the program directly from File Explorer), you may have to repeat the ENTIRE procedure]


- In each of these registry locations:

HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Main_ContextMenu
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Main_Tools
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Summary_Tools

----> Remove this key entirely: {2C0E9904-F32D-4f53-875F-479F5CA81E18}

- In this registry location: HKEY_LOCAL_MACHINE \ ControlPanel

----> Remove this key entirely: VoiceTagCPL


Step 2. Disable PTT and Enable PTT Button
----> Remove this key entirely: HKEY_LOCAL_MACHINE \ Services \ PTT

From HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Keys

- Add a new key called "40C6"
- Add a string under the key called "Name" with the value "Button 6"

- Add a new key called "40C7"
- Add a string under this key called "Name" with the value "Button 6 (hold)"


Step 3. Install MSVC 1.6

- Be sure to use the latest build, which can be found at http://www.sendspace.com/file/f48smf
< File Name: MSVC_US_PPC 1.6.17913.CAB Size: 3MB >
NOTE: this is licensed software; you should only download this update if you already have a licensed copy of MSVC 1.6


Step 4. Remap MSVC to PTT button (optional)


Step 5. Pair your headset

You should now be able to initiate MSVC from your BT headset and receive prompts thru its speaker.

In my testing I have found this so far. I use the HTC wired headset. The button on the headset only answers calls. It will not allow VC, I have to use button 6 to initiate any VC's. works for me great. Now I feel like I'm getting my money's worth. VC responds to all commands. Call announcements works great thru speaker without any headset also. thanks

Enjoy!

[URPREY]

The latest version of VC will do the call announce over BT with no hack also!

[Pampered4Life]

I have the Tilt with the latest official yet unreleased rom. I have voice command installed and without doing anything listed in here everything works perfectly. Im using Plantronics Voyager 520. The only thing i can note is that with the MS VC 1.6 first release i was unable to hear caller id announced. But with the lastest MS VC posted here now i have that as well. Finally no more whipping out the ole unit just to see whos calling.

[reitjam]

i want the rom please

[DJHile]

I've tried all of this and have had no luck getting VC to fire for me on a plantronics 520 headset. :-( It's the "one button navigator" BT headset so its a pain sometimes. I have all the other functions down but... obviously cant figure out how to activate VC through it. If I press it once, it opens the BT field and tries to accept a call... I double click, it calls the last number, i hold it down for 4-5 seconds, it shuts off... grr

so i'm not sure if I just don't know how to make the BT fire VC or this procedure just didn't work... ahh i hate it..

anyone else use the 520 plantronics?

[ahussam]

Hi, I have the BH S100 HTC bluetooth Stereo Headset, the announcements work fine through the normal phone speaker (I have the AT&T Tilt), but through Bluetooth I get only a ring, no announcements at all (although I tried every setting possible), any Ideas??

Note: for those who have trouble getting the annnouncements at all, you have to click on "Phone" then choose "Options" from the "Settings\Voice Command", and then enable "Announce Incoming Calls".

[ceevee369]

not in line with the OP first post, but with Alex V5.2 Home rom, where Cyberon is already installed, you can also install MS VC1.6 at the same time and use both , each linked to a diff. hardware button.

No issues so ever with BT hardware which can be handled by both soft's.

Accuracy wise, Cyberon is better I would say when comparing / testing both.
MS VC has a sexier voice though :D

[jcrompton]

not in line with the OP first post, but with Alex V5.2 Home rom, where Cyberon is already installed, you can also install MS VC1.6 at the same time and use both , each linked to a diff. hardware button.

No issues so ever with BT hardware which can be handled by both soft's.

Accuracy wise, Cyberon is better I would say when comparing / testing both.
MS VC has a sexier voice though :D


Are you using pre-recorded voice tags with Cyberon? the reason I ask is that I too am using Alex's ROM and would have preferred to use Cyberon but my voice accuracy was not just worse that the MSVC but essentially unusable in a side by side comparison. This is one of the most frustrating things about tweaking these devices is that two different users can get such different experiences!!

[jcrompton]

Is this just the design of the software ( MSVC ver 1.6 ) - when I switch my device to vibrate I no longer get Bluetooth Headset announcing of incoming calls?

Is there a way to leave the phone on vibrate but then when I connect the Bluetooth Headset be able to hear announcement of incoming phone calls?

[ceevee369]

Are you using pre-recorded voice tags with Cyberon? the reason I ask is that I too am using Alex's ROM and would have preferred to use Cyberon but my voice accuracy was not just worse that the MSVC but essentially unusable in a side by side comparison. This is one of the most frustrating things about tweaking these devices is that two different users can get such different experiences!!

No pre-recorded voice tags. I think that Cyberon is better in tonation differentiation. I got European and Chinese names as contacts and Cyberon is just better recognizing my voice.

[WhiteWizard]

After using VC with the patched files for months, I've finally purchased this same version and followed the procedure carefully, incoming calls work at first try (after unabling it, ofcourse).
The version witch I had previuosly was titled VC.... for M2M, I've got it from a torrent, so, nothing like the original!.