|
General
Sept 8, 2006 11:40:56 GMT -5
Post by Rick Price on Sept 8, 2006 11:40:56 GMT -5
|
|
|
General
Sept 8, 2006 11:42:02 GMT -5
Post by Rick Price on Sept 8, 2006 11:42:02 GMT -5
Bluetooth works by device and the Treo has trouble with Bluetooth.
|
|
|
General
Sept 8, 2006 11:43:50 GMT -5
Post by Rick Price on Sept 8, 2006 11:43:50 GMT -5
I got it installed and working the first try. But I know it can be hard.
VoiceDialSupport@fonix.com
|
|
|
General
Sept 8, 2006 13:45:50 GMT -5
Post by Rick Price on Sept 8, 2006 13:45:50 GMT -5
I just installed with a gentleman who has Verizon as his provider and we got the VoiceDial 2.1 SP2003 version on his.
Not the VoiceDial 2.1 WM5 SP.
|
|
|
General
Feb 3, 2007 12:10:33 GMT -5
Post by maxieboy on Feb 3, 2007 12:10:33 GMT -5
I have a Treo700wx running WM5 with Sprint as my provider. I also have a compatible Plantronics 640 Bluetooth headset. As of now Windows VoiceCommand 1.6 has limited utility on the Palm 700w. You can use the headset to initiate and receive a call. The problem is any audio dialog to and from the Treo is through its microphone and speaker. When driving in a noisy environment it's hard to understand the weak voice from the Treo especially when you have a headset plugged into one of your ears. (And yes the speaker volume is as high as it goes.) Does VoiceDial 2.1 allow all dialog through the bluetooth?
|
|
|
General
Feb 6, 2007 18:03:26 GMT -5
Post by Rick Price on Feb 6, 2007 18:03:26 GMT -5
Bluetooth is device driven. So it would depend on what you have. But you should be able to do the following.
Working VoiceDial with Bluetooth:
1) Launch the Bluetooth Headset. You should hear some kind of clicking noise, which is saying the audio gateway is open
2) Launch the VoiceDial Program
3) Begin Speaking
I found this in my archive and realized that I never responded. Anyway, I figured out the registry hack for how to map the bluetooth action key so that it establishes an audio gateway and opens Voicedial.
In the registry, there is a setting under:
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\
Under that entry, there is a path setting, which defaults to the VoiceCommand software that ships with the phone. If the path is changed to point to VoiceDial, it works great. I used:
\Program Files\Fonix\VoiceDial2EN\VoiceDial.exe VoiceCmdEnable DWord Value: 0 LaunchAPEnable DWord Value: 0
For version 2.1 make sure Bluetooth is enabled
Try at your own risk.
|
|