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]

You are correct. Even if you use battery service as secondary service, you would need one battery secondary service for each of the service you relate from.

There is very little if not, none, use of the secondary service. I would suggest you to simply put the battery service as the 2nd service of each device, like this:

Device 1 service: { char 1a, char 1b...etc }
Device 1 battery service: { char 1a, char 1b...etc }
Device 2 service: { char 2a, char 2b, ...etc }
Device 2 battery service: { char 1a, char 1b...etc }
Device 3 service: { char 3a, char 3b, ...etc }
Device 3 battery service: { char 1a, char 1b...etc }

I don't see any disadvantage doing it this way.