Bug: 314970357
Test: m a
Flag: EXEMPT, mechanical refactor

Change-Id: If11081de3d22e6673b8256b26d24d0053fbcbdc6

Bug: 301661850
Test: mma packages/modules/Bluetooth
Change-Id: I6aa2b466c8d73f67e0ebb173425e85da429c8363

Long time ago someone decided that using one callback for service
search and device search is good idea.
Turns out it's a bad idea that's causing service discovery callback when
name read callback comes back. This, in turn, causes profiles to not
connect properly.
To fix this, separate event is introduced for name read.

Test: atest net_test_btif_stack
Bug: 311217960
Change-Id: I343a585ffcb7b6112b493af1593beca871d70c91

Bug: 298403192
Test: m .

Change-Id: I6df4a4007c28f73ceca6e7ba48b7d2a166f58b15

Bug: 309512879
Test: m .

Change-Id: I5fd1a60dae87a57448e8f10c7fcbbf6cc79928cd

Bug: 301661850
Test: mma -j32
Change-Id: I496d968e4be5ef26f102d153e4fb11cc66b18e94

Bug: 301661850
Test: mma packages/modules/Bluetooth
Change-Id: I4ac1f56a997570ce138b4ee96837bc7a4702aa88

This reverts commit 9402f317.

Reason for revert: Build failure b/308624962

Change-Id: I3ac63565c9b2d8545b0154272f7276673d2e454e

Bug: 301661850
Test: mma -j32
Change-Id: I9e17bf1e6ad940213d611e5d91338c76f30d6f3f

Bug: 301661850
Test: mma packages/modules/Bluetooth
Change-Id: I55c60f4a91ae0a2ca1cda2045b48d960af756b90

Bug: 301661850
Test: mma packages/modules/Bluetooth

Change-Id: I5ed6c1ef897432277e995646f88a71ba2c1fb6b3

base::Bind and base::Callback are deprecated. Migrate the usages to
proper replacements.

The callback of LeRand is expected to be called for receiving the
resulting random number. It's called only once so it should be a
base::OnceCallback.

Bug: 272116782
Test: m .
Change-Id: I8dc78f54aae455f089bc29ee814c3e0c0635ba9e

Bug: 188297862
Test: mma .

Change-Id: Ib31787fa393090d1d1dfa9bc163c1c027d5f0930

[Root Cause]
When there are too much EIR or ble adv.
the device info in inquiry db will be cleared.
And when upper layer connect the device, there is no clock offset info in inquiry db and it may connect fail.

[Solution]
Record clock offset in config, then get it from config.

Bug: 266249327
Test: bond, connect successfully

Change-Id: Ifd606c5c549e3c79ed51e5b79dcfe72b4e2fe027

Don't bond with not valid CSIS devices if device was presented as member
of group by using matching RSI.

This part extends SMP module and related with callback to SIRK for
verification of potential members.

Tag: #feature
Bug: 278514112
Test: atest bluetooth_csis_test
Change-Id: If67b829b8dd1e5e4d2a9de08df92cff45b5c27f9

This reverts commit 0fd84ef2.

Reason for revert: b/269397845

Bug: 269397845
Test: mma
Change-Id: I0bc217670292449e0eab113688a4555833ca4271

Bug: 281763015
Test: Manual

Change-Id: I320d7ed678028df3014c338a85504a4e231cd4ee

Currently when there is an ongoing background scanning like 10% or 25%,
CSIS active scannning would not take effect since the first scanning
come first. This makes finding coordinate members more difficult as the
scanning % is not enough.

This Patch checks if current scan is for CSIS then stops any ongoing
scanning and uses low latency scanning for finding coordinate members.
This increases paring speed and also decreases the failure that we
do not find coordinate members.

Bug: 273958309
Test: make sure we find csis member with 100% scanning
Change-Id: I4b469166690f20306fcdcb57d7ca4a311d5969bc

