| View previous topic :: View next topic |
| Author |
Message |
cduret
n00b
Joined: 20 Mar 2018
Posts: 15
|
 Posted: Mon Nov 20, 2023 7:09 pm Post subject: bluetooth senheiser momentum true wireless 3 [SOLVED] |
 |
|
hello,
I just got my senheiser MOMENTUM True Wireless 3 headset and I struggle to make it work under my lenovo T460.
I have configured my kernel with the following bt parameters
| Code: |
$ uname -a
Linux darkstar 6.1.53-gentoo-r1 #3 SMP PREEMPT_DYNAMIC Tue Oct 31 10:06:22 CET 2023 x86_64 Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz GenuineIntel GNU/Linux
$ grep -nH "CONFIG_BT_RFCOMM\|CONFIG_BT_HIDP\|CONFIG_BT_HCIBTUSB\|CONFIG_BT_HCIUART" /usr/src/linux/.config
/usr/src/linux/.config:1613:CONFIG_BT_RFCOMM=m
/usr/src/linux/.config:1614:CONFIG_BT_RFCOMM_TTY=y
/usr/src/linux/.config:1619:CONFIG_BT_HIDP=m
/usr/src/linux/.config:1634:CONFIG_BT_HCIBTUSB=m
/usr/src/linux/.config:1636:CONFIG_BT_HCIBTUSB_BCM=y
/usr/src/linux/.config:1638:CONFIG_BT_HCIBTUSB_RTL=y
/usr/src/linux/.config:1640:CONFIG_BT_HCIUART=m
/usr/src/linux/.config:1641:CONFIG_BT_HCIUART_H4=y
/usr/src/linux/.config:1642:CONFIG_BT_HCIUART_BCSP=y
$ lsmod | grep "bt"
btusb 61440 0
btrtl 28672 1 btusb
btbcm 24576 1 btusb
btintel 49152 1 btusb
bluetooth 970752 20 btrtl,btintel,btbcm,bnep,btusb
$ rc-status | grep bluetooth
bluetooth [ started ]
|
I have installed the bluez package with the firmware from my wireless card broadcom
| Code: |
$ emerge -pv bluez broadcom-bt-firmware
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 4.62 s.
[ebuild R ] sys-firmware/broadcom-bt-firmware-12.0.1.1105_p3::gentoo 0 KiB
[ebuild R ~] net-wireless/bluez-5.70:0/3::gentoo USE="cups mesh obex readline udev -btpclient -debug -deprecated -doc -experimental -extra-tools -midi (-selinux) -systemd -test -test-programs" ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 0 KiB
|
I got the firmware loaded successfully
| Code: |
$ dmesg | grep Bluetooth
[ 3.843833] Bluetooth: Core ver 2.22
[ 3.843850] Bluetooth: HCI device and connection manager initialized
[ 3.843853] Bluetooth: HCI socket layer initialized
[ 3.843855] Bluetooth: L2CAP socket layer initialized
[ 3.843859] Bluetooth: SCO socket layer initialized
[ 3.977718] Bluetooth: hci0: BCM: chip id 101
[ 3.978718] Bluetooth: hci0: BCM: features 0x2f
[ 3.994719] Bluetooth: hci0: BCM4354A2
[ 3.994720] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
[ 3.998113] Bluetooth: hci0: BCM4356A2 'brcm/BCM4356A2-0a5c-640e.hcd' Patch
[ 4.809719] Bluetooth: hci0: BCM: features 0x2f
[ 4.825727] Bluetooth: hci0: BCM4354A2 USB 37.4 MHz wlbga_54z_iLNA
[ 4.825733] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0255
[ 5.725993] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.725996] Bluetooth: BNEP filters: protocol multicast
[ 5.725999] Bluetooth: BNEP socket layer initialized
[ 5.727901] Bluetooth: MGMT ver 1.22
[19373.468285] Bluetooth: hci0: BCM: chip id 101
[19373.469290] Bluetooth: hci0: BCM: features 0x2f
[19373.485313] Bluetooth: hci0: BCM4354A2
[19373.485317] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
[19373.486311] Bluetooth: hci0: BCM4356A2 'brcm/BCM4356A2-0a5c-640e.hcd' Patch
[19374.299308] Bluetooth: hci0: BCM: features 0x2f
[19374.315314] Bluetooth: hci0: BCM4354A2 USB 37.4 MHz wlbga_54z_iLNA
[19374.315334] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0255
[19374.374571] Bluetooth: MGMT ver 1.22
|
The pb with my headset is that I have an error while pairing
| Code: |
$ bluetoothctl
Agent registered
hci0 new_settings: powered bondable le secure-conn
[CHG] Controller 5C:93:A2:75:9F:2B Pairable: yes
AdvertisementMonitor path registered
[bluetooth]# show
Controller 5C:93:A2:75:9F:2B (public)
Name: BlueZ 5.70
Alias: BlueZ 5.70
Class: 0x00000000 (0)
Powered: yes
PowerState: on
Discoverable: no
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Microphone Control (0000184d-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Volume Offset Control (00001845-0000-1000-8000-00805f9b34fb)
UUID: Volume Control (00001844-0000-1000-8000-00805f9b34fb)
UUID: Broadcast Audio Scan (0000184f-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0546
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedCapabilities Key: MaxAdvLen
SupportedCapabilities Value: 0x1f (31)
SupportedCapabilities Key: MaxScnRspLen
SupportedCapabilities Value: 0x1f (31)
Advertisement Monitor Features:
SupportedMonitorTypes: or_patterns
[bluetooth]# power on
Changing power on succeeded
$ scan on
[bluetooth]# devices
Device 80:C3:BA:2F:E2:AD MOMENTUM TW 3
..
[bluetooth]# pair 80:C3:BA:2F:E2:AD
Attempting to pair with 80:C3:BA:2F:E2:AD
hci0 80:C3:BA:2F:E2:AD type LE Public connected eir_len 23
[CHG] Device 80:C3:BA:2F:E2:AD Connected: yes
hci0 80:C3:BA:2F:E2:AD User Confirm 600411 hint 1
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD Bonded: yes
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD UUIDs: 0000eb10-d102-11e1-9b23-00025b00a5a5
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD UUIDs: 0000fd92-0000-1000-8000-00805f9b34fb
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD UUIDs: 0000fdce-0000-1000-8000-00805f9b34fb
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD ServicesResolved: yes
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [CHG] Device 80:C3:BA:2F:E2:AD Paired: yes
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [NEW] Primary Service (Handle 0x0000)
/org/bluez/hci0/dev_80_C3_BA_2F_E2_AD/service0001
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [NEW] Characteristic (Handle 0x0000)
/org/bluez/hci0/dev_80_C3_BA_2F_E2_AD/service0001/char0002
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [NEW] Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_80_C3_BA_2F_E2_AD/service0001/char0002/desc0004
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [NEW] Characteristic (Handle 0x0000)
/org/bluez/hci0/dev_80_C3_BA_2F_E2_AD/service0001/char0005
00002b29-0000-1000-8000-00805f9b34fb
Client Supported Features
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> [NEW] Primary Service (Handle 0x0000)
/org/bluez/hci0/dev_80_C3_BA_2F_E2_AD/service000c
0000fdce-0000-1000-8000-00805f9b34fb
SENNHEISER electronic GmbH & Co. KG
...
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> Pairing successful
[] Accept pairing with 80:C3:BA:2F:E2:AD (yes/no) >> yes
User Confirm reply failed. status 0x03 (Failed)
hci0 80:C3:BA:2F:E2:AD type LE Public disconnected with reason 3
[CHG] Device 80:C3:BA:2F:E2:AD ServicesResolved: no
[CHG] Device 80:C3:BA:2F:E2:AD Connected: no
[bluetooth]#
|
I got this error while pairing.
| Code: |
$ tail -f /var/log/syslog
Nov 20 19:56:41 darkstar bluetoothd[1548]: profiles/battery/battery.c:foreach_batt_service() More than one BATT service exists for this device
Nov 20 19:56:42 darkstar bluetoothd[1548]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID: Invalid pdu length received
|
Any idea what might get wrong ?
Thanks
Cyrille
Last edited by cduret on Tue Nov 21, 2023 5:41 am; edited 1 time in total |
|
| Back to top |
|
 |
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6039
Location: Dallas area
|
| Posted: Mon Nov 20, 2023 9:16 pm Post subject: |
|
|
Looks like it's trying to connect with LE (low energy setting) which I had problems with, so I just turned it off.
| Code: | grep -i controller /etc/bluetooth/main.conf
# Restricts all controllers to the specified transport. Default value
#ControllerMode = dual
ControllerMode = bredr |
Default is dual bredr/LE, but several of my bluetooth devices didn't like le being enables, so I set it to straight bredr (/etc/bluetooth/main.conf)
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
cduret
n00b
Joined: 20 Mar 2018
Posts: 15
|
| Posted: Tue Nov 21, 2023 5:39 am Post subject: |
|
|
Ok,
I have added bredr to my main.conf
| Code: |
$ grep -nH "Controller" /etc/bluetooth/main.conf
/etc/bluetooth/main.conf:52:ControllerMode = bredr
|
I had an error
| Code: |
Nov 21 06:17:20 darkstar bluetoothd[24989]: profiles/audio/bap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled
|
which I fixed by adding experimental to my USE flags for bluez configuration
| Code: |
emerge -pv bluez
* IMPORTANT: config file '/etc/portage/package.use/use' needs updating.
* See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files.
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 5.14 s.
[ebuild R ~] net-wireless/bluez-5.70:0/3::gentoo USE="cups experimental mesh obex readline udev -btpclient -debug -deprecated -doc -extra-tools -midi (-selinux) -systemd -test -test-programs" ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 0 KiB
|
I can make the pairing successful but when I try to connect I still had an error
| Code: |
Nov 21 06:18:27 darkstar bluetoothd[24989]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 80:C3:BA:2F:E2:AD: Protocol not available
|
I read the post from https://bbs.archlinux.org/viewtopic.php?id=270465 then added the configuration
| Code: |
$ cat /etc/pulse/default.pa
# LDAC Standard Quality
load-module module-bluetooth-discover a2dp_config="ldac_eqmid=sq"
|
I then ensured pipewire was running
| Code: |
$ gentoo-pipewire-launcher
|
THEN IT DIT WORK !
AWESOME !
thanks |
|
| Back to top |
|
|
Banana
Veteran
Joined: 21 May 2004
Posts: 1251
Location: Germany
|
| Posted: Tue Nov 21, 2023 6:30 am Post subject: |
|
|
Just noted this in your code outputs:
| Code: | * IMPORTANT: config file '/etc/portage/package.use/use' needs updating.
* See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files. |
If you haven't already please run etc-update (as root)
_________________
My personal space
My delta-labs.org snippets do expire
PFL - Portage file list - find which package a file belongs to. |
|
| Back to top |
|
|
|
Multimedia
