diff options
| author | Nitin Shivpure <nshivpur@codeaurora.org> | 2018-07-30 18:14:54 +0530 |
|---|---|---|
| committer | Myles Watson <mylesgw@google.com> | 2018-08-23 21:24:44 +0000 |
| commit | ef617c38469e82666362b0b0e9c23fc0ebda2f17 (patch) | |
| tree | 183ab7471d0d58f215b7b775e7529468cecd4b1e /system/common/message_loop_thread_unittest.cc | |
| parent | 73a19a852f9d108188f61bc1b156c9a761fbbb46 (diff) | |
L2CAP: Handle no idle timeout (0xFFFF)
Precondition:
1. DUT acts as GATT server.
2. Remote acts as Gatt Client
Use case:
1. Remote device starts BLE scan
2. Remote device connects to DUT
3. Remote device keeps on sending notifications to DUT
Expected result:
Connection should be active after 18 hours
Observed Result:
Connection is dropped after 18 hours due to l2c_link_timeout.
Root Cause:
L2CAP is not properly handling no idle timeout(0xFFFF) and 65535000 ms
timer gets started after BLE connection, leading to connection getting dropped
after 18 hours.
Fix:
If there is no L2CAP dynamic ccb and no idle timeout is configured for
GATT or any other fixed channel, then cancel existing LCB timer.
Test: No BLE disconnection seen after 18 hours
Bug: 112249120
Change-Id: I58766564cf62efb7af0869035115459bae37c558
Diffstat (limited to 'system/common/message_loop_thread_unittest.cc')
0 files changed, 0 insertions, 0 deletions