BT Headphone doesn't autoconnect

Support and Help
, ,
1

Hello! I’m using Ubuntu MATE 24.04 LTS, Kernel version is 6.8.0-53.
Blueman version is 2.3.5, Bluez 5.72.
One year ago I bought a Panasonic Headset, I paired it with my BT dongle and it always worked fine. One week ago I paired the Headset with my cell phone, starting from that moment the headset doesn’t connect and disconnect. The only way to connect it was to re-pair it. Suerfing the web I found a possible solution: I edited the file /etc/bluetooth/main.com like this:

##############################
MinConnectionInterval=7
MaxConnectionInterval=9
##############################

Before my intervention the two lines were commented with no values.

Now I obtained that the headset can manually connect (sometimes I need 2 or 3 tries) and it disconnect automatically.
But no way to auto connect, obviously the device is paired and trusted.
Please note that I have others devices paired on the same dongle and they connect automatically with no problems.
Any suggestion to obtain auto connection for this device?

2

Where did you find this possible solution?

3

Does it work correctly during the same boot, or is the problem caused after a reboot or shutdown?

4

Make sure you disable your cell phone bluetooth transmitter before trying to connect with your Ubuntu Mate system. It is possible your Panasonic headphones connects to your cell phone.
IMHO, if BT device is connected to one system, it is not free to connect to another.

5

I founf it in Ubuntu Mate forum

6

No, it doesn’t. I always have to connect manually.

7

Yes, the Cell phone BT is off, I also removed the Headset from the cell phone known devices.

8

I was looking through /etc/bluetooth/main.conf and discovered down toward the bottom of the file there is a label, Policy. Below that, there are several sections that address Reconnect…
I admit I know next to nothing about configuring Bluetooth configuration files, but it is an subject you may wish to explore
further.

9

Ok so it’s extremely unlikely to be the dongle or the machine, but it should be specific to this device.

And you should probably undo what you did because those connection intervals will likely affect multiple Bluetooth devices and not just the one.

What I suggest is that you completely remove it from your Bluetooth devices and try to pair again.

If that’s still no good, give us some more specifics on this device. bluetoothctl can help out here.

10

I agree, because the others devices are working properly.

Well, actually those intervals makes that I can connect the device manually, before I had to repair it every time before connecting. The others devices aren’t affected, still work properly.

I have done it a plenty of times, with no success.

Here some info from bluetoothctl, let me know if you need more.
RB-HF420B is the name of the Headset that has problems.

BTW, thanks a lot for your help.

[RB-HF420B]# show
Controller F4:4E:FC:3F:AA:B4 (public)
	Manufacturer: 0x03e0 (992)
	Version: 0x0c (12)
	Name: pc-sala
	Alias: pc-sala 5.3
	Class: 0x007c0104 (8126724)
	Powered: yes
	Discoverable: no
	DiscoverableTimeout: 0x000000b4 (180)
	Pairable: yes
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0548
	Discovering: no
	Roles: central
	Roles: peripheral
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x05 (5)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
[RB-HF420B]# list
Controller F4:4E:FC:3F:AA:B4 pc-sala 5.3 [default]
[RB-HF420B]# devices
Device 40:EF:4C:FA:15:2B Philips BT2200
Device B4:6C:47:53:D0:D2 RB-HF420B
Device 41:42:B9:83:14:A1 ricevitore stereo BLS-B35
[RB-HF420B]# info
Device B4:6C:47:53:D0:D2 (public)
	Name: RB-HF420B
	Alias: RB-HF420B
	Class: 0x00260404 (2491396)
	Icon: audio-headset
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	Battery Percentage: 0x28 (40)
[RB-HF420B]#
11

Underneath Handsfree mine has another two lines,
UUID: PnP Information …
Modalias: bluetooth:v05D6p000Ad0240
Other than that, my output for same commands look like yours.

12

it could be some pairing or codecs or driver missing, but also…

It could be also pipewire or spa package issue and there is also some pipewire LE Audio + LC3 guide.

but maybe bluetooth, btusb, btaudio in /etc/modules-load.d/ also missing

pw-cli mon
pw-cli ls Port, Interface, Node

alsa card could also have optional alsa-card-profiles and could be also something set via
pactl set-card-profile alsa_card… profile
pactl
pactl set-default-sink
pactl set-default-source
pactl list

13

You was right, I found in Google the sequence for resetting the Headset BT and now it works fine.

Thanks to all for your answers and help.

1 Like
14

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.