This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PSA: beta 16.09 is out

This update, version 16.09, is a Release Candidate. "Release Candidate" means that this exact software version is planned to “Go Live” as a public update as long as no critical issues are observed. All copies of version 16.09 will be identical, so there are no differences in functionality whether you install version 16.09 as a Public Release Candidate or wait for the update to be a Live public update.

To download this update on the Forerunner 955 Series devices, go to: Main menu > Settings > System > Software Update > Check For Updates

Change Log

  • Adds muscle maps to HIIT, Cardio, and Pilates activities.
  • Adds the Endurance Score glance.
  • Adds the Hill Score glance.
  • Adds map types and map data field options.
  • Adds weather maps to the Weather glance.
  • Adds a Workouts app to the Activities & Apps list.
  • Adds new activities for team sports, racket sports, and more.
  • Adds notification watch face data field ability to display name or number
  • Adds support for new Di2 cassettes
  • Fixes Pace Pro screen freeze
  • Fixes flashlight not retaining last brightness level
  • Fixes some issues with Spotify
  • Fixes popularity map theme not being displayed
  • Fixes issues with glance folders
  • Various fixes for maps
  • Various other fixes
  • GPS Firmware Update
  • Sensor Hub Firmware Update

Top Replies

All Replies

  • It might be crucial to people using Stryd, but most people aren't using it. It's kind of interesting to see how often people with Stryd have problems with Garmin. I think there's pretty long track record for that.

    I also think it's pretty normal for Garmin to break things like that in their beta releases, even they are called RC. I don't understand why did you even install it. If you think the last release cycle and amount of the beta RC's there were, I would say that one should pretty much know that the first ones are not release quality. 

    Last release cycle:
    - Public Beta Version 15.19
    - Public Beta Version 15.17
    - Public Beta Version 15.15
    - Public Beta Version 15.12
    - Forerunner 955 Series Beta 15.11 (Pre-Rollout)
    - Forerunner 955 Series Beta 15.09 (Important Update In Notes)

    All but the first mentions RC and the first might have also been, but just no mention.

  • It's not just Stryd though, it's anything using CIQ. 

    Garmin shouldn't be stating anything about Release Candidate state if it's simply a Beta version, I'd rather they said it was Beta, because at this point for 16.09, who has been doing the initial Beta testing (in public)?

    https://en.wikipedia.org/wiki/Software_release_life_cycle

    Either way, I'm not here to argue with you, Garmin need to fix their issues, and my stance on the quality of this release still stands. 

  • Every FW that brings bigger fonts is welcome

  • Yes, but reasons to use CIQ are mostly what I've seen Stryd and then some other very exotic sensors. It might even be that they just test the features that the watch have with the watch itself and not with some 3rd party accessories and sensors and CIQ fields are not part that testing and those just come out when they release versions like this.

    Well, it's Garmin to decide what is RC. Being RC doesn't really mean anything about the bugs it might have.

  • Wifi connection also doesn't work...again!

  • Perfect timing with an ultra coming up this saturday, will be postponing this one till after that at least (also reading about the issues)...

  • CIQ has much more uses than that. I use the Exact Pace field as I don't want to have the smoothing and averaging that the Garmin Pace field has.

  • Yeah, CIQ is one of the strengths of Garmin... Pretty bad that it would be broken, generally, for datafields and they not noticing this before releasing it.

    Is the issue just with datafields or are there also issues with watch faces for example? 

  • And you mean that is a big audience that uses some CIQ data field that does that? I don't think that pretty much contradicts anything what I said.

    CIQ is pretty niche thing in big picture even how big the heavy users in this forum see it. I can easily imagine it being not so integral part of the testing process as most of them are just 3rd party things.

  • The fonts in general are broken.