My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 4848: Enable voice dialing through Bluetooth
345 people starred this issue.
Comments by non-members will not trigger notification emails to users who starred this issue.
Back to list
Status:  New
Owner:  ----

Restricted
  • Only users with Commit permission may comment.


Sign in to add a comment
 
Reported by marybeck...@gmail.com, Nov 16, 2009
Please enable user of droid to have voice dial through blue tooth. Trying
to dial or even press a speed dial while driving is extremely dangerous.
Perhaps there could be a physical button on the outside of the phone which
could turn this off and on.
Nov 17, 2009
#1 jbq+legacy@google.com
(No comment was entered for this change.)
Labels: Component-Applications Subcomponent-Telephony
Dec 29, 2009
#2 clcdan....@gmail.com
Ya, we should utilize a fast double-click on the menu button perhaps for that (while IN 
bluetooth mode)
Jan 13, 2010
#3 enrico.q...@gmail.com
It's preposterous! 4 years old Symbian phones support this feature. I wonder how
android wants to win the competition with symbian phones or blackberry or iPhone if
developers don't implement such a fundamental feature!
Don't forget the Milestone too!
Jan 18, 2010
#4 jodaboda
**********************************************************************************
**********************************************************************************

! EVERYONE PLEASE ! Contribute 2 seconds and 2 clicks to getting issues fixed!

PLEASE, open this link and click to "star" the issue:

https://code.google.com/p/android/issues/detail?id=1181