Thread hci status for remote name request back so SDP state machine may act upon it.  Subsequent CL will extend SDP state machine to condition upon hci_status.  bta_status should originate *at* the bta layer for upper layers.

Bug: 277388611
Test: Visual

Change-Id: I269660f451b7b70f70402c5e3291c7f4d90f87b1

The extern specifier in this case has no effect as the default
for functions is to have external linkage. However the extern
specifier affects code search ability to explore function
declarations and occurences as the prototype differs from
the declaration.

Test: mmm packages/modules/Bluetooth
Bug: 279964152
Change-Id: I4f2e680d49068a0f708c40373bbe865e110f7db1

Bug: 259118978
Test: bt_host_test_bta

Change-Id: I1cdb2669acf80135253b3efc2c25e889be17f167

Add API to configure device into Bredr limited discoverable mode.

Bug: 262485102
Test: Manually
Tag: #floss
Change-Id: I5408da1393df68289d26c47188f259878a840641

During system suspend, we need to use a separate set of LE scan window
and intervals that are specifically tuned for this purpose. In order to
do this only when suspended, we add |SetSystemSuspendState| to indicate
when we're entering and existing suspend.

We set the suspend state via |AllowWakeByHid| and remove the suspend
state via |RestoreFilterAcceptList|. Currently, we only restore LE hid
devices on resume to the accept list but we should also restore
non-direct gatt connections in the future.

Bug: 271159571
Tag: #floss
Test: Manual test, ChromeOS Autotest and unit tests
Change-Id: I3e67f06f7667dec69379468cc51b8405cf10de10

