[isomaniac]

I have both A2DP and handsfree profiles. I am using the i-tech S bluetooth handsfree (bthf) I have no problem to listen to Windows Media Player and TCPMP via A2DP profile with stereo sound output.

I changed the registry and then:

1. Connect the handsfree profile only, nothing happened when I press the button on the bthf. I can activate the Voice Command by pressing the hardware button on xda2i though. But even that, the command read out by Voice Command can only be heard HALF via the bthf.

2. Connect the A2DP profile only, nothing happened when I press the button on the bthf. I can activate the Voice Command by pressing the hardware button on xda2i though. But even that, the command read out by Voice Command can only be heard HALF via the bthf.

3. Connect the both handsfree profile and A2DP profiles, nothing happened when I press the button on the bthf. I can activate the Voice Command by pressing the hardware button on xda2i though. But even that, the command read out by Voice Command can only be heard HALF via the bthf.

What have I done wrong?

[isomaniac]

I have both A2DP and handsfree profiles. I am using the i-tech S bluetooth handsfree (bthf) I have no problem to listen to Windows Media Player and TCPMP via A2DP profile with stereo sound output.

I changed the registry and then:

1. Connect the handsfree profile only, nothing happened when I press the button on the bthf. I can activate the Voice Command by pressing the hardware button on xda2i though. But even that, the command read out by Voice Command can only be heard HALF via the bthf.

2. Connect the A2DP profile only, nothing happened when I press the button on the bthf. I can activate the Voice Command by pressing the hardware button on xda2i though. But even that, the command read out by Voice Command can only be heard HALF via the bthf.

3. Connect the both handsfree profile and A2DP profiles, nothing happened when I press the button on the bthf. I can activate the Voice Command by pressing the hardware button on xda2i though. But even that, the command read out by Voice Command can only be heard HALF via the bthf.

What have I done wrong?

[Rydawg]

Hello All,

I have a few quick ?’s about MS Voice Command activation from a BT headset.
I have read the JasJar tips and Tricks and I tried to drill down in the registry of my (Alltell) PPC-6700, which I believe is the same as the K-Jam (Right?) and have seen that these tricks work… But after the OEM Folder I don’t have VoiceCommand string or a folder. Now my PPC-6700 did not come with ANY voice dial software and that is why I bought MS Voice Command could this be what my problem is? I would REALLY like to activate VC through a BT headset.
Thanks again for your time.
rydawg

[Ed Hansberry]

Originally Posted by Rydawg

Hello All,

I have a few quick ?’s about MS Voice Command activation from a BT headset.
I have read the JasJar tips and Tricks and I tried to drill down in the registry of my (Alltell) PPC-6700, which I believe is the same as the K-Jam (Right?) and have seen that these tricks work… But after the OEM Folder I don’t have VoiceCommand string or a folder. Now my PPC-6700 did not come with ANY voice dial software and that is why I bought MS Voice Command could this be what my problem is? I would REALLY like to activate VC through a BT headset.
Thanks again for your time.
rydawg

It isn't the same. The iMate JasJar and K-Jam come with bluetooth voice command software that you have to assign a voice tag to. The registry hack simply tells the device to use Voice Command instead of the built in software. I don't think you can simply install VC and add this registry command to any device and get BT voice dialing to work.

[MaddogX007]

It seems these board msgs are old, so I hope someone is still reading this thread. I jut got the MDA Vario, which is identical to the Qtek 9100, K-Jam, and HTC Wizard. I tried this hack using a registry editor, and for the most part it worked great, WHEN it works. I am not sure what controls VC and bluetooth headset. I know Voice Command does not support, yet, bluetooth on Mobile 2005. Well like I said, when it works, it works great! But for reasons I am not sure, it drops off. I have no issues using VC directly from the pocket pc's assigned button. Voice Command is a much better product then Voice Dial period. Not sure why Microsoft who developes Voice Command, and Mobile 2005 did not incorporate VC into the OS.

With the registry hack I can't get VC to work using the connect button on the bluetooth, like Voice Dial did period, only when I press the assigned button can I hear VC via the bluetooth, but again, it lasts for a short while, then drps off. It seems I have to play tricks like, soft reset the device, then press the bluetooth connect button, and the assigned Vc button, and all of the suden, like magic, I hear VC on my headset, and it works fantastic while I am giving VC commands. But again, after a one call, in or out, or in a certain short period of time, it drops off again. Very frustrating, but still better then Voice Dial. I still leave the hack cause I would rather use Voice Command, even if it's from the device, and once in a while, when VC wants from the bluetooth.

The crazy fact is, it worked beautifully with my Mobile 2003 H6315, VC never gave me a problem with bluetooth.

Any ideas?

[adchaffey]

Originally Posted by MaddogX007

I tried this hack using a registry editor, and for the most part it worked great, WHEN it works.

@MaddogX007 - I think I might have finally found someone with the same problem as me! I also have the MDA Vario and have made the registry hack to activate Voice Command from my Sony Ericson headset. For me, the headset will only work the first time after a soft reset EXCEPT if I issue the command "cancel". Is this the same problem you are having? Or have you found a solution?!?

[martin_ayton]

I'd just like to record that I've just applied this hack to my MDA Vario II(which did come supplied with Cyberon Voice Dial) and it works great . Man I've been missing making calls over my headset since I handed my SonyEricsson T39m over to my wife. In reality, I should be really annoyed with Microsoft, HTC and T-Mobile for making a basic requirement so hard to implement, but now it is working... I'm like a kid at Christmas

[ctmagnus]

Originally Posted by martin_ayton

I'd just like to record that I've just applied this hack to my MDA Vario II(which did come supplied with Cyberon Voice Dial) and it works great .

So, are you using this hack with the Cyberon app or the MS app? (Sorry, your post is rather ambiguous )

I'd love to get the MS app, but ROM space is a serious issue for me.

[martin_ayton]

Originally Posted by ctmagnus

[So, are you using this hack with the Cyberon app or the MS app? (Sorry, your post is rather ambiguous )

I'm sorry - I was following on from the posts above and - I admit - I wasn't as clear as I could have been.

The phone arrived with Cyberon Voice Dial bundled in the extended ROM. Therefore, I *did* have the registry item referred to in the original post. That meant that I could modify the registry item as suggested to cause the button on my BT headset to start MS Voice Command instead. I had to buy and install MSVC separately.

It has worked fine. The only minor issue is that the first time I use it after a pairing, the headset button starts VC, but the sound is not routed to the headset until a call is extablished. Second and subsequent times work perfectly. The easy work around is that as soon as my headset is 'connected' I ask MSVC it what the battery level is. It's a good check that everything is working and after that, I'm ready for calls.

I have a 2GB microSD card and I have installed most of my extra apps to that. MSVC has to be installed to the device. I know what you mean about the memory thing though - coming from my BlueAngel to this has been a shock.