(Click the star so it's yellow, not white)

(all other similar complaints are being merged into this thread, so it's unnecessary
to bother with any of them)

**********************************************************************************
**********************************************************************************
Jan 18, 2010
#5 enrico.q...@gmail.com
Fix this safety issue, otherwise I'll go back to symbian!
Jan 28, 2010
#6 connelly...@gmail.com
Comment 4  by jodaboda, Jan 18, 2010: I no longer have any confidence that STAR'ing
an issue matters. This issue (like many others) have not been resolved in over a year
now!
Jan 28, 2010
#7 connelly...@gmail.com
Also I should point out that the other issues are related to voice prompt. 

The more important problem is that the ability to initiate voice dialing through
Bluetooth (usually a long press on the Bluetooth call button). 

It is currently impossible for a 3rd party developer to build this feature because
the code is missing from the Android SDK.

The Android team have known about this for more than a year! 

Jan 28, 2010
#8 TPaige...@gmail.com
I have no plan, but I do have a phone number.  I know they say nothing will happen if we call, but then again, 
apparently nothing happens if we star/e-mail/post.  Anybody else wanna try?  I'm going to:

Google Inc. 
1600 Amphitheatre Parkway
Mountain View, CA 94043
Phone: +1 650-253-0000
Fax: +1 650-253-0001
Jan 28, 2010
#9 TPaige...@gmail.com

        Know this is unlikely to work either, but I thought of something.  I am e-mailing Verizon to find out how 
to press them NOT to advertise this phone as having "voice-dial" as long as the voice-dial is not hands-free.  
Perhaps if we bring this discrepancy to the attention of Verizon, who DOES have a customer service 
department, if they stop advertising the phone as having voice-dial, people will not buy it and then it will hit 
Google in the pocketbook.  If I had known the voice-dial was nonfunctional, I would have saved my money or 
at least my time.  This is my sample e-mail:

I purchased a DROID ERIS that was advertised as having a voice-dialing feature.  What was not explained or 
advertised is that the voice dial is not hands-free--that is, does recognize your voice, but does not dial by 
voice alone--it requires you to look at the phone and touch a link for confirmation.  Because voice-dialing is 
not hands-free on this phone, it is useless.  I believe that Verizon or any other carrier that sells this phone 
should refrain from advertising it as having voice-dialing until Google fixes this issue.  It has been this way 
for 2 years, and Google is ignoring the posts and complaints of all of us who bought this phone, mistakenly 
thinking that the voice-dial feature was hands-free.  A voice dial feature that does not work only with the 
voice is rendered null and void, especially given that driving laws now dictate that cell phones can only be 
operated with hands-free usage.  Please tell me whom I would contact about this.  Thank you--

Sincerely--

(your name here)

Verizon did not publish their customer service e-mail, but you can compose and send an e-mail to customer 
service at this link:

http://www.verizonwireless.com/b2c/contact/index.jsp

The company addresses are also on this page.

Perhaps some of you are thinking that this is over the top, and a simple case of "caveat emptor".  I actually 
beg to differ.  What is the use of voice-dial that has to be confirmed by hand?  I think no one is looking to buy 
a phone that you simply know recognizes your voice without it being of any use to you at all.  Even a dog can 
recognize a vocal command and then perform an action to respond to it (no offense to dogs).  This 
smartphone is not that smart. "VOICE DIAL" Implies that the phone actually DIALS on recognition of the 
VOICE--this does not do so.  This phone has 'VOICE-CHOOSE"--it does not dial by voice alone.  It's simply 
false advertising.

*sigh* I know I am acting like a posting psycho but I'm just slightly pissed.

Let's see if anything gets done this year....
Mar 3, 2010
#10 kpacma...@gmail.com
Will return the phone if this is not fixed Ridiculous that we are even having this
discussion
Apr 23, 2010
#11 babblega...@gmail.com
I just dumped my BB in part because the voice recognition in the BT voice dialing is
so pitiful and I assumed from the all the stuff written about the N1's voice
recognition it would easily be better. I haven't got my N1 yet but from the gist of
this thread I have a feeling it will be be making an immediate return trip to Google
town. Unfortunate for the big number boys 'cause I knew of a whole bunch of BB users
looking for an alternate and I'll have to report its failure in this most rudimentary
of requirements for a 'mobile, phone. Not everyone rides the bus and if you happen to
drive anywhere in the civilized world handsfree is likely the law. WOW Google I
expected more. With this said they could keep in the N1 fold if they'd just respond
with a definitive answer on when and ho proper BT VD will be available.  
Apr 24, 2010
#12 davidpec...@gmail.com
I use Choice Dialer Free. I have the phone in a car holder so can I hold 
the search button down for a second to start it. Then I say "call Ed 
Adams at home" and it starts the call and switches to my BT headset or 
radio for the call.
May 2, 2010
#13 bryan.ha...@gmail.com
On a motorcycle this is an extreme safety issue as having to touch the phone means 1
hand off the bars along with a distraction from the road.  Headsets are available for
those too and support voice dialing if the handset supports it.  I would love to see
this feature and it would provide an incentive to keep buying android phones as it is
an area that both BB and proprietary phone OSes have mastered
May 5, 2010
#14 kentd...@gmail.com
I would like to add my two cents to this. I had a Motorola ROKR before my Droid with
the MotoRokr T505 car visor bluetooth device. You can press the phone button on the
T505 and use voice dialing through the ROKR phone. 

Droid does not support this because apparently the Bluetooth Stack does not support
callbacks to apps (See the HF Dialer app description of the problem). I am hoping
that the Android Developers will let Apps register call backs for Incoming Bluetooth
requests. Then, the button on my ROKR T505 can trigger an app like the HF Dialer to
start a hands-free voice dialing session. 
May 22, 2010
#15 morri...@gmail.com
 Issue 5956  has been merged into this issue.
May 26, 2010
#16 p.mitche...@gmail.com
If  issue 5215  is being merged with 4848 for de-duplication purposes, this issue
should be re-classified as a bug, not an enhancement.  The priority should also be
set to high/critical.
Jun 4, 2010
#17 brianope...@gmail.com
It is preposterous that a call cannot be intitiated via BT headset using Voice Dial.

Sucha product is in alpha stage of development and should not be released.
Jun 24, 2010
#18 johnsc...@gmail.com
This is an extremely important safety issue.  I can get a free phone from Verizon that will do this, but my $200 Droid phone can't!  In Pennsylvania and many other states it is a law that cell phones must be hands free.  I just bought an HTC Eris 5 days ago, and just found out that it may not get the 2.2 upgrade that is supposed to fix Bluetooth dialing, from an article I found on the web.  When I called Verizon to ask about this, they can't answer the question because it is not up to them, it is up to Google, and HTC.  I am ready to argue with Verizon about giving me another phone that will get the 2.2 upgrade and not have to pay the $35 restocking fee.
My problem is I am trying to replace a dying Palm pilot, and the only way to do that is to get a smart phone (or go back to a pencil and paper schedule, I don't want to lug a laptop every where I go).
Jun 24, 2010
#19 michael5...@gmail.com
This looks to be fixed in Android 2.2, according to the release notes.
Jun 24, 2010
#20 kajer%cz...@gtempaccount.com
nope, FRF50 still does not do anything when the BT button is short/long pressed
Jun 24, 2010
#21 michael5...@gmail.com
pressed

Interesting.  Perhaps your release is not the same as the "official" release
they've posted details on at developer.android.com then.  Remember that a
version of Android on your phone may or may not be a vanilla android
release, usually it's been messed with by the carrier/manufacturer.  Even if
that's google.
Jun 24, 2010
#22 sanjiv.p...@gmail.com
FRF50 on the n1 has blue tooth dialing, maybe your bluetooth handset is faulty?
Jun 25, 2010
#23 justinstrunk@gmail.com
2.2 on my Droid does have voice dialing over bluetooth with a long press of the bluetooth headset.  It works very well most of the time!
Jun 25, 2010
#24 parleyre...@gmail.com
You have 2.2 on your droid already?  I have the LG Ally and would love to have the features advertised in 2.2 especially BT Voice Dial.  I had a palm pre for 2 days and returned it because it too was missing this critical feature.
Jul 22, 2010
#25 sorka95...@gmail.com
I just got my first droid phone and have been unable to get this to work which is pretty much a deal killer. I had no inkling to even make sure this was supported. I just assumed it was. I walk around all day with the phone in my pocket and blutooth headset on. Now I have to take my phone out every time I want to make a call.
Jul 22, 2010
#26 divingda...@gmail.com
This capability is included in Android 2.2 (Froyo), and works very well.
Jul 22, 2010
#27 geoff.ri...@gmail.com
Diving, could you help me out, how do you initiate the voice dial with the headset. I have it and I haven't found a way to do that.
Jul 22, 2010
#28 omal...@gmail.com
Its only for ADP compliant devices which support stereo bluetooth headsets. Meaning the two ear ones.

Very minority one ear bluetooth headphones supported in 2.2

I have a PLantronics Voyager Pro which is not supported.
Jul 22, 2010
#29 divingda...@gmail.com
Somewhere on your headset will be what most manufacturers call an "action
button".  On my Aliph Jawbone Prime it is the "noise assassin" button on the
back end of the earpiece.  Just press and hold the "action button", and it
will launch voice dialing.  You'll see a message pop up on the phone, and in
the earpiece you'll hear a voice say "speak now".  Just say "call bob
smith", and it will do the rest.  If there are two numbers listed for Bob
Smith, it may come back and say "Call bob smith on home or mobile".   You
would just reply "mobile".  Nuthin' to it!
Jul 22, 2010
#30 geoff.ri...@gmail.com
thanks. too bad it doesn't work for wired. I will try out with a bluetooth
Jul 22, 2010
#31 cristinadriscoll
Must wait for 2.2 software update

Comment #27 on issue 4848 by geoff.ricks: Have voice dial work through
bluetooth - very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
Diving, could you help me out, how do you initiate the voice dial with the
headset. I have it and I haven't found a way to do that.
Jul 22, 2010
#32 john.na...@gmail.com
Comment 28 by omaleem:
>Its only for ADP compliant devices which support stereo bluetooth headsets.
>Meaning the two ear ones. Very minority one ear bluetooth headphones supported in 2.2

Gee, that's useful (and competitive with standard handsets).
NOT.
Jul 22, 2010
#33 jflewis88@gmail.com
that's all well and good, except it DOESN'T WORK on Droid.

Comment #29 on issue 4848 by divingdancer: Have voice dial work through
bluetooth - very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
Somewhere on your headset will be what most manufacturers call an "action
button".  On my Aliph Jawbone Prime it is the "noise assassin" button on the
back end of the earpiece.  Just press and hold the "action button", and it
will launch voice dialing.  You'll see a message pop up on the phone, and in
the earpiece you'll hear a voice say "speak now".  Just say "call bob
smith", and it will do the rest.  If there are two numbers listed for Bob
Smith, it may come back and say "Call bob smith on home or mobile".   You
would just reply "mobile".  Nuthin' to it!
Jul 22, 2010
#34 divingda...@gmail.com
Have it only because it is rooted.  Official release looks like it will be
out in a couple of weeks.

But I love it!  My wife is still running stock Android 2.1, and it feels
really clunky when I have to use it.  Loving Flash support (can watch the
Tour on my phone!), the new home screen navigation, bluetooth dialing, five
home screens,  built in tethering, and all the other goodies!
Aug 2, 2010
#35 wsdah...@gmail.com
Is not available with the official release. (Well, at least for me with a HTC Desire). I'm running android 2.2.
Aug 2, 2010
#36 gho57.sh...@gmail.com
It isn't included in the desire as standard but choice dialer now detects
it. Still not implemented properly though as the car still plays music and I
think the phone does not listen on the car mic. I hope a revision of choice
dialer fixes this as I don't want to have to wait for android 2.3!
Aug 2, 2010
#37 sherrife...@gmail.com
Did you contact Tone, the developer of Choice Dial? He is quite receptive
and will help you. I beta tested CD for him, and whenever there was a
problem or concern, he was right on it.

Comment #36 on issue 4848 by gho57.shadow: Have voice dial work through
bluetooth - very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
It isn't included in the desire as standard but choice dialer now detects
it. Still not implemented properly though as the car still plays music and I
think the phone does not listen on the car mic. I hope a revision of choice
dialer fixes this as I don't want to have to wait for android 2.3!
Aug 5, 2010
#38 MLBH18@gmail.com
This is a dangerous flaw 

 Let's hope it doesn't take death/injury lawsuits to get Google/Motorola attention 
Aug 6, 2010
#39 omal...@gmail.com
Whatever, stop making this more than what it is. No big f'n deal. Use your freakin' fingers to type and stop using this as an excuse to get the work done earlier. Im sure they have a proper priority list. 
Aug 6, 2010
#40 sherrife...@gmail.com
Except this IS a huge deal! In many states, you are not allowed to TOUCH the
phone while driving. If I need to place a call (ON ANY PHONE BUT ANDROID),
all I needed to do was push the button on my wireless Bluetooth earpiece. I
would hear "say a command" .....Reply: "call home". Would hear "connecting".
Done. Never touched phone. Phone could stay in briefcase.

Top priority, especially it you live in a hands free area. Basic function of
10 year old phones. Yes, some of these other issues are important, but most
of us need this functionality before Widgets. Bells, whistles and bullshit*t
instead of brilliance. Just dumb.

Comment #39 on issue 4848 by omaleem: Have voice dial work through bluetooth
- very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
Whatever, stop making this more than what it is. No big f'n deal. Use your
freakin' fingers to type and stop using this as an excuse to get the work
done earlier. Im sure they have a proper priority list.
Aug 6, 2010
#41 sorka95...@gmail.com
There's no doubt that this is a serious shortcoming. For years I've been able to initiate calls with voice dialing through my blutooth. This is the first phone I've had in 5 years where I couldn't do that. As much as I like my new Droid X, if I can't see there's a confirmed solution to this in FroYo before my 30 return option is up, the phone will have to go back. I have a 260 mile round trip commute and voice dialing through blutooth is simply not an option.
Aug 6, 2010
#42 john.na...@gmail.com
Comment 40 by sherrifelix:

You are not prohibited from touching the phone in states I know about -- you are just prohibited from making a call without a hands-free device. Voice dialing is not required. And you can always pull over to dial your call -- that's much safer in any event. This is a tempest in a teapot.
Aug 6, 2010
#43 john.na...@gmail.com
Comment 41 by sorka95032:

Voice dialing through speakerphone is both legal and workable. Try it.
I use a cable to connect my Android handset to my car stereo.
Supports Google Maps, music, Internet radio, and calling, better than Bluetooth 
I only use Bluetooth when walking around.
Aug 6, 2010
#44 cristinadriscoll
not everyone has that option, or wants to have to work around a feature that
has been available on practically every other phone for years!

Comment #43 on issue 4848 by john.navas: Have voice dial work through
bluetooth - very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
Comment 41 by sorka95032:

Voice dialing through speakerphone is both legal and workable. Try it.
I use a cable to connect my Android handset to my car stereo.
Supports Google Maps, music, Internet radio, and calling, better than
Bluetooth
I only use Bluetooth when walking around.
Aug 6, 2010
#45 cristinadriscoll
Plus the sound quality thru most stereos, and especially on the receiving
end is Lousy

Comment #43 on issue 4848 by john.navas: Have voice dial work through
bluetooth - very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
Comment 41 by sorka95032:

Voice dialing through speakerphone is both legal and workable. Try it.
I use a cable to connect my Android handset to my car stereo.
Supports Google Maps, music, Internet radio, and calling, better than
Bluetooth
I only use Bluetooth when walking around.
Aug 6, 2010
#46 michael5...@gmail.com
I'm  not sure why you guys are still going on about this, it works in
Android 2.2.  If you don't have that, upgrade your phone or complain to your
carrier.
Aug 6, 2010
#47 omal...@gmail.com
Here.. the complainers can read this:

http://www.androidcentral.com/android-22-froyo-bring-bluetooth-voice-dialing


Maybe you guys need to upgrade from the Tmobile G1's.
Aug 6, 2010
#48 john.na...@gmail.com
Comment 45 by cristinadriscoll:

Sound quality through all the car stereos I've used has been very good to excellent.
Have you actually tried it? ;)
Aug 6, 2010
#49 omal...@gmail.com
I can use my bluetooth to voice dial. Android 2.2 Froyo user here using Nexus One with a cracked screen.

I guess once your motorola gets to 2.2 you'll be able to do it too. Until then, I would advise you to utilize the local transit system if its such a big deal for you. 
Aug 6, 2010
#50 michael5...@gmail.com
I've been using bluetooth through my car stereo since the G1 was first
released.  It works fine for me.

Haven't tried voice-dialing with it on anything but a BlueAnt yet though, I
just got 2.2 on my G1, and my Droid is broken.
Aug 6, 2010
#51 cristinadriscoll
Yes, esp.. receiving end complains,  but also not very good when there is
ambient noise: road noise, other people etc.

Comment #48 on issue 4848 by john.navas: Have voice dial work through
bluetooth - very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
Comment 45 by cristinadriscoll:

Sound quality through all the car stereos I've used has been very good to
excellent.
Have you actually tried it? ;)
Aug 6, 2010
#52 omal...@gmail.com
Wow I didnt know G1 supported 2.2. Anyhow, if you do have 2.2 then you should be able to long press your bluetooth headsets call button and receive the long tone and a voice message indicating to speak the name of the person you'd like to call.


