[SOLVED] WF-1000XM3 not connecting to new computer / install via bluetooth
ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
WF-1000XM3 not connecting to new computer / install via bluetooth
So I recently purchased a new rig and have a fresh install of arch. I have decided to try pipewire as my default sound interface and on testing with plugged in headset it is working fine.
My next hurdle was to try and connect my bluetooth earbuds - Sony WF-1000XM3 (which are working fine on current install but via a separate dongle)
One of the requirements for my new box was to have bluetooth as part of the motherboard (ASUS ROG Crosshair VIII Hero)
It appears from a detection point of view that arch can see my bluetooth with no issue, but on connecting my earbuds I have had no joy.
So here is my most recent attempt to connect:
Code:
$ bluetoothctl
Agent registered
[CHG] Controller DC:41:A9:D8:A5:CB Pairable: yes
[bluetooth]# connect 94:DB:56:19:2B:3A
Attempting to connect to 94:DB:56:19:2B:3A
[CHG] Device 94:DB:56:19:2B:3A Connected: yes
[CHG] Device 94:DB:56:19:2B:3A Connected: no
[CHG] Device 94:DB:56:19:2B:3A Connected: yes
[CHG] Device 94:DB:56:19:2B:3A Connected: no
[CHG] Device 94:DB:56:19:2B:3A Paired: yes
Failed to connect: org.bluez.Error.Failed
Why don't you post on the arch forum. Some of them seem to know everything about arch. If you are using manjaro, say so, don't pretend that you are using arch. Ask if you've seen this happen on arch. You might get a shove in the right direction.
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Hi grail,
In my experience, using bluetooth audio peripherals on Arch requires several software packages. From memory :
bluetooth drivers (seems you have this already);
bluetoothctl or gui for interface (I see you have bluetoothctl ... this is what I use as well);
pulseaudio (I see pactl, so you seem to have pulseaudio there ...);
a pulseaudio / bluetooth layer (forgot the actual package name) ...
I like doing everything manually, so when I want to use bluetooth, I :
start pulseaudio;
start the bluetooth systemd service;
start the bluetoothctl interface (as root or with sudo);
power on the bluetooth adapter,
turn on the agent,
turn on scan,
pair the device using it's MAC address,
connect to the device.
In your outputs, I see references to pipewire (not familiar at all with that - from reading, it looks like a replacement for PulseAudio in certain cases ...) and jack (I use jack on one of my Arch systems that I use for audio recording). You may want to make sure these different components are properly configured.
Here are links to useful articles in the Arch Wiki :
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Hey again grail,
... afterthought here ... One of the times I experienced random bluetooth disconnections similar to what you're describing, it was a case of my phone grabbing the device (it was also paired with the phone) ... Solution was to turn off bluetooth on the phone while I was using the device with my computer ... ;-)
I can guarantee nothing else is via'ing for the attention of my ear buds. The only other thing they have connected to in earnest has been my old
PC via a dongle which seems to work without issue.
On your and teckk's links I have managed to get some connection happening with the aid of blueman (just no consistency as yet), but even once connected I
have zero sound. Not even the obligatory "bluetooth connected"
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Quote:
Originally Posted by grail
Thanks for the suggestions Rickkkk
I can guarantee nothing else is via'ing for the attention of my ear buds. The only other thing they have connected to in earnest has been my old
PC via a dongle which seems to work without issue.
On your and teckk's links I have managed to get some connection happening with the aid of blueman (just no consistency as yet), but even once connected I
have zero sound. Not even the obligatory "bluetooth connected"
Hey grail,
Similar problems (bluetooth speakers / headphones connect but no sound) in my past experience were usually due to incorrect PulseAudio settings (choosing and properly configuring device, output source and volume ...). I usually solved using pavucontrol. Since you're on Pipewire, you could perhaps double check everything there ... And ... really basic here, make sure your Alsa output channels aren't muted (I usually check with alsamixer).
Ok so I had forgotten all about alsa Now it didn't fix anything, as I saw nothing muted, however, what I have noted between the old and new machine
is that in the old, alsamixer lists one of my available cards (the default) as PulseAudio. Now this is not the case on the new machine.
So I am not sure if this is what I am supposed to be looking to get to appear or that is just a coincidence?
When using pavucontrol on old box my bluetooth headset is an optional item. It does not appear on the new machine. So I don't know if this is the
bluetooth side not connecting properly or the pipewire side not seeing it correctly
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Quote:
Originally Posted by grail
Ok so I had forgotten all about alsa Now it didn't fix anything, as I saw nothing muted, however, what I have noted between the old and new machine
is that in the old, alsamixer lists one of my available cards (the default) as PulseAudio. Now this is not the case on the new machine.
So I am not sure if this is what I am supposed to be looking to get to appear or that is just a coincidence?
When using pavucontrol on old box my bluetooth headset is an optional item. It does not appear on the new machine. So I don't know if this is the
bluetooth side not connecting properly or the pipewire side not seeing it correctly
Hello grail,
I'm at a disadvantage here since I don't use or know Pipewire. However, I notice you still seem to be dependent on PulseAudio, so my initial assumption that it "replaces" PulseAudio is perhaps incorrect. Since your device doesn't seem to have been picked up by Pipewire/Pavucontrol, I would go over the list of requirements from the 2 links I posted earlier from the Arch Wiki and make sure you're not missing a package.
So this will come as a very unpleasant solution, but after multiple installs and file re-creations, I have both connection and sound and have little to no understanding as to why
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.