Issue with scanning for BLE NUS on some Android devices.

[pmantri0412]

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 this app. 

Then while keeping the nRFConnect App open if we now go ahead and scan using the nRFToolbox app we are able to see the controller in the scan list. 

Can you let me know why we see this behaviour. Also is there an difference in the scanning method used between nRFtoolbox and nRFConnect? 

[run_ar]

Hi,

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.