<?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>Issue with scanning for BLE NUS on some Android devices.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67016/issue-with-scanning-for-ble-nus-on-some-android-devices</link><description>On some android phones we have observed that if we try to scan using nRFToolbox for nRF51/ nRF52 controller advertising with UART they do not show up in the scan list. But if we turn on nRFConnect app and scan with this app the controllers show up in</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Oct 2020 11:26:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67016/issue-with-scanning-for-ble-nus-on-some-android-devices" /><item><title>RE: Issue with scanning for BLE NUS on some Android devices.</title><link>https://devzone.nordicsemi.com/thread/274585?ContentTypeID=1</link><pubDate>Tue, 13 Oct 2020 11:26:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f24abfdf-214a-4ba8-bacd-98e0e213533d</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;which version of the uart app are you using and which version of nRF toolbox? I would guess the difference might be that nrf connect is a generic app and scans for everything, while nRF toolbox might be looking for a specific service that it might not find in the advertisement packet? But if the nRF connect app connects first, nrf toolbox will see that there is an existing device that supports the service it is looking for.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>