<?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 Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91964/ble-connection-dropping-immediately-on-samsung-s20-plus-phone</link><description>Hello, 
 Our production device is having issues with the BLE connection only identified with the Samsung S20+ model currently. We are using custom services for our phone App to communicate with our device. What is happening is that the connection is dropped</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 27 Sep 2022 16:51:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91964/ble-connection-dropping-immediately-on-samsung-s20-plus-phone" /><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/388210?ContentTypeID=1</link><pubDate>Tue, 27 Sep 2022 16:51:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c5c5ecf4-2d12-42db-afb7-9a934a6cd525</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m afraid I can&amp;#39;t spend any more time on this issue. One thing I saw was that in the example you provided there were other update calls occurring in the same connected callback. I&amp;#39;m not sure this matters, but I was only executing the MTU exchange request upon being connected, then waiting for that to complete. In any case, I think there is some wierd stack behavior going on here, but we got around it for now and need to move on.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks and regards,&lt;/p&gt;
&lt;p&gt;Pam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/388100?ContentTypeID=1</link><pubDate>Tue, 27 Sep 2022 10:57:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1cf6bf7-8ff0-4dc7-aec2-780a61ce4a77</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pam,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It can be difficult to debug without a way to print out log.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you test with the default peripheral_uart sample , do you get the RTT log ?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;I have made a very similar sample with peripheral_uart (which I assume you based your application on) that also request MTU exchange when in connected callback , very&amp;nbsp;close to what you have done in your application. Could you try to test with my sample ?&amp;nbsp; you can download it here at the end of section 2.2 :&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/building-a-bluetooth-application-on-nrf-connect-sdk-part-3-optimizing-the-connection"&gt;Building a Bluetooth application on nRF Connect SDK - Part 3 Optimizing the connection&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387994?ContentTypeID=1</link><pubDate>Mon, 26 Sep 2022 17:58:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:540144a4-2666-4b12-a746-14ded5f22865</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;It&amp;#39;s tricky to get logs because we are using the nRF52832 and there is only one UART, which is being used elsewhere in our application. Basically I was never even to get the RTT terminal output to work consistently, so I didn&amp;#39;t even consider adding the log complexity.&lt;/p&gt;
&lt;p&gt;I was able to repeat what I think is the same problem using the standard &amp;quot;peripheral_uart&amp;quot; sample application with a few changes. I added the following define to the prj.conf file:&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BT_GATT_CLIENT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;span&gt;This is to allow for the call to &amp;quot;&lt;/span&gt;&lt;/span&gt;bt_gatt_exchange_mtu&amp;quot; which our application needs to force the usage of the larger MTU. The issue occurs when this call is done immediately from the connection callback. If I actually call a parameter update first from the connection callback, then wait to call the MTU exchange update from the parameter update callback, there is no issue.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Attached is the updated main.c file I modified from the peripheral_update sample application.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/4478.main.c"&gt;devzone.nordicsemi.com/.../4478.main.c&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Hopefully this will help find the issue, which I also believe is something in the stack. For now we have a workaround, and have only seen the problem on the Samsung S20+ and Samsung S10+ phones.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Regards,&lt;/div&gt;
&lt;div&gt;Pam&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387819?ContentTypeID=1</link><pubDate>Mon, 26 Sep 2022 08:01:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d5e6766e-bcee-4b6c-9249-8f345f90c194</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pamela,&amp;nbsp;&lt;br /&gt;It&amp;#39;s good that you managed to get the sniffer working.&amp;nbsp;&lt;br /&gt;Our team is looking at a solution to make it work on DK v3.0.0&lt;/p&gt;
&lt;p&gt;Regarding the issue you are having with Samsung S20+. From what I can see is that the MTU exchange was performed without any problem. The&amp;nbsp;nRF52 requested and got the response.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;However what I see is that the slave (nRF52) stopped responding after packet #7852. The master retried after that until timeout happened:&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:113px;max-width:670px;" height="113" src="https://devzone.nordicsemi.com/resized-image/__size/1340x226/__key/communityserver-discussions-components-files/4/pastedimage1664178923011v1.png" width="670" alt=" " /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s hard to tell what happened without any log from the nRF52. Could you check if there is any log on the nRF52 ?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;It could be the issue either with the application or it could be the BLE stack that crashed.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;It&amp;#39;s why I was asking if you observe the same issue on the stock example in the SDK. Could you please try to reproduce the issue on one of the example ? If it doesn&amp;#39;t happen you may want to add what you added to your application for example MTU exchange.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;I have a Galaxy S10 and a Galaxy S22 here that can be used for testing. If you can provide any example to reproduce the issue it would be great.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387781?ContentTypeID=1</link><pubDate>Sun, 25 Sep 2022 22:52:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f5251d8f-a8e5-478c-9eb7-3ffff302be2e</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/SamsungConnectionDrop.pcapng"&gt;devzone.nordicsemi.com/.../SamsungConnectionDrop.pcapng&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387780?ContentTypeID=1</link><pubDate>Sun, 25 Sep 2022 22:51:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:082cc27b-5991-40e1-baf2-cd22485e3203</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;Actually maybe it would be best to have you guys look into the original issue of this case, which is certain Samsung phones dropping the BLE connection immediately after the MTU exchange occurs with our device using a nRF52832. I now do have a trace of the connection drop and it would be helpful to have some input on what was captured, the connection starts on item # 7840 of the capture. I&amp;#39;m having a hard time trying to figure out how to upload this file, so let me know if you can&amp;#39;t find it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks and regards,&lt;/p&gt;
&lt;p&gt;Pam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387772?ContentTypeID=1</link><pubDate>Sun, 25 Sep 2022 16:50:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5974c356-3530-447c-bc54-1c963e09c271</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;I finally got the sniffer working properly with the older nRF52-DK board. The issue was the JLink driver needed to be updated. So after checking the version and updating the JLink driver via the Segger Configurator tool, I was then able to follow the traffic for a specific device properly.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;You should definitely get the dev team to follow up on the 3.0.0 version boards not working correctly with the sniffer, my local apps engineer experienced the same issue. At this point however you can close this specific case.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks and regards,&lt;/p&gt;
&lt;p&gt;Pam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387619?ContentTypeID=1</link><pubDate>Fri, 23 Sep 2022 07:47:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e5e48ced-7816-4772-a35d-326aa572175c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pamela,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The firmware&amp;nbsp;&lt;span&gt;OB-nRF5340-NordicSemiV1.00 is actually correct. It&amp;#39;s because on v3.0.0 we use a nRF5340 as the interface chip instead of using the Jlink chip. So the target device is still nRF52 but the programmer/debugger is a nRF53.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;However, I did a test with a v3.0.0 board like your and got the same issue. Wireshark couldn&amp;#39;t detect the board. I suspect there is a compatibility issue between the extcap library we have and the new board. I will report this to the team to find a solution.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In the mean time, please try the suggestion from &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/83385/nrf-sniffer-does-not-show-connection-packets/346673"&gt;this ticket.&lt;/a&gt;&amp;nbsp; for the old board. Could you let me know the version of your board ? I remembered&amp;nbsp;the I experienced&amp;nbsp;the same issue a long time ago but haven&amp;#39;t seen that in the last few years.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Also you can try to get hold of a nRF52840 dongle (PCA10059). For the dongle , there is no update lately so I believe the sniffer should work.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Also please try to debug without the sniffer. Please try to test with a stock SDK example.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387546?ContentTypeID=1</link><pubDate>Thu, 22 Sep 2022 15:44:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:462912e1-6b98-4664-9dcb-b696ab1f0d03</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Below are some other points worth mentioning.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I am able to get the capture at least started and somewhat working&amp;nbsp;&lt;/span&gt;&lt;span&gt;with an older nRF52-DK board&lt;/span&gt;&lt;span&gt;, but it will not follow the connection process correctly. But with the brand new nRF52-DK board (version 3.0.0) I can&amp;#39;t even start the capture process. One thing that is strange with the new board is the name of the J-Link firmware listed when I use the Segger Configuration tool, it is shown as OB-nRF5340-NordicSemiV1.00. This makes no sense since the board uses an nRF52832 chip and not a nRF5340. Is there any way the wrong firmware image for the J-Link was programmed on this board at manufacturing? Note that if I try to update it with the Configuration tool it states that it is up to date and I don&amp;#39;t know how to manually force it to program with any other image.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387539?ContentTypeID=1</link><pubDate>Thu, 22 Sep 2022 14:35:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2abbd214-ac48-41e3-9cc5-922b8e27a2db</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hello Hung,&lt;/p&gt;
&lt;p&gt;We are not getting anywhere here, I have already gotten over the hump but need to get this sniffer working for future issues. Here is the answers to your questions:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Have you made sure you copied the extcap to&amp;nbsp;C:\Program Files\Wireshark\extcap not&amp;nbsp;C:\Users\pam\AppData\Roaming\Wireshark\ ? &lt;span style="color:#0000ff;"&gt;&lt;strong&gt;&lt;span style="background-color:#ffffff;"&gt;Yes&lt;/span&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Please make sure you have installed the&amp;nbsp;pyserial &amp;gt;v 3.5&amp;nbsp;&lt;em&gt;&lt;span style="color:#0000ff;"&gt;&lt;strong&gt;&lt;span style="background-color:#ffffff;"&gt;Yes&lt;/span&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Also have you tried to run&amp;nbsp;nrf_sniffer_ble.bat --extcap-interfaces in command line and check what show in the screen ?&amp;nbsp;&lt;em&gt;&lt;span style="color:#0000ff;"&gt;&lt;strong&gt;&lt;span style="background-color:#ffffff;"&gt;Yes&lt;/span&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Please answer the question on:&amp;nbsp;&lt;/p&gt;
&lt;div class="quote-header"&gt;&lt;/div&gt;
&lt;blockquote class="quote"&gt;
&lt;div class="quote-user"&gt;Hung Bui said:&lt;/div&gt;
&lt;div class="quote-content"&gt;Please try to test the phone with one of our example in the SDK to see if you get the same issue. &lt;span style="color:#0000ff;"&gt;&lt;b&gt;&lt;i&gt;I can&amp;#39;t even get the capture to start at this point, what I am trying to sniff is irrelavent.&lt;/i&gt;&lt;/b&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/blockquote&gt;
&lt;div class="quote-footer"&gt;&lt;/div&gt;
&lt;p&gt;What&amp;#39;s the&amp;nbsp;disconnect reason show on the peripheral side ? &lt;span style="color:#0000ff;"&gt;&lt;b&gt;&lt;i&gt;I believe there is a bug on the Samsung side, I have to play games with the stack to get around it. At this point I just want to get the sniffer working.&lt;/i&gt;&lt;/b&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387408?ContentTypeID=1</link><pubDate>Thu, 22 Sep 2022 07:54:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e0d0bf01-6f77-4cd0-9e75-c9200ff600b6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pamela,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;Have you made sure you copied the extcap to&amp;nbsp;C:\Program Files\Wireshark\extcap not&amp;nbsp;C:\Users\pam\AppData\Roaming\Wireshark\ ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please make sure you have installed the&amp;nbsp;pyserial &amp;gt;v 3.5&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Also have you tried to run&amp;nbsp;nrf_sniffer_ble.bat --extcap-interfaces in command line and check what show in the screen ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please answer the question on:&amp;nbsp;&lt;/p&gt;
[quote user="hungbui"]Please try to test the phone with one of our example in the SDK to see if you get the same issue.&amp;nbsp;[/quote]
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;What&amp;#39;s the&amp;nbsp;disconnect reason show on the peripheral side ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387362?ContentTypeID=1</link><pubDate>Wed, 21 Sep 2022 18:40:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d86d1a9c-bdb1-4f89-bdb4-c50bcbf2676a</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;No luck getting this working. I just received a brand new nRF52-DK and now having different issues. First I am having problems getting the interface to be shown in the Wireshark capture options. Then when I do finally get it to show up somehow I get the following error messages:&lt;/p&gt;
&lt;p&gt;Error by extcap pipe: FIFO does not exist!&lt;/p&gt;
&lt;p&gt;nRF Sniffer for Bluetooth LE could not find interface: COM11&lt;/p&gt;
&lt;p&gt;I have attached a Nordic sniffer log file for you to reference. Note that I also tried uninstalling and reinstalling the Wireshark program and even some python stuff. I also downloaded the latest Segger JLink program and updated the dev board JTAG firmware.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Any help would be great, this is frustrating to say the least. Thanks for your help and regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387213?ContentTypeID=1</link><pubDate>Wed, 21 Sep 2022 08:08:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e32cdfa9-a0f0-4f66-93dc-ed11224081df</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pam,&amp;nbsp;&lt;br /&gt;Please try to update the Jlink firmware and download our latest sniffer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Please try to test the phone with one of our example in the SDK to see if you get the same issue.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387150?ContentTypeID=1</link><pubDate>Tue, 20 Sep 2022 17:41:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1bb6adbf-fc49-43bf-87a2-ca9338eb7fea</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;Yes I tried selecting the correct device from the drop down box, but the sniffer is still not able to follow the connection process. Perhaps my dev kit board is too old and causing issues? I know it is an older version, I just ordered a newer one to try and see if it works any better.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Pam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/387030?ContentTypeID=1</link><pubDate>Tue, 20 Sep 2022 09:09:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1bb2071a-edb3-4828-a328-56a292783c51</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pam,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;You would need to select your device in the drop down list. Something like this:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:258px;max-width:454px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/908x516/__key/communityserver-discussions-components-files/4/pastedimage1663664861155v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;After that it should only follow the advertising of the device you want to follow. Only after that you should start the connection between the phone and the device.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/386966?ContentTypeID=1</link><pubDate>Mon, 19 Sep 2022 23:18:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f43e0857-e5e0-4941-b0e1-81fcea09b0ea</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;I am not able to capture any packets past the adversing stage with my sniffer setup. I even tried re-installing the Wireshark tools, but still can only see advertisement and scan packets.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;As an example I have attached a scan capture file taken when a valid BLE connection completed. Can you tell me if you notice anything wrong with my setup used for capturing this file? Note I am using the nRF52DK board PCA10040 version 1.2.4.&lt;/p&gt;
&lt;p&gt;Thanks for your help and regards,&lt;/p&gt;
&lt;p&gt;Pam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/386523?ContentTypeID=1</link><pubDate>Fri, 16 Sep 2022 07:22:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2786d920-64f7-4773-bd9f-6533ed6955a1</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pam,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s would be very useful to have the sniffer trace.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please try to follow a connection by selecting the advertiser on the drop down list as instructed in the documentation. Please try with the latest version of the sniffer.&amp;nbsp;&lt;br /&gt;Let us know if you have any problem.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/386464?ContentTypeID=1</link><pubDate>Thu, 15 Sep 2022 20:32:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ff2bcf4-8d91-4d83-b322-eeb60c51455f</guid><dc:creator>Pamela Keiles</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;At this point we&amp;#39;ve only seen it on several S20+ and one S10+. From our device logging the connection is dropped following the MTU update exchange, but I have not been able to repeat it with my setup yet. I will test with an&amp;nbsp;S20+ that I am receiving tomorrow to see if I can get more clues.&lt;/p&gt;
&lt;p&gt;What is your recommended means for performing the a BLE sniffer trace? I do have some of the Nordic dev kit boards and have tried to use Wireshark briefly in the past, but found it confusing to easily follow the communications for a single device.&lt;/p&gt;
&lt;p&gt;Thanks and regards,&lt;/p&gt;
&lt;p&gt;Pam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Dropping Immediately on Samsung S20 Plus phone</title><link>https://devzone.nordicsemi.com/thread/386373?ContentTypeID=1</link><pubDate>Thu, 15 Sep 2022 11:47:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da52ba8a-4ae5-4539-a22d-29bfd770836c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Pamela,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you check if there is any log on the device ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you managed to reproduce the issue in house ? If you did , please try capture a&lt;a href="https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le"&gt; sniffer trace&lt;/a&gt; , so we can investigate what could be wrong over the communication.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Did it only happen on S20+ phone&amp;nbsp;? have you observed the same on other Samsung S models ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>