This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF BLE Android - My BleScannerCompat doesn't detect a device, but nrf connect does

Hi,
I'm having this trouble since some weeks ago and I was looking for an answer in documentation and was impossible to find it.

I have a device with Nordic ble chip and I'm trying to find it trough android scanner's library (BluetoothLeScannerCompat.getScanner()) and is impossible to see it. But when I turn on the nrf connect app or bluetooth settings from phone settings, I see this device and, later, it appears in my app's scanner. Of course this is not a good solution to this problem, because I can't say to every user to do this to discover this devices.

Scanner settings:


val settings: ScanSettings = ScanSettings.Builder()
.setLegacy(false)
.setScanMode(ScanSettings.SCAN_MODE_LOW_LATENCY)
.setReportDelay(500)
.setUseHardwareBatchingIfSupported(true)
.build()


I don't know what to do to solve this. Any idea?

Thanks.
Parents
  • I have similar problem.  I am able to detect it in using nrf connect app, but not in nrf Blinky app.  Though in my case, the nrf Blinky app is still not able to detect it even after nrf connect app has detected it.  In my case, my nrf device was far away and the rssi was very low.  There is a function isNoise() in ScannerViewModel.java that would filter out low rssi device.

    Perhaps not the kind of problem you have...Just pointing out what I found.

Reply
  • I have similar problem.  I am able to detect it in using nrf connect app, but not in nrf Blinky app.  Though in my case, the nrf Blinky app is still not able to detect it even after nrf connect app has detected it.  In my case, my nrf device was far away and the rssi was very low.  There is a function isNoise() in ScannerViewModel.java that would filter out low rssi device.

    Perhaps not the kind of problem you have...Just pointing out what I found.

Children
  • Thank you for sharing what you have found, @kvc!

    It could indeed be that the device was filtered out due to low RSSI, but I still suspect that Joel's issue might have been with the enabling/usage of the BLE adapter - since they were able to find the device with both the native BLE scan through 'settings' and the nRF Connect application (after which it was also discovered in their own application).

    If this is still an issue for you I recommend that you open a separate ticket for this issue, to receive help debugging it! :) 

    Best regards,
    Karl

Related