Hi Scott, On Thu, Feb 28, 2013 at 11:25 PM, Scott James Remnant <keybuk@xxxxxxxxxx> wrote: > I guess I spoke too soon, I can get the endpoint connected with this > config change, but it just fails a little later now with > "avdtp_set_configuration: Transport endpoint is not connected" > > Here's the log of the connect call; note that I see the > SelectConfiguration and reply to it on the endpoint side - but never > receive a SetConfiguration call: > > bluetoothd[24139]: src/device.c:connect_profiles() > /org/bluez/hci0/dev_10_B7_F6_01_31_ED (all), client :1.389 > bluetoothd[24139]: profiles/audio/manager.c:a2dp_sink_connect() path > /org/bluez/hci0/dev_10_B7_F6_01_31_ED > bluetoothd[24139]: profiles/audio/avdtp.c:avdtp_ref() 0x7f68d07c8790: ref=2 > bluetoothd[24139]: profiles/audio/sink.c:sink_connect() stream > creation in progress > bluetoothd[24139]: profiles/audio/sink.c:discovery_complete() Discovery complete There is something off in this log, you should be getting at least the following: bluetoothd[27965]: profiles/audio/avdtp.c:avdtp_connect_cb() AVDTP: connected signaling channel to 58:17:0C:EB:F1:D6 bluetoothd[27965]: profiles/audio/avdtp.c:avdtp_connect_cb() AVDTP imtu=672, omtu=339 Otherwise there is no chance that discovery would complete without an error, anyway I wasn't able to reproduce with current upstream code which btw have some regression fixes when using PulseAudio BlueZ 5 testing tree but apparently that is not the case here. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
