From: Johan Hedberg <johan.hedberg@gmail.com>
To: Ting Chou <Ting.Chou@iaSolution.net>
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [BLE] org.bluez.Device1.Connect() returns org.bluez.Error.NotAvailable
Date: Thu, 13 Dec 2012 09:48:50 +0200 [thread overview]
Message-ID: <20121213074850.GA1348@x220> (raw)
In-Reply-To: <ADCBF04BB97EBF4AAE65663F8478B61CA99E65AC43@Luna.iaSolution.net>
Hi Ting,
On Thu, Dec 13, 2012, Ting Chou wrote:
> > > I'm not sure if I understand correctly. But do you mean the GCEP you
> > > mentioned above is applied while "reconnecting" to a supported device?
> >
> > Yes, all GAP connection procedures are applicable for re-connection.
> > There is no "reconnection" procedure as per GAP (as far as I know).
> > But note that each GATT profile can specify reconnection procedures in
> > case of disconnection due to link loss (most of those that I read have
> > this). For instance, in HTP:
> >
> > "5.2.4 Link Loss Reconnection Procedure
> > When a connection is terminated due to link loss, a Collector should
> > attempt to reconnect to the Thermometer using any of the GAP connection
> > procedures with the parameters in Table 5.2."
> >
> > This is what BlueZ is doing for profiles implemented internally, except
> > that the parameters we use are not the ones recommended on the profile
> > specs (that could be implemented in future, but for now GCEP uses fixed
> > connection parameters).
> >
>
> So I should exercise the D-Bus API like following for LE device:
>
> Adapter1.StartDiscovery
> Device1.Pair
> ...
> ...
> // link loss
> ...
> // auto reconnect
> ...
> Adapter1.RemoveDevice
>
> Is my understanding correct?
Yes, except that you should call Adapter1.StopDiscovery before calling
Device1.Pair.
Johan
prev parent reply other threads:[~2012-12-13 7:48 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
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 [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=20121213074850.GA1348@x220 \
--to=johan.hedberg@gmail.com \
--cc=Ting.Chou@iaSolution.net \
--cc=anderson.lizardo@openbossa.org \
--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).