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.
Related
I've searched everywhere but cant find a solution to this: I bought the HTC wired usb headset for the Tilt. With Cyberon voicedial, the button on the headset would activate the app and worked perfectly. As I prefer MS Voice Command, I then went ahead and uninstalled Voicedial and installed VC, but button doesnt work now. Anyone know how to remap the headset button to voice command?
Try this reg, should do it.
Thanks, I'll give it a try...what changes does it make?
Sometimes after installing MS Voice Command you need to do a reset once or twice before the BT headset is reconized properly. (battery out and back in...) And, some BT headsets don't work well at all. MS's BT driver set has a history of being bad.
I think you misread my post...I was asking about the WIRED headset, not the BT one.
okay my question is that the software that came with my tilt- voice dail thing,cyberon will only work if I activate it by clicking the icon, however, I can't start it with a BT headset that I have, can anyone help?
well first fo all did you even activate it for you to use it?
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
Hi together,
after all my cruise is now working quite good, and even the odd bt-headset problem is solved after installing the two bt-patches (I´m using Bepe V.0.67).
But now: I can´t commander voice command while pressing the speak button of my Nokia BH-602 headset. This worked before installing the patches.
So: Headset works, but without vc function.
Anybody got a workaround for this problem? Than cruise is almost perfect for me.
Thanks
amcom
That function did not work with my Jabra BT3030 before and still doesn't after the hotfixes.
edit: actually on further mucking about it does work. I have both BT hotfixes installed and it now works.
voice commander now works with my plantronics headset but it never ever dials the right person.. I had a blackberry pearl before this phone and the voice dailing worked even when using a power tool, but the one on HTC sucks real bad
OEMAGW.dll
After patch, OEMAGW.dll chanched, 2x Bigger.
I also want to run MVC BTbutton
This for OEM progs working, but sounds out device speaker
"Path"="\\WINDOWS\\voicecmd.exe"
I found a solution, working for me. After reinstalling an original ROM without MS VC implemented I installed VC seperate. After that I installed a small programm called jetware mobile. This programm routes all signals to the headset.
So everything works fine now. I´m happy, hope you´ll be too!
amcom
I have an Xda Orbit 2 (aka Polaris aka Touch Cruise) with MS voice Command 1.6 patched as per the instructions given at the link below in order to make incoming call announcements work.
http://forum.xda-developers.com/showpost.php?p=1548114&postcount=5
The above fix worked fine on my original Orbit (Mark 1) apart from the fact that incomimg hotmail emails are not announced. When I upgraded to the Orbit 2, I again installed the same patch and it worked again (minus hotmail announcements again) BUT with one additional issue: The blue Bluetooth LED never comes on. I can soft reset, power off and on again, turn Bluetooth off and on but nothing makes any difference. The lamp stays off. However Bluetooth works fine - I can transfer files to and from my PC and my Bluetooth headset works.
The practical issue is if for some reason for example a transfer fails or the headset has problems, I can't tell if Bluetooth has turned itself off or is still on without going into Comm Manager. If I'm driving and trying to use the headset I have to stop the car just to do this!
Today I did a hard reset. The Bluetooth light worked fine until I reinstalled Voice Command.
Does anyone know of a fix for this? A registry entry to change maybe?
Thanks in anticipation.