From b69edd55ffe953d4f71f4a948e3feb2243223980 Mon Sep 17 00:00:00 2001 From: Jakub Pawlowski Date: Wed, 24 May 2017 16:15:21 -0700 Subject: [PATCH] Fix GATT Server disconnecting for no reason When two devices are bonded, even if the device is supposed to act just as a GATT Server, service discovery is performed. Doing "read by type" should not trigger connection timeout, or disconnection, as the server should wait for the client to finish connection. Please note that it does not GATT Client behaviour, as they manage the connection timeout through L2CA_SendFixedChnlData called on each data packet. Bug: 34951749 Test: manual Change-Id: If53cf63dc204238a60839497992c870b1b39aa60 --- stack/gap/gap_ble.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/stack/gap/gap_ble.cc b/stack/gap/gap_ble.cc index 6e42ad538..d990d1ae6 100644 --- a/stack/gap/gap_ble.cc +++ b/stack/gap/gap_ble.cc @@ -548,7 +548,6 @@ void gap_ble_cl_op_cmpl(tGAP_CLCB* p_clcb, bool status, uint16_t len, /* if no further activity is requested in callback, drop the link */ if (p_clcb->connected) { if (!gap_ble_send_cl_read_request(p_clcb)) { - GATT_Disconnect(p_clcb->conn_id); gap_ble_dealloc_clcb(p_clcb); } } -- 2.11.0