tmassie / aospx

Automatically exported from code.google.com/p/aospx
0 stars 0 forks source link

BlueTooth audio issues when connecting to car radio. #111

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Please describe the problem in detail. Be sure to include:

What steps will reproduce the problem?
clean install, with inpiremod.
install any third party media player.
Connect phone via BT to a car with BT.
Try to play music, or use google maps navigator.

What is the expected output? What do you see instead?
To hear music, or turn-by-turn directions.

Instead, nothing is heard. Both the car radio, and the phone show as connected.

What version of aospX are you using? And when did the issue first start?
BR7.  I think it started with BR7, but did not use BT audio on BR6 or 5.

Please list the kernel version under Settings->About phone
Stock.

Does the issue happen after a full wipe and without any data restored?
yes

Inspire4G or DesireHD? (If Inspire, did you flash Inspiremod?)
Inspire4G, yes.

Please provide logcat ouput and any additional information below.
(logs required or I will discard the ticket.)

Using BT headphones, all media players work.  I'm not sure if this can be 
fixed, or if it's an issue with the car's radio.

As alwasys, if you need any additional info, let me know. 
Thanks for all the hardwork. :)

Original issue reported on code.google.com by patrick....@gmail.com on 14 Sep 2012 at 1:12

Attachments:

GoogleCodeExporter commented 8 years ago
Anyone else able to reproduce this?

Original comment by robbe...@gmail.com on 14 Sep 2012 at 4:32

GoogleCodeExporter commented 8 years ago
I did see "darkoon" (post# 5409) mention it on the XDA thread.

Original comment by patrick....@gmail.com on 14 Sep 2012 at 4:40

GoogleCodeExporter commented 8 years ago
I recognize this issue. I have a low-tech fix for it.

I use BR7 with a "JVC Bluetooth In-Dash Digital Media Receiver". Bluetooth 
pairs OK both for the phone part and the a2dp part. (a2dp = stereo streaming)

Connecting is sometimes troublesome. Often the stereo stream is not actually 
reaching the receiver even, as in your case, the icons on the radio show both 
connections. The receiver will then show "No name", but sometimes it'll show 
the titles of songs played (if I use the "Music" app) still with no sound. The 
sound producing app doesn't matter for whether sound goes through or not.

My fix consists of two parts. I made sure to hide the radio's bluetooth dongle 
not behind the radio itself(with metal parts) but right under a thin plasticy 
part of the dashboard. 

Then I hold the phone in front of the dashboard as it connects. If instead I 
stick the phone to my windshield before it's connected, then it often will not 
do a2dp. 

After connection, I place my phone in its holder. It won't loose a2dp once 
connected.

Don't know whether this will help you. I'm not sure the problem is with BR7 or 
Android or phone hardware. Could be the JVC. (Problem existed for all previous 
BRs I tested as well.)

Original comment by s.imph...@gmail.com on 29 Sep 2012 at 6:29

GoogleCodeExporter commented 8 years ago
New -> Verified

Marking as Verified, but im still not sure where the problem is coming from 
yet. This one will be a little harder for me to test since I dont have car 
audio BT. For those that can reproduce this, i need logs from everyone..that 
way I can compare them and see if i notice a common factor. So more logs the 
better :)... If there is another rom that this works correctly on, please post 
logs of it also so I can see what it should be showing. 

Original comment by robbe...@gmail.com on 4 Oct 2012 at 4:00

GoogleCodeExporter commented 8 years ago
I issued 

  logcat -r10000 -f /sdcat/mylog &

from adb shell. That should give me a 10MB logfile (perhaps up to 4 of them, if 
they're rotated, I'm not sure how this "-f" flag works). Then I unplugged my 
Inspire phone. Fortunately, the subprocess I just created didn't terminate! 
Back at home, I did 

  adb pull /sdcard/mylog ./mylog

so I could peek at it. 

I found some successful a2dp stream setups during an hour of actual use. And I 
caught one setup that wasn't succesful: in fact

  cat /sdcard/mylog | grep -iE 'blue|audio' 

yields (snippet):

D/BluetoothA2dpService( 1351): A2DP: onSinkPropertyChanged newState is: 0 
mPlayingA2dpDevice: null
I/BluetoothProfileState( 1351): Message:Entering Stable State
I/BluetoothDeviceProfileState( 1351): Entering ACL Connected state with: 102
D/BluetoothA2dpService( 1351): A2DP state : device: 00:10:60:D2:DC:6A State:1->0
E/BluetoothA2dpService.cpp( 1351): onConnectSinkResult: D-Bus error: 
org.bluez.Error.Failed (Stream setup failed)
I/Bluetooth HeadsetBase( 1533): headset read error 5
D/Bluetooth HSHFP( 1533): Device: 00:10:60:D2:DC:6A Headset  state2 -> 0
D/BluetoothEventLoop( 1351): Device property changed: 00:10:60:D2:DC:6A 
property: Connected value: false
I/BluetoothDeviceProfileState( 1351): Entering IncomingHandsfree state with: 51
I/BluetoothDeviceProfileState( 1351): Entering ACL Connected state with: 102
D/BluetoothAdapterStateMachine( 1351): BluetoothOn process message: 52
D/BluetoothService( 1351): CONNECTION_STATE_CHANGE: 00:10:60:D2:DC:6A: 2 -> 0

I'd be happy to send logs, but do I have to post them in their entirety? 
(Privacy concerns.) Also, I'd be happy to change log settings if that's useful.

Thanks,

imphead

PS: Apparently, the way to kill the subprocess spawned above is to first do 'ps 
|grep logcat'. Example: two logcat threads are shown: 

root      1263  1230  876    464   c01149a4 40010818 S /system/bin/logcat2
root      4897  1     2124   1716  c01149a4 40010818 S logcat

Second thing is to do is to issue a kill:

kill 4897

And 'ls -l /sdcard/mylog' reveals that /sdcard/mylog stops growing. I'm not 
sure whether I actually killed a real system process.

Original comment by s.imph...@gmail.com on 5 Oct 2012 at 8:38

GoogleCodeExporter commented 8 years ago
MR1 was released awhile back, can the original reporter or someone who has 
already posted please verify one of the following..

"This is still an issue in MR1"

or

"This has been fixed in MR1"

Original comment by robbe...@gmail.com on 23 Oct 2012 at 3:46

GoogleCodeExporter commented 8 years ago
Sorry, missed this. 

My vote is: "This is still an issue in MR1".

Original comment by klarl...@gmail.com on 13 Nov 2012 at 3:05