Related
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

Incorrect Firmware version status

2930847
over 2 years ago

I've been involved in beta program for my fenix 6 recently. Being a Linux user I have no possibilty to use garmin express.

I notice that the status of my device is false for as long as 22 days now.

The screen-shot indicate that I run 22.83 (which is the actual firmware on my fenix6) nevertheless, 2 beta and one CR have been pushed since (23.00 has been announced 7 days ago)https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/306162/system-software-23-00

But as of today 2022-08-30 the device's page in Garmin connect is still telling me i am up to date ("le logiciel est à jour"). The synchronisation with the device is ok ...so to me the problem rely in the back office, during the interrogation of Firmware status.
I imagine this explain the fact that I am still stuck in a old firmware version, and am still unable to update to 23.00 FW.

Am I the only one observing this problem (or Am i among the non garmin express user, the only one experiencing it  ?)

Could anyone at Garmin IT have a look on why is this page not working ? (I mean not telling me that I run an outdated firmware version ?)

Any help would be appreciated

Cheers

  • 0 over 2 years ago

    Wait for the rollout to be 100%. It is currently at 30%. Your watch is not in the 30% that it has been rolled out to. So, you got the latest firmware for your watch.

  • 0 over 2 years ago in reply to e7andy

    Thanks for the reply e7andy...I know that for an strange reason the firmware roll out is done by batches taking more than a week...anyway I was in the Beta program, where it should be expected that the roll out doesn't take more than 7 days as this is sometime the time between 2 firmware releases. I've been patient, and patient again....and as I say I'm still stucked with 22.83 firmware, and apparently a process that think everything is normal !

    My point here is that since 2022-08-15 (15 days ago) and the release of firmware beta 22.85, the Garmin connect web give an obviously wrong information. 22.83 is outdated since 2022-08-15, and 23.00 firmware should have been installed since 2022-08-18, so  the test behind the simple question "is the actual firmware the last one ?"  may help to better understand whats wrong in the update process.

    I know other user in the beta program had this update problem when relying only on garmin connect web/app, I wish they could confirm or infirm my observation.

  • +1 over 2 years ago in reply to 2930847

    You are not in the beta program now. The latest version for 30% of the watches that are not in the beta program is 23.00. For the other 70% the last version is 22.10. The watch checks if there is an update available and there is none for you since you got a version that is higher or equal to 22.10. I don't see the problem here. Do you think it is taking too long time? Or is it reporting the wrong version? 

    The beta releases are only available if you are in the beta program. If you join the beta program you will have new versions to install and can install the latest beta version which currently is the same as the final version.

    The rollout time depends on how the rollout goes. It can even be stopped so not all get access to a new version. The idea with a staged rollout is to see if any errors are reported before it rolls out to more users. Maybe Garmin is seeing an increased number of errors reported and therefore stopped the rollout at 30%.

  • 0 over 2 years ago in reply to e7andy
    e7andy said:
    You are not in the beta program now.

    I know....but I was ! I've been enrolled till I encounter the update problem. I've been asked to try to sign in and out of the beta program several time....just in case, it trigger an update.

    e7andy said:
    The watch checks if there is an update available and there is none for you since you got a version that is higher or equal to 22.10. I don't see the problem here.

    If you are sure that the test is actually : Test if fw version is >= 22.10 (22.10 being the last official version) than probably the test should be adjusted for the fact that you are in beta program or that you run an "unofficial release" (here are two screenshot done when I was in the beta program the first was on 2022-08-17 two day after 22.85 release and the second is on 2022-08-26 8 days after 23.00 release (as a RC not as the official which was announced the 2022-08-23)

    Do we agree that at that time, being in the beta tester group, the message could have been misleading (despite a logically correct test since 22.83 in all the case is in fact greater or equal to 22.10).

    e7andy said:
    if you are in the beta program. If you join the beta program you will have new versions to install and can install the latest beta version which currently is the same as the final version.

    From my experience (and based on the screenshot...)If you are in the beta program...you don't necessarily have  the new version. I did read some other user had difficulties generally when the also only rely on garmin connect web (not garmin express). I was trying to understand if the misleading information (possibly inadequate test) could also explain not being able to update my F6. The root cause being the same !

    Concerning the staged rollout...I did join the beta program and now try to find why I have so many difficulties to update just to avoid this kind of problem (errors not seen before).

    On a positive note, I must says that since 22.83....i haven't face any big problem, just some mis-computed training efforts, from time to time...but I am unable to says if the latter have been fixed since 22.85..and .filling a report would be helpless to says the least. Again, if the official firmware release take that long I could accept it. But a too long rollout is really problematic in a beta program, since you miss a lot of opportunity to test how reliable your new firmware is AND you keep receiving reports for fixed bugs.

  • 0 over 2 years ago in reply to 2930847

    Garmin Connect is closed source so we have no idea how the version check is performed. I just make assumptions from the most logical way to check if a watch got the latest version or not. 

    The beta program is pretty new. It might still have some bugs in the interface.

  • 0 over 2 years ago

    I had the same problem when 23.00 was still beta. I checked it like 10 times every day for 5 or more days 'till it finally started to be downloaded to my watch. What was interesting is that I downloaded the Explore app for android: https://play.google.com/store/apps/details?id=com.garmin.android.apps.explore and it did correctly show that there is an update. And when I exited the beta program and checked it after a minute it showed that I'm on the latest version. And when I enrolled again it showed again that there is an update. However Garmin Connect Android didn't think so. And the Connect website didn't think so. Garmin told me to unpair the watch from my phone and then re-pair again, which didn't help either. And suddenly after another few days it started to download it (when you go to GCM > menu > Garmin Devices you should see that it's either "Syncing" or "downloading software update" (or something similar))

    I still don't know what fixed it, IMHO there was (or according to your report still is) a bug in Garmin's apis. My guess is that the Explore android app uses some api to check for updates and the Garmin Connect android app uses some other api (which seems to be buggy)

  • 0 over 2 years ago in reply to flocsy🤠

    Hi thanks so much for your reply (You were my last hope to  get thing fixed).

    Explore App, did succeed to get the information correctly display in Garmin Connect Web after I sign-in to the beta program. (Otherwise the message was still that I was up to date)

    So apparently, :

    - there is a differentiated behaviour according to the fact that you are or not in the beta program as to the message displayed in Garmin connect Web. Apparently, if you are not in beta, but not running the real official Firmware 22.10 you see a see a message telling you are up to date (The test probably done to test whether you are up to date or not is like e7andy thought a greater or equal to 22.10). A refined test and message could be better  as it would avoid to report bugs for an obsolete Firmware hence saving time for developpers

    - I agree that the hypothesis of different API (or API  use)  between Garmin Connect Web and Garmin Connect App on one side and Garmin Explore app and Garmin Express on the other side could explain our observation....and should be investigated in order to have a coherent behaviour between product.

    While writing the firmware Download is on its way. I must says it's a tad bit longer than the download and copy via USB-cable that we use to have in the previous beta . Perhaps allowing a plan B (old fashion) for firmware upgrade could have been wide !

    Anyway thank you again for your help Gavriel.