MTU negotiation event diffs between IOS and Android

MTU negotiation event diffs between IOS and Androidhttps://devzone.nordicsemi.com/f/nordic-q-a/59733/mtu-negotiation-event-diffs-between-ios-and-androidDear Nordic: My peripheral is configured to use MTU 247. When connected by NrfConnect of IOS, I can receive NRF_BLE_GATT_EVT_ATT_MTU_UPDATED event and check the effecitve mtu. But with NrfConnect Android, I receive NRF_BLE_GATT_EVT_DATA_LENGTH_UPDATEDen-USTelligent Community 13Tue, 31 Mar 2020 12:52:51 GMTRE: MTU negotiation event diffs between IOS and Androidhttps://devzone.nordicsemi.com/thread/242701?ContentTypeID=1Tue, 31 Mar 2020 12:52:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:113b93fc-6237-463b-b146-7bcd3f357982Simonr<p>Hi</p> <p>This is likely just a difference between the Android and IOS stacks. I suggest setting NRF_SDH_BLE_GAP_DATA_LENGTH to 251 in the sdk_config.h header file as well as the MTU update to maximize data throughput.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>