You are not logged in.

#1 2021-10-16 15:17:54

kelen
Member
Registered: 2021-09-22
Posts: 7

[SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

When I use bluetooth, it can not  connect any device. Here is the error:
❯ bluetoothctl
Agent registered
[bluetooth]# connect 3C:86:D1:2E:DE:46
Attempting to connect to 3C:86:D1:2E:DE:46
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
[bluetooth]#

Last edited by kelen (2021-10-21 04:02:24)

Offline

#2 2021-10-16 23:41:48

AndreyTarkovsky
Member
Registered: 2017-03-26
Posts: 67

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Bluetooth support became a mess after the last updates. I have some controllers and some adapters. I have no idea what is happening. Sometimes they work and connect without issues, sometimes don't. Maybe some kernel driver related? I don't know

Offline

#3 2021-10-19 08:35:13

cypa
Member
Registered: 2021-06-30
Posts: 3

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

+1

kelen wrote:

When I use bluetooth, it can not  connect any device. Here is the error:
❯ bluetoothctl
Agent registered
[bluetooth]# connect 3C:86:D1:2E:DE:46
Attempting to connect to 3C:86:D1:2E:DE:46
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
[bluetooth]#

Offline

#4 2021-10-19 17:53:28

cypa
Member
Registered: 2021-06-30
Posts: 3

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

try
ControllerMode = bredr
in
/etc/bluetooth/main.conf

Offline

#5 2021-10-19 19:13:14

MrQubo
Member
Registered: 2021-10-19
Posts: 2

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Had the same error (with headphones).
It's seems like it's caused because something's missing in system: https://github.com/bluez/bluez/blob/bb1 … xt#L26-L30
I've installed `pulseaudio-bluetooth` and now it works. Btw, it's an optional dependency of `bluedevil`.

Last edited by MrQubo (2021-10-19 19:13:59)

Offline

#6 2021-10-20 08:32:43

rubenvb
Member
Registered: 2011-01-14
Posts: 98

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

I have the same issue.
Installing pulseaudio-bluetooth did not change anything, neither did setting "ControllerMode = bredr" in /etc/bluetooth/main.conf.

Offline

#7 2021-10-20 09:22:27

kelen
Member
Registered: 2021-09-22
Posts: 7

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Thanks for your replies, I will try them tonight. (*^_^*)

Offline

#8 2021-10-20 15:14:23

kelen
Member
Registered: 2021-09-22
Posts: 7

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

rubenvb wrote:

I have the same issue.
Installing pulseaudio-bluetooth did not change anything, neither did setting "ControllerMode = bredr" in /etc/bluetooth/main.conf.

Yes. The methods do not work for my bluetooth too.
It is  strange  that the bluetooth would connect my device for about two second  when I try to pair them,  then it will disconnect and repeat the previous error.
This error appeared since the last bluez update. I tried to test it on another PC and the same error appeared.

Offline

#9 2021-10-20 17:42:36

dw
Member
From: Vienna, Austria
Registered: 2006-11-25
Posts: 158

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

hi, after seeing exactly the same behaviour I just wanted to add my observations to this thread; i was able to reconnect with my headphones after doing a full reboot and then in bluetoothctl a trust <dev>; (before the update, the device was trusted of course); afterwards, i could connect without issues;

Offline

#10 2021-10-20 17:55:45

MrQubo
Member
Registered: 2021-10-19
Posts: 2

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

kelen wrote:

Yes. The methods do not work for my bluetooth too.
It is  strange  that the bluetooth would connect my device for about two second  when I try to pair them,  then it will disconnect and repeat the previous error.
This error appeared since the last bluez update. I tried to test it on another PC and the same error appeared.

What type of devices have you exactly tried to connect, headphones/speaker, or something else? Did you reboot after installing pulseaudio-bluetooth?

Offline

#11 2021-10-21 03:11:52

kelen
Member
Registered: 2021-09-22
Posts: 7

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

MrQubo wrote:
kelen wrote:

Yes. The methods do not work for my bluetooth too.
It is  strange  that the bluetooth would connect my device for about two second  when I try to pair them,  then it will disconnect and repeat the previous error.
This error appeared since the last bluez update. I tried to test it on another PC and the same error appeared.

What type of devices have you exactly tried to connect, headphones/speaker, or something else? Did you reboot after installing pulseaudio-bluetooth?


Hi. I have another PC (openSUSE leap), a mobilephone and two headphones. All of them can not connect to my Arch and they can connect to each other (Obviously the two headphones cannot be connected to each other).
The same error appeared after I installed arch on another computer. They worked well two weeks ago on arch.

Oh, it is my mistake. Yesterday I just restarted bluetooth.service with not reboot. The Bluetooth works now after I installed  pulseaudio-bluetooth and fully rebooted Arch. Thanks very much! The problem has been solved.

Last edited by kelen (2021-10-21 12:10:27)

Offline

#12 2021-10-21 09:45:23

rubenvb
Member
Registered: 2011-01-14
Posts: 98

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Works here too when rebooting after pulseaudio-bluetooth was installed.

Offline

#13 2021-10-22 11:15:21

wowsuchcode
Member
Registered: 2019-05-16
Posts: 11

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

There have been some weird problems with bluetooth for the last few days.

My bluetooth sometimes crash and I have to reboot the service. Something in systemd about "dbus message" not working or stuff.

If anyone have a solution... it doesn't happen very regularly but it's annoying. Hope it gets fixed by our volunteers soon.\

Offline

#14 2021-10-22 15:36:43

Tyskr
Member
Registered: 2019-12-11
Posts: 66

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Problem persists for me.

Offline

#15 2021-10-22 18:58:58

JagRoss
Member
Registered: 2020-10-12
Posts: 1

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Had pulseaudio-modules-bt installed.
Changed it for pulseaudio-bluetooth and my headphones worked after a restart.

Offline

#16 2021-10-23 22:10:33

Doctor Colossus
Member
Registered: 2012-08-26
Posts: 18

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

I am also experiencing this issue using pipewire after upgrading bluez, bluez-libs, and bluez-utils all from 5.61-1 to 5.62-1 today. I already had pulseaudio-bluetooth installed.

Last edited by Doctor Colossus (2021-10-23 22:10:58)

Offline

#17 2021-10-26 19:06:39

Doctor Colossus
Member
Registered: 2012-08-26
Posts: 18

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

For me the problem initially happened intermittently after restarting the service and rebooting.

Once I noticed in

systemctl status bluetooth

that the A2DP modules seemed to be getting loaded with a long delay.

When initially trying to connect to my headphones,

src/service.c:btd_service_connect() a2dp-sink profile connect failed for [MAC]: Protocol not available

was logged, but almost four minutes later it spontaneously connected, along with the following from the logs:

Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/ldac
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSink/aptx_hd
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/aptx_hd
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSink/aptx
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/aptx
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/aac
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSink/sbc
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/sbc
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSink/sbc_xq
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/sbc_xq
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/faststream
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/faststream_duplex
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Endpoint registered: sender=:1.628 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1

For now though, the problem seems to have inexplicably resolved itself.

Last edited by Doctor Colossus (2021-10-26 19:08:43)

Offline

#18 2021-10-31 14:50:24

leonixyz
Member
Registered: 2014-07-12
Posts: 62

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

I did a fresh installation yesterday. Today I installed bluez, bluez-utils (not yet pulseaudio-bluetooth), and started bluetooth.service.

$ pacman -Ss bluez | grep installed
extra/bluez 5.62-1 [installed]
extra/bluez-libs 5.62-1 [installed]
extra/bluez-utils 5.62-1 [installed]

Then I ran bluetoothctl, and was able to power on the controller, scan, find my headphones, pair with them and trust them.

After trusting them, i tried to connect, and bluetoothctl returned the error reported in the initial post: "br-connection-profile-unavailable".

So I found this post, installed pulseaudio-bluetooth, rebooted.

Now bluetoothctl says there is no default controller:

# bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available

rfkill says that no device is blocked

# rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

I tried stopping bluetooth.service and starting it in debug mode (and it still says in one of the last lines "Number of controllers: 0")

# /usr/lib/bluetooth/bluetoothd -n -d
bluetoothd[1218]: Bluetooth daemon 5.62
bluetoothd[1218]: src/main.c:parse_config() parsing /etc/bluetooth/main.conf
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cDiscoverableTimeout\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cAlwaysPairable\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cPairableTimeout\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cPrivacy\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cJustWorksRepairing\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cTemporaryTimeout\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cName\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cClass\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cDeviceID\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cReverseServiceDiscovery\u201d in group \u201cGeneral\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cCache\u201d in group \u201cGATT\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cKeySize\u201d in group \u201cGATT\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cExchangeMTU\u201d in group \u201cGATT\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cChannels\u201d in group \u201cGATT\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cSessionMode\u201d in group \u201cAVDTP\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cStreamMode\u201d in group \u201cAVDTP\u201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key \u201cRSSISamplingPeriod\u201d in group \u201cAdvMon\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cPageScanType\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cPageScanInterval\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cPageScanWindow\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cInquiryScanType\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cInquiryScanInterval\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cInquiryScanWindow\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cLinkSupervisionTimeout\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cPageTimeout\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cMinSniffInterval\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cMaxSniffInterval\u201d in group \u201cBR\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cMinAdvertisementInterval\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cMaxAdvertisementInterval\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cMultiAdvertisementRotationInterval\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanIntervalAutoConnect\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanWindowAutoConnect\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanIntervalSuspend\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanWindowSuspend\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanIntervalDiscovery\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanWindowDiscovery\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanIntervalAdvMonitor\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanWindowAdvMonitor\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanIntervalConnect\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cScanWindowConnect\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key \u201cMinConnectionInterval\u201d in group \u201cLE\u201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “MaxConnectionInterval” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “ConnectionLatency” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “ConnectionSupervisionTimeout” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “Autoconnecttimeout” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “AdvMonAllowlistScanDuration” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “AdvMonNoFilterScanDuration” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “EnableAdvMonInterleaveScan” in group “LE”
bluetoothd[1218]: src/adapter.c:adapter_init() sending read version command
bluetoothd[1218]: Starting SDP server
bluetoothd[1218]: src/sdpd-service.c:register_device_id() Adding device id record for 0002:1d6b:0246:053e
bluetoothd[1218]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[1218]: src/plugin.c:add_plugin() Loading hostname plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading autopair plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading policy plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading a2dp plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading avrcp plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading hog plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading gap plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading scanparam plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading deviceinfo plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading midi plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading battery plugin
bluetoothd[1218]: src/plugin.c:plugin_init() Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[1218]: profiles/input/suspend-none.c:suspend_init() 
bluetoothd[1218]: profiles/network/manager.c:read_config() Config options: Security=true
bluetoothd[1218]: plugins/hostname.c:read_dmi_fallback() chassis: laptop
bluetoothd[1218]: plugins/hostname.c:read_dmi_fallback() major: 0x01 minor: 0x03
bluetoothd[1218]: src/main.c:main() Entering main loop
bluetoothd[1218]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[1218]: Bluetooth management interface 1.21 initialized
bluetoothd[1218]: src/adapter.c:read_version_complete() sending read supported commands command
bluetoothd[1218]: src/adapter.c:read_version_complete() sending read index list command
bluetoothd[1218]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 0 soft 0 hard 0
bluetoothd[1218]: src/adapter.c:read_commands_complete() Number of commands: 84
bluetoothd[1218]: src/adapter.c:read_commands_complete() Number of events: 42
bluetoothd[1218]: src/adapter.c:read_commands_complete() enabling kernel-side connection control
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports the set_blocked_keys op
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports controller cap command
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports exp features
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports set system confic
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports ext adv commands
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports suspend/resume events
bluetoothd[1218]: src/adapter.c:read_index_list_complete() Number of controllers: 0
bluetoothd[1218]: src/profile.c:register_profile() sender :1.90
bluetoothd[1218]: src/profile.c:create_ext() Created "Headset unit"
bluetoothd[1218]: src/profile.c:register_profile() sender :1.90
bluetoothd[1218]: src/profile.c:create_ext() Created "Hands-Free Voice gateway"
bluetoothd[1218]: plugins/hostname.c:property_changed() static hostname: gear
bluetoothd[1218]: plugins/hostname.c:property_changed() pretty hostname: 
bluetoothd[1218]: plugins/hostname.c:property_changed() chassis: laptop

The kernel does not report any error, apparently (there are no red messages), but it says: "No device address configured"

# dmesg | grep Bluetooth
[    2.816296] Bluetooth: Core ver 2.22
[    2.816312] Bluetooth: HCI device and connection manager initialized
[    2.816314] Bluetooth: HCI socket layer initialized
[    2.816316] Bluetooth: L2CAP socket layer initialized
[    2.816318] Bluetooth: SCO socket layer initialized
[    2.911024] Bluetooth: hci0: Firmware timestamp 2021.38 buildtype 1 build 31586
[    2.912998] Bluetooth: hci0: No device address configured
[    2.913880] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[    2.913914] Bluetooth: hci0: Boot Address: 0x100800
[    2.913915] Bluetooth: hci0: Firmware Version: 98-38.21
[    2.913916] Bluetooth: hci0: Firmware already loaded
[    2.921446] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.921448] Bluetooth: BNEP filters: protocol multicast
[    2.921450] Bluetooth: BNEP socket layer initialized

