system-bt

Fork

Incremented buffer size to accomodate default MTU

L2CAP Config request was not sent from Bluedroid as the MTU size was
higher than the max buffer size for default apdu tx/rx sizes.
Incremented the buffer size to accomodate this default MTU size. Also
included new datatypes and corresponding tx/rx apdus. This will set the
MTU size to that defined in datatype config rather than selecting
default value.
b/10565872
Change-Id: Id469c836581fb3d020bcb88c381421e0ef965073

am 247c68fe: Add support for AbsoluteVolume

* commit '247c68fe6eee3660cbdcf4509195fe735ae25573':
Add support for AbsoluteVolume

Add support for AbsoluteVolume

Add support for AbsoluteVolume in BTIF
bug 9595622

Change-Id: I11b707f6ab50d31bd11e879b0ebe5ad5bac54ad9

Conflicts:
btif/src/btif_rc.c

am 607e3b79: Place handling of BTA_DM_DISC_BLE_RES_EVT in BLE feature ifdef

* commit '607e3b79f1731de0d08a2c03d38ae17874bc282d':
Place handling of BTA_DM_DISC_BLE_RES_EVT in BLE feature ifdef

Place handling of BTA_DM_DISC_BLE_RES_EVT in BLE feature ifdef

Without this fix, bluetooth fail to compile for non-BLE platform

Change-Id: Ida10c54ab841e0a2bcaeb389a9813dd846db8200

am cb21f043: Merge "LE: Add support for the HID-over-GATT profile (1/3)" into klp-dev

* commit 'cb21f0434223a51d94eb4c6b5b62f77f9efa0a83':
LE: Add support for the HID-over-GATT profile (1/3)

Merge "LE: Add support for the HID-over-GATT profile (1/3)" into klp-dev

LE: Add support for the HID-over-GATT profile (1/3)

bug:8330048
Change-Id: I5727161b0a87700487bee96cdffa8fd169034204

am 98497a52: Add support for ff/rew

* commit '98497a520010fc996a8ce490665cac6c1439dd2d':
Add support for ff/rew

Add support for ff/rew

Change-Id: I017a7ddc9f7255d84ad8bf3284fefc1b7040900f
(cherry picked from commit 342bdf540d8c183d14ec5fb436b73cd979df3a8f)

am 33a5e99f: Merge "bluedroid: Fix build with gcc 4.8"

* commit '33a5e99f9216f9aac3c46373139f7be3bb903f49':
bluedroid: Fix build with gcc 4.8

Merge "bluedroid: Fix build with gcc 4.8"

Merge "LE: Add peripheral role support (2/4)" into klp-dev

LE: Add peripheral role support (2/4)

Initial stack support for the LE peripheral role.

Change-Id: I261d751b43b7020760bff345b472b6f60caa60be

Merge "LE: Do not generate an error if a device is already whitelisted" into klp-dev

Merge "LE: Fix for back-to-back GATT connection request issues" into klp-dev

Merge "LE: Memory leak when caching GATT service change" into klp-dev

Merge "LE: Check encryption state before starting encryption" into klp-dev

Merge "LE: Add instance ID to descriptors (2/4)" into klp-dev

LE: Do not generate an error if a device is already whitelisted

If a device is added to the whitelist that is already listed, no error
should be generated.

Change-Id: I81ad47eec47157d5ab2b5b25db3ed15bf873794e

LE: Fix for back-to-back GATT connection request issues

When two GATT client connections were sent back to back, the first
connection will not be processed due to an address comparison error.
This patch corrects the error.

Change-Id: I8eb97cd2a34a81da460f448dc71445b2898a5d32

LE: Memory leak when caching GATT service change

When a GATT connection is disconnected, a bonded device will be added
into service change pending list. But if the device is already in the
list, a duplicate record will be added and one buffer is lost.

This change ensures that devices are only added if they are not already
in the list.

Change-Id: Ied6872b145ed28bde8044444cb6c9cbee525943d

LE: Check encryption state before starting encryption

Previously, the btif layer kept track of when a link was encrypted using
an internal list to track encryptino callbacks. This change switches to
querying the stack for the actual encryption state, since the btif layer
may not receive all encryption related callbacks.

Bug: BLTH02382147
Change-Id: I426b87d77e9a18531c2d42733a7e736a73bb116f

Move bta_dm_remove_sec_dev_entry declaration out of BLE ifdef

The method applies to non-BLE cases.

Change-Id: I57508d09015e4ec4a74edf2d1fbc607fd692b402

LE: Add instance ID to descriptors (2/4)

If a remote devices offers multiple descriptors with the same UUID, the
instance ID is used to differentiate between them.

Change-Id: I1f3c284d714719fe9fb9cbb297c70a061c62a96d

LE: UPF 45 bug fixes

This change fixes the following issues:
- Second GATT-over-BR/EDR channel cannot be established when there
already is an existing GATT-over-BR/EDR channel
- If encryption fails for an LE connection due to a missing key,
the security state is not being cleared and blocks all further
security processing
- When DM discovery of an LE Peripheral device fails with a
connection timeout, no further discovery requests can be made
- GATT service discovery can get into endless loop when duplicate descriptor
definitions are found on the remote device
- When GATT over BR/EDR fails, BTA does not give a connection
callback to the application initiating the connection
- BR/EDR connection to remote platform does not generate API callbacks
- Stack crash discovered during UPF after remote disconnects
- The host is sending HCI disconnect to invalid HCI handle when
SMP fails because of a connection timeout
- Possible race condition:
If a disconnect is immediately followed by a connection complete,
the connection complete cannot be processed in the BTA GATT state
machine
- Write Complete event is not triggered for Prepare Write requests

Change-Id: I539cdedd68007818ff4f0d0213cee1c913f72d0f

Conflicts:
bta/gatt/bta_gatts_act.c

LE: Add NULL check for GATT client callback

Change-Id: I1087102d8a740969fb0a98b409b58230a3236aeb

LE: Fix crash on LE mouse reconnect

Sometimes, a GKI exception may be observed when re-connecting to an LE
mouse. This patch properly handles the encryption state change, avoiding
a possible race condition leading to the exception.

Change-Id: I4cf139c1ac22e71b598272fccebf645cd73fdf6a

LE: Limit minimum MTU size

Check requested MTU sizes to ensure a minimum MTU size. Otherwise remote
devices may request an MTU that's too small, preventing any further
communication with the remote device.

Change-Id: I3ba97cf6e6c464825778a8c8902f99f6662c3762

LE: Send correct device name during SMP pairing

During SMP pairing the device name is not properly copied to the upper
Java layers, causing a potentially wrong device name to be displayed to
the user.

Change-Id: Iab43871defc7df52b0cd9c64f52208879abb50f2