| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Rather than using a text file and generating each buildcfg.h file
per device bdroid_buildcfg.h which supplies device specific values
and then bt_target.h will supply common values.
Change-Id: I12cb5408729c3e076562a292204f07a0c4b52628
|
|
|
|
| |
Change-Id: Iebc520d9b10ef220a83a16ff55efa46b4c5a0d27
|
|
|
|
|
|
|
| |
1. Per the spec, if both sides are using "No Bonding" for auth requirements, then the key could be considered a session key. Updated the pairing logic to handle this
2. If incoming JustWorks pairing is initiated, prompt the user for consent if the peer's io capabilities reflects DisplayOnly or NoInputNoOutput
Change-Id: If592c96203e7a4b25af3d87056d534131b606e58
|
|
|
|
|
|
| |
BT_PROPERTY_UUIDS of the remote device
Change-Id: I1facd9238cf847915df4c01b33c77b2fdaa168cb
|
|
|
|
|
|
| |
during inquiry scanning etc
Change-Id: Iadcd9242dac707a6db857bc9f2ab89e59499764b
|
|
|
|
|
|
|
| |
BT_DISCOVERY_STOPPED signals are sent only after receiving the
status/complete event from HCI for the start_inquiry/cancel_inquiry APIs
Change-Id: I14da272b3e0596c2062ce617e9dccb788cc80425
|
|
|
|
| |
Change-Id: I66794a8821481c58e045bb8acd8b7b758900d3e9
|
|
|
|
| |
Change-Id: I88ec6084c140fa257154a98e23e075900e84cc8c
|
|
|