I cannot think anything else that can help debug this issue.

The strange thing is that, before installing pulseaudio-bluetooth, i was able to use bluetoothctl up to a certain point. Then after installing it, i "lost" the default controller

Last edited by leonixyz (2021-10-31 14:56:40)

Offline

#19 2021-10-31 14:52:48

nesk
Member
Registered: 2011-03-31
Posts: 181

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Getting "br-connection-profile-unavailable" and "br-connection-unknown" intermittently on bluez 5.62 + pipewire 0.3.39 packages (only pipewire-media-session is 1:0.4.0 after routine pacman -Syu with default repos).

Offline

#20 2021-11-02 13:18:10

kelen
Member
Registered: 2021-09-22
Posts: 7

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

In this case, should I delete the ‘resolved’ in the title  or  re-report the issue?  I don't know.

leonixyz wrote:

I did a fresh installation yesterday. Today I installed bluez, bluez-utils (not yet pulseaudio-bluetooth), and started bluetooth.service.

I cannot think anything else that can help debug this issue.

The strange thing is that, before installing pulseaudio-bluetooth, i was able to use bluetoothctl up to a certain point. Then after installing it, i "lost" the default controller

Last edited by kelen (2021-11-02 13:20:01)

Offline

#21 2021-11-05 22:24:45

