i dont understand all this. how does the voice command work on the 750v through blue tooth and doesn't on the 700wx?
one answer was the voice command was writen for 16 kbs and bluetooths run on 8 kbs. i dont understand all this so i'm just asking, how come it worked on the ppc6700 and xv6700?
on the 750v, did thay change the voicecammand to work on 8 kbs with the 750v?
is it all in the bluetooth stack?
is this a new version of voicecommand that is not offered on the microsoft site yet? some thing like voice command 2.0
bottom line is this is what i miss the most from the 6700. is this something that we can see extracted from the 750v, or are we going to have to pray it comes with the update?
thanks, cody
Voice Commands
Yes, this is something that has to do with the Stack and the Bluetooth driver supporting. The software update for the 750 will add this feature.
Related
Since the 750V can use voice command through the bluetooth headset is there any chance that the developers will get this working on the 700wx?
There is a chance as long as the hardware is up to it on the 700wx.
this is the only thing i really want off the 750v for my 700wx. i can only hope
"codyPPC" seems like you and I are in the same boat. I see you in all of the other forums asking the same questions as me. The 700wx would be the absolute perfect phone for me if ONLY it had bluetooth voice command digit dialing and bluetooth name dialing. The other things from the 750v I don't care about and most likely wouldn't use them. But only if someone could just get the bluetooth digit and name dialing working on the 700wx then I would be all set.
any progress on this and or is anyone currently working on this? i cant belive there arent others as needed for this as i.
thanks, cody
well, benjimatt with hannip for the assist are attempting to replace all the BT files on the 700wx with the 750 ones, which would in theory allow to this to happen (as well as a2dp), but no one has tried it yet.
http://discussion.treocentral.com/showpost.php?p=1115023&postcount=44
basically you are hitting a limitation of the version of Voice Command on the 700wx. The 750v's Bluetooth isn't even supported but *kind of* works with some headsets. Microsoft won't support BT Voice Dialing officially until Crossbow so anything that works beforehand is out of luck. This is an OS limitation and not a Palm/Hardware 700wx limitation.
As somebody mentioned before, maybe using the Voice Command out of a newer AK may work.
jacinf said:
basically you are hitting a limitation of the version of Voice Command on the 700wx. The 750v's Bluetooth isn't even supported but *kind of* works with some headsets. Microsoft won't support BT Voice Dialing officially until Crossbow so anything that works beforehand is out of luck. This is an OS limitation and not a Palm/Hardware 700wx limitation.
As somebody mentioned before, maybe using the Voice Command out of a newer AK may work.
Click to expand...
Click to collapse
not to argue, but even with a different version of voicecommand (1.6) it still doesn't work. it has been said that it is in the bluetooth stack not voicecommand.
Hi I have an Alpine running 2003 se, with Fonix voice installed. I am not getting on very well with this software, what I would really would like is something like the software in my Razor V3, it gives me the ability press the button on my Blue tooth headset to voice dial a number, and when an incoming call is received it says the name in the bluetooth headest before ringing. Is there any software available that could do that with the Alpine ?
Microsoft Voice Command does this, and you can buy it on www.handango.com but check to see if it works on WM2003 as I'm not sure off the top of my head.
Hi unfortunately Voice Command only works with WM5
Maybe someone knows of another software that will do the job....
older versions of voice commander works on 2003
New Problem with VC 1.6 for Pocket PC and Bluetooth. I cannot use VC through the BT headset.
I check the Voice Command configuration and enabled the BT notifications. No joy: commands and notifications just pass through the speaker. My bluetooth headset is a Jabra JX10 Series 2 and it works well during call conversation, but when I press the VC activation button, the commands are "listened" through the Treo's mike. Run simple experiment: If you "cap" the mike with your finger and try to command through the BT headset it does not work. Tried to Softreset multiple times, re-pairing the headset..no joy.
Since it was well advertised that WM6 was carrying the BT voice command feature, I was really disappointed and getting a bit frustrated. Am I doing something wrong? Did I forget something?
Any help is greatly appreciated.
Rob
Configurationalm 750 unbranded. I upgraded it to WM6 (CE 5.2.1239 Build 17746.0.2.4) VC 1.6 for pocket PC
I've had the same issue with my Moto HF850 BT car kit. Eventually the bond "breaks" and the two wont communicate until I soft reset the treo. Wonder if the BT stack is getting updated in this mystical AT&T ROM release?
I made some more investigation on the net and apparently this issues should have been solved by the WM6 ROM release PALM announced. I have installed the generic unbranded but it does not cure the problem. Please let me know if the ATT ROM works or not. This can be very interesting.
I think VC is a great software and I really enjoy it.
I have looked around..Web Forum community is starting to call for VC 1.7 and WM7...we will see.
Voice Command 1.6 issues with BT on palm 750: PROBLEM SOLVED
Since my head is sometimes harder than a granite block I made some further experiment with my Palm 750 Registry and found that the issue is really on the Audiogateway registry.
When VC 1.6 gets itself installed, it modifies the following registry key from:
FROM: (Original Registry without VC1.6)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway:BTAGExtModule = BTAGExt.dll
TO: (with VC1.6 installed)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway:BTAGExtModule
=\Program Files\Voice Command\vcbthag.dll
This modification does not work on my palm 750 .
When I have set this registry back to BTAGExt.dll ( I have used CEregedit to make the replacement) my Jabra BT Headset was able to listen and deliver Voice Commands to the device and viceversa the device was able to deliver messages and notifications to the BT headset.
Only missing element is Music: Music is still played through the Palm speaker, but I am fairly happy to make calls handfree!
Better than nothing. I hope this hint will be helpful to others. Please let me know if this works.
Regards
RC
Did anyone manage it to run MS VoiceCommand via a bluetooth headset on this device?
Ok, I installed the latest version of voice command on the new O2 XDA Orbit 2.
It works good with the bluetooth headset without any patches.
However call notification does not work. Does anyone have any idea for that?
How can I disable Voice Command and make all sound being routed to the headset?
The solution with Mortscript (posted somewhere else in this forum) does not work... any other idea?
ulischultz, how did you manage to get ms voice command to work? I've got the HTC Touch Cruise, and I can't get MSVC to work via bluetooth. Works fine on my AT&T tilt with no hacks.
Dave
I am having the exact same problem: voice command works but will not announce incomming calls. I can't believe how much I've become dependent upon this feature. As for getting it to work, there was nothing special that I had to do other than install it and soft boot.
http://www.jetwaremobile.com/
I was having problems with some random disconnects of my TC from the car Parrot 3200LS BT Handsfree CarSystem.
I found this program mentioned on another site(http://www.htcwizardweb.net/node/456 ):
JETware Mobile (http://www.jetwaremobile.com/
I installed the trial today and so far it appears to be making a significant difference with the TC and MS VoiceCommand.
T
Hey there, I'm running Treo750 Unofficial WM6.1 OS5.2.19199 build 19199.1.0.0 - Standard OEM Version, which doesn't have Voice command included.
I was wondering where I might be able to find a cab file that installs Voice command 1.6 for WM6.1 on my 750. Would anybody be able to point me in the right direction?
just search the whole forum not the cab. The cab is for all Windows Mobile phones not just one particular for the Treo 750
found it, thanks, works like a charm.
are you able to voice dial with a bluetooth headset using VC and 6.1 ??
jcrompton said:
are you able to voice dial with a bluetooth headset using VC and 6.1 ??
Click to expand...
Click to collapse
If you have the 19209 build, that shouldn't be a problem.
kareem9nba said:
If you have the 19209 build, that shouldn't be a problem.
Click to expand...
Click to collapse
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
peeps said:
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
Click to expand...
Click to collapse
bump....anyone???
peeps said:
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
Click to expand...
Click to collapse
double bump...
Search for 'jabra bt registry' on this forum. I found a registry hack, that says this:
When VC 1.6 gets itself installed, it modifies the following registry key from:
FROM: (Original Registry without VC1.6)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Au dioGateway:BTAGExtModule = BTAGExt.dll
TO: (with VC1.6 installed)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Au dioGateway:BTAGExtModule
=\Program Files\Voice Command\vcbthag.dll
When I have set this registry back to BTAGExt.dll ( I have used CEregedit to make the replacement) my Jabra BT Headset was able to listen and deliver Voice Commands to the device and viceversa the device was able to deliver messages and notifications to the BT headset.
Simply make the registry change and soft-reset the phone, and you are back in business.