Compliance with Bluetooth Qualification - adopted services

[Mohammad Afaneh]

In the source files of standard/adopted services, there's a comment stating:

/* Attention!
 * To maintain compliance with Nordic Semiconductor ASA's Bluetooth profile
 * qualification listings, this section of source code must not be modified.
 */

If one wants to use one of these services and initialize it as a secondary service instead of a primary service, does that interfere with the qualification?

What's the best way to re-use one of these services as a secondary service? I assume modifying the original files for these services would not be a good idea(?)

[Hung Bui]

I don't think you need to use battery service as secondary service in your use case. I don't see any benefit here. It actually takes longer to discover secondary service than the primary one.

Are you planning to create a service for each of the device you connect to ? If they are sharing the same services, I would suggest to use one service for all of them, and use one extra byte or one extra characteristic as the identifier to select each of the peripherals.