My watch updated overnight and I did a15 mile run this morning and got auto lap announcements right where I was expecting them and the track looks good on the map.
On my 35km run today (v3.70), the watch notified me at least 50 times that "GPS ready" (couldn't quite count), meaning it dropped satellite acquisition, at least to some extent. When that happened, I could see on the map page that tracing was going crazy. This did not happen, except once or twice in 1-2 runs on v3.40.
Looking at the map now after my run, there are places where the watch puts me 80-100m from the path I was running on.
I did a longish run today and got the same thing a litte after the start, GPS ready around 10 times! The elevation graph is interesting because of that! I did wait for a gps lock plus 30 secs before I started btw.
I’m getting tired of having to power my 645m off and back on to fix the issue where music stops playing for no reason after a song ends (and won’t start the next song).
I realized my watch is an APAC version when I didn't get the update like everyone else. Could yours be the same?
May I ask you if you know of a certain way to determine whether the watch is an APAC or a ROW? I may have the same problem since it is not updating to 3.7 and Garmin express is telling me I am "up to date" with 3.40.
I am still on Version 3.40 but I had the mystery GPS fix about 4 miles into my run yesterday
Ha it's funny you say that because I had exactly the same thing happen today on my 19k run. Still on 3.40 and have done countless runs without issue. Then out of the blue the GPS fix alert comes up for the first time ever about 8k in. Was using live track connected to my phone, so I wonder if they've also made some server side changes which is triggering something on the watch.
I had my 645M reset today during the first mile of my run. Or just stopped tracking distance for 0.1.
I'm doing my warm up and I look down and my normal Run data screen is gone - it's back on the default watch face (I use a different watch face from CIQ). Without hitting a button, it goes back to my Run data screen. I look at the lap distance and lap pace. Appears it continued to track time during that reset, but failed to track about 0.1 of distance, so all of a sudden my lap pace looked super slow. I'd think it was just a GPS issue other than how it reset to the watch face and back... weird.
I think this was my 4th or 5th run with v3.7, the others worked just fine.
Still on 3.40, on my most recent run I got a GPS fix before starting as usual then proceeded to have the GPS alert about a dozen times in the first quarter mile but only occasionally after that. I concur that something seems to be going on external to the watches.
