Device requirements list

Former Member
Former Member
Is there a place where we can see what devices currently support what features? A list of firmware requirements, etc.... For example I can't easily find any reference to say there is a firmware version for Fenix 3 that supports apps yet.
  • I was prompted to this by bad reviews of my app. Why should I be getting 1 star reviews when my app works on the simulator? I don't think I should have to go digging around to find out the latest status of the firmwares on the supported devices.


    This is why I've suggested that the App store be made a bit smarter, where when an app is submitted, there is a way for the developer to say what's need in the app (functionality not in all versions of the FW for all the devices). That way, if someone tries to install an app, but which has an older version of the FW on their device, they could be told something like "You need to update your firmware to use this app".

    And example is "phoneConnected", It's not supported in the current FW for the vivoactive, but it probably will be soon, so the app store could block installing an app that doesn't have the FW version that supports it, but allow it for devices that do. That way the "store" can manage when a function is available on a specific version of the FW.
  • I think we could do a better job of communicating the kind of information sharkbait is asking for. Release notes are really the best reference right now, but as ruperthawkes noted, our use of "various bug fixes" isn't very helpful. In our defense, the various bug fixes statement typically covers under-the-hood fixes or optimizations that either won't affect developers or are from a context that won't be relevant to anyone outside of our team.

    I mentioned it earlier in another thread, but I'd like to eventually have some kind of status board that developers can refer to so check the status of various reported bugs, but it's not something that we'll be doing soon.

    I want to avoid a road paved with good intentions and all of that, so for now I think we can do a couple of things: provide more detailed release notes and document the CIQ release version supported by various device firmware releases. Does that sound like a good first step?
  • I think we could do a better job of communicating the kind of information sharkbait is asking for. Release notes are really the best reference right now, but as ruperthawkes noted, our use of "various bug fixes" isn't very helpful. In our defense, the various bug fixes statement typically covers under-the-hood fixes or optimizations that either won't affect developers or are from a context that won't be relevant to anyone outside of our team.

    I mentioned it earlier in another thread, but I'd like to eventually have some kind of status board that developers can refer to so check the status of various reported bugs, but it's not something that we'll be doing soon.

    I want to avoid a road paved with good intentions and all of that, so for now I think we can do a couple of things: provide more detailed release notes and document the CIQ release version supported by various device firmware releases. Does that sound like a good first step?


    Yes, go for it! ;-)
  • I think we could do a better job of communicating the kind of information sharkbait is asking for. Release notes are really the best reference right now, but as ruperthawkes noted, our use of "various bug fixes" isn't very helpful. In our defense, the various bug fixes statement typically covers under-the-hood fixes or optimizations that either won't affect developers or are from a context that won't be relevant to anyone outside of our team.

    I mentioned it earlier in another thread, but I'd like to eventually have some kind of status board that developers can refer to so check the status of various reported bugs, but it's not something that we'll be doing soon.

    I want to avoid a road paved with good intentions and all of that, so for now I think we can do a couple of things: provide more detailed release notes and document the CIQ release version supported by various device firmware releases. Does that sound like a good first step?


    +1
    (and keeping my finger crossed for the public board/issue system/whatever)
  • Former Member
    Former Member over 10 years ago
    All a step in the right direction. How about an email subscription to new firmware updates?
  • New updates are coming soon for the fenix 3 and vivoactive. Unfortunately the previous updates had to be pulled due to reasons outside of the control of the Connect IQ team. When the updates are released, the best way to get the update will be to use Garmin Express, as it'll take a bit for the update to appear over the BLE connection with your phone.


    To close the loop on this the fenix 3 update is available now via Garmin Express and the vivoactive will be available by tomorrow through Express as well.