Voice Command Over Bluetooth

[rjefferis]

Voice Command 1.6 seems to be a bit of a nightmare and i have given up on my hermes for now.

My trinity though is almost ok, the only thing that doesnt work is when i push the voice button on the headset the sound comes out the phone speaker.

If i use the button on the phone though the sound comes out the headset.

How can i change the action of the button on the bluetooth headset to do what the button on the device is doing.

Thanks all.

Rob.

[anonimo]

If i use the button on the phone though the sound comes out the headset.

How can i change the action of the button on the bluetooth headset to do what the button on the device is doing.


FYI I use a SonyEricsson stereo BT headset and I don't experience this problem.

[FuzzMunky]

Rjefferis, I experience the same problem as you.

I have a Jabra JX10 headset.

Confirmation voice always comes out of phone speaker, not headphone... and irritatingly, it takes microphone readings from the phone body too. Kind of defeating the idea of hands free voice dialling.

[rjefferis]

Rjefferis, I experience the same problem as you.

I have a Jabra JX10 headset.

Confirmation voice always comes out of phone speaker, not headphone... and irritatingly, it takes microphone readings from the phone body too. Kind of defeating the idea of hands free voice dialling.


Yeah this seems to be the problem on the hermes too. On mine it works correctly if i use the voice dial button on the phone. So the button on the headset and the button on the phone must be calling slightly different functions. All i need to know is what reg key i have to edit to make the headset button do the same as the phone one.

Try yours to see whether it works using the phone button. I think maybe my a2dp is getting involved somewhere as well.

[saminegm]

There is an option about Notifications and Bluetooth devices in the Voice command settings... does this solve you problem?

[FuzzMunky]

Not for me.
It is set to read only through handsfree. I havent got my headset here, so I will see what happens if I switch it to the opposite like rjefferis implied.

[rjefferis]

yeah i doesnt make a difference using the options in voice command.

I think maybe when i push the button on the phone it works through the a2dp to the headset which obviously it shouldnt be.

When i use a non stereo headset then i think it always comes out the phone no matter what.

[shoey5]

There are a number of threads regarding this issue and some semi-working fixes to get initiating a voice call through a mono bluetooth headset.

The problem seems to be a difference in the trinity passing audio through the audio gateway using a mono bluetooth headset. Not sure if this is a problem with the implentation of Microsoft's bluetooth stack on the TyTn/Trinity but I'm assuming that's the case.

According to Microsoft's Voice Command site, they indicate that the TyTn (put the Trinity in the same situation) passes audio through the device speaker. They also make note that devices running Windows Mobile build prior to 15097.3.0.0 will pass announcements through the device speaker. This leads me to believe that Microsoft fixed audio to a mono bluetooth headset but I've seen lot's of messages from people running roms higher than this version who still have the problem so sounds like HTC hasn't implemented it.

I've sent emails to HTC who indicate that it's a 3rd party program and there is no guarentee they will fix it as it's a Microsoft problem. I haven't been able to get word from Microsoft if it is being fixed but from their website, seems both parties are passing the buck on this one.

Considering HTC's lack of commitment in releasing updates for their branded products and the delay, we probably won't see another rom after their first release for a while if any since they seem more committed to releasing new products increase their bottom line without keeping their current customers happy. So if it's not in their upcoming rom update and Microsoft isn't releasing a fix, we could be waiting a while. I'd recommend anyone who cares about this issue to send an email to HTC Support. You'll get the generic response but hopefully if enough people complain about it, a fix might fall into their update