On Thu, 12 May 2016, at 08:41 PM, Marco Trapanese wrote: > Il 12/05/2016 12:33, Marco Trapanese ha scritto: > > Il 12/05/2016 09:39, Arun Raghavan ha scritto: > >> This should not happen. It might be worth looking at PulseAudio and > >> bluetoothd verbose logs to see what's happening. > > > > I attach them to this email. > > I think there is something about this behavior, but I have not the > > knowledge to understand why this happens. > > > After the audio begin to play pulseaudio shows the following errors: > > > E: [alsa-sink-bcm2835 ALSA] alsa-sink.c: ALSA woke us up to write new > > data to the device, but there was actually nothing to write. > > E: [alsa-sink-bcm2835 ALSA] alsa-sink.c: Most likely this is a bug in > > the ALSA driver '(null)'. Please report this issue to the ALSA developers. > > E: [alsa-sink-bcm2835 ALSA] alsa-sink.c: We were woken up with POLLOUT > > set -- however a subsequent snd_pcm_avail() returned 0 or another > > value < min_avail. > > then it plays via A2DP (with quite poor quality). I don't know if those > errors are related to the releasing of the bluez source after the > streams stops for a while. I didn't see anything Bluetooth related in your PulseAudio server log, though. -- Arun
