90dcc56c1357f2f0b2fa03638033455d89a8a758 |
|
20-Mar-2015 |
Nitin Arora <niarora@codeaurora.org> |
Disconnect Gatt during failure of service changed discovery process Gatt service changed discovery holds link till it completes discovery of service, characteristics, descriptots and writing notification for characteristic descriptor, this change takes care of removing the link if service discovery fails during any stage of this process. Bug: 21896912 Change-Id: Ie97a039568fedc66403895e7e917e4d72a5419e1
/system/bt/stack/gatt/gatt_attr.c
|
1e1761c19c0bf5420cabfdacf1994add2b0527cb |
|
20-Mar-2015 |
Nitin Arora <niarora@codeaurora.org> |
Rectify allocation of GATT control block This change ensures that a valid value is returned while requesting available control block or allocating memory for a new control block for saving GATT discovery handles. The bug if not fixed causes memory corruption and thus modifying some callback handles. Change-Id: I148ee82d2ea9fe77bebd34fd345b4fb6a6eee3cd
/system/bt/stack/gatt/gatt_attr.c
|
adc9f28ad418356cb81640059b59eee4d862e6b4 |
|
06-Dec-2014 |
Chaojing Sun <cjsun@broadcom.com> |
LE: Register for service change indication Some bonded remote devices require the client to register for service change indication and actually set the client configuration descriptor before service change indications can be removed. This change add an additional step after device bonding has occured to register for service change indication if possible. Bug: 18173911 Change-Id: I25386faec0d58834ee2b0a9d1db2d2e052311264
/system/bt/stack/gatt/gatt_attr.c
|
4dcde90649cc51ca815a50d338a73adb408ab258 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of b44cc59d to master Change-Id: I74c86dd5a13d4cc0b225a4b1d516904c4382db74
|
17b04bd498405f2bb109a85562ebbdcb6bb06e95 |
|
28-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add notification sent and congestion callbacks (2/4) This change introduces two new callbacks for applications to better handle LE notification flow control and transport congestion. The notification callback is invoked when the remote platform confirms an indication or when a local notification has been passed to the controller. No new notifications should be sent until a callback is received. Congestion callbacks are triggered when a GATT operation cannot be sent to the local Bluetooth controller. Repeatedly calling writeCharacteristic() for example will eventually trigger a congestion callback. Applications cannot send additional data until a further callback is received, indicating that the congestion has cleared up. Also fixes a memory leak issue that can trigger GKI exception for certain GATT operations. Change-Id: Ib470c15ca1f577573a632e9afe4cb9e86680fd8c
/system/bt/stack/gatt/gatt_attr.c
|
b44cc59d286ad255e872c60df02e032bd8d9d75b |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: AVRC, MCA, GATT, and SMP. Change-Id: I6d1e61ff023b5fd19f144955cff16831cc18c6e6
/system/bt/stack/gatt/gatt_attr.c
|
7fa4fba6f59f97df00aff07dbe8fb21b114b3c2c |
|
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features The features include: - LE Peripheral Mode - Link Layer topology (LE Central & Peripheral Concurrency) - Dual Mode Topology (Ability to choose LE transport when connecting with other Dual Mode devices) - Fast advertising Interval - Limited Discovery Time Changes - GAP Authentication and Lost Bond - Dual Mode Addressing - Common Profile and Service Error Code - 32 bit UUIDs Change-Id: Ic6701da4cf6aaa390ff2c8816b43157f36b7fb42 Conflicts: stack/btu/btu_hcif.c
/system/bt/stack/gatt/gatt_attr.c
|
8fe58875ce67c6e1099e7ba2339dcd2b979491b0 |
|
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features The features include: - LE Peripheral Mode - Link Layer topology (LE Central & Peripheral Concurrency) - Dual Mode Topology (Ability to choose LE transport when connecting with other Dual Mode devices) - Fast advertising Interval - Limited Discovery Time Changes - GAP Authentication and Lost Bond - Dual Mode Addressing - Common Profile and Service Error Code - 32 bit UUIDs Change-Id: Ic6701da4cf6aaa390ff2c8816b43157f36b7fb42
/system/bt/stack/gatt/gatt_attr.c
|
5cd8bff2dd0337cb52bf48f312e3d2d55a8882fb |
|
01-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Major warnings cleanup Mostly fixing unused parameter warnings. A few other warnings also fixed like possible use of unitialized variables (no real issue found, just compiler couldn't follow the path), signed vs unsigned warning. Also fixed some typos, indent issues, removal of dead code, etc. Change-Id: I95eb887aefc4d559d7921f71a0af5f3bfb01ac01 Signed-off-by: Mike J. Chen <mjchen@google.com>
/system/bt/stack/gatt/gatt_attr.c
|
7051db3a486aae771d9b5a81c3546790f86ede34 |
|
13-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
BLE HID device connection failure due to security error. When HID BLE device start encryption, if some other GATT application already start encryption(but not finished yet) by calling gatt_security_check_start. The HID BLE device will be failed to start encryption, which will cause it to disconnect the BLE HID connection. The solution is to check whether we already started the encryption , If the encryption is already started, wait until the encryption finished, then continue to start security check for BLE HID device. add encrytion complete event to notify all GATT client encryption done. filter the event just for BTA HH LE GATT client. bug:11636246 Change-Id: If58e57c623cc8cfa05208587b010bec68c71306c
/system/bt/stack/gatt/gatt_attr.c
|
ead3cde4bac0c3e32cd31f149093f004eef8ceeb |
|
06-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Initial version of BLE support for Bluedroid Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
/system/bt/stack/gatt/gatt_attr.c
|
5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/system/bt/stack/gatt/gatt_attr.c
|