Voice Command Caller Announcements on BT - Real FIX

[Big D5]

Originally Posted by avaya

i wonder if it could be because we are using the vc oem instead of installing it?

My MSVC is installer the old fashioned way, no oem here so I don't think that's it. All the other commands work like asking the time or date, was that working before the edit?

[LeanGreen]

Originally Posted by avaya

i wonder if it could be because we are using the vc oem instead of installing it?

Originally Posted by Big D5

My MSVC is installer the old fashioned way, no oem here...

But it works for Big D5, and not for avaya, so perhaps that is it... Anyone else have it installed in the conventional manor that can test this?

[sonnemad]

What if the MSVC installer makes different changes to the registry based on what AKU you have installed. It may detect if inband audio is available and add/change the appropriate registry entries at that time. Since the VC OEM's were created before the true AKU3.5's were available for the apache, they are incomplete in regards to the call announcements.

Just a thought

--Dan

[jimnutt]

Based on this snippet from the

Incoming caller ID announcements will be spoken via the phone speaker on devices with a Windows Mobile build prior to 15097.3.0.0. To check which build is on your device, go to settings >about or start >controlpanel >about. If your build number is lower thatn 15097.3.0.0, this will be true for your device.

VoiceCommand web site, I think sonnemad has hit the nail on the head. So, I'm building a ROM without VC, installing it and seeing if it works. If it does, I'll compare the registries and post the differences

[jimnutt]

No joy, still sends the output to the speaker. I'm not sure what's up, as it should work according to the MSVC site. I'll explore it more later.

[LeanGreen]

I'm still having good luck with this... It seems to send the ring tone through the headset though, so I've just been using it in combination with vibrate, rather than ring.

The only time it has sent it through the device speaker for me is if it doesn't recognize the headset. It usually happens if I've received a few calls without using BT, then turn the headset on. If I turn on the headset and call myself from another phone, the first announcement will sometimes go to the speaker. Then, later, if I let it ring long enough, the announcement transfers to the headset. On subsequent calls it works perfectly.

I can get it to go on the first try if I turn on the headset with the device powered on and issue a voice command through the headset. It's almost like VC is operating separately from the phone and BT stack in the background, much like Bad Sectors's IDTransfer, and has to know the headset is available and ready to go. Then, when a call comes in, it performs it's own OEM version of IDTransfer.

[PaulFix]

I have tried the above settings and still no luck, phone rings, and I have to press my headset button for the phone to transfer the call to my ear, btw I use a Moto h350

[cobra04972tx1]

No luck here either. Man I was hoping I had found the solution to a long time annoyance.