| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
When a client requests to update the LE transport MTU, the server
currently does not get notified and can therefor not properly size
notifications appropriate to the current MTU.
Bug: 18388114
Change-Id: I136f32cba48da3302e13fb9a9ec81b8e01712138
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Change-Id: I613cbf968770921f853a407888bb8308849039f3
|
|
|
|
|
|
|
| |
Support for passing preferred transport for GATT connections as part of
Connect APIs
Change-Id: I83ba256574234c0a15a4bff48bcffa2e237c9393
|
|
|
|
|
| |
Bug: 8589393
Change-Id: I1c9d83b988cad71c5652ecf4025fdc6f650fff42
|
|
Change-Id: Iacf3a56943b31c4fd4f4b833ed675a35cbd47104
|