yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] JimSmith94:
I just flashed my Sprint Nexus to JB last night and have exactly the same problem. I hadn't tried any calling on ICS before I flashed, so I can't compare on the same phone.

I just came from an Epic 4G Touch that used Vlingo, and it was always about 95% accurate. I hate to step backwards, but I may have to switch back to that.

Why can't anyone mimic the old MS voice dial where it asked for confirmation before dialing? If I said, "Call mom on mobile", it would ask, "Call mom on mobile?" I said "Yes" and it would dial.

The way it is now goes against all safety concerns for hands-free driving. Now I have to look at the screen as it starts to dial and madly grab at the End Call button when it guesses the wrong name to call. :eek:
[Samsung Galaxy Nexus] urushiol:
Im glad someone finally responded and said yes i have this problem, or no i use this feature and it works every time.

THis is a huge concern and i feel its only happening on the ported(CDMA) roms.

Can anyone else confirm this on a toro or toroplus, and confirm that this is not an issue on GSM gnexus's?

Thanks!
[Samsung Galaxy Nexus] UnknownFearNG:
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
[Samsung Galaxy Nexus] urushiol:
This makes me feel very strongly that the issue has been caused by something in the porting process. I will PM on of the devs. and see if he can reproduce it.
[Samsung Galaxy Nexus] djh36:
i am also having this problem on my CDMA nexus with JB. Everytime it's not even remotely close to properly detecting my call request.
[Samsung Galaxy Nexus] NCguy:
I absolutely love the cyberon voice dialer because it works and it has verification.

Unfortunately, under JB when you press the dial button on the bluetooth headset the google now voice dialer overrides my cyberon voice dialer. The only way to make cyberon work is to completely disable google search. This completely disables all the new voice command support and google now as well.

Basically 3rd party voice dialers are no longer compatible!

No, the built in dialer is still unusable especially without verification.
[Samsung Galaxy Nexus] kynolin:
For me, I've always had absolutely horrible results when using voice dial initiated from the Bluetooth earpiece (two different Jawbone Icons, three different Android phones, Eclair through Jelly Bean, official or custom ROM.)

Using voice search, Google Now, JB voice typing, or Dragon with Swype, it's perfect..
[Samsung Galaxy Nexus] JimSmith94:
Can the long button press be changed from voice dial to voice search? (I think those are the right terms.) Voice search understands and dials much better. Plus, it sucks to be limited to just dialing from the headset.
[Samsung Galaxy Nexus] NCguy:
Cyberon is awesome. I wouldn't use a voice dialer without confirmation. I don't want people calling me back because my dialer got it wrong. Sometimes this can cause serious problems. If google adds a confirmation option that's when I'll give them a serious try. I've been told even the iphone voice dialer has confirmation.
[Samsung Galaxy Nexus] martonikaj:
Same.
[Samsung Galaxy Nexus] NCguy:
Are you both dialing through bluetooth? Honestly it hasn't got one right for me yet. Not one where cyberon is dead on.
[Samsung Galaxy Nexus] martonikaj:
Just dialing with the voice button from the homescreen (or in Google Now, same thing). Not using Bluetooth.
[Samsung Galaxy Nexus] NCguy:
I suspect it had issues with bluetooth dialing.
[Samsung Galaxy Nexus] albina_0:
Bluetooth Voice dialing issue in JB

I can confirm that I have experienced identical problems with the new Voice Dial in JB.

Tried at least 3 different JB ROMs - initial Google release, bigxie's OTA and the MoDaCo JB with identical, miserable results.

Voice Dial worked like a charm on every version of ICS that I have used since November last year on my GSM GNEX.

I switched back and forth between ICS and JB to make sure that my BT headset hasn't gone bad (plantronics discovery 975), used the exact same contacts list, sorted same way, but the results couldn't be any more different.

Not once was I able to get a contact right from the dialer in JB while I get 90%+ in ICS.

I know the problem is with the dialer because the voice recognition in search is amazing, almost flawless.

Anyway, I hope this helps in getting the message out to Google that we have a problem.
[Samsung Galaxy Nexus] NCguy:
And if you're lucky there might be a fix in key lime pie. I just prey that the JB code is exposed enough for an app developer to allow a 3rd party app to be the default dialer which is apparently not possible at the moment.

Also, i assume you are all voice dialing via bluetooth because I'm not sure that voice dialing through the phone mic has the same problem.

