2009-06-26 16:30:30

by Michal Sojka

[permalink] [raw]
Subject: RE: Headset doesn't work at all (ALSA)

John Frankish wrote:
> Then I tried:
>
>>$ aplay -D bluetooth 'rec.wav'
>>Playing WAVE 'rec.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono
>>aplay: pcm_write:1528: write error: Connection timed out
>
>>> does aplay -D plug:bluetooth rec.wav help?

No, it doesn't help. The corresponding bluetoothd output is:

Jun 26 18:28:50 resox bluetoothd[14098]: Accepted new client connection on unix socket (fd=22)
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_REQUEST <- BT_GET_CAPABILITIES
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_RESPONSE -> BT_GET_CAPABILITIES
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_REQUEST <- BT_OPEN
Jun 26 18:28:50 resox bluetoothd[14098]: open sco - object=ANY source=ANY destination=00:07:A4:87:E2:EE lock=write
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_RESPONSE -> BT_OPEN
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_REQUEST <- BT_SET_CONFIGURATION
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_RESPONSE -> BT_SET_CONFIGURATION
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_REQUEST <- BT_START_STREAM
Jun 26 18:28:50 resox bluetoothd[14098]: socket(SEQPACKET, SCO): Too many open files (24)
Jun 26 18:28:50 resox bluetoothd[14098]: start_resume: resume failed
Jun 26 18:28:50 resox bluetoothd[14098]: Audio API: BT_ERROR -> BT_START_STREAM
Jun 26 18:28:50 resox bluetoothd[14098]: Unix client disconnected (fd=22)
Jun 26 18:28:50 resox bluetoothd[14098]: client_free(0xb9649ea8)