Scan response data and Advertising data, making difference on HRM iOS Apphttps://devzone.nordicsemi.com/f/nordic-q-a/13547/scan-response-data-and-advertising-data-making-difference-on-hrm-ios-appHaving too much fun with iOS Apps :-D I am using heart rate example from SDK11. Firmware example and HRM in nRF Toolbox worked well. Then I moved advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]); advdata.uuids_completeen-USTelligent Community 13Mon, 02 May 2016 11:38:43 GMTRE: Scan response data and Advertising data, making difference on HRM iOS Apphttps://devzone.nordicsemi.com/thread/51684?ContentTypeID=1Mon, 02 May 2016 11:38:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4bee71d6-6d23-4ee2-8a43-d3b4d4a63d26run_ar<p>Actually I don&#39;t think the app can decide if iOS should do active scanning or not. My understanding is that this is handled by coreBluetooth, but that iOS will in general do active scanning when the app is in the foreground, while it switches to passive scanning in background mode. I would also expect it to switch to passive scanning if scanning for a long time in foreground mode as well, but I don&#39;t know if this is the case.</p><div style="clear:both;"></div>RE: Scan response data and Advertising data, making difference on HRM iOS Apphttps://devzone.nordicsemi.com/thread/51683?ContentTypeID=1Thu, 28 Apr 2016 21:26:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e0e7c5b4-d4d0-43f1-8b15-e46ef3205e08Paul<p>LOL. That&#39;s what I thought happened.</p><div style="clear:both;"></div>RE: Scan response data and Advertising data, making difference on HRM iOS Apphttps://devzone.nordicsemi.com/thread/51682?ContentTypeID=1Thu, 28 Apr 2016 18:08:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b92afc57-5e37-42f7-a5b3-41a51219a1ebRichieJH<p>Yes, I posted that answer but then read your question again and saw you were talking about the HRM module in the nRF ToolBox which is specifically looking for an HRM device and if it doesn&#39;t see one advertised it takes no action. So I deleted it :) But the real answer is that it is fine for you to have the UUID in scan response providing your master always does a scan request when they see your original advertisement (whatever that may be) to unveil the HRM UUID. It&#39;s just that it appears nRF Toolbox is not doing that.</p><div style="clear:both;"></div>RE: Scan response data and Advertising data, making difference on HRM iOS Apphttps://devzone.nordicsemi.com/thread/51681?ContentTypeID=1Thu, 28 Apr 2016 16:17:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:267d5b27-854a-4c56-8bc8-f8ca478d9ab2Paul<p>I saw RichieJH posted an answer about UART example is using scan response data only to pass the 128 bit UUID. Yes, I tried that example. And UART App is able to find it. But I think UART App and HRM App are using different way to search devices. HRM App is looking for the service 0x180D. But UART is looking for everything and probably sending scan response data request to every device that is advertising.</p> <hr /> <p>PS. I don&#39;t know why his answer is now showing up here, weird. (I got notification in my email, also his answer listed in my devzone inbox)</p><div style="clear:both;"></div>