[Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness

[Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness

[Chris Carlin]

With the amount of experimentation I've done in the past couple of days 
it's hard to figure out what information is relevant. I'll try to boil 
it down:

I couldn't get btsco to work, though a2play did.

With pcm_a2dpd I get occasional (~one every two minutes) chirps out of 
the headphones, mainly when interrupting ogg123 (aplay, whatever). 
hcidump -X -V shows no traffic except briefly when those chirps occur. 
Sound is fine through the alsa redirect.

With pcm_a2dpd2 I have jumpy, very sped up sound from the headphones and 
plenty of traffic through hcidump. Alsa redirect sounds about the same 
as the headphones, but the daemon gives the following errors:

A2DPD[21:11:15.563]: alsa_transfer_raw: (errno=32:Broken pipe)EPIPE(-32)
A2DPD[21:11:15.983]: append_to_ring_buffer: Ring buffer is full
A2DPD[21:11:15.983]: append_to_ring_buffer: Ring buffer is full
A2DPD[21:11:15.986]: append_to_ring_buffer: Ring buffer is full

and on, filling the screen with the full buffer messages.


I suppose that basically describes the situation. The rest is 
background. I'm willing to do whatever I can to help, but as my C is 
rusty I figure it's time to ask the devs.

~Chris



Background:
I followed the build instructions and troubleshooting for Plugz at 
bluetooth-alsa.sf.net. Everything went without a hitch as far as I can see.

I have a pair of Creative CB2530 headphones. I've tried them with four 
different bluetooth dongles including both Broadcom and CSR (currently a 
DLink DBT-120). There were no differences between dongles. Connecting is 
never problematic at all.

This is Gentoo with Bluez 3.9 and kernel 2.6.20 with the sco patches.

carlin1 ~ # hciconfig -a
hci0:   Type: USB
         BD Address: 00:17:9A:2B:73:53 ACL MTU: 384:8 SCO MTU: 64:8
         UP RUNNING PSCAN
         RX bytes:989913 acl:63621 sco:0 events:13344 errors:0
         TX bytes:7630626 acl:24367 sco:0 commands:67 errors:0
         Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
         Link policy: RSWITCH HOLD SNIFF PARK
         Link mode: SLAVE ACCEPT
         Name: 'BlueZ (0)'
         Class: 0x3e0100
         Service Classes: Networking, Rendering, Capturing, Object 
Transfer, Audio
         Device Class: Computer, Uncategorized
         HCI Ver: 2.0 (0x3) HCI Rev: 0x77b LMP Ver: 2.0 (0x3) LMP 
Subver: 0x77b
         Manufacturer: Cambridge Silicon Radio (10)

carlin1 ~ # hcitool info 00:0D:E8:01:BB:A3
Requesting information ...
         BD Address:  00:0D:E8:01:BB:A3
         Device Name: CB2530
         LMP Version: 1.2 (0x2) LMP Subversion: 0x3d
         Manufacturer: Zeevo, Inc. (18)
         Features: 0xff 0xff 0x05 0x78 0x18 0x18 0x00 0x80
                 <3-slot packets> <5-slot packets> <encryption> <slot 
offset>
                 <timing accuracy> <role switch> <hold mode> <sniff mode>
                 <park state> <RSSI> <channel quality> <SCO link> <HV2 
packets>
                 <HV3 packets> <u-law log> <A-law log> <CVSD> <power 
control>
                 <enhanced iscan> <interlaced iscan> <interlaced pscan>
                 <inquiry with RSSI> <AFH cap. slave> <AFH class. slave>
                 <AFH cap. master> <AFH class. master> <extended features>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness

[Brad Midgley]

Chris

> With pcm_a2dpd2 I have jumpy, very sped up sound from the headphones and 
> plenty of traffic through hcidump. Alsa redirect sounds about the same 
> as the headphones, but the daemon gives the following errors:

I'm not following you here. What's the difference between using
pcm_a2dpd2 and the "alsa redirect"? I didn't catch what "same as the
headphones" was referring to either.

Brad



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] RE : Plugz, a2dpd, and a2dpd2 strangeness

[Frederic Dalleau]

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

Brad,
> I guess he is talking about sending sound from plugins to alsa instead of bt 
> enablealsaredirect=1

Chris
> hcidump -X -V shows no traffic except briefly when those chirps occur.
I understand you have sound through alsa but not through a2dp, and only occasional chirps?
What headset/adapter is it? Did you start hcidump before a2dpd?
Make sure to use 44100hz 16bits samples.
I need the full a2dpd -g output or enabledebug=1 in a2dprc to help more.
Use pcm_a2dpd if it gives good result through alsa.

Frederic

-------- Message d'origine--------
De: bluez-devel-bounces@lists.sourceforge.net de la part de Brad Midgley
Date: ven. 27/04/2007 06:03
À: BlueZ development
Objet : Re: [Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness
 
Chris

> With pcm_a2dpd2 I have jumpy, very sped up sound from the headphones and 
> plenty of traffic through hcidump. Alsa redirect sounds about the same 
> as the headphones, but the daemon gives the following errors:

I'm not following you here. What's the difference between using
pcm_a2dpd2 and the "alsa redirect"? I didn't catch what "same as the
headphones" was referring to either.

Brad



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3608 bytes --]

[-- Attachment #3: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness

[Chris Carlin]

Brad Midgley wrote:
>> With pcm_a2dpd2 I have jumpy, very sped up sound from the headphones and 
>> plenty of traffic through hcidump. Alsa redirect sounds about the same 
>> as the headphones, but the daemon gives the following errors:
> 
> I'm not following you here. What's the difference between using
> pcm_a2dpd2 and the "alsa redirect"? I didn't catch what "same as the
> headphones" was referring to either.

In retrospect I think I wasn't clear about pcm_a2dpd and pcm_a2dpd2. By 
those I meant the alsa plugins (libasound_module_pcm_a2dpd[2].so) as 
opposed to the similarly named daemon and NOT a definition in my .asoundrc.

The "alsa redirect" meant setting enableredirectalsa=1 in .a2dprc. I 
gather that this causes the a2dpd system to spit sound back out through 
alsa to speakers instead of through a bluetooth connection.

To restate more clearly (maybe) I'll give you a chart:

a2dpd plugin ("type a2dpd" in .asoundrc):
	bluetooth headphones (enableredirect=0 in .a2dprc):
		occasional chirps
		almost no traffic through hcidump
		flags=1 only gives info upon occurrance of chirps
	normal computer speakers (enableredirect=1):
		music sounds fine
a2dpd2 plugin ("type a2dpd2"):
	bluetooth headphones (enableredirect=0):
		garbled, sped up sound
		plenty of hcidump traffic
		flags=1 reports once a second or so
	normal computer speakers (enableredirect=1):
		garbled, sped up sound
		ring buffer full messages spew forth

An interesting thing to me is that enableredirect, if it does what I 
think it does, seems to show a non-bluetooth problem...

~Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] RE : Plugz, a2dpd, and a2dpd2 strangeness

[Chris Carlin]

carlin1 ~ # a2dpd -g
A2DPD[10:29:49.541]: init_ipc: Selected IPC: unix, addr=127.0.0.1, 
bcst=127.0.0.255, port=21453
A2DPD[10:29:49.541]: make_daemon_process: a2dpd [Apr 26 2007 17:07:32] 
starting ...
A2DPD[10:29:49.541]: main: (errno=9:Bad file descriptor)a2dpd 
addr=00:0D:E8:01:BB:A3 timer=999 us [Apr 26 2007 17:07:37]
A2DPD[10:29:49.541]: a2dpd_signal_init: Getting on DBUS
A2DPD[10:29:49.542]: a2dpd_signal_init: Installing watch
A2DPD[10:29:49.542]: add_dbus_watch: Added watch 0 0x809b8b8 disabled
A2DPD[10:29:49.542]: add_dbus_watch: Added watch 1 0x809b8e0 enabled
A2DPD[10:29:49.542]: a2dpd_signal_init: Registering object path: 
/com/access/a2dpd
A2DPD[10:29:49.542]: a2dpd_signal_init: Acquiring service: com.access.a2dpd
A2DPD[10:29:49.542]: a2dpd_signal_init: OK
A2DPD[10:29:49.542]: a2dpd_signal_init: OK
A2DPD[10:29:49.542]: a2dpd_register_sdp: OK
A2DPD[10:29:49.542]: add_avrtg:
A2DPD[10:29:49.542]: add_a2source:
A2DPD[10:29:49.542]: main_loop:
A2DPD[10:29:49.542]: make_server_socket:
A2DPD[10:29:49.542]: bta2dpdevicenew:
A2DPD[10:29:49.542]: a2dpd_signal_address_changed: 00:0D:E8:01:BB:A3
A2DPD[10:29:49.543]: a2dpd_signal_set_socket: Signal socket set to 7
A2DPD[10:29:49.543]: a2dpd_signal_state: Disconnected
A2DPD[10:29:49.543]: a2dp_alloc:
A2DPD[10:29:49.543]: a2dp_alloc: (a2dp = 0x80a9290)
A2DPD[10:29:49.543]: a2dp_new: 00:0D:E8:01:BB:A3, 32000
A2DPD[10:29:49.543]: a2dp_new: State AVDTP_STATE_DISCONNECTED
A2DPD[10:29:49.543]: alsa_new:
A2DPD[10:29:49.543]: alsa_new: device=plughw:0,0, framerate=32000
A2DPD[10:29:49.543]: alsa_new: State ALSA_STATE_DISCONNECTED
A2DPD[10:29:49.543]: alsa_new: returning 0x80ab418
A2DPD[10:29:49.543]: sco_new:
A2DPD[10:29:49.543]: sco_new: State SCO_STATE_DISCONNECTED
A2DPD[10:29:49.543]: sco_state_disconnect: Filtering state : already 
disconnected
A2DPD[10:29:49.543]: main_loop: Bluetooth Device Settings [32000 hz, 2 
channels, 16 bits]
A2DPD[10:29:49.544]: avrcp_new: Listening for AVRCP on socket 9
A2DPD[10:29:49.544]: avrcp_new: 0x80ab528

***hit play***

A2DPD[10:29:53.502]: pollfd_cb_sockfd: Client 10 got index 0
A2DPD[10:29:53.502]: stream_client_state_streamingsetup: PLAYBACK thread 
client_index=0, socket=10, id=0 started (44100 Hz, 2 channels, 16 bits)
A2DPD[10:29:53.503]: a2dp_state_connect: State AVDTP_STATEX_SDP_CONNECTING
A2DPD[10:29:53.503]: a2dp_state_machine: Role is INITIATOR
A2DPD[10:29:53.503]: a2dp_state_machine: (errno=115:Operation now in 
progress)SDP connection on socket 11
A2DPD[10:29:53.503]: a2dp_state_machine: State 
AVDTP_STATEX_SDP_CONNECTING_WAIT
A2DPD[10:29:53.503]: a2dpd_signal_state: Connecting 00:0D:E8:01:BB:A3
A2DPD[10:29:56.722]: a2dp_state_machine: SDP connection terminated
A2DPD[10:29:56.744]: get_avdtp_psm: Parsing results
A2DPD[10:29:56.744]: get_avdtp_psm: Record
A2DPD[10:29:56.744]: get_avdtp_psm: Service Search OK
A2DPD[10:29:56.761]: get_avdtp_psm: Checking non spec audio
A2DPD[10:29:56.761]: a2dp_state_machine: Found psm 25
A2DPD[10:29:56.761]: a2dp_state_machine: State AVDTP_STATEX_CTL_CONNECTING
A2DPD[10:29:56.761]: a2dp_state_machine: Socket is 11
A2DPD[10:29:56.761]: a2dp_state_machine: (errno=115:Operation now in 
progress)State AVDTP_STATEX_CTL_CONNECTING_WAIT
A2DPD[10:29:56.784]: a2dp_state_machine: State AVDTP_STATE_IDLE
A2DPD[10:29:56.785]: a2dp_state_machine: State AVDTP_STATEX_DISCOVERING
A2DPD[10:29:56.786]: a2dp_state_machine: State AVDTP_STATEX_DISCOVERING_RESP
A2DPD[10:29:56.800]: a2dp_handle_avdtp_message: Read non command packet 
(msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_DISCOVER)
A2DPD[10:29:56.800]: a2dp_state_machine: AVDTP_DISCOVER success
A2DPD[10:29:56.800]: a2dp_state_machine: State 
AVDTP_STATEX_GETTING_CAPABILITIES
A2DPD[10:29:56.801]: a2dp_state_machine: Getting capabilities for SEID=1
A2DPD[10:29:56.801]: a2dp_state_machine: State 
AVDTP_STATEX_GETTING_CAPABILITIES_RESP
A2DPD[10:29:56.812]: get_socket_omtu: Socket 9 imtu=672, omtu=0, 
flush_to=65535
A2DPD[10:29:56.812]: pollfd_cb_avrcpfd: socket 12: Connection from 
A3:BB:01:E8:0D:00, mtu=610 accepted at index 0
A2DPD[10:29:56.814]: a2dp_handle_avdtp_message: Read non command packet 
(msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_GET_CAPABILITIES)
A2DPD[10:29:56.814]: a2dp_state_machine: AVDTP_GET_CAPABILITIES success 
for seid 1
A2DPD[10:29:56.814]: a2dp_state_machine: servcap_cap=1, servcap_len=0,
A2DPD[10:29:56.814]: a2dp_state_machine: cap_type=7, length=6
A2DPD[10:29:56.814]: a2dp_state_machine: media_type=0, codec=0
A2DPD[10:29:56.814]: a2dp_state_machine: A2DPD  Prefered bitpool 32
A2DPD[10:29:56.814]: a2dp_state_machine: Device Prefered bitpool 2 -> 250
A2DPD[10:29:56.814]: a2dp_state_machine: A2DPD  Selected bitpool 32
A2DPD[10:29:56.814]: a2dp_state_machine: State 
AVDTP_STATEX_SETTING_CONFIGURATION
A2DPD[10:29:56.815]: a2dp_state_machine: State 
AVDTP_STATEX_SETTING_CONFIGURATION_RESP
A2DPD[10:29:56.834]: a2dp_handle_avdtp_message: Read non command packet 
(msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_SET_CONFIGURATION)
A2DPD[10:29:56.834]: a2dp_state_machine: AVDTP_SET_CONFIGURATION success
A2DPD[10:29:56.834]: a2dp_state_machine: State AVDTP_STATEX_STREAM_OPENING
A2DPD[10:29:56.835]: a2dp_state_machine: State 
AVDTP_STATEX_STREAM_OPENING_RESP
A2DPD[10:29:56.851]: a2dp_handle_avdtp_message: Read non command packet 
(msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_OPEN)
A2DPD[10:29:56.851]: a2dp_state_machine: AVDTP_OPEN success
A2DPD[10:29:56.851]: a2dp_state_machine: State AVDTP_STATE_CONFIGURED
A2DPD[10:29:56.852]: a2dp_state_machine: State 
AVDTP_STATEX_STREAM_CONNECTING
A2DPD[10:29:56.853]: a2dp_state_machine: Socket is 13
A2DPD[10:29:56.853]: a2dp_state_machine: (errno=115:Operation now in 
progress)State AVDTP_STATEX_STREAM_CONNECTING_WAIT
A2DPD[10:29:56.884]: a2dp_state_machine: Stream connected
A2DPD[10:29:56.884]: get_socket_omtu: Socket 13 imtu=672, omtu=678, 
flush_to=65535
A2DPD[10:29:56.884]: a2dp_state_machine: State 
AVDTP_STATE_OPEN_START_STREAMING
A2DPD[10:29:56.885]: a2dp_state_machine: State AVDTP_STATEX_STREAM_STARTING
A2DPD[10:29:56.885]: a2dpd_signal_state: Connected 00:0D:E8:01:BB:A3
A2DPD[10:29:56.886]: a2dp_state_machine: State 
AVDTP_STATEX_STREAM_STARTING_WAIT
A2DPD[10:29:56.900]: a2dp_handle_avdtp_message: Read non command packet 
(msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_START)
A2DPD[10:29:56.900]: a2dp_state_machine: AVDTP_START success
A2DPD[10:29:56.900]: a2dp_state_machine: State AVDTP_STATE_STREAMING

***ogg123 says it's playing; no sound except for occasional chirps; no 
new messages from a2dpd***

***hit stop***


A2DPD[10:30:22.184]: pollfd_cb_clients: Client 0: Error detected (err=0, 
toc=0, err=0, hup=1)

> What headset/adapter is it? Did you start hcidump before a2dpd?

Headset is Creative CB2530. I've had identical results from four 
different adapters including both Broadcom and CSR chipsets, currently 
using a DLink DBT-120.

Started hcidump before.

~Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] RE : Plugz, a2dpd, and a2dpd2 strangeness

