Jelly Bean Bluetooth Voice Dialing is totally useless

**techie1961** · 07-20-2012, 07:50 PM

I just received the update to Jelly Bean and the voice dialing over Bluetooth is totally useless. I did some searching and noticed that others are having similar issues. When i was using ICS, I got a relatively good recognition hit but with JB, it doesn't find a single name; ever!

Google, please do something with this ASAP. I desperately need voice dialing as I am on the road all of the time and have to use Bluetooth.

**iKron** · 07-28-2012, 10:03 PM

Just use Jeanie App until Google gets this whole asinine CrApple Universal Search w/ Voice Actions thing ironed out. They had to pull it when iCrAppleholics started crying about Google Voice Actions being better than Siri. So don't blame Google or your device maker for stupid iCrAp removal of Universal Search and Voice Actions.

We need to start a drive and make some noise about this. So this asinine bunch of morons at the Appeals Court realize that Universal Search has been being used long before CrApple got either the patent for Universal Search in 2004 or this new Siri Universal Search just granted in December 2011! ........how about that? They just applied for it 8 months earlier. While Google has been waiting 4 years for Notifications Patent to be granted!

**Zeinzu** · 07-29-2012, 12:28 AM

I made 6 calls today initiated from my Bluetooth, handled by the stock AOSP Google Now application. It recognized me perfectly and launched each call with no issue.

My advice, get a better Bluetooth.

Sent from my AOSP Android 4.1.1 Galaxy Nexus

**ncguy** · 08-04-2012, 08:02 PM

unfortunatly 3rd party bluetooth dialer apps no longer work under jelly bean without disabling google search entirely

**JimSmith94** · 08-25-2012, 03:06 PM

Originally Posted by Zeinzu

I made 6 calls today initiated from my Bluetooth, handled by the stock AOSP Google Now application. It recognized me perfectly and launched each call with no issue.

My advice, get a better Bluetooth.

Sent from my AOSP Android 4.1.1 Galaxy Nexus

Did you use Voice Dial, where you press the BT headset talk button to activate it, or did you use Voice Search, where you initiate the call from the phone? For me, Voice Search dials correctly every time, but Voice Dial gets it wrong every time.

**Zeinzu** · 08-25-2012, 04:55 PM

I removes voice dial as Google Now replaces its functionality. I initiate call from Bluetooth and it is handled by Google Now's built in voice dial functionality. Sorry, should have mentioned that before. Might have been helpful for others.

Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus

**JimSmith94** · 08-25-2012, 05:21 PM

Originally Posted by Zeinzu

I removes voice dial as Google Now replaces its functionality. I initiate call from Bluetooth and it is handled by Google Now's built in voice dial functionality. Sorry, should have mentioned that before. Might have been helpful for others.

Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus

Wow, you're the only person I've seen that has posted success with it! Dialing through Voice Search works but Google Voice Dial itself never gets the name right. Did you do something to get it to recognize the names you were calling?

Please take a look at all the posts about this Google issue:

**ncguy** · 08-25-2012, 05:35 PM

Originally Posted by JimSmith94

Wow, you're the only person I've seen that has posted success with it! Dialing through Voice Search works but Google Voice Dial itself never gets the name right. Did you do something to get it to recognize the names you were calling?

Please take a look at all the posts about this Google issue:

Neither voice search or voice dial are usable for me with bluetooth. Don't bother telling me its my bluetooth device because it works perfectly on JB with the cyberon voice dialer. Unfortunately I have to disable google search to use Cyberon on JB. I am clearly better off on ICS than JB until they fix the problem, assuming that they ultimately will fix it. I'm not confident that they will. Google search is so embedded that it may never coexist with a third party dialer any longer.

**GUHoya94** · 09-25-2012, 06:18 PM

I am also now facing the issue with voice dialing and Bluetooth since the ota Verizon upgrade. It's driving me nuts with a 100% failure rate and I really don't want to have to disable search to fix it. Has anyone heard of any other ways around it?

Sent from my Galaxy Nexus using Android Central Forums

**ncguy** · 09-26-2012, 03:08 AM

Originally Posted by GUHoya94

I am also now facing the issue with voice dialing and Bluetooth since the ota Verizon upgrade. It's driving me nuts with a 100% failure rate and I really don't want to have to disable search to fix it. Has anyone heard of any other ways around it?

Sent from my Galaxy Nexus using Android Central Forums