Currently, allow_wake_by_hid tries to configure set event filter to
allow all classic devices that are HID major class to attempt connection
and wake us from suspend. This is insufficient to keep us from being
woken by unbonded devices (which we don't want).

The refactor does the following:
* Gets a list of classic hid devices (where DevClass matches either
  keyboard or pointing device).
* Program event filter using BD_ADDR instead of Class of Device
  filtering. Only bonded devices will be able to reconnect until we
  clear the Event Filter on resume.

Bug: 269835025
Tag: #floss
Test: Manual suspend test + autotest
Change-Id: I392bd63a8ebe0e8b7d53524dd24777b599ca8e41

Bug: 259118978
Test: net_test_stack_sdp

Change-Id: I3c9da3800acda3e521fd80e5b858b4ef396df847

Bug: 263885771
Test: TreeHugger
Change-Id: I2dbbdacafb9ef760710b5b5ba83e23d8a18c2087

These headers are now in base/functional/.

Bug: 266161904
Tag: #floss
Test: ./floss/build/build-in-container.py and emerge floss

Change-Id: Iaac7673f7c61d55e2d1572c92799d670fef65e72

Bug: 267796404
Tag: #floss
Test: ./build.py
Change-Id: I13bf5b07899150045d60948c787ecd6b226da008

This is a synchronous API on BluetoothDevice rather than a
callback-based one on BluetoothGatt.

Test: compiles
Bug: 261093955
Change-Id: I3e008e84e1b2e19158984ecee963b9a63e74b8b1

As per BAP 1.0.1 and CAP 1.0 specs, LE Audio capable device shall/should
put Service data for some services into the Advertisement.
If these are detected, such devices should be treated as LE Audio
capable for bonding.

This is addition to existing mechanisms that was using just CoD field.

Bug: 246560805
Test: pair with dual mode capable devices
Merged-In: Icd6287fecbeadbc853e1ae4146937c85adea9104
Change-Id: Icd6287fecbeadbc853e1ae4146937c85adea9104

As per BAP 1.0.1 and CAP 1.0 specs, LE Audio capable device shall/should
put Service data for some services into the Advertisement.
If these are detected, such devices should be treated as LE Audio
capable for bonding.

This is addition to existing mechanisms that was using just CoD field.

Bug: 246560805
Test: pair with dual mode capable devices
Change-Id: Icd6287fecbeadbc853e1ae4146937c85adea9104

Snapshot as of e71c3481c888c5dcb56c15d6b8e85f658152ef82

Bug: 248126637
Test: atest BluetoothInstrumentationTests
Change-Id: I88151930690bfdb2ed7ab0cbf27fd9fb661e0db3

Bug: 254884279
Test: gd/cert/run
Tag: #refactor
BYPASS_LONG_LINES_REASON: Bluetooth likes 120 lines

Change-Id: I8f634f3597139ec759f4da89c12015dfb843916f

Differentiate between services disovered by SDP and LE GATT discovery.
Service avaliability differs between transports.

This patch is not making any functional changes, just making code
clearer.

Test: perform LE and Classic pairing to dual mode device
Bug: 248340112
Merged-In: I7be9d2c0549f8c33eff16b70d6f54dd1f08a71a0
Change-Id: I7be9d2c0549f8c33eff16b70d6f54dd1f08a71a0

Differentiate between services disovered by SDP and LE GATT discovery.
Service avaliability differs between transports.

This patch is not making any functional changes, just making code
clearer.

Test: perform LE and Classic pairing to dual mode device
Bug: 248340112
Change-Id: I7be9d2c0549f8c33eff16b70d6f54dd1f08a71a0

When performing CTKD, we know about it in SMP, but don't pass this
information to BTA and BTIF layer. In BTIF, we guessed wether CTKD
happens by checking if address returned from pairing is different than
one we requested pairing on. This assumes device is using RPA or Static
address over LE. This is incorrect - device can advertise using Public
address over LE, and still perform CTKD.

Bug: 246560805
Test: pair with device using Public transport over LE multiple times
     ensure device is paired and visible in settings.
Merged-In: Iacefcd0439d7fba1c1b1ab873f79c6aae9c73eb8
Change-Id: Iacefcd0439d7fba1c1b1ab873f79c6aae9c73eb8

The suspend implementation in Floss wants to mask away some events to
prevent spurious wakes. This change updates the btif api
|set_default_event_mask| to also accept bit masks that will be disabled
from the final event mask that is sent to the controller.

As part of this change, suspend will now stop calling |clear_event_mask|
during suspend and instead will just disable the Disconnect and Mode
change events only.

Bug: 231345733
Tag: #floss
Test: Manual test on ChromeOS.
Change-Id: I0105085c465666e5a8c0e7890c36072234fe05e2

Raw addresses for paired devices aren't only stored as public addresses.
Since we filter for LE HID attributes, provide both the RawAddress and
LE address type when we provide the list of devices that can wake the
system.

In order for LeAddressManager to re-arm connection, we need to add these
devices via |AcceptLeConnectionFrom| instead of
|AddDeviceToFilterAcceptList|.

Bug: 231345733
Tag: #floss
Test: Manual test on ChromeOS.
Change-Id: I8ae8bc0f71ed07260f5f1880ab6bb8f27ffff972

When performing CTKD, we know about it in SMP, but don't pass this
information to BTA and BTIF layer. In BTIF, we guessed wether CTKD
happens by checking if address returned from pairing is different than
one we requested pairing on. This assumes device is using RPA or Static
address over LE. This is incorrect - device can advertise using Public
address over LE, and still perform CTKD.

Bug: 246560805
Test: pair with device using Public transport over LE multiple times
     ensure device is paired and visible in settings.
Change-Id: Iacefcd0439d7fba1c1b1ab873f79c6aae9c73eb8

This can be used to tell the upper layers that connection fails,
therefore they can provide better feedback to the user. Additionally
floss will also use it for metrics.

Bug: 240782154
Tag: #floss
Test: Verify btadapter print warn "Connection to <address> failed"
      when connection failed.
Change-Id: Id2ec0d71bf5392fdc8314349296d71a6af1e76ba