I had trouble getting my Bluetooth headset to activate Voice Command (VoiceCommand), and the following solution fixed it. Just sharing.
http://forum.xda-developers.com/showthread.php?t=296171
btw, I am using a Tmobile Wing with OpenTouch 3.0 and separately installed MS VoiceCommand 1.6
Related
So many new WM5 releases... Still no bluetooth fix?
Hi
Unfortunately - yes.
But good guys are working on it.
It's matter of short time when Ivan's ROM will have it.
It's the only thing that keeps me staying on WM2003...[/b]
Dont count on it being fixed, not with the MS stack anyway.
lets all cross our fingers and hope that widcomm 1.7 works
i doubt there would be a fix with MS Stack, unless we can get broadcom or widcomm stack running.. then everything, including A2DP should run just fine.
I'm currently testing the broadcom/widcomm 1.71 stack, result are still inconclusive, but its better than the M$ one
Everything apart from bluetooth voicedial.......
Hi
Most of you already know this, but:
The newest relase of Ivan's ROM has the BT disconnect issue resolved permanently.
Have fun with it
Yes it is a step in right direction, but still have nasty bug with most BT Headsets, no voce in call. I am sure that mamaich ivan and Midget_1990 will find a solution for this bug soon. We will just wait and see
any progress?
I have widcomm stack 1.7 in my ipaq 6965, and I can control audio input/output over bluetooth by press of button on the headset (press and hold for 2 sec it'll trigger a redial AT command I think) but it just can't trigger an application like voicecommand in the pda. What's fustrating is that there's no documentation of widcomm sdk, so there's no way to figure out what's required in the registry (plus what dll needs to be develop) in order to handle the AT+CPR200 (I think that's the AT command for bluetooth button press) event.
If somebody has some clue or progres, please share here and hopefully more brains can be put together and fix this once and for all!
I do not know what is the problem with your ipaq, but the bt bug is fixed now, you can search the forums for it
xplode said:
I do not know what is the problem with your ipaq, but the bt bug is fixed now, you can search the forums for it
Click to expand...
Click to collapse
hi, my problem is not about auto-disconnect or no sound. everything works perfectly fine with 1.7 widcomm stack except that I can't do voice dial. specifically, I can't activate a voice cmd application with the press of bluetooth button. When I press the button, the audio streaming is turned on (and mic is working over bluetooth) but it just doesn't start the voice cmd application, which I have to manually turn it on from the pda device.
if your BA's widcomm can enable the voice dial, I would like to request if you can share your registry and the necessary dLL
we dont use widcomm anymore because someone fixed the M$ stack.
FYI
Just installed MS Voice Command 1.6 Retail (1.60.4622.0) and it seems to run fine on my AKU3.2 1.3.2
Does it work over bluetooth handsfree voice dial activation?
Mr_Ding
do you use bluetooth handsfree to voice dial?
i have been trying to get it working with IIs with no luck (I use ITech mini II bt handsfree + XDA IIs)
If not, I guess Cyberon voice dialer is better than VC1.6 - less memory and very accurate.
cheers
No, haven't tried bluetooth handsfree.
I defined 1 hardware button as Voice Command, press it, then I say "Call Mary at home" for example.
Will try next week (have my BT headset at work, since I hardly use it)
joseph.sapri said:
Mr_Ding
do you use bluetooth handsfree to voice dial?
i have been trying to get it working with IIs with no luck (I use ITech mini II bt handsfree + XDA IIs)
If not, I guess Cyberon voice dialer is better than VC1.6 - less memory and very accurate.
cheers
Click to expand...
Click to collapse
Check this thread for a cab file that allowed me to get VC to work via BT...
http://forum.xda-developers.com/showthread.php?t=283412&page=5
more questions
ercave1,
Thanks for the info. I checked the forum and got the cab file. At the moment I have not tried it, however got some questions:
1. After installing VC1.6, wireless icon disappear from the tray... where has it gone? does it affect wireless funct? After uninstalling, the icon comes back... weird...
will try the cab later and give feedback...
cheers
Was anyone able to trigger the Ms VoiceCommand from a Parrot kit ?
I have a Parrot CK3000 Evo, and the Kaiser won't launch the msvc invit
... while it does perfectly from a bluetooth heaset (motorola something)
At the opposite, my Blackberry 8820 works great...with the Parrot (else I still don't like Blackberry OS )
any idea?
Thanks
It works fine for me with CK3000 Evo (v5.08), Kaiser and Voice Command v1.6. It even anounces incoming calls and reads messages
The only problem is that sometimes the Parrot fails to start up correctly and needs to be power cycled.
Thanks Steve for the input,
I'm wondering if you recorded some voicetags in the Parrot ?
(maybe that would explain why it trigger the VoiceCommand invit)
Mine is just checking its own memory, but it does not pass the ball to the VoiceCommand software.
(I had the Parrot weird association once, it was acting like when the phone is sending audio.... but of course that was not the case, and even turning off the BT on the phone didnt help. Next time I started the engine, everything fine again...)
Edit : Now I see, don't ever record voicetag on the Parrot itself (else it won't trigger the phone voicecommand)
That was my problem (clearing the kit memory RED+GREEN, and repairing fixed it !)
I'm having a rather odd problem using Dutty's 6.1 rom with Microsoft Voice & my bluetooth.
While it works fine when it comes to initiating itself appropriately, once the connection between VC and the bluetooth are supposed to terminate, they don't, and consequently all sounds are routed to my BT after using VC.
I'm assuming it's something to do with an incompatability between WM 6.1 and Voice Command because I didn't have this issue with Dutty's WM6-based V4 rom.
Any ideas?
I remember seeing some sort of registry tweak that could fix certain problems with VC, but I can't find the thread using the same search keywords I used before.
Still struggling with this one. Thus far the only way to get the BT to turn off is to either power down the Kaiser, the Bluetooth, or disable BT on the Kaiser.
i cant find how to get this working on my kaiser.
ive got s2p i heard thats supported
jayjay8585 said:
i cant find how to get this working on my kaiser.
ive got s2p i heard thats supported
Click to expand...
Click to collapse
Yes, s2p will work ok with wireless stereo bt devices. I use motorola s705 and t505 a2dp devices. I don't think that the apps need to specifically support a2dp since every multimedia app I have used has worked.
Sometimes the a2dp connection is not established when I want it. Note that both devices also work in modes other than a2dp.
BatteryStatus includes optional tray icons for phone, wifi and BT. The BT icon menu includes an a2dp indicator/on-off switch. Sometimes i use this for the T505 to force the a2dp connection.
A2DPToggle also works. It is a Today plug-in. I read that it is a battery hog but haven't confirmed. If you can't get a2dp working using A2DPToggle then you might want to dig deeper into your phone/rom.
I am using stock WM 6.1 roms from HTC or at&t (official - test) generally without problems but have to muck around sometimes to get a2dp working by either toggling BT on/off on either the handset or BT device.
i want to kno how to use it tho there doesnt seem to be an app for it i tried finding my mates stereo with my bluetooth stock app and it didnt work how do you initiallise a2dp on the stock roms.