leonixyz
Member
Registered: 2014-07-12
Posts: 62

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

after a system update, the bluetooth works perfectly. The list of upgraded packages:

[2021-11-05T23:00:14+0100] [ALPM] upgraded iana-etc (20210903-1 -> 20211025-1)
[2021-11-05T23:00:14+0100] [ALPM] upgraded glib2 (2.70.0-2 -> 2.70.1-1)
[2021-11-05T23:00:14+0100] [ALPM] upgraded libcap (2.59-1 -> 2.60-1)
[2021-11-05T23:00:14+0100] [ALPM] upgraded libgpg-error (1.42-1 -> 1.43-1)
[2021-11-05T23:00:14+0100] [ALPM] upgraded iso-codes (4.7.0-1 -> 4.8.0-1)
[2021-11-05T23:00:15+0100] [ALPM] upgraded firefox-developer-edition (94.0b9-1 -> 95.0b3-1)
[2021-11-05T23:00:15+0100] [ALPM] upgraded i3-gaps (4.20-1 -> 4.20.1-1)
[2021-11-05T23:00:15+0100] [ALPM] upgraded libheif (1.12.0-1 -> 1.12.0-2)
[2021-11-05T23:00:15+0100] [ALPM] upgraded linux (5.14.15.arch1-1 -> 5.14.16.arch1-1)
[2021-11-05T23:00:16+0100] [ALPM] upgraded linux-firmware (20210919.d526e04-1 -> 20211027.1d00989-1)
[2021-11-05T23:00:16+0100] [ALPM] upgraded linux-headers (5.14.15.arch1-1 -> 5.14.16.arch1-1)
[2021-11-05T23:00:16+0100] [ALPM] upgraded nemo (5.0.4-1 -> 5.0.5-1)
[2021-11-05T23:00:16+0100] [ALPM] upgraded unzip (6.0-14 -> 6.0-15)