Aug 6, 2010
#53 cristinadriscoll
If you have no issue , I'm haapy for you. This forum is for those wishing to
discuss and get the issue resolved for all.

Comment #49 on issue 4848 by omaleem: Have voice dial work through bluetooth
- very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
I can use my bluetooth to voice dial. Android 2.2 Froyo user here using
Nexus One with a cracked screen.

I guess once your motorola gets to 2.2 you'll be able to do it too. Until
then, I would advise you to utilize the local transit system if its such a
big deal for you.
Aug 6, 2010
#54 michael5...@gmail.com
It doesn't officially, but that's irrelevant, it's very easy to get if you
want.

But back on topic, yes, Android 2.2 supports voice dial just fine, so this
issue probably should be closed.  I see no further need for discussion.
Aug 6, 2010
#55 john.na...@gmail.com
The issues is probably NOT going to be solved on earlier handsets.
What you got is what you got. It's unrealistic to expect more and for free.
If you were unhappy, you should have returned it.
If you're still unhappy, you should upgrade to a handset more to your liking.
This issue should be closed. I'm removing my star. Good luck.
Aug 6, 2010
#56 sherrife...@gmail.com
If a state trooper on NY sees you holding or touching a phone, you can get
pulled over and ticketed. I have used stereo,  but to start a call you need
to touch phone!

