Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

Bluetooth issues - stock player fine, nothing else works over A2DP

bluetooth a2dp

  • Please log in to reply
1 reply to this topic

#1 goyuix

goyuix
  • Members
  • 2 posts
  • Country:us
  • Device Model:N1
  • MOD Version:CM6
  • Recovery Image:Amon_RA

Posted 06 January 2012 - 09:23 PM

The headset profile seems to work when paired with my Toyota Tundra as does audio from the stock Music app (not Google Music) - but pretty much anything else that generates audio over A2DP is broken: Games, Movies, even just an MP3 being played in-browser or from something like File Expert. I noticed this start happening about the same time as the artist/album information was being displayed on the radio display. I believe this started with an upgrade to the bluez stack around CM7.1, though I am not 100% sure. I am still trying to track down some better info before reporting it as a bug.

Has anyone else experienced something like this? I am currently flashed to the latest nightly #253. I have created a pastebin with the logcat data. I have alogcat running, switch over to Google Listen, hit play - after a second of it not working (but acting like it is trying to) I pause the playback and switch back to alogcat:

http://pastebin.com/58fnURt0

Any help? I looked at the commits to the bluez source tree on github.com and it looks like there are some tweaks that were introduced to deal with wonky Ford/Sony stereos. I am not sure who Toyota sourced their deck from, and I am not sure how to even grab the needed information to pass it along with a bug report.

I have also tested this with a SoundFly BT->FM radio adapter and it works fine in all different audio modes and sources. It seems to be something peculiar with the Tundra radio itself. Any help getting the needed info so it can be pushed upstream into CM9 would be awesome. Thanks!

#2 nemooo

nemooo
  • Members
  • 2 posts
  • LocationPARIS
  • Country:fr
  • Device Model:N1 / NS I9023
  • MOD Version:N1 CM7 RC2 / NS CM9 latest NB
  • Recovery Image:ClockworkMod

Posted 29 March 2012 - 11:19 AM

Hi,


You're right since bluez arrive i have the same issue in my nexus one even in the last RC 7.2.

I see the same thing of you, even more, since it's paired with the car receiver ( a toyota auris ) the default gapps music player it's launched. And if you launch any other audio apps ... like spotifiy or navigation in my case, the car receiver made pause.

I have a nexus S too ... in the first CM9 with stock bluetooth stack everything working fine. Since my last nighlty it's launched the default gapps music but, if switch to other audio source the streaming it's still working.

As i can look in the bluetooth specifaction for me it's not A2DP but AVRCP.


AVRCP

A/V Remote Control Profile. Commonly used in car navigation systems to control streaming Bluetooth audio.

I have two headset too. A philips and a seinhenser and there are no issue for its.


So AVRCP seems to be invoke for specific devices as car BT devices.


I never find any related lines in my logcat !!!

So for me it's bug . But it can be place in toyota side.

ThKZ

N






Also tagged with one or more of these keywords: bluetooth, a2dp