From: Johan Hedberg <johan.hedberg@gmail.com>
To: Tobias Jakobi <liquid.acid@gmx.net>
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [bluez-5.14] connect fails with 'org.bluez.Error.NotAvailable'
Date: Mon, 7 Apr 2014 10:45:35 +0300 [thread overview]
Message-ID: <20140407074535.GA8112@t440s.lan> (raw)
In-Reply-To: <5341D403.8050001@gmx.net>
Hi Tobias,
On Mon, Apr 07, 2014, Tobias Jakobi wrote:
> I think I isolated the issue. The problem is that the profiles that are
> associated to the NAP, PANU and GN services haven't got the auto_connect
> flag set.
>
> So during connect_profiles() they're never considered, and there is no
> way to change this via the cmdline tools. Which effectively disables
> this functionality.
>
> Maybe the DBus interface can change these setting for built-in profiles,
> but you honestly can't expect the enduser to fiddle around with that.
There is actually another D-Bus method that can be used to connect any
profile, regardless of the auto_connect value: Device1.ConnectProfile().
The test-device script already supports it by doing something like
"test-device connect <addr> nap" instead of "test-device connect <addr>".
I think it might be a good idea to extend bluetoothctl to support the
same.
Johan
prev parent reply other threads:[~2014-04-07 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 22:25 [bluez-5.14] connect fails with 'org.bluez.Error.NotAvailable' Tobias Jakobi
2014-02-28 12:16 ` Anderson Lizardo
2014-02-28 16:57 ` Tobias Jakobi
2014-02-28 17:11 ` Anderson Lizardo
2014-03-02 18:54 ` Tobias Jakobi
2014-04-06 15:59 ` Tobias Jakobi
2014-04-06 22:24 ` Tobias Jakobi
2014-04-07 7:45 ` Johan Hedberg [this message]
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=20140407074535.GA8112@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=liquid.acid@gmx.net \
/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