No option to check if LDAC is being used when connecting via bluetooth using a Headphone amp with HiRes Audio

REPRODUCIBILITY (% or how often): Always
BUILD ID = OS VERSION (Settings > About product): latest build
HARDWARE (Jolla1, Tablet, XA2,…): Sony Xperia 10 Plus Dual SIM
REGRESSION: (compared to previous public release: Yes, No, ?): ?


When connected a headphone amp like my FiiO Headphone amp, on checking the settings in bluetooth there is no way of checking whether it is connected using LDAC to take advantage of the optimum sound quality passing through it to hi-res headphones eg: my Sony MDR-Z7 headphones.


Test using a Hi-Res amp connected via Bluetooth


  1. Pair the Hi-Res amp via bluetooth to your mobile
  2. Go back to bluetooth settings


You should be able to check the settings used for each device paired to your mobile like:
HD Audio
Phone calls
Media audio
Contact sharing

etc or similar.


None of this information is available to be seen not even in developer settings unless I am missing something.


Again by now I would of thought all these default things should now be present for all devices. Prior to installing Sailfish O/S on one of the recommended devices the Sony Xperia 10 Plus - Android 9 did allow me to see those options and switch on or off after pairing the device should I wish to change.

1 Like

I’m somewhat sure, Sailfish only supports SBC right now, no high quality codec. So there would be no settings to check.

1 Like

Yes that’s what I suspected having tested the same music vis My Google Pixel mobile as a backup plan. Maybe in the next release we can dream.

bluez5 version in sailfishos is currently v5.54 (iirc), which does have support for multiple bluetooth A2DP audio codecs.

The problem is in pulseaudio, which does not (yet) have support for multiple codecs. Basicly pulseaudio currently only supports SBC (with quite low quality settings).

1 Like

There is a project that enables all the fancy stuff in pulse:

But given its gpl3 don’t expect it coming to SFOS. You can thank the FSF for that :slight_smile:

1 Like

In theory it should be easy enough to package that on openrepos. It’s really just corporate interests, that are incompatible with the GPL3, but that discussion does not belong here.