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
Bug-AGL: SPEC-795 SPEC-913
Change-Id: Ic66d97e559e5ed8fada4ca0a4a7bb481a19bdc36
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.
Change-Id: I0db62e93dfae92a63cbd6f45515093344322f2ca
Bug-AGL: SPEC-722
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.
Change-Id: I336e496b589a23767003e186473c4aed49471fba
Bug-AGL: SPEC-569
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>
|