Linux bluetooth development
 help / color / mirror / Atom feed
From: Andrejs Hanins <andrejs.hanins@ubnt.com>
To: Tim Tisdall <tisdall@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-bluetooth@vger.kernel.org
Subject: Re: bt dongle goes awry after too many connections
Date: Mon, 09 Mar 2015 18:59:52 +0200	[thread overview]
Message-ID: <54FDD188.4000201@ubnt.com> (raw)
In-Reply-To: <CAGxYWpYQGAYpDoa3=G+fwUxcqsA2pNbq81y4=-6ww8QXxeg+jQ@mail.gmail.com>


On 2015.03.09. 18:53, Tim Tisdall wrote:
> On Mon, Mar 9, 2015 at 12:47 PM, Andrejs Hanins <andrejs.hanins@ubnt.com> wrote:
>> Sure, I noticed that lots of work has been done lately in regard to LE, so
>> I'm indeed using 5.28 daemon@3.19.x kernel in LE-only mode and so far so
>> good.
>> One of the useful things which still seems to be missing is the control over
>> LE advertisements via D-Bus iface. "Discoverable" property change does not
>> affect LE advs. I'm currently using 'hciconfig hci0 leadv' to make it work.
>> But still, LE advs stop and do not re-start after adapter is
>> connected/disconnected to some peripheral.
> It's doing what I'd expect then...  I expect dongles to be reset if
> they're unplugged and then re-attached.  I don't know if there's an
> expectation for devices to be returned to their last state if they're
> disconnected and re-connected when using DBUS, though.
I didn't mean physically re-plugging the adapter. LE advs stop when 
adapter (controlled via D-Bus) is connected to some other device and 
does not start again when connection is closed. The adapter itself stays 
as it is.
>   I've pretty
> much avoided the DBUS interface since most of what I'm doing is simply
> not possible through it.

  reply	other threads:[~2015-03-09 16:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 20:25 bt dongle goes awry after too many connections Tim Tisdall
2015-03-03  0:17 ` Marcel Holtmann
2015-03-03 16:02   ` Tim Tisdall
2015-03-03 16:07     ` Tim Tisdall
2015-03-03 16:19     ` Marcel Holtmann
2015-03-03 16:41       ` Tim Tisdall
2015-03-09 14:40         ` Tim Tisdall
2015-03-09 15:27           ` Andrejs Hanins
2015-03-09 16:21             ` Marcel Holtmann
2015-03-09 16:47               ` Andrejs Hanins
2015-03-09 16:53                 ` Tim Tisdall
2015-03-09 16:59                   ` Andrejs Hanins [this message]
2015-03-09 17:10                 ` Marcel Holtmann
2015-03-09 17:22                   ` Andrejs Hanins
  -- strict thread matches above, loose matches on Subject: below --
2015-03-02 20:41 Tim Tisdall

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=54FDD188.4000201@ubnt.com \
    --to=andrejs.hanins@ubnt.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=tisdall@gmail.com \
    /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