<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Galaxy S5 can&amp;#39;t scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46737/galaxy-s5-can-t-scan-bluetooth-devices</link><description>Hi, 
 
 SDK15.2 
 Softdevice: S132 6.1.0 Device: NRF52832 
 Mobile phone:Galaxy S5 (Android 6.0.1) 
 I have a problem with the Galaxy S5 can&amp;#39;t scan Bluetooth devices. During the test, I found that when the device name is 3 or 4 characters, S5 cannot scan</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 30 Apr 2019 07:44:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46737/galaxy-s5-can-t-scan-bluetooth-devices" /><item><title>RE: Galaxy S5 can't scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/thread/184454?ContentTypeID=1</link><pubDate>Tue, 30 Apr 2019 07:44:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54f2509b-cf90-44e8-967a-4251597fa393</guid><dc:creator>kxct</dc:creator><description>&lt;p&gt;S5 can normally parse the UUID of the broadcast packet.Thanks for your support&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy S5 can't scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/thread/184450?ContentTypeID=1</link><pubDate>Tue, 30 Apr 2019 07:37:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a267a36-9389-49e5-b093-0ab46b9a81b7</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Interesting to see that putting the name into the scan response packet fixed the issue. It should not be any risk to do this, but it depends on what&amp;nbsp;criteria the central connects on, since you now moved the UUID to the normal advertising packet. Is the UUID&amp;nbsp;in the advertising packet parsed&amp;nbsp;correctly by the S5 phone?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy S5 can't scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/thread/184411?ContentTypeID=1</link><pubDate>Tue, 30 Apr 2019 01:15:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e73b02b-42fd-4e07-9ab0-204ff07139b2</guid><dc:creator>kxct</dc:creator><description>&lt;p&gt;Sigurd,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;Modify the code of the initialization part of the Advertising data, the problem is solved.&lt;br /&gt;What is the risk of doing this?&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp;I only know some basic Bluetooth specifications, not very clear about the specific details.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;//    init.advdata.name_type          = BLE_ADVDATA_FULL_NAME;
//    init.advdata.include_appearance = false;
//    init.advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE;

//    init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
//    init.srdata.uuids_complete.p_uuids  = m_adv_uuids;

    init.srdata.name_type          = BLE_ADVDATA_FULL_NAME;
    init.advdata.include_appearance = false;
    init.advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE;

    init.advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    init.advdata.uuids_complete.p_uuids  = m_adv_uuids;&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy S5 can't scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/thread/184408?ContentTypeID=1</link><pubDate>Tue, 30 Apr 2019 00:09:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c68a08f7-8c20-463d-ac02-065feb740918</guid><dc:creator>kxct</dc:creator><description>&lt;p&gt;I will update the firmware of my mobile device before I try.&lt;/p&gt;
&lt;p&gt;thank you for your reply&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy S5 can't scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/thread/184380?ContentTypeID=1</link><pubDate>Mon, 29 Apr 2019 15:23:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d3c0ed3e-03e8-465c-9322-49ebdbcdd012</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The only thing that is different, is that we starting from SDK 14 are using channel select algorithm(CSA #2). This is a mandatory feature in Bluetooth version 5, and can not be disabled. In the Advertising channel PDU Header, shown in the picture below, this is one bit that is changed from 0 to 1. This was added starting from S132 v.5(SDK14). It seems that the phone does not handle this small change, and is therefore not able to parse the data correctly. This is then be a bug with phone, and unfortunately nothing we at Nordic can do anything about.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Advertising channel PDU Header in Bluetooth 5.0:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img alt=" " height="149" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/8764.pastedimage1528472025244v1.png" width="335" /&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy S5 can't scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/thread/184300?ContentTypeID=1</link><pubDate>Mon, 29 Apr 2019 12:13:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2915942c-03ed-4de9-8416-48667e6f0a76</guid><dc:creator>kxct</dc:creator><description>&lt;p&gt;&amp;nbsp;Modify the example ble_app_uart (SDK12.3) device name is &amp;quot;1234&amp;quot;, S5 can scan to the device normally.&lt;br /&gt;SDK14.2 and SDK15.2 are not normal&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy S5 can't scan Bluetooth devices</title><link>https://devzone.nordicsemi.com/thread/184208?ContentTypeID=1</link><pubDate>Mon, 29 Apr 2019 06:47:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a35a15c0-da2c-4be4-95dd-1e9ecf1efd63</guid><dc:creator>kxct</dc:creator><description>&lt;p&gt;The Galaxy S10 can scan Bluetooth devices normally.&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/WeChat-Image_5F00_20190429144652.jpg" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>