SBC-XQ > aptX-HD!?! (Audio/Bluetooth codecs)

Hey all, how's it hangin'? I recently bought a 10,000mAh Bluetooth Headset off of Ali Express straight from China because, while I own more headphones, wireless earbuds (as well as wired, obviously) and random Bluetooth accessories like BT receivers/adapters than is probably necessary (bordering on excessive), I got sick of dealing with friggin batteries and charging. The best I could do was a pair of over the ear headphones, that are quite decent sounding and have pretty decent battery life at ~14-15 hours (they're supposed to get 30h with ANC turned off and 20 with it on but I get about ¾ of that personally) with ANC on. I rarely use them without ANC. Still, with daily use charging becomes extremely tedious and before long, the bane of my existence.

Enter the 1,000 hour playback Bluetooth headphones. While I've never let them go far enough to test whether they're capable of reaching that figure, I know they can hold a charge for at least a week and still have a good 70% or so in the tank. I did catch the seller/manufacturer in one lie, and that is that they are actually 5,000mAh, not 10,000 which was a bummer but if you consider the standard capacity of 18650 cells and the fact that the headset in question only carries 2 of them, it quickly become apparent that 10,000mAh is an exaggeration, similar but nowhere near as egregious as Chinese sellers are wont to claim regarding flashlight luminosity. You probably know what I'm talking about but it's not uncommon to see a flashlight "rated" at 99,999,99LM (typo added for authenticity) when it's likely 900 lumens, at best. Turns out that not only do they still have BY FAR the best battery life of any headset/headphones/audio equipment I've ever owned, regardless of having half of the stated capacity (aside from a few exceptions like laptops and battery packs, they may surpass most of any of my gadgetry, audio or otherwise) but I ended up getting them for free because, as suspected the seller was not interested in me posting my findings on their product page because I further suspect and am reasonably certain that a 10,000mAh model does not exist and have photo evidence of the unit I received housing (2) 2,500mAh cells, contradicting the figure stated in the area of 20+ times throughout the product page which would equal a lot of refunds and pissed off buyers. If you're willing to wait 3ish weeks for them to show and be out $25-30 in the interim, you could very probably get away with the same move :wink:

Anyway, I was and still am thrilled about the extreme battery life this headset features, however, there was one thing that really kind of bugged me about their feature set that I would have been much more upset about had I not technically gotten them free of charge and that's the fact that on the surface they have inferior Bluetooth audio codec support with my phone indicating that they only support SBC. Well, upon playing around with the Bluetooth/ audio settings found on Garuda Linux, I discovered that they actually have support for several different types of SBC codec, one of which being SBC-XQ. Admittedly I was unfamiliar with this codec and upon further digging I came across some fairly shocking information. Going into my "research" I was under the impression that aptX/aptX HD/aptX LL were the best Bluetooth audio codecs that exist presently, which are supported by only the best and most expensive Bluetooth headsets and equipment, which comes at no surprise.

Meanwhile, SBC is generally thought of as an inferior codec and on paper, rightfully so however, all Bluetooth headsets and equipment support the codec. What I didn't know and you may be unaware of as well, is that while its standard HQ bitrate of 328kbit/s is only barely passable sound-wise, it turns out that it can actually work at much higher bitrates but the Bluetooth Special Interest Group (SIG) recommend 328kbit/s be the bitrate at which SBC would be considered "high quality." What this resulted in, which is still playing out today, is that most operating systems etc. Simply feature SBC high quality at 328kbit/s and nothing further. This in spite of the fact that it's actually being capable of reaching bitrates of 512kbit/s on paper and reaching as high as 551.2 kbit/s (source). On the low end, this makes SBC-XQ as good as aptX-HD 529kbit/s (the difference between 512 and 529 kbit/s would be entirely indistinguishable audibly even with the best of headphones/audio equipment) and even capable of surprising aptX-HD on the higher end of 551.2kbit/s (I guess the latter figure is reached on ERD3 BT devices, which I really don't know much about or what qualifies as ERD3 vs ERD2 but the fact remains)

There is some good news. While the damage is done regarding SBC's reputation with the average consumer (assuming they know the first thing about BT codecs), however, A2DP now requires decoders to support higher quality streams, up to 512 kbit/s, as there are now some experimental encoders that use SBC XQ, for example Lineage OS and, as we know and which I'm grateful for - the Bluetooth stack incorporated into Garuda Linux (I'm assuming SBC-XQ support comes via Pipewire but I also read about and saw some Pulse Audio patches that being support for it hosted on GitHub so a patch is also a possible source for the support being present or if the box.

Either way, it's greatly appreciated since, the Chinese seller/manufacturer that brought this 5,000mAh headset into being didn't supporting for aptX (or any of its variations) support, though now I'm thinking they may have made the better call.

File this one under "TIL" (TODAY I LEARNED)

Be good to one another. Take care Garudians!

2 Likes

garuda-inxi?

3 Likes

Do you need it if I'm not raising any issues or asking for any help/troubleshooting? I'm happy to provide it but didn't think there was a need as I was simply making conversation. Give me a sec, though. I'll play ball...

System:
Kernel: 5.17.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=256afd7f-c837-4d0d-91da-717c96d4acf4 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1
resume=UUID=efe2f980-2caa-43f8-99ca-dfcf2b1ee1f5 loglevel=3
Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: 4X4-4000 Series
serial: <superuser required> UEFI: American Megatrends v: P1.30
date: 11/27/2020
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Device-2: hidpp_battery_1 model: Logitech K520 serial: <filter>
charge: 50% (should be ignored) rechargeable: yes status: N/A
Device-3: hidpp_battery_2
model: Logitech M720 Triathlon Multi-Device Mouse serial: <filter>
charge: 50% (should be ignored) rechargeable: yes status: N/A
CPU:
Info: model: AMD Ryzen 5 4500U with Radeon Graphics bits: 64 type: MCP
arch: Zen 2 family: 0x17 (23) model-id: 0x60 (96) stepping: 1
microcode: 0x8600103
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB
desc: 2x4 MiB
Speed (MHz): avg: 2566 high: 3990 min/max: N/A cores: 1: 2371 2: 1925
3: 3990 4: 2371 5: 2371 6: 2371 bogomips: 28446
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Renoir driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-1, DP-2, DP-3, DP-4 empty: none bus-ID: 05:00.0
chip-ID: 1002:1636 class-ID: 0300
Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2278 s-dpi: 96 s-size: 1013x601mm (39.88x23.66")
s-diag: 1178mm (46.37")
Monitor-1: DP-1 mapped: DisplayPort-0 pos: 1-4 model: D32hn-E4
serial: <filter> built: 2018 res: 1366x768 hz: 60 dpi: 60 gamma: 1.2
size: 575x323mm (22.64x12.72") modes: max: 1366x768 min: 720x400
Monitor-2: DP-2 mapped: DisplayPort-1 pos: primary,3-3
model: Panasonic PanasonicTV0 serial: <filter> built: 2012 res: 1920x1080
hz: 60 dpi: 70 gamma: 1.2 size: 698x392mm (27.48x15.43") modes:
max: 1920x1080 min: 640x480
Monitor-3: DP-3 mapped: DisplayPort-2 pos: 2-2 model: Sony TV
serial: <filter> built: 2010 res: 1920x1080 hz: 60 dpi: 30 gamma: 1.2
size: 1600x900mm (62.99x35.43") diag: 1836mm (72.3") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
Monitor-4: DP-4 mapped: DisplayPort-3 pos: 4-1 model: Sony TV XV
serial: <filter> built: 2007 res: 1920x1080 hz: 60 dpi: 30 gamma: 1.2
size: 1600x900mm (62.99x35.43") diag: 1836mm (72.3") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
OpenGL: renderer: AMD RENOIR (LLVM 13.0.1 DRM 3.44 5.17.9-zen1-1-zen)
v: 4.6 Mesa 22.1.0 direct render: Yes
Audio:
Device-1: AMD Renoir Radeon High Definition Audio vendor: ASRock
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASRock
driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
snd_pci_acp6x, snd_sof_amd_renoir
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: ASRock
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-4: JMTek LLC. TKGOU PnP USB Microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 2-1.3.3.4:17
chip-ID: 0c76:1467 class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.17.9-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 16.0 running: no
Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 01:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp1s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: ec00 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0f0 state: down mac: <filter>
Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Device-4: TP-Link Archer T9UH v1 [Realtek RTL8814AU] type: USB
driver: rtl88XXau bus-ID: 2-2.1.1:9 chip-ID: 2357:0106 class-ID: 0000
serial: <filter>
IF: wlp5s0f3u2u1u1 state: up mac: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 4-3:2 chip-ID: 8087:0029 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 10.01 TiB used: 5.88 TiB (58.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT500P2SSD8
size: 465.76 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: P2CR010
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT500MX500SSD1
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s type: SSD serial: <filter> rev: 020 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital
model: WD easystore 25FB size: 9.1 TiB block-size: physical: 4096 B
logical: 512 B type: N/A serial: <filter> rev: 3004
Partition:
ID-1: / raw-size: 432.15 GiB size: 432.15 GiB (100.00%)
used: 148.43 GiB (34.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 432.15 GiB size: 432.15 GiB (100.00%)
used: 148.43 GiB (34.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 432.15 GiB size: 432.15 GiB (100.00%)
used: 148.43 GiB (34.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 432.15 GiB size: 432.15 GiB (100.00%)
used: 148.43 GiB (34.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 33.31 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
ID-2: swap-2 type: zram size: 30.28 GiB used: 190.8 MiB (0.6%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 36.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 370 Uptime: 1d 10h 16m wakeups: 121 Memory: 30.28 GiB
used: 15.67 GiB (51.7%) Init: systemd v: 251 tool: systemctl Compilers:
gcc: 12.1.0 clang: 13.0.1 Packages: 1883 note: see --pkg apt: 0
pacman: 1870 lib: 475 flatpak: 13 Shell: fish v: 3.4.1 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.16
Garuda (2.6.3-2):
System install date:     2022-01-26
Last full system update: 2022-06-04 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:            lidarr.service systemd-networkd-wait-online.service

TL;DR :smiley: :grin:

We delete promotion!

Reboot :smiley:

2 Likes

LOL

Promotion? That would suggest that I am affiliated with the Bluetooth Special Interest Group or Advanced Audio Distribution Profile (A2DP) or otherwise stand to benefit from choices in BT codec support.

Nevermind, garuda-inxi provided

:: Contacts higher-ups at SIG to tell boys the plan is afoot :: :eyes:

Just joshing, ofc. I'll keep this in mind for future posts of a similar nature. Thanks for the heads up and not just deleting me without warning

1 Like

Reboot :smiley:

Good looking out @SGS

You're good people, I honestly forgot I didn't reboot because I was juggling things, as per usual

2 Likes

Here's one reason why we need it. LOOOLLLLLLLL You made me laugh pretty good. :smiley:

1 Like

garuda-inxi?

Do you need it if I'm not raising any issues or asking for any help/troubleshooting?

Good looking out @SGS
You're good people, I honestly forgot I didn't reboot

Here's one reason why we need it. LOOOLLLLLLLL You made me laugh pretty good. :smiley:

Which part? Me suggesting @SGS is good people? That's not very nice :joy:

1 Like

A post was merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)

image

Why is there a "solution" marked for this thread? :joy:

What is the method for enabling SBC XQ? I became curious after reading your post, but I do not see anything related to SBC XQ in the Bluetooth settings of either Garuda or my Lineage OS phone. I inspected a few bluetooth devices I have kicking around, but most of them don't have anything beyond a few basic buttons to interact with.

1 Like

image

???

2 Likes

Honestly, I don't know because I didn't mark a solution knowingly. I'm commenting on my phone, though so it's entirely possible I tapped the checkbox by accident. My phone's touch screen is a sensitive lil b*tch lol jk there's no shame in being in touch with ones sensitive side.

As for enabling SBC-XQ, I suspect it's enabled by default and the only trick to its utilization it's having a device that supports the codec but that's just an assumption. All I know for certain is that I didn't do anything in particular from my end to enable its use.

OK so I tried a couple of other devices and now I'm not so sure about what I said regarding enabling it. I still maintain that I didn't do anything however either all 3 of the devices I connected have support for the SBC-XQ codec or something else is attributing to its presence. See screenshots:


Device #1, 5,000mAh headset:_2

1 Like

5 posts were merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)