Draft: Pebble timeline support

Currently untested, because my sfdk is apparently broken. Will update!

added 9 commits

• 5e3bd656 - Stub PebbleManager
• e8a6aeda - Initial Pebble pinning support
• 54d50dae - fixup! Initial Pebble pinning support
• 1f89732c - Reduce update frequency to 1/min
• 5224840d - fixup! Initial Pebble pinning support
• 70f53987 - fixup! Initial Pebble pinning support
• ad8b7e54 - fixup! Initial Pebble pinning support
• 9ad4d8f5 - Actually trigger the Pebble updates
• f021ebf0 - More elaborate pin

Compare with previous version

Screenshots of my watch.

marked this merge request as ready

Current version also displays the pace and elevation change (if over 5, that should probably be 5000).

I'm not sure how this will respond on systems where the Rockpool daemon is inactive. The error might be overly verbose there, but it shouldn't hamper the functioning of Kuri.

added 1 commit

• 678e624d - Correct unit conversions

Compare with previous version

This wasn't great yet, will report on next activity.

Current version looks a lot better, except for elevation. @elBoberido, what do these elevationUp and elevationDown represent? I just did a walk of 5km with a minimum height of 4m and max of 6m. Elevation up gives 842.4*1000 and elevation down 836.2 * 1000.

It's the sum of all positive and negative deltas to the previous position. But this needs some filtering before it gets useful since a noisy signal will lead to quite a big change in the sum.

What would you say, just leave this out of the screen? I went hiking with this in the alps last week, and showing elevation (change) since start (or so) would be really neat :-)

Elevation difference to start should be work fine. If you want, please add that in a follow up MR.

added 5 commits

• 8a9899b4 - Initial Pebble pinning support
• d8ace402 - Reduce update frequency to 1/min
• 01fdc042 - Actually trigger the Pebble updates
• 969ac481 - More elaborate pin
• dbf085ee - Correct unit conversions

Compare with previous version

I just skimmed over the small changes and need some time for a thorough review.

In general, having this feature merged is not a problem, but keeping it functional will be since I cannot easily test it. Can I ping you to test a pre-release once this is merged an new releases are imminent?

I just skimmed over the small changes and need some time for a thorough review.

No problem, let me know what you think needs changing.

Can I ping you to test a pre-release once this is merged an new releases are imminent?

Absolutely. I might not be the quickest to respond on Gitlab, but feel free to ping me on Matrix/IRC/email/Signal! I'll happily go on a walk through the city to test it :-)

I've pushed two fixups; if they look good to you, I'll sqaush them into their originating commits.

added 2 commits

• 98d3045d - fixup! Correct unit conversions
• 47bd2b32 - fixup! Actually trigger the Pebble updates

Compare with previous version

marked this merge request as draft from rubdos/kuri@98d3045d

It seems this is never called. Please remove.

What implications does this have for users who do not have a Pebble?

This should also not be in RecordPage.qml but probably in harbour-kuri.qml

Please wrap this into an if-statement and only call it if a Pebble is actually used.

This value can be accessed from QML with Settings.workoutType. It seems I forgot to rename the property to Settings.activityType. It's now renamed on master. Please rebase and use Settings.activityType instead of adding a new property.

Sorry for the long delay. I hope you are still interested in bringing this upstream.

left review comments