• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 42 replies
  • Subscribers 24 subscribers
  • Views 1728 views
  • Users 0 members are here
Options
Related

Support for sports and sub-sports

flocsy🤠
24 days ago

I'd like to add 2 settings where the user can set the sport and the sub-sport. However I am not sure exactly how am I allowed / supposed to use these constants. IMHO there's some confusion in the documentation about the min api level: https://forums.garmin.com/developer/connect-iq/i/bug-reports/fix-documentation-of-min-api-level-in-activity-sport_-and-sub_sport_ 

Secondly am I allowed to combine each available sport with any available sub-sport? For example can I create a session with: SPORT_MOTORCYCLING and SUB_SPORT_INDOOR_ROWING? 

And more importantly how do I know either in compile time and / or run-time whether a device supports something? Does it matter at all? Or am I able to use ANY number as :sport and :subSport when creating a session as long as Garmin Connect supports it?

What about Rucking for example (https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-documentation-or-sdk-missing-recently-added-sports)

  • 0 18 days ago

    I am able to record a Rucking activity on fr965 using:

    :sport => Activity.SPORT_HIKING, //17
    :subSport => 124

    However now there's a new problem: until Garmin adds Activity.SUB_SPORT_RUCKING there's no way to know if a device supports it. When I try it on fr55 then it crashes, and it's not a catchable exception :( 

  • 0 18 days ago in reply to flocsy🤠

    Given that fr55 is on CIQ 3.4.2, and FR965 / Fenix 8 / etc are on CIQ 5.1.0, a reasonable heuristic could be to check the CIQ version at runtime.

    If CIQ >= 5.1.0, assume rucking is available.

    Advantages:

    - It works on FR965, Fenix 8, Tactix 8, and many other newer devices

    - If rucking is also supported on CIQ 5.0 devices, then that's a shame, but at least your app won't crash

    Disadvantages:

    - If some 5.1 devices don't support rucking, then your app will still crash

    Yeah, I know all of that is obvious.

    If you're really worried, you should def wait until SUB_SPORT_RUCKING is actually added to the SDK/API.

  • 0 18 days ago in reply to FlowState

    And I'll add that specifically in case of Rucking I'm not sure how useful it would be considering there's no way to set the weight of the backpack...

  • 0 18 days ago in reply to flocsy🤠
    flocsy🤠 said:
    And I'll add that specifically in case of Rucking I'm not sure how useful it would be considering there's no way to set the weight of the backpack...

    Maybe this is the root cause of the reported bug where there's no SUB_SPORT_RUCKING in the SDK.

    Then again, no sports or subsports have been added since 4.1.6. Kinda raises the question of whether any sports have been added on the real devices since then. If the answer is yes, then it could just be that nobody's bothered to add *any* new sports to SDK since 4.1.6.

  • 0 18 days ago in reply to FlowState

    no, because in fr965 it works without weight.

    Sure: Rucking was added on at least tactix8 and the :subSport for it is 124, so I would say that probably for every number between SUB_SPORT_TABLE_TENNIS (97) and 124 there is a sub-sport now. So in theory the fr955 or fr965 might be able to record all kinds of 1 second sessions, with all the possible combinations of sport and subSport and see which one doesn't crash and how it's displayed in GC.

  • 0 17 days ago in reply to flocsy🤠
    flocsy🤠 said:
    And I'll add that specifically in case of Rucking I'm not sure how useful it would be considering there's no way to set the weight of the backpack...
    FlowState said:
    Maybe this is the root cause of the reported bug where there's no SUB_SPORT_RUCKING in the SDK.
    flocsy🤠 said:
    no, because in fr965 it works without weight.

    Maybe I didn't make myself clear. Once again, an egregious failure to communicate.

    I was suggesting/implying that perhaps SUB_SPORT_RUCKING was not added to the SDK because, as you said, it's not clear how useful it would be without the ability to set the backpack weight.

    Given the choice between adding a half-assed and useless feature (rucking with no weight config) and not adding the feature at all, it seems like the better choice is doing nothing at all.

    Just to be explicitly clear, the hypothesis here is that adding the rucking backpack weight setting in CIQ would be more work than the CIQ team management is willing to take on at this moment.

    That was originally just a throwaway comment btw.

    As I also said, the other explanation is simpler: that they just didn't bother adding all the new sports/subsports to CIQ, and rucking just happens to be one of them.

  • 0 17 days ago in reply to FlowState

    Oh and just to absolutely clear: I was specifically referring to adding a CIQ enum called SUB_SPORT_RUCKING (or whatever) to the SDK / device firmware, not just the fact that the integer value to works on a real device.

    The fact that the integer value works on FR965 is a separate matter.

    To be clear: it's different matter because devs aren't *supposed* to hardcode those values, we're supposed to use the CIQ enums.

  • 0 17 days ago in reply to FlowState

    Having said all of that, I wouldn't be surprised if SUB_SPORT_RUCKING is eventually added, but with no way to configure the backpack weight.

    That's why I said it was a throwaway comment. It wasn't supposed to be that deep.

  • 0 17 days ago

    I wanna know when can JUMP_ROPE be added. The official Jump Rope has been released for several years.

  • 0 17 days ago in reply to li2niu🏃🏻

    Yeah, you could save an official jump rope activity and have a look in fitfileviewer.com to see the sport and subSport. But you'll have the same problem as I have with rucking that you'll need to guess on which devices it's possible to use it...

    You can vote on this: https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-documentation-or-sdk-missing-recently-added-sports

    maybe it helps. I think this should be relatively easy to fix, because Garmin only needs to add them to the documentation. I mean, not sure where the constants reside for the has check... Maybe that's in the firmware? Or is it something they only need to add to the SDK?