[Question] Hands free Bluetooth dialing

[teddyearp]

OK, here comes the earp with another lengthy question. I only ask this since we early adopters of the Moto A855 (OG Droid) who came from Moto (and other) phones were really disappointed with the lack of this feature from a flagship phone (which the A855 was at the time).

A bit of background. With the 'prior to Android' Moto (and other makes) a simple press of the button on your BT headset would give a vocal prompt in your BT headset, "Say a command". And the voice recognition was very good as it would also prompt you with, "Did you say call xxx?" before executing the command. Now I have found that the dev of this software was Nuance and it was included in Moto Android devices that had Blur. But anyways for the A855 any hint of this type of functionality was totally gone until the device got upgraded to Froyo, but even then it was not that good as Android/Google's dialer was still un par. Then when the A855 got Gingerbread through CM7, the functionality was broken again in favor of DSP, but was fixable, but still sub-par.

So what I want to know is since the voice recognition engine is much better with ICS, does this 'spill over' to a true hands free BT dialer? And I am not asking about any other app, like Vlingo, Choice Dialer, etc., I just want to know if this has been improved now on the VZW Gnex (i515) and further if it works any better on any custom roms.

And as I said, please do not reply with "Just use Vlingo", or any other app as all I want was close to the same as I had on my other phones.

Thanks in advance.

 

[pool_shark]

No. The BT voice dialing on this device is a HUGE step backward.
It doesn't have an option for adaptation and it doesn't prompt for verification, it simply dials whatever it thinks it heard, which is usually incorrect.

The software on the Droid X was much better.

 

[notalent_assclowns]

No. The BT voice dialing on this device is a HUGE step backward.
It doesn't have an option for adaptation and it doesn't prompt for verification, it simply dials whatever it thinks it heard, which is usually incorrect.

The software on the Droid X was much better.

We're having different experiences. I've had the Droid X and X2 and while the accuracy was pretty decent, it took between 15-20 seconds to actually start the app, so I just quit using it since it was quicker to just do it myself.

The one on the Nexus is just about instant and I haven't had a single issue since launch, so maybe it just picks up my voice better than yours or something.

 

[pool_shark]

We're having different experiences. I've had the Droid X and X2 and while the accuracy was pretty decent, it took between 15-20 seconds to actually start the app, so I just quit using it since it was quicker to just do it myself.

The one on the Nexus is just about instant and I haven't had a single issue since launch, so maybe it just picks up my voice better than yours or something.

You're talking about using a headset?
I initiated voice command once using my headset and didn't say a word, in fact I didn't even open my mouth, it said "calling Scott".

 

[john30308]

BT dialing is working about the same as previously for me.

 

[teddyearp]

Wow, this is an area where Android just falls flat on it's face IMHO. Makes me tempted to just drop smartphones and hook my V9m back up. . . .

Thanks.

 

[pool_shark]

Wow, this is an area where Android just falls flat on it's face IMHO. Makes me tempted to just drop smartphones and hook my V9m back up. . . .

Thanks.

It isn't a global Android problem, it's the way the manufacturer implemented the software.

I had absolutely no problems using voice commands on my Droid 2 or Droid X. They used a different implementation of the software than the Nexus.

 

[speede541]

This is an area where BlackBerry has been years ahead in terms of voice recognition, comprehension, confirmation, and speed.

The stock Nexus dialer is behaving for me as with pool_shark: no confirmation, just dials, incorrectly.

I haven't been having a whole lot of luck with Vlingo, either, and dislike that it needs a network connection to do what it does.

 

[pool_shark]

This is an area where BlackBerry has been years ahead in terms of voice recognition, comprehension, confirmation, and speed.

The stock Nexus dialer is behaving for me as with pool_shark: no confirmation, just dials, incorrectly.

I haven't been having a whole lot of luck with Vlingo, either, and dislike that it needs a network connection to do what it does.

I have noticed that if you talk quietly it's better at understanding, but that's hard to do in a running vehicle. I really wish it would do a confirmation though.

Speaktoit works very well, but it doesn't listen over BT and you can't set it to be the default voice software.

 

[teddyearp]

It isn't a global Android problem, it's the way the manufacturer implemented the software.

I had absolutely no problems using voice commands on my Droid 2 or Droid X. They used a different implementation of the software than the Nexus.

However, the D2 and DX both had Motorola's Blur over the top of vanilla Android. That is not a different implementation of Android but the inclusion of another piece of software as blur also included the same software that Motorola has been using for years on their cell phones back at least as far as the V3, most likely further. And said software is made by Nuance.

 

[pool_shark]

However, the D2 and DX both had Motorola's Blur over the top of vanilla Android. That is not a different implementation of Android but the inclusion of another piece of software as blur also included the same software that Motorola has been using for years on their cell phones back at least as far as the V3, most likely further. And said software is made by Nuance.

I'm talking specifically about the voice command software not android itself or manufacture's skin.
The Droid 2 and X used nuance voice software, the nexus doesn't. That's a different implementation of the voice command software.
Therefore it is not a global android problem.