On Wednesday 01 May 2019 13:25:04 Luiz Augusto von Dentz wrote: > Hi Pali, > > On Wed, May 1, 2019 at 12:09 PM Pali Rohár <pali.rohar@xxxxxxxxx> wrote: > > > > On Tuesday 30 April 2019 12:42:28 Luiz Augusto von Dentz wrote: > > > 1. At least Android seems to prefer aptX-HD but that doesn't seems to > > > produce any audio, in fact it crashed a few times so either have to > > > find out why aptX-HD is not working or don't include it. > > > 2. Codec switching with Android always seems to timeout. > > > 3. There seem to be some regression with loopback module, there seems > > > it always produces some glitch when resuming (during the playback it > > > seems alright): > > > > > > I: [alsa-sink-ALC293 Analog] module-loopback.c: Dropping 17414 usec of > > > audio from queue > > > I: [alsa-sink-ALC293 Analog] module-loopback.c: Dropping 20317 usec of > > > audio from queue > > > I: [alsa-sink-ALC293 Analog] module-loopback.c: Adding 30657 usec of > > > silence to queue > > > I: [alsa-sink-ALC293 Analog] module-loopback.c: Dropping 105170 usec > > > of audio from queue > > > > Can you send btmon/wireshark dump? I can inspect aptx HD packets if > > decoder can correctly decode them. > > You can probably reproduce this faster with a phone, I suspect it also > doesn't work with iOS either. Sure, but all tested android phones lacks aptX HD support. They have only aptX and aptX is working fine. Codec switching is sometimes working fine and sometimes android does not send any sound data, only shows that it is connected. It is strange, but nothing I can debug if other side do not send anything, also no error. I just found one problem in enumeration of SBC capabilities. I will fix it in next SBC patch series. -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
