Using nRF Connect (Windows) to connect to a peripheral using a bigger MTU.https://devzone.nordicsemi.com/f/nordic-q-a/38252/using-nrf-connect-windows-to-connect-to-a-peripheral-using-a-bigger-mtuI have a peripheral (nrf52832) which is using a higher MTU (140 bytes). When I connect to it using the nRF Connect Android app, everything works. I can see the BLE_GAP_EVT_PHY_UPDATE_REQUEST and BLE_GAP_EVT_PHY_UPDATE being handled on the peripheral afteren-USTelligent Community 13Fri, 07 Sep 2018 11:00:48 GMTRE: Using nRF Connect (Windows) to connect to a peripheral using a bigger MTU.https://devzone.nordicsemi.com/thread/147761?ContentTypeID=1Fri, 07 Sep 2018 11:00:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b8220980-3fb9-493a-be49-2217f3550e8cBj&#248;rn Kvaale<p>Hi,</p> <p>The problem lies with nrf connect for desktop. It is currently using the s132 v3.1 softdevice, whereas the phy update request functionality was implemented in a later softdevice (s132 v5). Could you please explain why you are referring to the phy update request when you want to use a higher MTU?</p><div style="clear:both;"></div>