Connections to Moto E4 fail with 0x3d Connection Terminated Due To MIC Failurehttps://devzone.nordicsemi.com/f/nordic-q-a/26287/connections-to-moto-e4-fail-with-0x3d-connection-terminated-due-to-mic-failureI&#39;m working on porting our connectivity application from SDK11/SD132v2.0.0 to SDK14/SD132v5.0.0. Currently, though most Android phones I&#39;ve tried can connect, the Moto E4 exhibits strange behavior on only the SDK14 version, where it will connect anden-USTelligent Community 13Thu, 26 Oct 2017 20:50:22 GMTRE: Connections to Moto E4 fail with 0x3d Connection Terminated Due To MIC Failurehttps://devzone.nordicsemi.com/thread/103470?ContentTypeID=1Thu, 26 Oct 2017 20:50:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:07a55386-5f2e-483d-8f2b-fcf5fbf2414aSeth Foster<p>I ended up fixing this in a fairly unexpected way.</p> <p>The fix ended up being delay connection parameter negotiation until after attribute discovery by setting the connection parameter module&#39;s <code>start_on_notify_cccd_handle</code> to a handle that is always set to notify after connection.</p> <p>I still don&#39;t know for sure why starting conn param negotiation immediately after a connection was established broke things on the moto e4, but I suspect its LE controller really wanted to go through its feature discovery and enumeration sequence unbothered. Either way, the problem is solved.</p><div style="clear:both;"></div>