In test_btp_GAP_CONN_DCON_1, everything works until the tool set the Mynewt DUT in direct advertising and Android DUT tries to connect.
It seems that Mynewt successfully advertises, but there is a connection timeout when Android tries to read remote features. This timeout doesn't happen on the previous connection earlier in the test.
This could be an Android issue.
Android logs
11-29 17:30:20.552 8526 8526 D BluetoothGatt: connect() - device: D7:C7:4B:26:8C:21, auto: false
11-29 17:30:20.616 16240 16315 I bluetooth: packages/modules/Bluetooth/system/stack/gatt/connection_manager.cc:437 on_connection_complete: Le connection completed to device:d7:c7:4b:26:8c:21
11-29 17:30:20.709 16240 16315 E bt_btm_ble: packages/modules/Bluetooth/system/stack/btm/btm_ble_gap.cc:3222 btm_ble_read_remote_features_complete: Failed to read remote features status:Connection Timeout
Last Mynewt logs
01938 [DBG] find_btp_handler: opcode 21
001938 [DBG] start_direct_adv:
001938 [ts=15140616us, mod=4 level=1 ]GAP procedure initiated: advertise; disc_mode=0 direct_addr_type=1 direct_addr=74:3f:d7:36:24:2b adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=0 adv_itvl_max=0
Android HCI logs
449 299.234062 host controller HCI_CMD 6 Sent LE Read Remote Features
450 299.235054 controller host HCI_EVT 7 Rcvd Command Status (LE Read Remote Features)
Status: Pending (0x00)
455 299.370385 controller host HCI_EVT 15 Rcvd LE Meta (LE Read Remote Features Complete)
Status: Connection Timeout (0x08)
In test_btp_GAP_CONN_DCON_1, everything works until the tool set the Mynewt DUT in direct advertising and Android DUT tries to connect.
It seems that Mynewt successfully advertises, but there is a connection timeout when Android tries to read remote features. This timeout doesn't happen on the previous connection earlier in the test.
This could be an Android issue.
Android logs
Last Mynewt logs
Android HCI logs