Offline

#22 2021-11-18 02:50:37

sfairmm
Member
From: São Paulo
Registered: 2021-11-18
Posts: 1

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

rubenvb wrote:

I have the same issue.
Installing pulseaudio-bluetooth did not change anything, neither did setting "ControllerMode = bredr" in /etc/bluetooth/main.conf.

Thank you, solved my problem.

Offline

#23 2021-11-18 14:05:17

burny02
Member
Registered: 2021-07-01
Posts: 23

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

For anyone else, I was having similar issues until I recompiled the btusb module.

The problem was the 'alt' mode of the adapter. 

Here is the btusb.c code - btusb_work

* Bluetooth USB spec recommends alt 6 (63 bytes), but
             * many adapters do not support it.  Alt 1 appears to
             * work for all adapters that do not have alt 6, and
             * which work with WBS at all.  Some devices prefer
             * alt 3 (HCI payload >= 60 Bytes let air packet
             * data satisfy 60 bytes), requiring
             * MTU >= 3 (packets) * 25 (size) - 3 (headers) = 72
             * see also Core spec 5, vol 4, B 2.1.1 & Table 2.1.
             */
            if (btusb_find_altsetting(data, 6))
                new_alts = 6;
            else if (btusb_find_altsetting(data, 3) &&
                 hdev->sco_mtu >= 72 &&
                 test_bit(BTUSB_USE_ALT3_FOR_WBS, &data->flags))
                new_alts = 1; /* MY EDIT - WAS 3 */
            else
                new_alts = 1;

