<?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>BLE 5.0 Pairing Problem throughput test with Galaxy S8</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41644/ble-5-0-pairing-problem-throughput-test-with-galaxy-s8</link><description>Hello, I have a discovery issue that seemingly only happens with the Samsung Galaxy S8. 
 I want to throughput test BLE5.0(2Mbps). 
 I using the nRF52832(BMD-300) with SoftDevice S132 SDK 15.2.0, and programmed examples\ble_central_and_peripheral\experimental</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Dec 2018 14:15:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41644/ble-5-0-pairing-problem-throughput-test-with-galaxy-s8" /><item><title>RE: BLE 5.0 Pairing Problem throughput test with Galaxy S8</title><link>https://devzone.nordicsemi.com/thread/162105?ContentTypeID=1</link><pubDate>Mon, 17 Dec 2018 14:15:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7ba625d-c281-42cb-9bf9-7499228cd79b</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;This example is not really intended to connect to a phone. It is not a standard service, and the reason that you are probably not seeing any services is that the example works both as a central and a peripheral.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Try to use one of the other examples, e.g. the ble_app_uart. This is an example that will have the settings pretty optimized for throughput. You might want to change to PHY = 2Mbit, which you can request in the CONNECTED event in main.c.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you want to test the throughput,&amp;nbsp; you should continuously trigger ble_nus_data_send() in your main() function. You can call this again, as long as it returns NRF_SUCCESS. When it returns NRF_ERROR_RESOURCES, it means that the buffer is full, and you must wait for the TX_COMPLETE event before you will be able to queue new packets. Use this event to signal to the main() function that you can trigger new samples. Also, use large packets to reduce the overhead.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This is probably not very well explained, but there are a lot of questions with good answers about this on devzone. Search for &amp;quot;ble_app_uart throughput&amp;quot;, and you should find some relevant information. If not, let me know. You can start here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/28522/how-to-make-uart-throughput-match-that-of-att_mtu"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/28522/how-to-make-uart-throughput-match-that-of-att_mtu&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>