Titan Kitchen CE OS 5.2.19209 (Build 19209.1.0.2) aka 5060

[esqueue]

You aren't getting charged extra. You don't need to do anything. If it is annoying, I think that you can make a new #777 connection in your connection manager but you don't need to worry about anything.

[datguy810]

how do u work the new voice dial and is there anyway to go back to old version ?

[pachock]

I am sorry if this was asked before. When I go in the mail application, xt9 icon is displayed and I can not enter some of the characters and autocomplition does not work. Is there a way to completly disable xt9?

[MN-Joe]

Masters of the OEMs for the Kitchen - can we get the following added in so we can activate Microsoft Voice Command from the headset without having to add the entry. I've only tried the highest revision numbered one and the entire key is mssing.

[HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand]
"Path"="\\Windows\\VoiceCMD.exe"

Edit: Apparently this was only for a V1.6 Cab build and not required - I removed and still works.

[justpctech]

MN Joe: not sure where you got that key from, but I dont have it in my build, I used the latest version also, and it works with my Jabra 350 headset fine.

[colonel]

Originally Posted by pachock

I am sorry if this was asked before. When I go in the mail application, xt9 icon is displayed and I can not enter some of the characters and autocomplition does not work. Is there a way to completly disable xt9?

Use a different SIP. Also, I beleive there was a post somewhere today about disabling xt9. I will look for it.

[MN-Joe]

Originally Posted by justpctech

MN Joe: not sure where you got that key from, but I dont have it in my build, I used the latest version also, and it works with my Jabra 350 headset fine.

See any of a dozen posts - http://forum.ppcgeeks.com/showpost.p...46&postcount=2

Normally you have to change this setting, but in the build from BuildOS the entire key is missing.
Guys I swear I could not get this working and finally added this and it worked

EDIT - NOT Required - still not sure what was my problem, but I removed this and it continues to work.

[colonel]

Originally Posted by MN-Joe

Voice Command works just fine, but with your build can you activate it from the headset? I have no issues using the hardware button, but in order to get activation by touching the button on my bluetooth headset I believe this needs to be there. Without it there my headset will not activate Voice Command.

See any of a dozen posts - http://forum.ppcgeeks.com/showpost.p...46&postcount=2

Normally you have to change this setting, but in the build from BuildOS the entire key is missing.

You should never have to change the setting. MSVC launch from my BT headset works fine with the included reg entries. That thread is talking about the VC 1.6 that is installed via cab.

[MN-Joe]

VoiceCommand
I swear I couldn't get this working and then tried this and it works - based on what you are saying I went back in and removed it and it works just fine so you are correct, but I'm left wondering what was causing it not to work before? I did nothing this evening except that one change. Thanks for setting me straight!

[colonel]

Just glad its working for you. Sometimes headsets can be a little picky, but it should work without any changes needed.