On Wed, May 27, 2009 at 8:10 PM, Raymond C. Rodgers <[email protected] > wrote:
> > Raymond C. Rodgers wrote: > > Nick Pelly wrote: > >> On Sun, Dec 21, 2008 at 12:29 PM, Raymond Rodgers > >> <[email protected]> wrote: > >> > >>> I just signed up for service with T-mobile and got a G1 yesterday, and > >>> right away paired it with my Jabra BT5020 which I've had for about a > >>> year now. Right off the bat I discovered that using the headset's call > >>> button does not trigger the voice dialing/command feature of the > >>> G1/Android. As it wasn't urgent, I dismissed that, and did a bit of > >>> research later. It appears that this functionality is hit and miss with > >>> various bluetooth headsets; some messages on various forums report that > >>> some headsets work perfectly while others don't, some say that it just > >>> doesn't work with Jabra headsets, and still others claim that it's only > >>> Jabra headsets that have the problem. > >>> > >>> I contacted Jabra's tech support and they suggested resetting the phone > >>> (by removing the battery for 10 seconds and then powering it back up) > >>> and headset (by charging it for 5-10 seconds), but this didn't solve > >>> the > >>> problem either. I also sent an email to T-mobile's tech support, but I > >>> haven't gotten a response back yet. I know it's not my headset itself > >>> that is the problem because it still works fine with my previous phone > >>> (LG enV/VX9900). > >>> > >>> Is this an Android compatibility issue? If so, is this something that's > >>> being worked on? > >>> > >> > >> Bluetooth voice dialing support was added in the cupcake codebase. > >> It's not in 1.0. > >> > >> Nick Pelly > >> Android Systems Engineer > >> > >> > > (Old, brief conversation that I'm moving over to this list because the > > developer's list isn't appropriate.) > > > > I just updated my G1 (not ADP1) to 1.5 "cupcake" and it appears that > > this issue hasn't been resolved. Under 1.1, and I believe 1.0, I was > > able to press the call button twice within a short time to get the > > phone to redial the last number called, and that is still present, but > > just pressing the call button once should at least bring up the voice > > dialing functionality, which it does not. > > > > Did this feature get missed for 1.5? Is this something that still > > hasn't been implemented? Or is it just that my Jabra headset doesn't > > work with that feature? > > > > Thanks, > > Raymond > Nick are you still out there? > We implemented it, but pulled it from cupcake before release, due to poor user experience: 1) We don't yet have text-to-speech, so there was no way to confirm your call without interacting with the phone. This defeated the point of using BT voice dialing. 2) The voice recognition engine used for voice dialing turned out to be very inaccurate with the 8 khz stream Bluetooth is capable of. Given these problems it was better to remove this feature, allowing headsets to map the button that triggers voice dialing to some more useful feature (such as redial). It is up to the headsets to decide how to map buttons to features but they can use the hint that we do not advertise voice dialing in our AT+BRSF exchange. If you are prepared to live with the problems i've mentioned then you can make a custom Android build with BT voice dialing enabled: In BluetoothHeadset.java change DISABLE_BT_VOICE_DIALING to false. Nick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