If you're a bluetooth user here are some other JB observations that just may drive you back to ICS.

If your listening to media and take a call with your BT headset, when you hangup your media resumes at zero volume every time. I am still testing but I think I've also noticed cases where the media went to zero volume but didn't pause during the call.
[Samsung Galaxy Nexus] cobusk:
Voice dialing not working on stock JB

I received the OTA update last night and was blown away by how much better voice search now recognizes what I say - 90% accuracy at least. That was basically useless for me on ICS. But the exact opposite happens in voice dialing - I couldn't get it to recognize a single contact. Not one. ICS got it right almost 100% of the time.

Very annoying.
[Samsung Galaxy Nexus] NCguy:
Just curious is your dialing with a BT headset or with the phone mic? Is your accuracy better with the phone mic?
[Samsung Galaxy Nexus] cobusk:
I don't think you can load the voice dialer with the phone mic - I don't see the dialer in the launcher at all.

So voice search with the phone mic is brilliant, but dialing with the BT car kit is useless. Yesterday the BT still worked brilliantly with ICS, so I believe the problem is with Jelly Bean's dialer.

---------- Post added at 04:45 PM ---------- Previous post was at 04:25 PM ----------

Here's another thing I tried:

I enabled Talkback in the Accessibility settings and navigated to one of my contacts so I could hear how the text-to-speech pronounces the name. Pronouncing it the exact same way, I couldn't get the voice dialer to recognize the name. I know the two are completely separate pieces of tech, but there is no other way to figure out in what way I need to pronounce (closer to butcher) my wife's name to get it recognized.
[Samsung Galaxy Nexus] NCguy:
I would pay big $ if someone could figure out a way to allow a 3rd party app to be the default voice dialer like in ICS.
[Samsung Galaxy Nexus] Herbie555:
I have no way to confirm this, but my suspicion is that the voice dialer is NOT opening the Bluetooth MIC during this process - it uses the handset MIC.

I too was getting super-craptastic results on Voice dialing after the ICS->JB update. Both of my cars have JVC bluetooth head units that I've been using for a long time with multiple handsets, and I've NEVER had performance this bad until my GSM GNex updated to jellybean. Both head units have external microphones mounted in good locations, etc., but I suspect that they are NOT being used.

The only test I've been able to conduct was to try using voice dialing with the phone in a cradle or in the center console (depending on vehicle). Getting the usual awful recognition. Then, if I pick up the handset and hold it close to my head (even though it's supposedly connected via bluetooth) and try again, I seem to get improved performance - though still with mixed results depending on road noise, etc.

Anyone have a way to verify if the Bluetooth MIC is (or is NOT) being used during a voice recognition session?

---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------

I have a Play Store unlocked GSM handset and came to this thread specifically searching for why voice dialing seems to be so incredibly borked after the jellybean OTA update. Everything worked awesome on ICS. So this is definitely a GSM issue also.
[Samsung Galaxy Nexus] NCguy:
But even if the BT mic worked that doesn't solve the problem. The stock voice dialer has no confirmation which is absolutely required. Prior to JB you could use several third party dialers that worked well and also had confirmation. With JB you now have to disable half the phone to use a third party dialer. That, IMO, is the real problem and a huge step backwards.
[Samsung Galaxy Nexus] embeeowes:
Not just CDMA (Toro)

I have that exact problem on a stock Jellybean GSM Nexus. The voice dial matching is ATROCIOUS!
[Samsung Galaxy Nexus] dougleto:
same problem on JB ROM Bugless Beast

I'm having the exact same problem on a VZW galaxy nexus running the Bugless Beast JB ROM. After 3ish weeks on JB, using the voice dialer on bluetooth has *never* come up with the right contact and the lack of confirmation has, as previously noted, resulted in some awkward, 'umm sorry about that, didn't mean to call you" conversations. I'm glad to hear that this isn't just a bugless beast problem but I guess the fact that its endemic to JB and is, therefore, not likely to be an easy fix makes it even worse. Here's hoping this gets resolved soon so I don't have to fool with my phone every time I need to make a call in the car.

It certainly would be nice if we could just change the default behavior to use the google now voice search (that gives you the option of confirming who you actually want to call) and circumvent the faulty voice dialer entirely.