Comment #43 on issue 4848 by john.navas: Have voice dial work through
bluetooth - very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
Comment 41 by sorka95032:

Voice dialing through speakerphone is both legal and workable. Try it.
I use a cable to connect my Android handset to my car stereo.
Supports Google Maps, music, Internet radio, and calling, better than
Bluetooth
I only use Bluetooth when walking around.
Aug 6, 2010
#57 sherrife...@gmail.com
No local transit system on Long Island. In NYC, yes. Upstate NY? Gotta be
kidding...Looks like they pushed back the release of Froyo due to bugs....

Comment #49 on issue 4848 by omaleem: Have voice dial work through bluetooth
- very important driving safety isse!


https://code.google.com/p/android/issues/detail?id=4848
I can use my bluetooth to voice dial. Android 2.2 Froyo user here using
Nexus One with a cracked screen.

I guess once your motorola gets to 2.2 you'll be able to do it too. Until
then, I would advise you to utilize the local transit system if its such a
big deal for you.
Aug 9, 2010
#58 adam.mob...@gmail.com
wow, i dont use headset but i just bought the HTC Legend and learned of this google OS issue.  Kind of makes iPhone very appealing! In fact, I would have to say this product is less functional then even the iPhone4 and its antenna issues. On BT headset your not holding iPhone4.  Consumer Electroinc Review people have done a dismal job of imforming people of this massive short coming in the Google platform. But at 200,000 a day sold, why would Google care what any of you think? Did you Bing search this issue or Google it :-) they get paid when you look for problems with their junkie OS. Glad I am tied to a 3 year term on this Legend! It be going up for sale and I get me a phone that has the technology of 5 years ago today.
Aug 9, 2010
#59 randy.du...@gmail.com
I hear rumors that Froyo (2.2) will address this issue, but that is of no help to those of us who are early adopters with phones less than a year old, like the HERO, that won't get an upgrade.  We can't even get a discount on new phones for at least another year.

