| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
BTM, BTU, and BTA modules were preset with hardcoded trace level
(BT_TRACE_LEVEL_DEBUG) during early development days. Since the trace levels
have been made configurable in /etc/bluetooth/bt_stack.conf at run-time,
removing those hardcoded settings.
So, the compile-time default trace level BT_TRACE_LEVEL_WARNING (set in
bt_trace.h) will be used if the bt_stack.conf is missing, or if the
TraceConf=false is given in the bt_stack.conf.
Change-Id: I76d905adbfda3c40f714398da86ebec90a1a8a40
|
|
|
|
|
|
|
|
| |
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: I9137c1313e9e132d71f61ff571af683f8ca6728b
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
event when Authentication fails
Change-Id: I0102762b8bfa06b8d99227c431be881269c14961
|
|
|
|
| |
Change-Id: I788b170b47fb4ec1febe60444960e10df4a3f419
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Included more code to support mouse connectiona and reconnection
Signed-off-by: Priti Aghera <paghera@broadcom.com>
Change-Id: I1e20997e85eda5919f20a069131e580bcbb0ca63
|
|
|
|
| |
Change-Id: I88ec6084c140fa257154a98e23e075900e84cc8c
|
|
|