Hi Colin > I did ping the bluez folks on this, but no takers. Sorry I missed your query on linux-bluetooth. > On 10/16/2009 01:31 PM, Colin Beckingham wrote: > > > > Noted that there is an upgrade to bluez, 4.56 (I was using 4.54) so > > compiled new version. Above "seid 64" error has gone, but pulseaudio > > still fails with POLLERR. > > > > Oct 16 13:14:37 : Audio API: BT_REQUEST <- BT_START_STREAM > > Oct 16 13:14:37 : State changed > > /org/bluez/11455/hci0/dev_00_1A_45_32_E7_16: HEADSET_STATE_CONNECTED > > -> HEADSET_STATE_PLAY_IN_PROGRESS > > > > Oct 16 13:14:37 : module-bluetooth-device.c: Trying to receive > > message from audio service... > > Oct 16 13:14:38 : Received AT+BTRH? > > Oct 16 13:14:39 : Received AT+VGS=15 > > Oct 16 13:14:39 : Received AT+VGM=15 > > Oct 16 13:15:17 : HUP or ERR on socket > > ... > > Oct 16 13:15:17 : module-bluetooth-device.c: Received BT_INDICATION > > <- BT_NEW_STREAM > > Oct 16 13:15:17 : module-bluetooth-device.c: Stream properly set up, > > we're ready to roll! > > Oct 16 13:15:17 : module-bluetooth-device.c: FD error: POLLERR > > Oct 16 13:15:17 : module-bluetooth-device.c: IO thread failed > > Oct 16 13:15:17 : module-suspend-on-idle.c: Sink > > bluez_sink.00_1A_45_32_E7_16 becomes idle, timeout in 5 seconds. > The problem is most likely an incompatibility/bug between the BT radio and your headsets. My guess is that they've negotiated an eSCO connection that one or the other does not actually support. Please re-post this over on linux-bluetooth and enclose "hciconfig -a" output, "bluetooth -nd" log and a "hcidump -t -X -V" capture of a failed headset connect. Also, please be sure to include how you're initiating, ie. powering-on headset, connect using gnome-bluetooth, whatever. Regards, Peter