This issue should be solved on 2.1, and not just 2.2
Aug 9, 2010
#60 bwilliam...@gmail.com
This issue is fixed and workable quite nicely on the EVO, and other devices
running Android 2.2 ..froyo.

and

this

why

sale
Aug 9, 2010
#61 michael5...@gmail.com
Are you going to demand it be fixed in obsolete versions like 1.5 and 1.6
too?  This is unreasonable.

The problem is fixed in 2.2.  Upgrade to 2.2.  If this doesn't work for you,
perhaps you should see if the manufacturer of your phone, or your service
provider has a forum/bug reporting site where you can take this up with
*them*.  From here, it's no longer a Google issue, your complaints are
misplaced.
Aug 9, 2010
#62 bwilliam...@gmail.com
I agree!
Aug 12, 2010
#63 renn...@gmail.com
How long is it going to take to get this fixed.  Phones did this years ago and this advanced device can't handle a basic task
Aug 12, 2010
#64 historyg...@gmail.com
I understand your statement about 1.5 and 1.6, but those of us with 2.1
deserve to have this upgrade.  It's not that big of a deal to push that out
to us.
Aug 12, 2010
#65 michael5...@gmail.com
Oh sure, but your ire is misplaced, you should be discussing this with your
carrier or hardware manufacturer.
Aug 12, 2010
#66 historyg...@gmail.com
It would seem that Google doesn't see this as "solved" or they would've
closed comments and marked it as solved.  I also have shared my concern with
HTC and with Verizon.
Aug 12, 2010
#67 sherrife...@gmail.com
How can this be a carrier or manufactuer problem? All of Verizon's other
phones have voice dial through Bluetooth, so it isn't carrier related. Had a
Motorola Q. Daughter has a Motorola Razor. Both do it as well, showing it
isn't a manufactuer problem. That leaves Google, which we know is where the
fault lies.

