[How to do instruction] Moode 8: Add bluetooth codec support for AAC, aptX & aptX-HD to bluez-alsa package

[TheOldPresbyope]

As a follow-up to my previous post, I followed Jens's instructions to add the extra codecs. Then I paired and connected to my Sennheiser 4.50BT headphones (which contain SBC and aptX codecs)

Code:

# check that the codecs are available
pi@moode:~ $ bluealsa-cli status
Service: org.bluealsa
Version: v4.0.0
Adapters: hci0
Profiles:
 A2DP-source : SBC AAC aptX aptX-HD LDAC
 A2DP-sink   : SBC AAC aptX aptX-HD

# check UUID of my headphones
pi@moode:~ $ bluetoothctl info
Device 00:16:94:29:7F:10 (public)
    Name: HD 4.50BTNC
    Alias: HD 4.50BTNC
    Class: 0x00240404
    Icon: audio-card
    Paired: yes
    Trusted: yes
    Blocked: no
    Connected: yes
    ...

# look to see which codec was negotiated in the pairing process (noting it's the right UUID)
pi@moode:~ $ gdbus call --system -d org.bluealsa -o /org/bluealsa -m org.bluealsa.Manager1.GetPCMs
({objectpath '/org/bluealsa/hci0/dev_00_16_94_29_7F_10/a2dpsrc/sink': {'Device': <objectpath '/org/bluez/hci0/dev_00_16_94_29_7F_10'>, 'Sequence': <uint32 0>, 'Transport': <'A2DP-source'>, 'Mode': <'sink'>, 'Format': <uint16 33296>, 'Channels': <byte 0x02>, 'Sampling': <uint32 48000>, 'Codec': <'aptX'>, 'Delay': <uint16 150>, 'SoftVolume': <true>, 'Volume': <uint16 32639>}},)

Yay. The "higher" quality aptX codec was selected during the negotiation rather than the SBC.

However, moOde seems to think it's connected to a Bluetooth source rather than sink because the webUI is overlaid with "Bluetooth Active: HD 4.50BTNC" and the Bluetooth control button?!? 


Regards,
Kent

Thats strange. Check the audio output setting in Bluetooth Config.

Well, that's embarrassing. Guess who forgot to switch to Bluetooth speaker output  

All's well. Now to jury-rig some BT sources with advanced codecs.

Regards,
Kent