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]

Hi Mohammad,

It would reduce the time needed to do service discovery. It requires a few more packets to discovery a service, compare to an extra characteristic inside the defined service.

The advantage of separated battery service is interoperability. If you use battery service as standard SIG service, other 3rd party app can read and interpret the service.

However, if your main service is proprietary, then I don't think it would be a big advantage.