They have admitted it, and are trying to correct it in 2.2. (Which I have,
but haven't tried Bluetooth yet).

Please do not tell us that we are complaining to the wrong people.

your
Aug 12, 2010
#68 michael5...@gmail.com
You are, because as we have been saying, the problem IS corrected in 2.2.

It's not google's problem you don't have that yet.

a

the
Aug 12, 2010
#69 michael5...@gmail.com
Of course, I spoke too soon.

Seems that for the brand new Droid2, Verizon Wireless replaced the default Android 2.2 voice stuff (which DOES work with Bluetooth) with some crap from Nuance Communications that does NOT support Bluetooth.

Really Verizon?  Why?

Looks like I'll root and reflash this thing as soon as I can.  Idiots.

Also yes, I *am* going to report this problem to Verizon, rather than complain about it here :)  I just figured I'd provide the community this update.
Aug 12, 2010
#70 michael5...@gmail.com
Okay I spoke too soon yet again.

I'm not sure what was going on, but I had the headset paired and working fine, but it wasn't working.... and now it does.

So confirmed, Android 2.2 on the Droid2 does do this, albeit via a nonstandard application.

Upgrade time, everyone!
Aug 12, 2010
#71 rstu...@gmail.com
Thanks for the update, and warning, I was thinking of getting a Droid2 and
auction off my Droid.  Maybe I'll just put 2.2 on my Droid instead.
Aug 12, 2010
#72 brianhan...@gmail.com
I rooted my Droid with Sapphire.  Running 2.2.  Bluetooth works.
Aug 20, 2010
#73 stagecoa...@gmail.com
This is an appalling oversight, the latest technology is missing the ability to voice dial thru bluetooth which has been available for at least 8 years on much lower tech phones.  Despite the fact that it would be stupid to try to use the phone in a car under these circumstances, someone is going to!
Aug 20, 2010
#74 kentd...@gmail.com
For all that are appalled....

Android 2.1's bluetooth stack was not written to make calls to apps on its own. The bluetooth stack could only respond to requests from apps. This meant that an external device could not start the voice dialer on the phone.

This is fixed in Android 2.2. Buy the VoiceDialer HF app. That's what I did. It is a very good app and it does now get started when an external device's phone button is pressed. I have a Motorola T505 handsfree device and it does work from that device. 

There is still some development that needs to be completed to support handsfree dialing completely. At present, your phone must be out of your pocket and unlocked since the VoiceDialer HF uses the internal microphone on the phone to get your command. However, I've been told that the VoiceDialer HF folks are working on that right now and it will be available eventually. 

I hope this explains the problem and solution well enough for folks. 



Aug 20, 2010
#75 tvkin...@gmail.com
Thanks for the info kentdlee. I thought I saw somewhere that even in 2.2 to use hands free dialing over Bluetooth the phone has to be unlocked.

I hope that's not the case. 

Can anyone verify this? 
Aug 20, 2010
#76 kentd...@gmail.com
I have not done development work for Android so what I'm telling you is what I was told by the VoiceDialer HF folks. They told me that they are working on supporting voice dialing even when the phone is locked but it is not implemented yet. From that comment I'm assuming that there must be some support when the phone is locked.

So, I can only tell you what I was told at this point and it appears there will be full handsfree support in the near future, but I can't promise that since I'm not a developer for the VoiceDialer HF app.

Aug 20, 2010
#77 michael5...@gmail.com
Verified, this is false.  There may be phone-specific restrictions, but
Android 2.2 supports this properly.
Aug 24, 2010
#78 Jeffpack...@gmail.com
It supports it, but not "properly"

There is no verification that what the phone recognized, is what was said.

So I get so many misdials, its almost useless.

Aug 24, 2010
#79 sherrife...@gmail.com
Totally useless for me. Has not got one command correct.
Aug 24, 2010
#80 chad.sim...@gmail.com
Tested on 2.2 (nexus one)with Jawbone Icon. It is a subpar implementation at best I haven't had it get one thing correct(which is strange as the google voice to text service works great for everything else on the phone). It is very hard to understand the voice that tells you what the phone is doing and it doesn't ask for confirmation. Worst of all it just doesn't do anything if you have your phone set up to ask you if you want to use google voice or your regular # to make the call. Come on Google this was a $500.00 phone and while it is years ahead of anything Apple makes it shouldn't be hard to fix these small problems and patch the 2.2 code.
Aug 24, 2010
#81 cristinadriscoll
Is not working on my Droid
...

phone).

google

$500.00
Aug 24, 2010
#82 rstu...@gmail.com
Voice dial is working good for me so far, I had to edit some contacts that
had extra

