Yes, I had the GPS on and the Google Services off.
Originally Posted by mespiff
I did another quick experiment. I took a short trip to the grocery store (1-1/4 miles) and put the Pre on the dash of my car with FitTrack on. I did not reboot my Pre. FitTrack told me I had 1/2 a full signal. On the way there, it initially seemed OK. When I got there, my average speed seemed very slow (14 mph) since I didn't hit any traffic lights. I checked the map and again there was a short section where my path disappeared off the screen. This seems to indicate I lost the GPS connection for a small portion of the trip. The distance read 1.25 miles.
I checked the signal before my trip back home and it told me I had a full signal. This time the app worked almost perfectly. Only the elevation was messed up. Average speed was 20.81 which seems right since I hit a traffic light. I checked the map and it was spot on. The distance read 1.27 miles. Two 10ths more than the trip to the market... another indication that I lost the signal on the way there. The signal was locked in nicely for the trip back. When I got home, it told me the accuracy was less than 10'.
I'm not sure why it's so inconsistent but here are some observations... I thought with the walk, it might have been that I had my hand wrapped around the phone blocking it from picking up the signal. Either that or it might have had issues with me swinging my arms while walking. When I went to the market, I started off before it had a full signal. It probably couldn't "lock in" because I was moving. My Garmin sometimes has this same issue. On the way back, I was in an open parking lot and it got the full signal before I started off. It was "locked in". Looks like I might just need to be a little more patient.