Yes, there is a workaround. You can install the AOKP jelly bean rom. Apparent they left the old voice dialer intact on their JB port. I've been using it for several weeks and its probably more reliable than the stock rom and the dialer is functional again. I've heard CM10 also works in a similar way. Third party dialers still don't work but the old stock dialer works and is very accurate. I've actually been using the gsm version but I think there is also a Verizon version if you're bootloader is unlocked.

**GUHoya94** · 09-26-2012, 10:30 AM

Thanks @ncguy . I had hoped I would get away without rooting as I also have my mother on a nexus in another state and really don't want to try to walk her through it. I may have to for myself though as I seriously am annoyed.

**ncguy** · 09-26-2012, 11:35 AM

Originally Posted by GUHoya94

Thanks @ncguy . I had hoped I would get away without rooting as I also have my mother on a nexus in another state and really don't want to try to walk her through it. I may have to for myself though as I seriously am annoyed.

The interface isn't that much different. I wouldn't think that it would cause a problem.

**GUHoya94** · 09-26-2012, 01:04 PM

@ncguy I'm not worried about the interface so much as trying to walk my mother through rooting her phone remotely in order to fix it on hers too. lol. Me rooting while not something I wanted to do right now is do-able; walking her through it to give her back her bluetooth voice functionality is the stuff of nightmare. On the positive side the bug has got a lot of additional comments in the last day. Maybe more people will star it. ()

**LATom** · 10-08-2012, 12:00 PM

I've tried the factory data reset suggested by Verizon after the OTA JellyBean update without any success. Voice Dialing is 100% wrong - Truly Useless. How does one initiate voice dialing through Google Search using Bluetooth (one touch dialing as required by many states for commercial drivers)?

Has Google officially acknowledged this issue? There is no shortage of posts on forums, but I haven't seen anything indicating that a fix is in the works.

**ncguy** · 10-08-2012, 01:03 PM

Originally Posted by LATom

I've tried the factory data reset suggested by Verizon after the OTA JellyBean update without any success. Voice Dialing is 100% wrong - Truly Useless. How does one initiate voice dialing through Google Search using Bluetooth (one touch dialing as required by many states for commercial drivers)?

Has Google officially acknowledged this issue? There is no shortage of posts on forums, but I haven't seen anything indicating that a fix is in the works.

No they haven't acknowledged it yet AFAIK. Keep in mind that to date less than 2% of Android users are on JB. In my opinion the noise level is about to ramp up as all the new devices start shipping with JB.

**ctechnow** · 10-11-2012, 02:47 PM

Originally Posted by Zeinzu

I removes voice dial as Google Now replaces its functionality. I initiate call from Bluetooth and it is handled by Google Now's built in voice dial functionality. Sorry, should have mentioned that before. Might have been helpful for others.

Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus

I want my BT headset to use Google Now by default instead of voice dialer. How did you set yours up this way?

**vicw926a4** · 10-11-2012, 04:04 PM

I was able to use Titanium Backup to freeze Google Search, and then use the BTconnection to manage Voice Calls and other functions with the a 3rd party app (Vlingo InCar beta). The app gave me good results on contact recognition, so I'm pleased that I at least I have a temporary workaround for the problem. After Unfreezing Google Search, everything seems to be back to normal.

The process isn't exactly convenient, and I hope Google properly fixes this problem very soon.

**ncguy** · 10-11-2012, 05:02 PM

Originally Posted by vicw926a4

I was able to use Titanium Backup to freeze Google Search, and then use the BTconnection to manage Voice Calls and other functions with the a 3rd party app (Vlingo InCar beta). The app gave me good results on contact recognition, so I'm pleased that I at least I have a temporary workaround for the problem. After Unfreezing Google Search, everything seems to be back to normal.

The process isn't exactly convenient, and I hope Google properly fixes this problem very soon.

Interesting. What do you sacrifice with search frozen out?

**vicw926a4** · 10-11-2012, 06:14 PM

Originally Posted by ncguy

Interesting. What do you sacrifice with search frozen out?

I didn't test it exhaustively - just a quick run in the car. The Google Search grey bar on the home screen was still there, but blank, and I assumed that would be unresponsive, but in addition to the Bluetooth calling capability, I was able to use the app for navigation from the BT button. I haven't yet tried any of the other app BT functions.

Using the phone directly, I was still able to search locations in Maps, and contacts in People.

**ncguy** · 10-11-2012, 06:38 PM

Originally Posted by vicw926a4

I didn't test it exhaustively - just a quick run in the car. The Google Search grey bar on the home screen was still there, but blank, and I assumed that would be unresponsive, but in addition to the Bluetooth calling capability, I was able to use the app for navigation from the BT button. I haven't yet tried any of the other app BT functions.