I agree, it's very robotic sounding voice and not as pleasant to listen to
or understand.  I'm guessing the BB voice-dialer used prerecorded voices and
not a true computer-generated voice that Android uses.
Oct 1, 2010
#83 dapas...@gmail.com
Hi, the voice dial througth bluetooh it's a basic funcionality for a middle cost phone. And not only in english, it's important in all languages.

Sorry for my english, I've to improve it.
Oct 1, 2010
#84 DulcetT...@gmail.com
Choice Dialer Plus (and Choice Dialer Plus Free) support Bluetooth voice dialing on Android 2.2 phones, addressing fully these issues cited above:

1.  it works from a locked, sleeping phone.
2.  it confirms by interactive voice before making a call  ... OR ...
3.  it offers verbal feedback of an unconfirmed call being made

An adjustable preference allows the user to establish a confidence threshold as to whether and when the app offers behavior 2 or (when the command seemed crystal clear) behavior 3.
Oct 1, 2010
#85 Vallely...@gmail.com
DulcetTone, does this app use the headset or vehicle's microphone? Or still the phone mic as it is now since 2.2?
Oct 1, 2010
#86 rstu...@gmail.com
Moto's Droid 2 uses some third party voice dial app.  It sucks and doesn't
work most of the time if you have Exchange email setup.
Oct 1, 2010
#87 sorka95...@gmail.com
I've been on Froyo 2.3.15 (verizon's release) on my droid x for a week now. The built in void dialer can now be activated through my Plantronics Voyager 510. However, it is always 100% inaccurate. It NEVER recognizes the name I'm trying to call. I did the voice training on it multiple times and it makes no difference.

Every other phone I've had for the last 5 years with that specific headset has been 98% accurate at voice recognition.
Dec 31, 2010
#88 Salmoncannon@gmail.com
While I support any issues being fixed because you people will keep driving while talking on your cell phones no matter what, be aware that no matter how you're talking on your phone while you're driving ITS JUST AS DANGEROUS AS WHILE HOLDING THE PHONE.

The reason why talking and driving is dangerous is because of DIVIDED ATTENTION, NOT because YOU'RE PHYSICALLY HOLDING OR TOUCHING THE PHONE.
Dec 31, 2010
#89 gho57.sh...@gmail.com
And a happy new year to you too mate
Jan 2, 2011
#90 lid...@gmail.com
I was pleased to note that bluetooth voice dialing is available in Froyo, but like some of the others, it is entirely inaccurate. I haven't been able to get it to do one thing correctly (while the normal voice actions work fine). Does anyone have it actually working?
Jan 2, 2011
#91 acastell...@gmail.com
I have to say I get about 80 - 90% accuracy on voice dialing through my bluetooth headset through my EVO. I have not done anything special, but do find I need to talk very slowly and enunciate every syllable. Are you using the correct syntax - "call firstname lastname on mobile" or "call firstname lastname at home?"
Jan 5, 2011
#92 lid...@gmail.com
Yep, I've tried using the exact examples given on the dialogue.
Jan 6, 2011
#93 angieb.m...@gmail.com
I think that for many of us, it is not that you cannot place a voice-enabled bluetooth call using the headset of your choice.  My issue is that the voice recognition sometimes doesn't get it RIGHT and proceeds to dial the wrong number causing me to have to pick the phone up to eventually stop the bad call.

I am SHOCKED that the powers that be would actually design a phone WITHOUT the confirmation capability!! What are we in, the 1990's?? C'mon! Give me a break!

The way it SHOULD work is like this:
1. I initiate voice dialing on my headset and say "Call John Doe at Mobile"
2. The PHONE should recognize my command and come back CONFIRMING with something like "Did you say Call John Doe at Mobile?"
3. I say YES and it immediately dials.

In the instance that it was WRONG in the confirmation, it should come back with perhaps 3 alternative suggestions offering confirmation after each one... "Did you say Call John Doe at Home?"...NO..."Did you say Call John Lowe at Mobile?"...YES!




