borine

The reason that volume update events from bluealsa are not received by snapclient is a bug in the snapclient mixer initialization code. The call: ``` err = snd_ctl_poll_descriptors(ctl_, fd_.get(), 1);...

@maxlueerprivate this issue has received no updates for five months. Is it still of interest or can it be closed?

@Asikbct are you starting `bluealsad` with `-p hfp-ag` or `-p hfp-hf` ? If so, please can you test without the hfp profile enabled to see if that makes a difference....

I've just seen an issue in bluez, which is not quite the same as yours, but may be related: https://github.com/bluez/bluez/issues/868 Basically its saying that some speakers will not play A2DP...

> unless the source also has an AVRCP player oops! sorry, please ignore my previous comment. I got that completely back-to-front. In that issue the the user is **building a...

@Asikbct you have not replied to my question about hfp, however as the only similar bug report I can find for Bluez is the one previously referenced which turned out...

> Does the Realme Buds expect the remote device (DUT) to register a transport or start audio streaming soon after connection? The Bluetooth specifications do not require that; I have...

There is a relevant interesting comment by Pauli Virtanen in a Bluez issue here: https://github.com/bluez/bluez/issues/1064#issuecomment-2585452184 where he states: > some devices have firmware bugs triggered by many endpoints. Pauli is...

@Asikbct This issue has been idle for quite some time now; did you ever manage to test bluealsa with the patch posted by @arkq in the previous comment? If this...

> reading sped-up The rate that audio is played is determined by the playback device, not the source (bluealsa) device. Perhaps audio frames are being dropped within the bluealsa server...