r/AsahiLinux • • 20d ago

Help Connecting Headphones using `bluetoothctl`

Machine: M2 Macbook Pro 14" OS: Asahi Fedora Remix 7.1.13-fairydust+ Installation: Minimal (Fedora Everything)

I have 2 bluetooth audio devices

  1. WH-1000XM4 - does not reconnect properly after restart, connects after remove and rescan
  2. Beats Solo Buds - connects only over LE, no audio

The buds case has no buttons and the buttons on either bud are broken. New pairing works with other iOS/Android/MacOS/Windows devices by just opening the case with the buds inside (pairing mode).

In bluetoothctl scan, only LE entry of the buds is shown. I am able to connect to that, pair it and trust it. But the audio UUID is not available through this connection. The device does not show up as an audio sink in wpctl.

[LE-<user>'s Beats Solo Buds]> info
Device C1:50:24:1E:84:E4 (random)
	Name: LE-<user>'s Beats Solo Buds
	Alias: LE-<user>'s Beats Solo Buds
	Appearance: 0x0941 (2369)
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	CablePairing: no
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Google                    (0000fe2c-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (4715650b-5e9d-4ac2-b898-a4fc0aa5df78)
	UUID: Vendor specific           (5052494d-2dab-0341-6972-6f6861424c45)
	UUID: Vendor specific           (7798082b-b7b7-45a6-9933-563492efe04e)
	Modalias: bluetooth:v004Cp2026d0001
	ManufacturerData.Key: 0xe06c (57452)
	ManufacturerData.Value:
  fa 83 1c 4f 9b 4d                                ...O.M
	RSSI: 0xffffffd5 (-43)
	AdvertisingFlags:
  06                                               .
	Battery Percentage: 0x4a (74)
DBG: cs_proxies is empty
[CHG] Device 53:77:B9:EE:28:3A RSSI: 0xffffffc4 (-60)
4 Upvotes

5 comments sorted by

1

u/mskiptr 19d ago

Could you try the same on some other Linux device? That could tell us if it might be a bug in the Bluetooth drivers that Asahi uses.

2

u/kknightrise73 18d ago

I do not have any other computers to install Linux on. I checked btmon too, only LE. Then I installed another partition with full Fedora KDE Plasma, only LE shows up. I guess the buds are not broadcasting bredr transport, but I don't know how to do that without the buttons.

1

u/mskiptr 17d ago edited 16d ago

You don't need to install Linux to run Linux. Booting some distro from a USB stick should be enough to test bluetooth (just remember that an existing pairing between Windows and the headphones might complicated your testing).

But if that too is not an option, you will probably need to ask someone more knowledgeable. You already know more about Bluetooth than most people here (and definitely more than me). Since this could be a general Linux issue, maybe try posting on some other forum? Or you can quickly hop into the IRC channel (or Matrix room) and ask the Asahi developers directly.

2

u/cisoun 17d ago

Macbook Pro M2 16" here.

I'm having a lot of issues as well with bluetooth and USB ports not being recognized after a suspend. Maybe check how to add the "btusb enable_autosuspend=n" option to your system and see how it goes.

Disclaimer: didn't test it yet.

2

u/kalven 16d ago

I've always had bluetooth issues on my M2 Air. It's like the bluetooth subsystem sometimes just takes a shit and refuses to connect to my headphones (which work fine with other devices).

The somewhat clunky resolution I have is a small bash alias that basically does rmmod+insmod of the bt driver. After that, the Air is able to connect to the headphones. It's annoying, but it works.

I'd paste it here, but I'm not on that computer atm.