Jan 6, 2011
#94 keithho...@gmail.com
I totally agree.  That's the way my LG phone worked from day one and I had
that phone
over 5 years ago!  It seems as though the Google folks are so full of
themselves that
they don't stop to find out what the rest of the world wants, needs, and is
already
happy with. They assume that they are so much more advanced that they ignore
the customer entirely.
Jan 6, 2011
#95 rstu...@gmail.com
Worse is the Moto X and Droid 2 with their 3rd party dialer.  It won't work
if the phone screen is locked... but if by some chance it does it will to
the "Did you say Call..." verification.
Jan 7, 2011
#96 pieter.n...@gmail.com
More and more I am appreciating my old win6.1 phone. Voice dial like a dream on BT. I'll return my captivate (with ATT states supports voice dial on the ATT product page!)
http://www.wireless.att.com/cell-phone-service/cell-phone-details/index.jsp?device=Samsung+Captivate+-+Black&q_sku=sku4760319  "Voice dialing and voice commands"
Let's check out some win7 phones...
Jan 10, 2011
#97 kconove...@gmail.com
I am using an HTC EVO with 2.2 (froyo) and cannot use voice dialing with my Parrot CK3100 handsfree kit (one of the most popular units), which consists of a directional mike, wiring to mute the stereo and allow sound through the car stereo speakers, and a small dashboard unit with a green button, a red button, a dial, and a very small LCD display. It worked fine with my (now-dead) Treo 755p. With the Treo, I relied on voice recognition on the unit itself. I could say a command work (prikazvyet is what I chose, Russian for command, as in Larry Niven's "The Integral Tress" series), or press the green button, and then say the name of a phone number I had previously trained. Worked like a charm.

But with my new HCT EVO/Android 2.2, the phone's internal dialing service seems to disable the CK3100's internal functions. That would be OK, except that after a quick request to speak, the connection with the phone disconnects and give an error message before I have a chance to say anything. 

Browsing the web, it's been suggested that this is an internal bug in Android 2.2, such that if one has more than 800 contacts (I have 1700), this premature disconnect will occur. At this point, I've concluded this is a bug in Android 2.2 - would like to be proven incorrect and a fix suggested.

Thanks for any thoughts. 
Jan 12, 2011
#98 RLEngst...@gmail.com
This needs to be HIGHEST priority
Jan 20, 2011
#99 ssvangu...@gmail.com
Ah, just noticed I was posting to a redundant thread.  Glad we have this one moving up the 'must fix' list!
Jan 21, 2011
#101 bossk...@gmail.com
Although I desperately want this correctly implemented, it's important for the developers to realize that voice confirmation prior to dialing is an integral part of this function.
Jan 21, 2011
#102 gajic.zo...@gmail.com
I miss my "stupidphone" SEK770i when I am in my car, old school voice recorded actions are the simple and rock solid solution, but that will be a step backward.
Feb 1, 2011
#103 farfigneutron
Voice dial confirmation ( auditory ) is essential. Please fix.
Feb 13, 2011
#104 marchin...@gmail.com
It's truly incredible that this basic feature, available for years on dumb Nokia, Motorola, etc. phones, is not available for Android.
Feb 19, 2011
#105 nfsmit...@gmail.com
I realize this issue has been fixed for many Galaxy S phones, but NOT YET WITH AT&T's Captivate. It's late February 2011 already, and STILL not fixed. Disgusting.
Mar 29, 2011
#106 derek.pi...@gmail.com
I found this thread trying to see if I was doing something wrong with my new Android phone in that it wouldn't just get on with it and dial without displaying a prompt. Surely make it selectable. If you want to risk dialing the wrong person, I'd like that option.
Jan 8, 2012
#107 mschaffe...@gmail.com
I see something that used to be taken for granted on *much* older phone platofrms is still buggy or simply doesn't work.
Truly sad.

This still doesn't work on the HTC Evo 4G.  (Well, maybe once in a "Blu" moon.)  Usually, the voice dial app crashes.  There's an almost 100% probability that, if it does diegn to work that the Blutooth volume is set to something inaudible (regardless of how many times it has been increased prior to using it) so that you cannot possibly hear the "say a command" prompt.

Also.  Honestly.  Doesn't anyone ever try to use it?  Have you tried redialing?  The confirmation prompt states (in "English")  REE-DEE-AL.

It's all truly sad.
Feb 10, 2012
#108 kent94...@gmail.com
I just got an HTC Sensation (T-Mobile) with 2.3.4.  I discovered that the voice dialing had no confimation when I tried to "call traffic" and the phone decided to connect me to a former employee who was let go.  Mighty awkward.

I assumed I'd just failed to enable some setting, but I was amazed to find that this is a known problem and that Google, for whatever reason, has just let it slide.  The mad scramble to abort a mis-dial is definitely less safe in a car than dialing by hand in the first place would have been.

This situation truly defies my understanding of what Google is thinking.  Seeing literally several years' worth of complaints go unaddressed seems both clueless and arrogant.  I can't believe there is a technical obstacle to having a confirmation step, and if it's really a patent question, Google should step up and pay the $$ or work out a licensing trade, or something.  And (gasp) acknowledge the problem!

Maybe it will take a media/gov't spin of "Android phones don't qualify as hands free devices and therefore can't be used in a car" to light a fire under Google.
Mar 16, 2012
#109 adam.her...@gmail.com
agree with previous posters, a simple confirmation of "did you say, dial John Smith" would greatly improve the user experience. I don't want to add an additional app for functionality that my phone already has. Confirmations would be a great improvement!
Sign in to add a comment

Powered by Google Project Hosting