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
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.
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
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
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.
Hello,
I have been doing a lot of research on this problem and I can't find any solution to this. My voice command on my updated phone from windows mobile 6.1 to 6.5 does not announce incoming calls over my bluetooth head set. I have a Jawbone Prime and I ONLY once have heard it announce a call over the BT headset and I beleive this was under version 6.1 of windows mobile. It announces just fine over the regular speaker but not anything over BT. Does anyone have a solution to this? Everything else works just fine just not this, which I find to be the most important part. Yes the options are checked under voice command to announce incoming calls. Any help would be great!
Thanks.
Update
It appears that the bluetooth announce call stuff works just fine over bluetooth. The only thing you need to do other than making sure VC is enabled to announce is go under the bluetooth settings and select advance and then audio and under the audio settings check the check box for play system sounds on remote hands-free device. After doing this it worked just fine. Also before I did any of this I did a master reset on my device just incase any of the past reg. edits were possibly a problem, and I just wanted to make sure I started from a clean slate. But it works just fine!
decepts said:
Hello,
I have been doing a lot of research on this problem and I can't find any solution to this. My voice command on my updated phone from windows mobile 6.1 to 6.5 does not announce incoming calls over my bluetooth head set. I have a Jawbone Prime and I ONLY once have heard it announce a call over the BT headset and I beleive this was under version 6.1 of windows mobile. It announces just fine over the regular speaker but not anything over BT. Does anyone have a solution to this? Everything else works just fine just not this, which I find to be the most important part. Yes the options are checked under voice command to announce incoming calls. Any help would be great!
Thanks.
Click to expand...
Click to collapse
Possible fix
I downloaded a an app called high tech speaking. Initially it did not work BUT for some strange reason, it began began announcing the caller via voice command. The problem is that i could not push the talk button on my headset to answer the call. I had to push the button on the phone. This, however, is a step in the right direction. I am not a programmer by any means but someone out there is. Get this app and correct problem for all voice commanders out there.
decepts said:
Hello,
I have been doing a lot of research on this problem and I can't find any solution to this. My voice command on my updated phone from windows mobile 6.1 to 6.5 does not announce incoming calls over my bluetooth head set. I have a Jawbone Prime and I ONLY once have heard it announce a call over the BT headset and I beleive this was under version 6.1 of windows mobile. It announces just fine over the regular speaker but not anything over BT. Does anyone have a solution to this? Everything else works just fine just not this, which I find to be the most important part. Yes the options are checked under voice command to announce incoming calls. Any help would be great!
Thanks.
Click to expand...
Click to collapse