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

18.23 is still at 20%

Piero
over 1 year ago
  1. why is 18.23 still at 20%? 
  • 0 over 1 year ago

    Because it works so well Laughing Every time they publish beta candidates for release 3 or 4 times, then the "stable" version arrives, then the fix arrives and maybe this time we can also get the fix of the fix. I really don't understand the rush to publish buggy SW and then chase it

  • 0 over 1 year ago

    I think something similar happened with 18.22, then it jumped to 100%.

    Luca said:
    Because it works so well

    I'm using 18.23 since it was released with no problems. I used 18.22 before and had no problems either.

  • 0 over 1 year ago in reply to Luca
    Luca said:
    Because it works so well 

    Yeah, or maybe they just did not update the % in time, while in reality it was rolled out constantly.
    Anyway I received it today, OTA via Garmin Connect Bluetooth Connection without searching for it or using PC and Garmin Express.

    Luca said:
    I really don't understand the rush to publish buggy SW and then chase it

    I would like to see your perfect software...

    While on the one hand there definitively is a lot of room for improvement in Garmins development process, especially regarding transparency of bugtracking, communication to the users, beta testers and in general...

    ...on the other hand I personally know of no software project, that DOESN'T need hotfixes. And I am both interested in all kinds of open source projects and read news on that and also work in corporate software projects for years. At some point, you just have to do it and release and see what happens in the wild. Your test set will never be perfect.
    And if your usecases are complex, your software will  also be.

    But anyway, I know I'm just wasting time here. Just go on with Garmin bashing, they are so horrible bla bla. Enjoy!

  • 0 over 1 year ago in reply to Grumpy from dawn till dusk

    Yesterday rope jumping training at home at 21 degrees celsius, I put on the armband but I forgot to turn it on, after a few HR jumps at 155, I turn on the band and it drops to 106 in a few seconds (the transition works very well). In a watch sold by Garmin for 600 euros (955 solar) which you then find in the store for 460, as the best product in the range, do you find this normal? All the algorithms are based on HR and therefore everything is altered, you are completely free to waste your money, the old 945 works even better. Then comes the track running correction, I would like to understand how many use it compared to 100% heart rate.

  • 0 over 1 year ago in reply to Luca

    Unfortunately, yes it's pretty normal for watches with OHR to o rubbish with things like jumproping, weightlifting, etc.

    It works good (enough) for running and cycling (I think at least) but it's just limited by what it is. Could or should Garmin do better? I think so, other brands seem to have shown that they can do better with their OHR (again, for running etc mainly) and it being Garmin's core business as well as a LOT being based on it, yeah they should do better...

    But jump roping is not a good example here.

  • 0 over 1 year ago in reply to FlipStone
    FlipStone said:
    yes it's pretty normal for watches with OHR

    No. It is not normal since 18.22. It was normal one version before. Not perfect, but OK. And if i have my HR at 55 now after 50 sit ups and 20 pushups, I have a slight suspicion that something is wrong witch a garmins brand new firmware.