Return-Path: MIME-Version: 1.0 In-Reply-To: <54FDCEBC.2050705@ubnt.com> References: <6EDCDCB4-6F4D-4DE6-88DB-88D333FC2CCC@holtmann.org> <54FDBBD2.10608@ubnt.com> <185295B8-ABD9-4EDF-B290-12C430CCA906@holtmann.org> <54FDCEBC.2050705@ubnt.com> Date: Mon, 9 Mar 2015 12:53:57 -0400 Message-ID: Subject: Re: bt dongle goes awry after too many connections From: Tim Tisdall To: Andrejs Hanins Cc: Marcel Holtmann , linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=UTF-8 List-ID: On Mon, Mar 9, 2015 at 12:47 PM, Andrejs Hanins 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've pretty much avoided the DBUS interface since most of what I'm doing is simply not possible through it.