RSC from nRF Toolbox does not work

[bluefirepatrick]

Hello,

With Segger ES I am able to compile and run the Blinky example (pca10040, S132) from the nRF5 SDK without any issues, it loads on my nRF52 DK board on and it shows up in all the right places when I scan for it on my Android phone (Bluetooth Settings, nRF Connect, my own app).  I can also build the RSCS example without any problems and it looks like it loads on the board just fine as well.  I can see that it has a SoftDevice and an Application in the memory map using nRF Connect Desktop.  The problem is that it does not show up when scanning with the RSC app in nRF Toolbox Android (from the Play Store) nor does it show up in Bluetooth Settings or anywhere else.  Should it?

[AndreasF]

Hi.

Running Speed & Cadence is according to this chart not supported on Android devices, only iOS unfortunately.

Therefore I don't expect it to show up.

Best regards,

Andreas

[bluefirepatrick]

Thank you very much for your prompt reply.  Please take a look at this project from your repo on Github.

https://github.com/NordicSemiconductor/Android-nRF-Toolbox

specifically:

https://github.com/NordicSemiconductor/Android-nRF-Toolbox/tree/master/app/src/main/java/no/nordicsemi/android/nrftoolbox/rsc

It seems to indicate that the RSC app that ships with the Android toolbox would support the RSC application running on the DK. Perhaps the author, philips77, works on your team and could be asked?

I also tried the nRF Toolbox running on iOS and it has the same results as Android: neither nRF Connect nor the scanner in the RSC app see the device -but other examples run fine.

Is there a chance that the example code for Segger in the latest SDK is incompatible with the Toolbox for iOS and Android?

I ask because the RSC app seems to be the goto example for background services on mobile devices which interests me for my project.

Thanks again,

Patrick

 

[AndreasF]

Hi.

I've talked to the author, philips77, about this issue, this is what he replied:

If you are testing against the SDK 15.x (perhaps 14.x as well?), the SDK team decided to use Advertising Extension (Bluetooth 5 feature) in that sample (I guess to demonstrate how to use it in the SDK).

Advertising Extension is supported on Android since Oreo (8.0). To match behaviour with older API, by default scanning does not return AE packets. A method setLegacy(false) needs to be called on the ScanSettings.Builder.

This will, however, be ignored on pre-Oreo devices, as they don't support Advertising Extension. iOS also does not support Advertising Extension. That's why you don't see your device in nRF Toolbox or nRF Connect on iOS.

To try that sample you need to have Android Oreo or newer phone. Also, I'm not sure what version of nRF Toolbox is currently in the Play Store, so perhaps you need to run the app from Github's code or use nRF Connect for Android.

I would recommend checking CSC sample, which is very similar to RSC, but may use legacy advertising.

I hope this information helps you.

Best regards,

Andreas

[bluefirepatrick]

Thank you very much.  This is extremely helpful.

Patrick