https://devzone.nordicsemi.com/f/nordic-q-a/127664/l2cap-socket-fail-to-open-if-pairing-bonding-is-enabledEnvironment - MCU : nRF52832 (custom board) - SDK : nRF Connect SDK v3.2.2 Problem Summary Our nRF52832 firmware implements OTS (Object Transfer Service) with L2CAP for file transfer. The L2CAP server registers successfully and exposes its PSM viaen-USTelligent Community 13Tue, 07 Apr 2026 16:52:40 GMThttps://devzone.nordicsemi.com/thread/564552?ContentTypeID=1Tue, 07 Apr 2026 16:52:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:23bf23c3-9b45-4fcc-b33a-2f377aa91749Allan P<p><span>Thanks for the reply, I just got it working.</span><br /><span>In fact, Android was expecting level 3 with MITM.</span><br /><br /><span>The bug was, in fact, a communication issue between teams.&nbsp;</span> </p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/564535?ContentTypeID=1Tue, 07 Apr 2026 13:23:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8bdf9bec-e880-4162-97a2-bf7bf98b7881Einar Thorsrud<p>Hi,</p> <p>It seems like the problem is on the Android side, and that is where the focus should be. I am not an Android developer, but have some questions:</p> <ol> <li>It would be interesting to know if the app implementation is calling&nbsp;Are they calling createL2capChannel(37) or createInsecureL2capChannel(37)?</li> <li>Do you see this on all Android devices and Android versions or just some specific? If only some, which have tested and which fail?</li> <li>Which exception or error do you get from the socket creation or call to connect()?</li> </ol><div style="clear:both;"></div>