(As a postscript, I'm so glad to find others with this same problem, I've raised the issue on a couple bugless beast forums and haven't gotten any responses.)
[Samsung Galaxy Nexus] Monkypirate:
I am also having problems with voice dialing. I use a Sena SMH-10 motorcycle bluetooth and a LG HBS700. When I was on ICS it worked flawlessly. Now on JB, as soon as I hit the voice dial button on either BT device, I dont even get a voice prompt that says "say a command". Just the tone after it supposed to say "say a command". And like the others its inaccurate. Any fixes yet?
[Samsung Galaxy Nexus] NCguy:
In case some of you didn't see it, there is a temporary workaround. You can go into apps,all and then temp disable google search. You can then use a third party voice dialer with confirmation like cyberon. You can easily toggle google search back on when you need it. Not a great solution but I rely on voice dialing so much it was worth it to me. Its like trading bluetooth voice dialing for all the newest features in JB.
[Samsung Galaxy Nexus] Tatsch:
@NCguy:

How can you "easily" toggle google search?? Too many clicks ,,,

I tried to manage it with Tasker app (depending on bluetooth connection), but it's not possible to disable an app with Tasker.

Is there a fast way to toogle google search enable/disable? Is there a shortcut?
[Samsung Galaxy Nexus] NCguy:
By easy I just meant that it wouldn't hurt anything by toggling it on and off. I didn't mean to imply that it was in any way convenient. A shortcut would be awesome if someone could come up with one. I tried going through the same thought process as you and got no where. So at this point I would say its only practical to toggle it off, leave it off, and then live without google search until sometime hopefully solves this issue. I know how much this sucks, believe me I do. Our only hope is that currently less than 1% of Android users are on jelly bean. More noise will be made as the rest come over.
[Samsung Galaxy Nexus] Tatsch:
Ok, then let's start making noise .. ;)
[Samsung Galaxy Nexus] NCguy:
To start, someone should open a google bug report or whatever they call them. If enough people pile on to the report it ups the priority. I've never opened one but if nobody else does it I will have a go at it.
[Samsung Galaxy Nexus] scarecrow2012:
Issue has been reported but we need to make more noise

http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=35199
[Samsung Galaxy Nexus] NCguy:
That is a valid bug report. Unfortunately it doesn't address third party dialers no longer working without having to disable google voice.
[Samsung Galaxy Nexus] gbarayah:
I had this same problem when I was running Bigxie's ROM but since switching to AndroidME, the voice dialer is working just fine.

Lack of confirmation is lame but accuracy for me on AndroidME has been VERY good - can't recall the last time it miss dialed and I use my bluetooth multiple times a day in the car.

GSM Nexus with a Motorola Roadster Bluetooth Speaker.
[Samsung Galaxy Nexus] NCguy:
Is AndroidMe a JB based ROM?

EDIT: I see now that it is JB AOSP

Will it allow you to use a 3rd party voice dialer like cyberon without disabling google voice? It doesn't look very modded.
[Samsung Galaxy Nexus] gbarayah:
No its very close to stock and you cannot use a 3rd party voice app to override Google.
[Samsung Galaxy Nexus] cgulliver:
I can confirm this exact issue on my GS3 and it is maddening. I can ask my phone what the population of Mongolia is but not "Call Home." WTF Google????
[Samsung Galaxy Nexus] E--Man:
Had anyone figured out how (if possible) to do other actions in the Bluetooth voice dialing such as sending SMS messages or scheduling appointments? I used to be able to do this on ics.
[Samsung Galaxy Nexus] JimSmith94:
Has it been confirmed that this is an issue only on CDMA JB ROMs? From reading this thread, it seems that the only people this works for are on GSM phones.
[Samsung Galaxy Nexus] Herbie555:
Definitely BROKEN on my GSM phone - Playstore i9250, w/ stock JB ROM.
[Samsung Galaxy Nexus] gbarayah:
I am starting to think this is dependent on the ROM:

Last week, I flashed rasjellybean and could not use voice dialing, or any other voice commands for that matter, at all. It could hardly recognize anything I was saying.

On Bixie's rooted stock, I could use the voice dialer but the accuracy was awful.

For me, only AndroidME has been good with voice dialing - an important feature for me, as I often take/make calls while driving via bluetooth.
[Samsung Galaxy Nexus] E--Man:
Anyone? ? ?
[Samsung Galaxy Nexus] NCguy:
Here is an update.

I installed the JB based AOKP and dialing behavior is much different than stock.

When Bluetooth off:

Uses google now for all voice actions including calling via the phone mic. I couldn't get it to launch the old voice dialer with bluetooth off. Google now seemed to be pretty accurate for all voice actions through the phone mic except voice dialing. It was more accurate than the unusable stock Jelly Bean for voice dialing but not accurate enough.

With Bluetooth On:

Surprisingly, it launches the old voice dialer when the call button on the Bluetooth device is pressed. I was very surprised to see this because on stock JB the call button launches google now, not the old voice dialer. I just started playing with it but so far the dialing accuracy of the old voice dialer is surprisingly accurate. It will take a few more days with background noise to give a more conclusive report.

So with a BT device and AOKP it would appear that pressing the call button will let you make a voice call using the old voice dialer. If you want to perform some other google now voice command while using BT you need to press the mic button on the phone to initiate google now and then you can speak and hear your command through the BT device.

So whoever mentioned that BT behavior is apparently different based on the ROM seems to be on the money. This AOKP ROM, while based on the stock rom, clearly has differences with regard to BT, dialing, and google now behavior. Even though there still appears to be no way of engaging google now along with a third party dialer, the fact that it engages the old voice dialer with what appears to be improved accuracy may allow us to have BT dialing and google now at the same time.
[Samsung Galaxy Nexus] Maxxy13:
Hi, I own a HTC Inspire (almost identical to more well-known Desire HD) and there were few JB ROMs going around for our devices. The issue with voice dialing on JB for us is exactly as described in this thread.

One thing I'd like to point out is that the old Voice Dialer you've discovered on AOKP port is a separate program from Google Now. The way it works when you press BT button the Voice Dialer call takes a priority over the GN call. If your phone is rooted you can uninstall or freeze Voice Dialer using TiBa. After reboot you'd get GN responding on BT button.

I agree with other users that the voice recognition on GN over bluetooth is atrocious. It may be the reason why in AOKP the old Voice Dialer was added back. However it doesn't support confirmations and therefore is unacceptable for me.

So for now we're stuck with either GN with crappy BT voice recognition or a 3rd party voice dialer but no GN.
[Samsung Galaxy Nexus] NCguy:
Thanks for that info. I agree 100% about the need for confirmation. This however seems to be the only solution right now for voice dialing without having to disable GN. So is it possible, until this is resolved, to flash (or copy) the old voice dialer onto the stock JB? Don't suppose it would be as simple as backing it up from AOKP with Tib and restoring it to stock JB?
[Samsung Galaxy Nexus] JimSmith94:
I had the Google Dial problem where it would never dial the right person on Alpha JB ROMs a month or so ago. However, dialing through Google Voice always worked correctly.

Over the last week I've installed a couple of the CM10 ROMs. I have been pleasantly surprised that every call I have initiated from my BT headset was understood and dialed correctly.

I agree that there needs to be confirmation though. Even my old Windows Mobile phones had that!
[Samsung Galaxy Nexus] NCguy:
CM10 must be using the old voice dialer also. Can you tell? If you go into settings, apps, all - is there an app called voice dialer in the list?
[Samsung Galaxy Nexus] JimSmith94:
Yes, Voice Dialer is there. It's listed as "version 4.1.1-eng.phantomphreak53.2010911.030129". I'm currently running the PhantomPhreak's CM10 9/11 nightly, so that's part of the version data. Maybe the "030129" is the Google version.

So is Voice Dialer the old one or a new JB version?
[Samsung Galaxy Nexus] NCguy:
It was replaced by google now in the stock JB ROM. Apparently the custom roms brought it back because GN is practically useless as a bluetooth voice dialer. It may have some slight mods to make it compatible with JB.
[Samsung Galaxy Nexus] gagb1967:
I have a strong accent, but most of the time it works fine, both voice dialer and Google now

Sprint JB stock
[Samsung Galaxy Nexus] JimSmith94:
Voice Dialer was on the JB ROMs last month. I could make accurate calls every time with Voice Search but never with Voice Dialer. I haven't even tried dialing with Voice Search on the latest CM10 ROMs because Voice Dialer hasn't let me down.

I still wish we had the option for a long press on my BT headset to start Voice Search instead. I'd like to get the weather, send a text, get directions, etc. that way, like we used to with Windows Mobile and even Vlingo.
[Samsung Galaxy Nexus] NCguy:
Are you sure "voice dialer" was on the stock JB rom last month? I really don't think that's the case. I don't think stock JB ever had it.
[Samsung Galaxy Nexus] gagb1967:
You Google now and voice dialer, stock jb Sprint genex
[Samsung Galaxy Nexus] JimSmith94:
I've never had "stock JB", but the Sprint Nexus I had for a while with a JB 4.1.1 ROM and the JB ROMs on my E4GT all said "Speak Now" and they all looked the same.

Something must have changed somewhere, although no one in this Android Issue thread says anything about it working: http://code.google.com/p/android/issues/detail?id=35199
[Samsung Galaxy Nexus] juzzie:
I remember hearing it on the radio like a month ago that Google had to disable some phone number search related features due to patent issues with Apple. Even though "voice search" is not exactly as "phone number search", but my guts feeling tells me it was done on purpose and maybe they overdid it by mistake. If it was not a mistake, then we all doomed by the lack of this feature in JB and next Android releases. I tell u one thing: if Google start to surrender under Apple's pressure and drop features here and there, I will think twice before buying any Android device. I hope they realize that. :(
[Samsung Galaxy Nexus] NCguy:
The AOSP code and change log just dropped for the 4.1.2 update. The log is cryptic but I didn't notice any fixes in there for bluetooth voice dialing.

I think this is the change log.

http://www.funkyandroid.com/aosp-JRO03D-JZO54K.html

I have been running CM10 as someone suggested and bluetooth voice dialing works remarkably well. It still won't allow third party voice dialer apps however.
[Samsung Galaxy Nexus] RandomIO:
Same problem diff phone

I have the exact same result with a GS3 (TMO - GSM) running stock JB OTA. I experience the problem when the phone is connected to my bluetooth car stereo. It is infuriating me... My MyTouch4G running a completely hacked/butchered up ICS rom worked incredibly well with the same car. I think we can safely narrow it down to the Google Now voice dial functionality (or lack there-of).
[Samsung Galaxy Nexus] wailly:
Just got my new Plantronics Legend headset, and of course like everyone else, the BT voice dial is screwed on my Galaxy Nexus on stock JB 4.1.2. It has done absolutely nothing except to fix that December bug (which I never used since like... never).

Off I go to CM10 it is.
[Samsung Galaxy Nexus] mahsan988:
I just came across this thread and wanted to offer some insight.. Unfortunately I have this issue with my Nexus since there as a small update pushed to the phone (forget whether it was a 4.0.2 or 4.0.4)

I used to use this feature to call places I did not have the number for. For example, "call honda in westborough" and it always used to work FLAWLESSLY.

I tried to factory reset, and the problem was still there. I have since tried different ROMs and the problem is still there. Which is frustrating because believe it or not this was on my top 5 why I love Android list. It was absolutely amazing at calling places I did not have the number to while I was driving. But after evaluating this issue further I know for a fact that this has to do with that bull**** patent Apple won. The patent in question was the one involving Siri and voice dialing. This patent question is the '604 patent. The worst part is that it is such a vague patent like every other Apple patent. But pity on the patent office for approving such bull**** and on the judge who agrees. (http://patft.uspto.gov/netacgi/nph-...50&s1=8086604.PN.&OS=PN/8086604&RS=PN/8086604)

Everyone has this issue, and I can tell you how to replicate it.

Open google search, speak "call honda in westborough" it will respond "cannot find any contacts to call" (sometimes it might offer a random contact from your phone book). Now leaving that "call honda in westborough" in the search bar, go ahead and tap on that as if you are going to make a change by typing. Do no make any changes, just hit the search key on the keyboard, and viola it immediately starts dialing "Herb Chambers Honda of Westborough." You can do this all day long, voice to dial does not work, yet typing the same exact command is pin point as it used to be because Google voice search is the ****.

I hated Apple with a passion already, but after this bull****... there has been so much more fuel added to the fire. I cannot wait to see the day Apple falls. :mad:
[Samsung Galaxy Nexus] Neera:
I am having trouble with voice dialing lately as well. It's not bluetooth related though.

Most of the time now when I I use a voice command to call one of my contacts Google Now will perfectly understand the name, but still try and attempt to call a different contact.

See my screenshot:

I asked Google to "Call Joliet Cabinet" and it typed it back to me perfectly "Call Joliet Cabinet Company, Inc." which is how the name appears in my contacts, but then starts to dial "The Centre of Oral Surgey in Joliet" which is also in my contacts.

What is up with this? *scratches head*