Changing the alt to 1 (it was 3) sorted all my issues

Offline

#24 2021-11-25 15:04:14

nesk
Member
Registered: 2011-03-31
Posts: 181

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

Was working for a while, now fails again (br-connection-profile-unavailable) on bluez 5.62/kernel 5.15.1. Downgrading to 5.14.14 does not help.

Offline

#25 2021-11-25 15:13:14

nesk
Member
Registered: 2011-03-31
Posts: 181

Re: [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable.

burny02 wrote:

For anyone else, I was having similar issues until I recompiled the btusb module.

The problem was the 'alt' mode of the adapter. 

Here is the btusb.c code - btusb_work

* Bluetooth USB spec recommends alt 6 (63 bytes), but
             * many adapters do not support it.  Alt 1 appears to
             * work for all adapters that do not have alt 6, and
             * which work with WBS at all.  Some devices prefer
             * alt 3 (HCI payload >= 60 Bytes let air packet
             * data satisfy 60 bytes), requiring
             * MTU >= 3 (packets) * 25 (size) - 3 (headers) = 72
             * see also Core spec 5, vol 4, B 2.1.1 & Table 2.1.
             */
            if (btusb_find_altsetting(data, 6))
                new_alts = 6;
            else if (btusb_find_altsetting(data, 3) &&
                 hdev->sco_mtu >= 72 &&
                 test_bit(BTUSB_USE_ALT3_FOR_WBS, &data->flags))
                new_alts = 1; /* MY EDIT - WAS 3 */
            else
                new_alts = 1;

Changing the alt to 1 (it was 3) sorted all my issues

Are you normally running a manually compiled kernel or stock one from repos? Could you post some instructions on how you recompiled only one module?

Offline

Board footer

Powered by FluxBB