Bluetooth Voice Dialer Issues

[furbearingmammal]

I've found the old standby of "talk slowly, clearly, and loudly" is actually incorrect on this -- talk loudly, clearly, and naturally works a heck of a lot better!

 

[JasonD18]

I've found the old standby of "talk slowly, clearly, and loudly" is actually incorrect on this -- talk loudly, clearly, and naturally works a heck of a lot better!

Funny enough, the voice recognition on the S4 itself worked amazingly well. For some reason (custom rom?) the only way I can get the phone to dial is by saying "Voice Commands", which then brings up the Droid's built in voice recognition.

And for the record "Dad" was recognized as "Matt" and "home" was recognized as both "Hans" and "Molly".

 

[hobbes105]

"and never works, dial amy, calling dave on mobile no prompt to bail."

I've asked this before. Why is there no confirmation prompt?

This is one of my few complaints of an Android phone. Other phones I've used always gave you that confirmation prompt before dialling and I always used BT voice dial, but I just can't use it any more because I'm sick of it calling the wrong person with no chance to stop the phone from dialling first.

 

[furbearingmammal]

I ALWAYS get a "dial home at home" or if it's glitching "dial 854-677-3256" before it dials. Are you running stock?

 

[hobbes105]

I'm running CM6 Stable.

I do get the home or work prompt, but only if the contact has 2 different numbers stored. Any contact with only one number will call without a prompt. (and it usually picks the wrong contact)

 

[furbearingmammal]

I had to put the RC-3 VoiceDialer.apk back on to get it to work at all, but the RC-3 apk did EXACTLY what I described.

 

[hobbes105]

Ok, I feel stupid now. I just played around with it and I am getting the prompt. Maybe I remembering this from another rom (I've had so many on this phone I can't remember)

One thing though, the prompt is not audible threw my A2DP ear piece. I only get a pop up notification on the screen. I swear I remember hearing prompts threw the ear piece before. A pop up on the screen is nice, but does not help if the phone is in a belt pouch.

 

[furbearingmammal]

Have you tried to put the RC-3 .apk on in place of the stock 6.0 one? It works great and gives you that notice you wanted. Yeah, typing the commands in is a pain, but it works fine.

Of course, with 6.1 right around the corner you might not need to do anything unless you want it fixed RIGHT NOW! :woot:

 

[hobbes105]

furbearingmammal,

Thanks for the help. I just installed the apk and I do get the voice notification, but how do you cancel when the phone picks the wrong contact with out having to get the phone out of your pocket and press cancel. I'm back to the same problem of the phone telling me who it's going to call and then it just calls that person. I can't seem to stop it from calling when it picks the wrong contact.

I just accidentally called a customer of mine at 11:15pm and nothing I did would stop the phone from calling. This is why I just gave up on voice dialling on Android.

I would like to be able to say "no" or "cancel" when it reads back the wrong contact. If I need to hit cancel on the touch screen, that kind of defeats the purpose of having the ability to voice dial - I might as well just dial from the touch screen. If this can be done, I'm not sure how.

 

[furbearingmammal]

I just press the button on my headset again. It kills the call before it can start, at least with my setup. I got so used to having to cancel 3/4 of all my calls I normally keep my finger on the button, ready to press, whenever I voice dial.

 

[giant25]

Is anyone having an issue where you initiate a call from your BT headset, but the BT dialer hangs on the "Starting Up" screen and never prompts for a command? I usually get one or two calls in, and then my BT "halfway" quits. Basically, no sound comes through the headset anymore except the beep when I hang up. I usually have to at least power off the headset, sometimes, cycle BT on the phone, and sometimes have to reboot. Anyone else? Could this be a kernel thing or more likely ROM-related? I have a Jawbone Prime, BTW. Thanks.

 

[furbearingmammal]

What ROM are you running? If it's a CM 6.1 RC, which one? What kernel?

I occasionally have had that problem, but it's been much better since I moved past RC2 -- of course, I skipped 3 altogether and have been running a a nightly build since. If it freezes on the voice dialer's load I have to unlock my phone and hit the back softkey. That clears it and it works the next time I hit the button on my headset.

Rather inconvenient while driving, however.

 

[giant25]

What ROM are you running? If it's a CM 6.1 RC, which one? What kernel?

I occasionally have had that problem, but it's been much better since I moved past RC2 -- of course, I skipped 3 altogether and have been running a a nightly build since. If it freezes on the voice dialer's load I have to unlock my phone and hit the back softkey. That clears it and it works the next time I hit the button on my headset.

Rather inconvenient while driving, however.

Good to know others have seen it. I'm actually not running a CM ROM...yet. I'm running UD 1.0.0 with Chevy's ULV 1.0 (would the kernel matter for this?) GHz. I was actually reading in here with the thought of jumping over to CM, and I found this thread. I also noticed that UD "borrows" a lot of material from CM, so I thought I'd see if it's having some of the same issues. I use bluetooth everyday, so I'd love a reliable option. Thanks.

 

[furbearingmammal]

Give it a try. Worst that can happen, really, is that you have the same problem.

It's VERY rare that I have the issue, though.

 

[giant25]

I think I will give it a shot. I saw the power control on the notification pulldown in person today, that was cool. Is anyone having issues with Jawbone Prime headsets? I just read another post about a similar problem and that person had a Prime like me. Could be a coincidence, or not...