What steps will reproduce the problem?
1. Connect a bluetooth handsfree
2. Use your handsfree's "BT Action" button
3. Try voice dialing
What is the expected output? What do you see instead?
Voice Dialer/Search stuck on "Initializing".
Tried other apps such as Cyberon Voice dialer, Tasker. The result is about the
same: you hear a prompt (or a part of it), then it does not receive your voice
and hangs there. If cancelled (e.g. with the Back button), you may hear a sound
too. In other words, it can talk to you, but you can't talk to it.
Sometimes some apps seem to keep a handle to the device opened, so audio
doesn't work properly until reboot.
What version of the product are you using? On what operating system?
Using R8, then clean flashed R9, and then dirtyflashed R10 over the R9.
Please provide any additional information below.
Tried it with two BT handsfrees. As far as I know, they are NOT A2DP capable.
As per other posts in forums, I've tried:
- Disabling Google Voice Dialer
- Disabling Google Search (and trying other apps such as Cyberon)
I've tried debugging and fiddling with some kernel drivers (msm7x30.c), but no
success (probably because I haven't bothered to reverse-engineer the whole darn
thing), but I think the problem is as likely to be caused by the android
system, as by the driver.
I'm just reporting this here, though it seems to have come from CM. If anyone
wants to "join the battle", I'll provide whatever logs on demand.
In the meantime, if more people could confirm this, it would be nice. Please,
if you test this, do tell if your headset is A2DP, and/or if you have a "media
audio" channel (besides the "phone audio") in the bluetooth settings for the
handsfree.
Similar bugs have been reported all over the Internet regarding Jeally Bean and
Bluetooth voice dialing. Some of them 'fix' it by disabling the 'media' channel
for the handsfree (on A2DP-capable headsets).
Thank you for your attention (it was a big post to read :))
Original issue reported on code.google.com by jabad...@gmail.com on 14 Jun 2013 at 6:15
Original issue reported on code.google.com by
jabad...@gmail.comon 14 Jun 2013 at 6:15