Bug 1217349 - [Regression from Leap's GNOME 41.5] Bluetooth picks wrong, unusable audio quality level for Anker Soundcore Life Q30 headphones
Summary: [Regression from Leap's GNOME 41.5] Bluetooth picks wrong, unusable audio qua...
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Leap 16.0
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-21 00:26 UTC by ell1e
Modified: 2023-11-21 02:59 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ell1e 2023-11-21 00:26:49 UTC
I just upgraded from Leap 15.5's GNOME 41.5 to Slowroll's GNOME 45.0, and there's a regression regarding bluetooth picking a wrong, unusable audio quality level for Anker Soundcore Life Q30 headphones:

Previously, only 5% of the time, the HFP profile picked was some completely, utterly broken bitrate sounding like a 64kbps mp3 or something, with mono sound, no proper volume adjustment, and audio quality so bad you can basically understand people fine but any use beyond that, like music, is impossible due to heavy, extreme audio artifacts. Whenever that rarely happened, toggling the bluetooth device off and back on fixed it most of the time.

Now this unusably low quality HFP profile is picked by the bluetooth stack 100% of the time, and toggling (whenever you get toggling to work at all, see #1217348 ) seems to do absolutely nothing to fix it.

I'm suggesting severity major because so far, I haven't been able to find any workaround.
Comment 1 ell1e 2023-11-21 00:31:05 UTC
There are interesting and weird messages in dmesg about this, the "hci0: corrupted SCO packet" errors are new and I never saw these before:

[ 1309.377239] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 1309.382243] Bluetooth: hci0: Device revision is 5
[ 1309.382259] Bluetooth: hci0: Secure boot is enabled
[ 1309.382266] Bluetooth: hci0: OTP lock is enabled
[ 1309.382271] Bluetooth: hci0: API lock is enabled
[ 1309.382276] Bluetooth: hci0: Debug lock is disabled
[ 1309.382281] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 1309.499175] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 1311.141313] Bluetooth: hci0: Waiting for firmware download to complete
[ 1311.142278] Bluetooth: hci0: Firmware loaded in 1604587 usecs
[ 1311.142367] Bluetooth: hci0: Waiting for device to boot
[ 1311.154191] Bluetooth: hci0: Device booted in 11586 usecs
[ 1311.154206] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 1311.155687] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[ 1311.159224] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 1311.160219] Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021
[ 1311.162220] Bluetooth: hci0: Reading supported features failed (-16)
[ 1311.162241] Bluetooth: hci0: Error reading debug features
[ 1311.162249] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[ 1311.207687] Bluetooth: MGMT ver 1.22
[ 1334.249825] input: Soundcore Life Q30_BLE (AVRCP) as /devices/virtual/input/input40
[ 1337.601214] Bluetooth: hci0: corrupted SCO packet
[ 1337.601252] Bluetooth: hci0: corrupted SCO packet
[ 1337.601270] Bluetooth: hci0: corrupted SCO packet
[ 1337.601284] Bluetooth: hci0: corrupted SCO packet
[ 1337.601298] Bluetooth: hci0: corrupted SCO packet
[ 1337.601312] Bluetooth: hci0: corrupted SCO packet
[ 1337.601324] Bluetooth: hci0: corrupted SCO packet
[ 1337.601337] Bluetooth: hci0: corrupted SCO packet
[ 1337.601351] Bluetooth: hci0: corrupted SCO packet
[ 1337.601363] Bluetooth: hci0: corrupted SCO packet
[ 1337.611213] Bluetooth: hci0: corrupted SCO packet
[ 1337.611249] Bluetooth: hci0: corrupted SCO packet
Comment 2 ell1e 2023-11-21 02:59:36 UTC
Upgrading to slowroll and then switching to pipewire actually seems to have fixed this for now.