Add motion service

[JF002]

This PR adds a new Motion service, which exposes the "live" step count and raw motion values (X/Y/Z).

API definition:

• Service : 00020000-78fc-48fe-8e23-433b3a1942d0
  • Characteristics
    • Step count (1 * uint32_t) : 00020001-78fc-48fe-8e23-433b3a1942d0 00030001-78fc-48fe-8e23-433b3a1942d0 (READ/NOTIFY)
    • Motion values (3 * int16_t) : 00020002-78fc-48fe-8e23-433b3a1942d0 00030002-78fc-48fe-8e23-433b3a1942d0 (READ/NOTIFY)

I also improved notifications so that they are processed and send only if the companion app registered to them (and applied to change to the heart rate service).

[Elara6331]

The BLE characteristic UUID for step count is identical to the one used to get responses from call notifications. One of them needs to be changed.

[JF002]

@Arsen6331 Good catch! I totally forgot about that custom "service"! And it's unfortunately not mentioned in the doc page...
The Motion service will move to 0003xxxx-..., then!

[ajack2001my]

How much is the battery affected by this service? Can it be switched off?

[JF002]

@ajack2001my This is BLE service, meaning that it exposes some values to the companion app, but it won't consume any power/cpu time unless the companion app actually read those values (or subscribe to notification).

[Elara6331]

I've implemented this in itd. The issue description should be edited in case someone tries to look for the UUIDs and gets confused by there being two differing sources.

[JF002]

I've implemented this in itd.

Awesome!

The issue description should be edited in case someone tries to look for the UUIDs and gets confused by there being two differing sources.

Indeed, I've just edited, thanks!

[Elara6331]

Notify on the step count characteristic seems to only populate one byte of data. Once the step count goes above 255, it resets to 0. Reading from the characteristic instead of using notify yields the full, 4-byte value.

[JF002]

Notify on the step count characteristic seems to only populate one byte of data. Once the step count goes above 255, it resets to 0. Reading from the characteristic instead of using notify yields the full, 4-byte value.

Woops ! You are right : https://github.com/InfiniTimeOrg/InfiniTime/blob/develop/src/components/ble/MotionService.cpp#L83
The step count is passed as a single byte in this function, while the original variable is a uint32_t... The joy of C++ and implicit casting...
I'll fix this asap!

[JF002]

Fixed in 71ce13d

In this screenshot, the number of steps is 0x12345678 :

[xan-m]

Step count implemented in InfiniLink on iOS. This was one of my most frequently requested features, thanks for adding it @JF002!

[Elara6331]

Fixed in 71ce13d

Just tried it, it now works. Thank you.

[JF002]

Step count implemented in InfiniLink on iOS. This was one of my most frequently requested features, thanks for adding it @JF002!

Thanks for integrating it!