https://devzone.nordicsemi.com/f/nordic-q-a/4663/bond-connection-questionsHi, Some questions in example ble_app_hids_keyboard/main.c Why set the adv_params.timeout to zero in BLE_DIRECT_ADV (Line 779) ? That will cause no BLE_GAP_EVT_TIMEOUT event come, right? If no BLE_GAP_EVT_TIMEOUT event come, whichen-USTelligent Community 13Thu, 11 Dec 2014 13:04:10 GMThttps://devzone.nordicsemi.com/thread/16553?ContentTypeID=1Thu, 11 Dec 2014 13:04:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:eb15ffd9-fa5c-4b55-bdca-aaea4d769a37Petter Myhre<p>It is a bit confusing. In the <code>BLE_DIRECTED_ADV</code> state the device will be put in &quot;Directed Connectable Mode&quot; (see <a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/0676.Core_5F00_v4.1.pdf">Bluetooth Core Specification 4.1</a>, Volume 3, Part C, Section 9.3.3.</p> <p>Last sentence: &quot;The Host shall configure the Controller to send directed connectable advertising events.&quot;</p> <p>In Volume 6, Part B, Section 4.4.2 (Table 4.1) you can see that ADV_DIRECT_IND should be used for connectable directed events.</p> <p>The connectable directed event type is explained in Volume 6, Part B, Section 4.4.2.4. The SoftDevice uses &quot;High Duty Cycle Directed Advertising&quot;. This shall not last more than 1.28 seconds.</p> <p>This 1.28 seconds limit is enforced by the SoftDevice, it seems it just ignores the set timeout value.</p> <p>So, after 1.28 seconds you will get <code>BLE_GAP_EVT_TIMEOUT</code>, <code>m_direct_adv_cnt</code> will be decreased and so on.</p> <p>Regarding your issue with iOS8 and Android, could you add this as a new question? Please try to provide some more information. <a href="https://devzone.nordicsemi.com/blogs/7/how-should-i-ask-my-question/">This</a> may be helpful.</p><div style="clear:both;"></div>