Have been having the same issues with the NAVI showing me friving miles from where I actually am.

Will be updating the firmware this afterrnoon so will give that a couple days and see if the issue is corrected.

It is a very huge pain in the butt though!

If this does not resolve will return to Best Buy.

Has anyone running the 1.00003 been having the issue?

Yes, even the 1.003 firmware the nav will occasionally go into "airplane mode" and have you fly over fields and lakes a mile or two from where you really are. Eventually it usually corrects itself, but the logic it's using kind of escapes me. What's odd is that the compass shows north correctly, and the direction and speed of travel is matched perfectly, just the location is off. It seems the GPS has some signal but there is a bug in locking into a specific location perhaps a little too quickly, and once it does, is reluctant to second guess and correct itself. I've not seen a GPS with a weak signal react in this manor so I think its more software related. Maybe it's trying to prevent a weak signal from causing it to stray off target, but in fact is protecting a poor location lock in the first place?

I watched it on a recent drive home about 20 minutes out. At first I was skimming over a nice lake, but once I started tracking thru streets it would try to do it's best to lock me onto one of them (if I got low enough to the ground I guess ). But gradually as it jumped me street to street it would tend to lock onto a street that was a bit closer to where I really was, finally gear down for landing after about 15 minutes.

I'm trying to figure out if it's related to where I park. Most often I've seen the problem after parked facing north against 2 story high concrete wall. I've been backing in for a clear southerly view lately to see if that makes a difference.

Yes, even the 1.003 firmware the nav will occasionally go into "airplane mode" and have you fly over fields and lakes a mile or two from where you really are. Eventually it usually corrects itself, but the logic it's using kind of escapes me. What's odd is that the compass shows north correctly, and the direction and speed of travel is matched perfectly, just the location is off. It seems the GPS has some signal but there is a bug in locking into a specific location perhaps a little too quickly, and once it does, is reluctant to second guess and correct itself. I've not seen a GPS with a weak signal react in this manor so I think its more software related. Maybe it's trying to prevent a weak signal from causing it to stray off target, but in fact is protecting a poor location lock in the first place?

 

I watched it on a recent drive home about 20 minutes out. At first I was skimming over a nice lake, but once I started tracking thru streets it would try to do it's best to lock me onto one of them (if I got low enough to the ground I guess ). But gradually as it jumped me street to street it would tend to lock onto a street that was a bit closer to where I really was, finally gear down for landing after about 15 minutes.

 

I'm trying to figure out if it's related to where I park. Most often I've seen the problem after parked facing north against 2 story high concrete wall. I've been backing in for a clear southerly view lately to see if that makes a difference.

Nice summary. I think you described problem pretty good. Once it goof up the calculation of go-ordinates on the map, it sticks to its guns and continue unless we re-dock it again.

I do not think it has anything to do with where we park. It happend few times at home, and office and sometimes in open parking lots with clear skys.

I am pretty sure it is a software screw up by Pioneer. I would assume they would fix these kind of things in immediately following releases atleast, but I am not seeing solution anytime soon.

Just a quick update...

Has been better since updating the firmware.

But noticed a new issue yesterday driving home. While the map appeared to have me in the correct location, the street name it said I was on was wrong. It took a good 2 or 3 minutes before that corrected.

Now if they could just do something about the BlueTooth quality