That looks about right. That is, that's the kind of huge error I'd get from my Gear Fit. I've given up on it. I have a Garmin Forerunner 235 now (it's mostly for running; $199 on Amazon) and the GPS simply works. No more BS. It locks on quickly, follows my path accurately enough, and I can finally get accurate pace, speed, stride length and calories data. And the heart rate monitor is also very good . The joke is it's not even a new device - it came out in 2015. I love Samsung phones but I'll stick to fitness wearables made by companies specializing in that segment of the market.
The irony is that I had a Samsung Gear S3 which i used for the same thing coupled with an iPhone X and that worked fine.
I really like this band more than the Gear S3 cause it's smaller and cheaper so I don't have to worry about damaging it. But this GPS thing is really annoying.
I just hope it was caused by the fact that the phone was in power saving mode.
Ok, after turning off power saving mode on the phone (Galaxy Note 9), the GPS seems to work fine.
Andrew - from what I understand S Health uses the phone's GPS to track your location and uses the band only for the heart rate, the duration of the exercise, the step count and stuff like that.
I think it uses the Gear Fit's GPS unit only if during the exercise the band is not connected to the phone. So you wear the band, you leave the phone at home and go exercise and when you come back S Health downloads all the exercise information (including GPS info) from the band. However, if it is connected to the phone it does not use the band's GPS unit, I think. Or maybe for accuracy it uses both? But that would seem like a waste of power since the phone GPS is good enough ever for high speed tracking when driving.
My issue is that Gear Fit2 Pro activity imported to strava shows wrong pace.
I had strava and endomondo apps running on mobile and recoding acgivity, and `workout` on the watch. Now, I got the watch activity through Samsung health uploaded into strava.
I can compare the graphs side by side.
Respective graphs show the same distance between two selected points on the map. The times differs hugely though.
In my case distance is 3.2km, native strava recording shows 15:12s elapsed between the points.
While activity imported from watch shows 14:25s. Endomondo supports strava with 15:08s.
Have you guys seen Gear fit2 pro inflating your speed?
So, I have run with friends the same track and time discepancy between GearFit2-Pro strava imported activity and their strava activity clearly showed.
I exported GPX file from samsung health and imported it in strava manually through the web-page.
And voila, timings got fixed. So it seems the seconds disappear at the point when strava automatically imports activities.
... however, this way heart rate data does not get into Strava ... so basically pointless.
Just to show you discrepancies (this is the same activity automatic import vs manual import):
6 5:10 /km
7 5:19 /km
8 5:47 /km
6 5:30 /km
7 5:40 /km
8 5:57 /km
The differences are pretty big.
I have had one for 8 months. GPS fixed once, but still not great. Battery replaced once, but, two days later, drains to 60% after 90 minutes. A very poor product. Having it repaired again: third time lucky?
I got the gear fit2 pro in July 18 after a year+ with the gear fit2. I had frequently had the lag time issue of GPS locking in with the older unit and would usually have to wait a couple of minutes before beginning a bike ride or run.
Initially I was very happy with the improved performance on the gear fit2 pro. The GPS was locking in within a few seconds of opening the bike, walk, or run workout screens - before even starting the workout. Did many accurately recorded workouts from July through November.
Then I slowed down due to weather and some injuries and didn't use the trackers much. Recently began running again and now the GPS will not lock in AT ALL until you are at least 5 minutes into the workout. Small problem for walks. Significant problem for runs. Huge issue for bike rides, as I am usually a mile into the ride before the GPS starts accurately tracking.
What would have caused this massive downgrade in performance over a couple of months??