You are not logged in.
I just purchased a DKnight MagicBox II, I went through my first bluetooth setup with Arch. I followed the bluetooth headset Arch wiki with this ballpark process (as far as I can recall):
$ sudo pacman -Syu pulseaudio-alsa pulseaudio-bluetooth bluez bluez-libs bluez-utils bluez-firmware
$ sudo modprobe btusb
$ sudo systemctl start bluetooth
$ sudo bluetooth
[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on
[bluetooth]# devices
Device 00:02:5B:AC:B0:A8 MagicBox II
[bluetooth]# pair 00:02:5B:AC:B0:A8
[bluetooth]# connect 00:02:5B:AC:B0:A8From there, I was able to use pavcontrol to play audio successfully through the speaker while watching a movie. I've also already used it plenty with both my and my wife's phones (android), though this was the first time using it with Arch. I simply closed my lid when I was done, and my wife wanted to use it, but it wasn't listed in her bluetooth discovered devices. I found the same from my phone and resumed my laptop to check things out. It seems I can't re-create my process either...
I now get this with any command using the above MAC address:
[bluetooth]# pair 00:02:5B:AC:B0:A8
Device 00:02:5B:AC:B0:A8 not available
[bluetooth]# info 00:02:5B:AC:B0:A8
Device 00:02:5B:AC:B0:A8 not availableIn looking at the speaker manual, it says that upon power up, a blue light will be flashing if it's in discoverable mode, and the light indeed blinks. It also says that the play button can be held for 5 seconds to manually register it as having disconnected from the last device. I did this and see no obvious change (it's already blinking, suggesting it doesn't think it's paired, so this isn't surprising).
Not having used bluetooth on Arch before, I guess I'm curious if I could have somehow changed any of the device settings by connecting to it (or failing to disconnect through some required method). I've rmmod-ed btusb, stopped the bluetooth service, and even rebooted, but continue to not see the speaker from either phone. Seems like a stretch, but I thought it'd be good to double check with the forums before seeking out the manufacturer's help/forums.
Thanks for any suggestions, and any other information I can provide if that would be helpful. One of the first suggestions is to make sure bluetooth is actually enabled and not rf-killed. I've done that (no soft/hard block on hci0), but perhaps there's something else that might help troubleshoot. I don't think it's on my end since the phones can't find it anyway, but really am not sure what else to check!
Offline