You are not logged in.
Hi all!
I have some Sennheiser Momentum headphones I wish to connect via bluetooth
I can connect and operate them without any issue on my android phone.
However despite my spending a lot of time trying and researching the internet these headphones are not detected by the system.
... this fix proposed in the wiki didn't work either.
[gazeto@opaque ~]$ systemctl start bluetooth.service
[gazeto@opaque ~]$ bluetoothctl
[NEW] Controller B8:76:3F:A7:AA:F0 opaque [default]
[NEW] Device BC:44:34:3B:F6:1F LENNY2
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# scan on
Discovery started
[bluetooth]# devices
Device BC:44:34:3B:F6:1F LENNY2
[bluetooth]# show
Controller B8:76:3F:A7:AA:F0 (public)
Name: opaque
Alias: opaque
Class: 0x001c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: yes
[bluetooth]# exit
Agent unregistered
[DEL] Controller B8:76:3F:A7:AA:F0 opaque [default]Does anybody have some ideas or a hint for me?
Thanks!
Other outputs in case useful:
[gazeto@opaque ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2018-02-02 16:32:49 CET; 30min ago
Docs: man:bluetoothd(8)
Main PID: 589 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─589 /usr/lib/bluetooth/bluetoothd[gazeto@opaque ~]$ pacman -Q | grep bluetooth
gnome-bluetooth 3.26.0+1+g3875844-1
pulseaudio-bluetooth 11.1-1[gazeto@opaque ~]$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: noLast edited by gazeto (2018-02-03 17:42:12)
Offline
Update:
After I tried the same thing (according to arch wiki trouble shoot) over and over again I once(!) got this result:
[bluetooth]# scan on
Discovery started
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller B8:76:3F:A7:AA:F0 Discoverable: yes
[bluetooth]# pairable on
Changing pairable on succeeded
[NEW] Device 00:1B:66:80:BB:DF 00-1B-66-80-BB-DF
[CHG] Device 00:1B:66:80:BB:DF LegacyPairing: no
[CHG] Device 00:1B:66:80:BB:DF Name: MOMENTUM M2 AEBT
[CHG] Device 00:1B:66:80:BB:DF Alias: MOMENTUM M2 AEBT
[CHG] Device 00:1B:66:80:BB:DF LegacyPairing: yes
[bluetooth]# pair 00:1B:66:80:BB:DF
Attempting to pair with 00:1B:66:80:BB:DF
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[DEL] Device 00:1B:66:80:BB:DF MOMENTUM M2 AEBT
[bluetooth]# pair 00:1B:66:80:BB:DF
Device 00:1B:66:80:BB:DF not available
[bluetooth]# devices
Device BC:44:34:3B:F6:1F LENNY2This is the device I wish to connect: 00:1B:66:80:BB:DF MOMENTUM M2 AEBT
Unfortunately I have not been successful reproducing this scan result ... ![]()
So, again: No scanning result, no paring possible.
Any ideas?
Offline
The problem is solved.
Reason seems to be a hardware issue: Once I removed my Lenovo from the docking station and placed it literally ON the headphones, the connection could establish.
Offline