linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominik 'Rathann' Mierzejewski <dominik@greysector.net>
To: linux-bluetooth@vger.kernel.org
Subject: [BlueZ] connection failure or profile unavailability when connecting two devices with overlapping profiles
Date: Wed, 1 Aug 2018 16:06:18 +0200	[thread overview]
Message-ID: <20180801140618.GD10915@sakura.greysector.net> (raw)

Dear list,
I reported this originally in Fedora 27
(https://bugzilla.redhat.com/show_bug.cgi?id=1541575), but maybe someone
here has a better idea, since it's still reproducible on Fedora 28 with
newer versions of bluez and pulseaudio.

Description of problem:
I'm unable to connect the Creative MUVO 2c speaker if a Jabra Evolve 65
headset is connected already. If I connect the speaker first, then I'm
able to connect the Jabra headset, but only HFP profile works (A2DP sink
is not selectable). There are no issues adding an Android phone to the
mix in any order, seemingly because it only has non-overlapping profiles
A2DP source and HFP audio gateway).

Version-Release number of selected component (if applicable):
bluez-5.50-1.fc28.x86_64
pulseaudio-12.2-1.fc28.x86_64

How reproducible:
Always.

Case 1:
Steps to Reproduce:
1. bluetoothctl
2. connect 50:1A:A5:xx:xx:xx # Jabra Evolve 65
3. connect 00:02:3C:yy:yy:yy # Creative MUVO 2c

Actual results:
Attempting to connect to 00:02:3C:yy:yy:yy
Failed to connect: org.bluez.Error.Failed

Expected results:
Attempting to connect to 00:02:3C:yy:yy:yy
[CHG] Device 00:02:3C:yy:yy:yy Connected: yes
Connection successful
[CHG] Device 00:02:3C:yy:yy:yy ServicesResolved: yes

Case 2:
Steps to Reproduce:
1. bluetoothctl
2. connect 00:02:3C:yy:yy:yy # Creative MUVO 2c
3. connect 50:1A:A5:xx:xx:xx # Jabra Evolve 65
4. pactl set-card-profile bluez_card.50_1A_A5_xx_xx_xx a2dp_sink
5. pactl list sinks short |grep bluez

Actual results:
$ pactl set-card-profile bluez_card.50_1A_A5_xx_xx_xx a2dp_sink
Failure: Input/Output error
$ pactl list sinks short |grep bluez
26	bluez_sink.00_02_3C_yy_yy_yy.a2dp_sink	module-bluez5-device.c	s16le 2ch 44100Hz	SUSPENDED
27	bluez_sink.50_1A_A5_xx_xx_xx.headset_head_unit	module-bluez5-device.c	s16le 1ch 8000Hz	IDLE

Expected results:
$ pactl set-card-profile bluez_card.50_1A_A5_xx_xx_xx a2dp_sink
$ pactl list sinks short |grep bluez
26	bluez_sink.00_02_3C_yy_yy_yy.a2dp_sink	module-bluez5-device.c	s16le 2ch 44100Hz	SUSPENDED
27	bluez_sink.50_1A_A5_D7_43_93.a2dp_sink	module-bluez5-device.c	s16le 2ch 44100Hz	SUSPENDED

Additional info:
Selecting a2dp_sink when Jabra is the only device with a2dp_sink
connected works just fine.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPMFusion   http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

             reply	other threads:[~2018-08-01 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 14:06 Dominik 'Rathann' Mierzejewski [this message]
2018-08-01 15:08 ` [BlueZ] connection failure or profile unavailability when connecting two devices with overlapping profiles Luiz Augusto von Dentz
2018-08-01 21:33   ` Dominik 'Rathann' Mierzejewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180801140618.GD10915@sakura.greysector.net \
    --to=dominik@greysector.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).