From: Johan Hedberg <johan.hedberg@gmail.com>
To: Ting Chou <Ting.Chou@iaSolution.net>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [BLE] org.bluez.Device1.Connect() returns org.bluez.Error.NotAvailable
Date: Wed, 12 Dec 2012 12:07:37 +0200 [thread overview]
Message-ID: <20121212100737.GA6620@x220> (raw)
In-Reply-To: <ADCBF04BB97EBF4AAE65663F8478B61CA99E65ABDA@Luna.iaSolution.net>
Hi Ting,
On Wed, Dec 12, 2012, Ting Chou wrote:
> > That means that the profiles that are supposed to be supported with
> > this device are not calling either device_set_auto_connect() or
> > btd_device_add_attio_callback(). Both of those functions should cause
> > bluetoothd to start doing passive scanning and try to connect to the
> > device. Btw, which kernel version are you using. IIRC you'll need
> > something like 3.5 or newer for LE passive scanning to work.
> >
>
> I tried to let btd_device_add_attio_callback() get called by
>
> Characterisitc.DiscoverCharacteristics()
I thought you said some internally supported profiles get detected? Why
then do you need to use the ATT D-Bus interface? FWIW, since
attrib/client.c implementation doesn't match what's documented and since
there hasn't been anyone stepping up to update the code to use D-Bus
properties we'll probably not have the entire Characteristic D-Bus
interface in the 5.0 release. Instead, there's a plan to have a more
comprehensive and generic GATT D-Bus API for both peripheral and central
roles, which will probably land in 5.1 or one of the subsequent
releases.
> But still the Device1.Connect() after Device1.Disconnect() does not establish
> the connection. connect_profiles() returns btd_error_not_available() since
> !dev->pending:
It seems you've misunderstood this part. If the functions I mentioned
are used correctly you will not need to use Device.Connect at all.
Instead bluetoothd will start doing passive scanning and automatically
establish a connection to any device doing connectable advertising.
Johan
next prev parent reply other threads:[~2012-12-12 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 3:57 [BLE] org.bluez.Device1.Connect() returns org.bluez.Error.NotAvailable Ting Chou
2012-12-12 7:52 ` Johan Hedberg
2012-12-12 9:10 ` Ting Chou
2012-12-12 9:25 ` Johan Hedberg
2012-12-12 9:47 ` Ting Chou
2012-12-12 10:07 ` Johan Hedberg [this message]
2012-12-12 10:21 ` Ting Chou
2012-12-12 10:36 ` Johan Hedberg
2012-12-12 10:58 ` Anderson Lizardo
2012-12-12 10:53 ` Anderson Lizardo
2012-12-12 11:30 ` Ting Chou
2012-12-12 12:20 ` Anderson Lizardo
2012-12-13 2:33 ` Ting Chou
2012-12-13 7:48 ` Johan Hedberg
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=20121212100737.GA6620@x220 \
--to=johan.hedberg@gmail.com \
--cc=Ting.Chou@iaSolution.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).