I attempted my first run with my new GPS watch this morning and came home disappointed. Everything was great for the first half mile, but when I turned onto a different street it continued to record time but not distance. I thought GPS satellites were awesome, and the only time it couldn't get a signal was when it's in a tunnel or something? When I reached the end of the street it started recording distance again but by then it said my pace was ridiculously slow - don't get me wrong, I'm slow, but not THAT slow. So why did this happen? I'm hoping it's a fluke, I'm going to go for another run on Thursday I think and I'll take the same route so we'll see what happens then.
This is the road where it didn't record distance on the way down, but it did on the way back... hmm.
As you can see, there are a lot of trees on both sides of the road once you get farther down there but that really shouldn't affect GPS satellites, right? I did run my trusty Endomondo app as well - proven to be accurate because I've used it in multiple 5K runs. Here are the final results:
My adorable watch says I only went 2.31 miles. I beg to differ.
I stopped the app at 3.1 on purpose and walked the last little bit to the house. I was SO close to getting it in under 30 minutes (yes, still taking a few short walk breaks too). The watch and app are off by 5 seconds but that's because I started Endomondo first, shoved my phone into my Flipbelt and then started the watch. I will try to start them at the exact same time on my next attempt.
I'm really hoping this was a one-time thing because I'll be bummed out if I have to return the watch. I will let you know how things go after my next attempt! If anyone has a logical explanation for this feel free to share as I'm still new to using running tech.
1 comment:
I attempted my first run with my new GPS watch this morning and came home disappointed. Everything was great for the first half mile, but when ... tomtomrunner.blogspot.de
Post a Comment