Re: MS Voice Command bugs
Found a solution on PDAPHONEHOME & XDA...
This is what I had to do to get Incoming Call Name Notification from MS Voice Command on Bluetooth headset:
Edit this registry key:
HKCU\ControlPanel\Sounds\TTSAnnounce\Category
Change from VoiceCommand1 to Ring
no need to reboot.
This was the original text:
------------------------------
With this fix - the ring tone will play for a second and then be cut off by the call announcement. The announcement will be at a lower volume. The announcement will repeat - the ring tone will not be played again.
NOTE THAT YOU SHOULD ATTEMPT THIS FIX ONLY IF YOU ARE COMFORTABLE IN UPDATING YOUR REGISTRY.
Change the following registry keys:
HKCU\ControlPanel\Sounds\TTSAnnounce\Category
change from VoiceCommand1 to Ring
HKCU\ControlPanel\Sounds\TTSAnnounce\Script
change from as5p to v0p (that's v-zero-p) - for vibrate & ring, or p (ring only)
The above fix seems to get the announcements reliably, and doesn't break the set vibrate/set ringer features in the TF3D interface.
Hopefully we can find a better solution - that will restore the full functionality of Voice Command incoming call announcements - and not need this hack.
Another option is to manually overwrite the ringtone file name:
HKCU\ControlPanel\Sounds\RingTone0\Sound
change to \Application Data\Volatile\TTSCallerID.wav
This fix replaces the ringtone with the call announcement - and at full volume.
BUT this solution has several problems, including breaking the set vibrate/set ringer feature in TF3D.
--------------------------
Last edited by ramborami; 12-03-2008 at 01:27 AM.
|