15.3.0 NUS based on 13.1.0 BLE android application VUS

RE: 15.3.0 NUS based on 13.1.0 BLE android application VUS

Vidar Berg — Wed, 18 Sep 2019 06:47:09 GMT

The point of testing with nRF connect app first was to find out if the 52 FW works as intended without your custom app. Did you try nRF connect with the old FW as well?

RE: 15.3.0 NUS based on 13.1.0 BLE android application VUS

tommy.lane — Tue, 17 Sep 2019 15:44:24 GMT

When I connect to the device it lists the services, but doesn't allow me to interact with any of them. Does this mean something on the embedded platform exhibits unexpected behavior?

RE: 15.3.0 NUS based on 13.1.0 BLE android application VUS

awneil — Tue, 17 Sep 2019 15:42:28 GMT

nRF Connect can connect to the device, discover Services & Characteristics, and then lets you read & write Characteristics, receive Notifications, etc ...

RE: 15.3.0 NUS based on 13.1.0 BLE android application VUS

tommy.lane — Tue, 17 Sep 2019 14:49:17 GMT

I'm confused as to how the nrfConnect application can help me here. How would I get to the point where I could interrogate the device?

RE: 15.3.0 NUS based on 13.1.0 BLE android application VUS

Vidar Berg — Tue, 17 Sep 2019 12:11:08 GMT

Hi,

You shouldn't have to port anything on the Android side if the new FW include the same services. Unless the Android app is relying on hardcoded attribute handles. The attribute handles will become different with the new Softdevice, so a new service discovery is required. My suggestion is to try and verify the functionality of the new 52 FW with the nRF connect app on Android first.