[Frederic Dalleau]

The only thing I see is you use rate=32000, use rate=44100.
The whole a2dpd connection seems established.
I suggest you try another headset.


Chris Carlin wrote:
> carlin1 ~ # a2dpd -g
> A2DPD[10:29:49.541]: init_ipc: Selected IPC: unix, addr=127.0.0.1, 
> bcst=127.0.0.255, port=21453
> A2DPD[10:29:49.541]: make_daemon_process: a2dpd [Apr 26 2007 17:07:32] 
> starting ...
> A2DPD[10:29:49.541]: main: (errno=9:Bad file descriptor)a2dpd 
> addr=00:0D:E8:01:BB:A3 timer=999 us [Apr 26 2007 17:07:37]
> A2DPD[10:29:49.541]: a2dpd_signal_init: Getting on DBUS
> A2DPD[10:29:49.542]: a2dpd_signal_init: Installing watch
> A2DPD[10:29:49.542]: add_dbus_watch: Added watch 0 0x809b8b8 disabled
> A2DPD[10:29:49.542]: add_dbus_watch: Added watch 1 0x809b8e0 enabled
> A2DPD[10:29:49.542]: a2dpd_signal_init: Registering object path: 
> /com/access/a2dpd
> A2DPD[10:29:49.542]: a2dpd_signal_init: Acquiring service: com.access.a2dpd
> A2DPD[10:29:49.542]: a2dpd_signal_init: OK
> A2DPD[10:29:49.542]: a2dpd_signal_init: OK
> A2DPD[10:29:49.542]: a2dpd_register_sdp: OK
> A2DPD[10:29:49.542]: add_avrtg:
> A2DPD[10:29:49.542]: add_a2source:
> A2DPD[10:29:49.542]: main_loop:
> A2DPD[10:29:49.542]: make_server_socket:
> A2DPD[10:29:49.542]: bta2dpdevicenew:
> A2DPD[10:29:49.542]: a2dpd_signal_address_changed: 00:0D:E8:01:BB:A3
> A2DPD[10:29:49.543]: a2dpd_signal_set_socket: Signal socket set to 7
> A2DPD[10:29:49.543]: a2dpd_signal_state: Disconnected
> A2DPD[10:29:49.543]: a2dp_alloc:
> A2DPD[10:29:49.543]: a2dp_alloc: (a2dp = 0x80a9290)
> A2DPD[10:29:49.543]: a2dp_new: 00:0D:E8:01:BB:A3, 32000
> A2DPD[10:29:49.543]: a2dp_new: State AVDTP_STATE_DISCONNECTED
> A2DPD[10:29:49.543]: alsa_new:
> A2DPD[10:29:49.543]: alsa_new: device=plughw:0,0, framerate=32000
> A2DPD[10:29:49.543]: alsa_new: State ALSA_STATE_DISCONNECTED
> A2DPD[10:29:49.543]: alsa_new: returning 0x80ab418
> A2DPD[10:29:49.543]: sco_new:
> A2DPD[10:29:49.543]: sco_new: State SCO_STATE_DISCONNECTED
> A2DPD[10:29:49.543]: sco_state_disconnect: Filtering state : already 
> disconnected
> A2DPD[10:29:49.543]: main_loop: Bluetooth Device Settings [32000 hz, 2 
> channels, 16 bits]
> A2DPD[10:29:49.544]: avrcp_new: Listening for AVRCP on socket 9
> A2DPD[10:29:49.544]: avrcp_new: 0x80ab528
>
> ***hit play***
>
> A2DPD[10:29:53.502]: pollfd_cb_sockfd: Client 10 got index 0
> A2DPD[10:29:53.502]: stream_client_state_streamingsetup: PLAYBACK thread 
> client_index=0, socket=10, id=0 started (44100 Hz, 2 channels, 16 bits)
> A2DPD[10:29:53.503]: a2dp_state_connect: State AVDTP_STATEX_SDP_CONNECTING
> A2DPD[10:29:53.503]: a2dp_state_machine: Role is INITIATOR
> A2DPD[10:29:53.503]: a2dp_state_machine: (errno=115:Operation now in 
> progress)SDP connection on socket 11
> A2DPD[10:29:53.503]: a2dp_state_machine: State 
> AVDTP_STATEX_SDP_CONNECTING_WAIT
> A2DPD[10:29:53.503]: a2dpd_signal_state: Connecting 00:0D:E8:01:BB:A3
> A2DPD[10:29:56.722]: a2dp_state_machine: SDP connection terminated
> A2DPD[10:29:56.744]: get_avdtp_psm: Parsing results
> A2DPD[10:29:56.744]: get_avdtp_psm: Record
> A2DPD[10:29:56.744]: get_avdtp_psm: Service Search OK
> A2DPD[10:29:56.761]: get_avdtp_psm: Checking non spec audio
> A2DPD[10:29:56.761]: a2dp_state_machine: Found psm 25
> A2DPD[10:29:56.761]: a2dp_state_machine: State AVDTP_STATEX_CTL_CONNECTING
> A2DPD[10:29:56.761]: a2dp_state_machine: Socket is 11
> A2DPD[10:29:56.761]: a2dp_state_machine: (errno=115:Operation now in 
> progress)State AVDTP_STATEX_CTL_CONNECTING_WAIT
> A2DPD[10:29:56.784]: a2dp_state_machine: State AVDTP_STATE_IDLE
> A2DPD[10:29:56.785]: a2dp_state_machine: State AVDTP_STATEX_DISCOVERING
> A2DPD[10:29:56.786]: a2dp_state_machine: State AVDTP_STATEX_DISCOVERING_RESP
> A2DPD[10:29:56.800]: a2dp_handle_avdtp_message: Read non command packet 
> (msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_DISCOVER)
> A2DPD[10:29:56.800]: a2dp_state_machine: AVDTP_DISCOVER success
> A2DPD[10:29:56.800]: a2dp_state_machine: State 
> AVDTP_STATEX_GETTING_CAPABILITIES
> A2DPD[10:29:56.801]: a2dp_state_machine: Getting capabilities for SEID=1
> A2DPD[10:29:56.801]: a2dp_state_machine: State 
> AVDTP_STATEX_GETTING_CAPABILITIES_RESP
> A2DPD[10:29:56.812]: get_socket_omtu: Socket 9 imtu=672, omtu=0, 
> flush_to=65535
> A2DPD[10:29:56.812]: pollfd_cb_avrcpfd: socket 12: Connection from 
> A3:BB:01:E8:0D:00, mtu=610 accepted at index 0
> A2DPD[10:29:56.814]: a2dp_handle_avdtp_message: Read non command packet 
> (msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_GET_CAPABILITIES)
> A2DPD[10:29:56.814]: a2dp_state_machine: AVDTP_GET_CAPABILITIES success 
> for seid 1
> A2DPD[10:29:56.814]: a2dp_state_machine: servcap_cap=1, servcap_len=0,
> A2DPD[10:29:56.814]: a2dp_state_machine: cap_type=7, length=6
> A2DPD[10:29:56.814]: a2dp_state_machine: media_type=0, codec=0
> A2DPD[10:29:56.814]: a2dp_state_machine: A2DPD  Prefered bitpool 32
> A2DPD[10:29:56.814]: a2dp_state_machine: Device Prefered bitpool 2 -> 250
> A2DPD[10:29:56.814]: a2dp_state_machine: A2DPD  Selected bitpool 32
> A2DPD[10:29:56.814]: a2dp_state_machine: State 
> AVDTP_STATEX_SETTING_CONFIGURATION
> A2DPD[10:29:56.815]: a2dp_state_machine: State 
> AVDTP_STATEX_SETTING_CONFIGURATION_RESP
> A2DPD[10:29:56.834]: a2dp_handle_avdtp_message: Read non command packet 
> (msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_SET_CONFIGURATION)
> A2DPD[10:29:56.834]: a2dp_state_machine: AVDTP_SET_CONFIGURATION success
> A2DPD[10:29:56.834]: a2dp_state_machine: State AVDTP_STATEX_STREAM_OPENING
> A2DPD[10:29:56.835]: a2dp_state_machine: State 
> AVDTP_STATEX_STREAM_OPENING_RESP
> A2DPD[10:29:56.851]: a2dp_handle_avdtp_message: Read non command packet 
> (msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_OPEN)
> A2DPD[10:29:56.851]: a2dp_state_machine: AVDTP_OPEN success
> A2DPD[10:29:56.851]: a2dp_state_machine: State AVDTP_STATE_CONFIGURED
> A2DPD[10:29:56.852]: a2dp_state_machine: State 
> AVDTP_STATEX_STREAM_CONNECTING
> A2DPD[10:29:56.853]: a2dp_state_machine: Socket is 13
> A2DPD[10:29:56.853]: a2dp_state_machine: (errno=115:Operation now in 
> progress)State AVDTP_STATEX_STREAM_CONNECTING_WAIT
> A2DPD[10:29:56.884]: a2dp_state_machine: Stream connected
> A2DPD[10:29:56.884]: get_socket_omtu: Socket 13 imtu=672, omtu=678, 
> flush_to=65535
> A2DPD[10:29:56.884]: a2dp_state_machine: State 
> AVDTP_STATE_OPEN_START_STREAMING
> A2DPD[10:29:56.885]: a2dp_state_machine: State AVDTP_STATEX_STREAM_STARTING
> A2DPD[10:29:56.885]: a2dpd_signal_state: Connected 00:0D:E8:01:BB:A3
> A2DPD[10:29:56.886]: a2dp_state_machine: State 
> AVDTP_STATEX_STREAM_STARTING_WAIT
> A2DPD[10:29:56.900]: a2dp_handle_avdtp_message: Read non command packet 
> (msgtype=MESSAGE_TYPE_ACCEPT,signal=AVDTP_START)
> A2DPD[10:29:56.900]: a2dp_state_machine: AVDTP_START success
> A2DPD[10:29:56.900]: a2dp_state_machine: State AVDTP_STATE_STREAMING
>
> ***ogg123 says it's playing; no sound except for occasional chirps; no 
> new messages from a2dpd***
>
> ***hit stop***
>
>
> A2DPD[10:30:22.184]: pollfd_cb_clients: Client 0: Error detected (err=0, 
> toc=0, err=0, hup=1)
>
>   
>> What headset/adapter is it? Did you start hcidump before a2dpd?
>>     
>
> Headset is Creative CB2530. I've had identical results from four 
> different adapters including both Broadcom and CSR chipsets, currently 
> using a DLink DBT-120.
>
> Started hcidump before.
>
> ~Chris
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] RE : Plugz, a2dpd, and a2dpd2 strangeness

[Chris Carlin]

Well there are things that make me think it almost works. For example, 
a2play under btsco basically worked, and if I force the chirps to occur 
quickly enough (by pausing and unpausing the player's process... each 
cycle causes a chirp) they merge into music. To my uninformed mind this 
suggests that plugz might work with the headphones if it would just send 
the data.

So perhaps just to satisfy my own curiosity, why is a2dp not sending any 
data over bluetooth, as shown through hcidump? Is it waiting for some 
sort of acknowledgment from the headset?

And what's the status of a2dpd versus a2dpd2?

~Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel