Age | Commit message (Collapse) | Author | Files | Lines |
|
Autoconnection was causing some devices not to be spotted ever
when discovery mode was requested
It can be safely assumed on user loading the Bluetooth setting
page no currently paired devices are expected to autoconnected
Change-Id: Ic66d97e559e5ed8fada4ca0a4a7bb481a19bdc36
Bug-AGL: SPEC-795
Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
|
|
Store list of the order of devices paired to deduce priority of which
should be autoconnected to first.
Bug-AGL: SPEC-722
Change-Id: I0ab36b62842296ce5cc5c2bbfdbba1d4d2319f51
Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
|
|
On certain platforms like RPI3 and Porter there is a possible
race condition to systemd-rfkill service if using a USB BT device,
and this patchset listens for rfkill events, unblocks and brings
up hci interface.
Bug-AGL: SPEC-569
Change-Id: Id16f26953d17cbe2068807b538c52759016d3e50
Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
|
|
Allow Bluetooth binding to be build separately and installed
as a system wide service
Bug-AGL: SPEC-661 SPEC-715
Change-Id: I12feefa2908243aa3bdcb0341f9bc9654c23741e
Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
|