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

No more LTH (Auto Detect)?!

So, Garmin solved the problem with LTH simply by not recording anymore LTH?!

I had no more LTH since 10 days....

  • Just to add that I'm agree with you, my last auto LTH was january 31st

  • I hope I misunderstood and you're still working on a way to bring back auto LHT updates after runs. Or do you want me now to open another thread with the issue of not having the auto LHT update since months? You can find many users in this thread here not getting updates since many months...

    From the emails I've had, this is definitely something they're actively working on.

  • Garmin has disabled on purpose the lt detection to avoid the real Lt bug (if you sync a new detected Lt thru Garmin Connect then Lt if synced incorrectly -and most sport science behind the Watchwatch depends on this-)

  • For me it looks like NOBODY at Garmin know how this works. 

  • Garmin people who write on this forum are just passersby 

  • Probably. But when they see a repeated error reported like this you should expect them to bring it forward to someone who can correct the error.

    But therein lies the real problem itself, such are not available at Garmin unfortunately.

  • any news? We are not speaking about a minor issue as the color of backlight, this is a MAJOR issue of a feature that was working good until last january. How is it possible that Garmin can't understand/discover what Garmin itself changed 2 months ago to make LTH detection broken?! In a normal software house all the developers would have been fired weeks ago...

  • I'm working in software development myself and I know that fixing bugs takes sometimes more time than someone from the outside would think. However 2 months are gone now and I really think there should have been a reaction by now...this bug does not only affect the 955, but also all other watches!

  • But you also know that if a bug pops out and in the previous sw version there wasn't, you can do a step back, release a "fix" that is the previous SW release and in the meanwhile work to solve the bug for future release

  • If the software were written in a workmanlike manner there wouldn't be all these problems but unfortunately it's a big tangle of spaghetti. They would do better to rewrite it from scratch