Using the phone directly, I was still able to search locations in Maps, and contacts in People.

Thanks for that info. I'm definitely going to give it a try. I had completely given up on my third party dialer. I'm anxious to see if it will work.:-)

**ncguy** · 10-11-2012, 07:15 PM

I tried freezing it. Unfortunately it had the same affect as just going into apps and disabling it there. It does what you said but unfortunately it also disables google now.

Still the only way that I have found so far to preserve google now on jelly bean and still use bluetooth voice dialing is by going to cm10 or AOKP.

FWIW, CM10 and AOKP were rock solid when I tested and CM10 is currently my daily driver. Its already on 4.1.2 and more stable than stock IMO.

**vicw926a4** · 10-11-2012, 08:34 PM

Originally Posted by ncguy

I tried freezing it. Unfortunately it had the same affect as just going into apps and disabling it there. It does what you said but unfortunately it also disables google now.

Still the only way that I have found so far to preserve google now on jelly bean and still use bluetooth voice dialing is by going to cm10 or AOKP.

FWIW, CM10 and AOKP were rock solid when I tested and CM10 is currently my daily driver. Its already on 4.1.2 and more stable than stock IMO.

I expect the affect of the apps/disable would be the same, it just seemed a bit more convenient to us TB to stop the app temporarily. I haven't really been using Google Now much, so that wouldn't impact me much, and I just plan to use it while travelling. For the moment, I'm trying to stay on a stock JB to make sure one of the BT bugs I experienced on a JB ROM doesn't occur, but once I finish that monitoring, I might try CM10 and AOKP. I appreciate knowing they have been solid for you.

P.S. - I meant to ask if the JB ROMs will allow you to connect to a 3rd party BT app?

**ncguy** · 10-12-2012, 05:04 AM

Originally Posted by vicw926a4

P.S. - I meant to ask if the JB ROMs will allow you to connect to a 3rd party BT app?

Unfortunately no, they won't. That said, for some reason the stock voice dialer with bluetooth is now amazingly accurate. Its only problem occurs when you ask it to call someone not in your contacts. Instead of saying not found it seemingly picks someone in your contacts at random and dials. That situation is fairly rare for me so overall the Bluetooth voice dialing is working out better than I expected without my favorite 3rd party dialer.

**vicw926a4** · 10-12-2012, 08:11 AM

Originally Posted by ncguy

Unfortunately no, they won't. That said, for some reason the stock voice dialer with bluetooth is now amazingly accurate. Its only problem occurs when you ask it to call someone not in your contacts. Instead of saying not found it seemingly picks someone in your contacts at random and dials. That situation is fairly rare for me so overall the Bluetooth voice dialing is working out better than I expected without my favorite 3rd party dialer.

That inability will probably keep me from trying the ROM alternative. I hate the frenzy that follows the realization that it is dialing a number apparently snatched at random, while I'm focused on driving.

Using the BT Dialer function of the Vlingo InCar app, while it may rarely dial the wrong number, has a nice big Cancel button displayed that makes it easy to stop the action, without colliding with oncoming traffic.

Perhaps using the Answer/End button on the BT will accomplish an immediate hangup, but I believe there is no visual or audible confirmation that has been done.

Clearly Google needs to fix this one properly, but perhaps in the meantime, one of the geniuses at XDA will come up with a small MOD that would provide a convenient and transparent temporary solution to the problem.

Sent from my Galaxy Nexus using Tapatalk 2

**ncguy** · 10-12-2012, 11:59 AM

Originally Posted by vicw926a4

That inability will probably keep me from trying the ROM alternative. I hate the frenzy that follows the realization that it is dialing a number apparently snatched at random, while I'm focused on driving.

Using the BT Dialer function of the Vlingo InCar app, while it may rarely dial the wrong number, has a nice big Cancel button displayed that makes it easy to stop the action, without colliding with oncoming traffic.

Perhaps using the Answer/End button on the BT will accomplish an immediate hangup, but I believe there is no visual or audible confirmation that has been done.

Clearly Google needs to fix this one properly, but perhaps in the meantime, one of the geniuses at XDA will come up with a small MOD that would provide a convenient and transparent temporary solution to the problem.

Sent from my Galaxy Nexus using Tapatalk 2

I think then that you would like cyberon even better. It is also very accurate and it uses voice verification. No need to touch any buttons to cancel dialing. It would be my first choice if I could use it without having to disable search and google now.