Elevation gain still not fixed with the new firmware, way too low. Have come to the conclusion the Altimeter is not fit for purpose in this device so use the correct elevation option afterwards.
Same problem with two devices after Garmin replaced one.
Did you calibrate the Altimeter? You can do that starting 3.70.
Yeah I did but it’s not the starting point that’s the problem, it’s the overall gain. Always much lower than the GPS track itself would suggest. It’s not the pressure that’s the issue, I have your widget and hardly any change.
i noticed the 935 had a firmware upgrade that tried to fix too much smoothing out. Not sure if it did and that is the problem here. I have the Edge 1000 for cycling which is bang on with the Altimeter. So at least that takes care of cycling where elevation is a more important metric.
I realized my watch is an APAC version when I didn't get the update like everyone else. Could yours be the same?
No, I don’t have an APAC version (bought the watch in The Netherlands and that shop got it from Garmin in the UK). All firmware updates until version 3.40 installed fine. 3.70 is still missing in action and watch is set to automatic updates and I sync multiple times per day with my iPhone 6.
Edit: Just rebooted the watch and then noticed the 3.7 update was available to install on the watch from the settings menu. So... it’s installed now. :D
Has anyone run a longish run while listening to music with 3.70? 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).
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.
talsela, I would restore factory settings on your watch and then check if this issue still occurs. If so... I think you may have a faulty GPS sensor? I had my first run (15.8 km) after the firmware updated to 3.7 yesterday evening and all is working fine.
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.
