Prasad Alatkar

@rymanluk Apologies for not updating the PR for long time. I have incorporated your suggestions. Please take a look and suggest if any improvements. I am expecting few CI test...

@andrzej-kaczmarek @rymanluk Could you guys please take a look ?

@rymanluk Can you please take a look at the PR ?

> @prasad-alatkar looks like unit tests are failing. newt test @apache-mynewt-nimble/nimble/host/test could you check that? Also could you please add a patch to btshell which would allow to test this...

Hi @lucachapelle , according to BLE spec maximum length of attribute value can be 512 Bytes (Ref: version 5.0, Vol 3, Part F, Section 3.2.9). This maximum size is for...

@lucachapelle @bbinet Sorry I could not follow up on this issue because of some other commitments. There is an ongoing discussion about similar issue internally, I will look into the...

Hi @mitchjs Can you please provide complete logs from boot up for both INFO and DEBUG prints ? Is it possible for you to share Android side logs as well...

Yes, Error status = 26 translates to `BLE_ERR_UNSUPP_REM_FEATURE`: Unsupported Remote Feature / Unsupported LMP Feature. If not possible to share log from boot up, please share it from connection request....

From 'ESP32-NimBLE-log 2.text', the disconnect is happening because of TIMEOUT `Disconnection Complete: status=0 handle=0 reason=19`. After successfully sending command (`BLE_HCI_OCF_LE_RD_REM_FEAT`), it waits for ACK from peer for `BLE_HCI_CMD_TIMEOUT_MS` (2 seconds)....

Hi @h2zero @mitchjs the corresponding fix is already present in `esp-nimble` commit: c6fa32fc > Yes hang is it sits there long time... then it does the disconnect If it disconnects...