OK, so 2nd attached log indicates that your audio device got busy and
no way to writing data timely. Then Audio Flinger just blocks there.
There might be some initialization stuff not done well in the driver,
so after you reconnect A2DP to the Android device it could recover
streaming.
Sincerely,
Better attach logs after "D/A2dpAudioInterface( 890):
A2dpAudioStreamOut::set 80, 0, 0, 0", indicating seconds of activities
after you start the A2DP streaming but without audio. There usually
should be something printed out.
Losing audio would be either caused by a2dp_write failure or lengthy
pen
Hi Nick,
Supporting connection to a single device can be understood. I
want to expand the topic a bit, related to multiple connections to a
same device. For example, cupcake already supports A2DP and HFP
connection to a same headset in concurrent way, although audio data
(A2DP/SCO) need b
