RE: How to connect to specified service when duplicate services discovered with same UUID in one peripheral?

esonhon — Wed, 07 Sep 2022 06:05:14 GMT

Hi Hung,

Thanks for ur valuable advice. And yes, after a power recyle, duplicate services gone, my board works. You saved my ass!!

For others who may be interested in this topic, I'd like to share more information.

Actually, restart the android APP will release the service. But if you terminate the APP by pushing te STOP DEBUG button in Android Studio, the zombie-service created.

RE: How to connect to specified service when duplicate services discovered with same UUID in one peripheral?

Hung Bui — Tue, 06 Sep 2022 11:47:21 GMT

Hi Weihe,

I would need to check with our Android experts to check if there is anything wrong.
But could you try to do a test to reset the phone (and turn off and on Bluetooth) and try again. I suspect that every time you run your app it will try to create a new UART service on the phone and it explain why you have so many duplicated.

We will need to look into how the service should be released after the app is closed.

The reason for that you can use only one single service and not able to choose between them when there are multiple duplicated is that the ble_app_uart_c or specifically the database discovery module was not designed to handle multiple instance of the same service on a server. So it basically return the first instance of the service in the table. And I don't think there is a straightforward way to continue discovery the next service except for manually start the discovery again using ble_db_discovery_start() with correct curr_char_ind and curr_srv_ind parameter.

I would suggest to focus on solving the issue on the Android app.