4 hours ago is available new software, but via cable i can't download still not visible for me via Garmin express webupdate , mobile app. My watch is no APAC so should be visible. How long should I wait?
Saw the thread there as well indeed. However, after 3 days (updated on Sunday) and looking back at the graphs I think the 'error' is not as big as a previously thought. [TABLE="align: left, border: 1, cellpadding: 5"] [TR] [TD]Day[/TD] [TD]RHR[/TD] [TD]Lowest on All-Day HR graph*[/TD] [TD]Delta[/TD] [/TR] [TR] [TD]Thursday (v7.60)[/TD] [TD]36[/TD] [TD]39[/TD] [TD]-3[/TD] [/TR] [TR] [TD]Friday (v7.60)[/TD] [TD]33[/TD] [TD]37[/TD] [TD]-4[/TD] [/TR] [TR] [TD]Saturday (v7.60)[/TD] [TD]38[/TD] [TD]39[/TD] [TD]-1[/TD] [/TR] [TR] [TD]Sunday (v8.00)[/TD] [TD]50[/TD] [TD]43 (this caused my concern)[/TD] [TD]+7[/TD] [/TR] [TR] [TD]Monday[/TD] [TD]44[/TD] [TD]42[/TD] [TD]+2[/TD] [/TR] [TR] [TD]Tuesday[/TD] [TD]42[/TD] [TD]40[/TD] [TD]+2[/TD] [/TR] [TR] [TD]Wednesday[/TD] [TD]54[/TD] [TD]49[/TD] [TD]+5[/TD] [/TR] [TR] [TD]Thursday[/TD] [TD]47[/TD] [TD]46[/TD] [TD]+1[/TD] [/TR] [/TABLE]
Note that the All-Day HR Graph in both Garmin Connect Mobile and Web show a 2-minute interval - this can be the cause of a delta in the RHR (1-min interval) and what we can see/determine from the graph.
I'll keep monitoring this to see how it develops. But from what I see now, it appears that the algorithm may have been too kind before (v7.60), and is now a little bit too strict (v8.00).
Updated my stats for the past 2 days. Still seeing a delta. I've e-mailed Garmin Support about it as well.
Floor counting seems to have stopped with this update. This is not definitive because on some days it doesn't work well and others it does. Today it isn't counting floors at all on my 5x and I do 20 floors. Anyone else?
Lucky you, I never had a problem with that on my 935 until i loaded veriosn 8.0.0.
Hmmm, a bit of an own goal here Garmin as version 8.0 seems to be total pants! I wonder if it is worth starting a fresh forum where people can just pop in a list of all the issues so that Garmin can collate the issues and then fix them.
I'm not sure about the connection to FW 8 (which is now on my watch) specifically, but since FW 7.6 I have had three instances of the GPS taking absolute ages to lock on. The previous two instances, this was after I had changed locale, so I put it down to having to reacquire the satellites. But this time it was in a spot where I run every day and had run the two previous days. The sky was completely clear, and everything else was exactly the way it is every day. For some reason, the GPS took more than 3 minutes to lock on (in fact I started the run without GPS lock eventually, as I don't have the time to stand around in the cold for 10 minutes - and it took 1.5 KM for the GPS to lock on), when the usual is less than 20 seconds. I have been using the watch in that exact same spot for the past six months, and this particular problem appeared the first time after FW 7.6.
As an add-on: the GPS tracks on the map that GC shows look absolutely the same as usual - in all three instances that this happened, and in all their erratic glory. So, either the "lock-on" is an incorrect message because in fact the GPS does lock on, or, the GPS lack of accuracy (about which I have posted a number of times) is such that it doesn't really matter whether the GPS is "locked on" or not... Either way it's a bit pathetic. It confirms my conclusion, which is that the GPS function is helpful to guide on a preplanned but unknown track (whilst being conscious that e.g. the turn indicator lags with regard to the real location on the ground), and that for the rest the recorded tracks have only documentary value as to where the run was, and close to zero value as to real pace or distance.
Colleagues What about LTHR , I running with version 8 from 16 February 5 times per week and do a lot of training intervals long run like today halfmarathon and still I have information: "Manual entry "
2 issue Why now always i have pop up "updating" after connect with phone, finish activity or connect with wifi.
You have to run the right sort of run to get a LTHR. You have to run at various paces below and above LTHR, it won’t just magically appear. Try a guided test, or some pyramid intervals and see if that works.
Has anybody actually got any sort of response from Garmin on the post version 8.0 issues? I raised a case via the website mid week last week and still have had no response to it. I assume that they must be aware that this code version has caused numerous issues.
Saw the thread there as well indeed. However, after 3 days (updated on Sunday) and looking back at the graphs I think the 'error' is not as big as a previously thought. [TABLE="align: left, border: 1, cellpadding: 5"] [TR] [TD]Day[/TD] [TD]RHR[/TD] [TD]Lowest on All-Day HR graph*[/TD] [TD]Delta[/TD] [/TR] [TR] [TD]Thursday (v7.60)[/TD] [TD]36[/TD] [TD]39[/TD] [TD]-3[/TD] [/TR] [TR] [TD]Friday (v7.60)[/TD] [TD]33[/TD] [TD]37[/TD] [TD]-4[/TD] [/TR] [TR] [TD]Saturday (v7.60)[/TD] [TD]38[/TD] [TD]39[/TD] [TD]-1[/TD] [/TR] [TR] [TD]Sunday (v8.00)[/TD] [TD]50[/TD] [TD]43 (this caused my concern)[/TD] [TD]+7[/TD] [/TR] [TR] [TD]Monday[/TD] [TD]44[/TD] [TD]42[/TD] [TD]+2[/TD] [/TR] [TR] [TD]Tuesday[/TD] [TD]42[/TD] [TD]40[/TD] [TD]+2[/TD] [/TR] [TR] [TD]Wednesday[/TD] [TD]54[/TD] [TD]49[/TD] [TD]+5[/TD] [/TR] [TR] [TD]Thursday[/TD] [TD]47[/TD] [TD]46[/TD] [TD]+1[/TD] [/TR] [TR] [TD]Friday[/TD] [TD]52[/TD] [TD]35 (43) lowest could be error[/TD] [TD]+17 (+9)[/TD] [/TR] [TR] [TD]Saturday[/TD] [TD]54[/TD] [TD]47[/TD] [TD]+7[/TD] [/TR] [TR] [TD]Sunday[/TD] [TD]47[/TD] [TD]46[/TD] [TD]+1[/TD] [/TR] [TR] [TD]Monday[/TD] [TD]51[/TD] [TD]36 (48) lowest could be error[/TD] [TD]+15 (+3)[/TD] [/TR] [/TABLE]
Note that the All-Day HR Graph in both Garmin Connect Mobile and Web show a 2-minute interval - this can be the cause of a delta in the RHR (1-min interval) and what we can see/determine from the graph.
I'll keep monitoring this to see how it develops. But from what I see now, it appears that the algorithm may have been too kind before (v7.60), and is now a little bit too strict (v8.00).
Updated again. Deviations persist. No reponse from Garmin Support yet on my e-mail.
