https://devzone.nordicsemi.com/f/nordic-q-a/58674/observing-stuck-thread-in-android-ble-library-while-registering-characteristicsHello, We are leveraging the Android BLE Library from Nordic available on GitHub (release v2.1.1). In a scenario where there are repeated requests to connect as a result of being on the edge of the link budget, we&#39;ve observed that the thread responsibleen-USTelligent Community 13Wed, 11 Mar 2020 11:43:17 GMThttps://devzone.nordicsemi.com/thread/239312?ContentTypeID=1Wed, 11 Mar 2020 11:43:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:617570c7-f80f-46af-b7cd-73ba69bc7d12Aleksander Nowakowski<p>Hello,</p> <p>All non-timeoutable requests are waiting for the system callback. In general a new request could not be performed when a previous one still didn&#39;t get a callback. But of course we know how it is.</p> <p>To cancel current task and all queued, call</p> <p>&nbsp;<pre class="ui-code" data-mode="java">cancelQueue()</pre></p> <p>in the manager. This will cancel the current one with REASON_CANCELLED. The state of the device is undefined at that moment, so you may need to disconnect and reconnect, etc. I have never tried this. Of course, as you&#39;re using synchronous calls, call this method from another thread, as that one is hanging.</p><div style="clear:both;"></div>