Startup GPS Lock Wrong

I don't believe it is only because of the time synchronisation. It does not help me. I am standing at the same place receiving 6-8 excellent satellite-signals. Last night and this morning it is pointed me 300m away to the east direction from my real position permanently. Now it points me 300m away to the south, south-east direction. And it is keep changing now. I have had that kind of movements earlier but only with smaller distances at poor GPS reception with some older quick GPS fix. I have noticed some errors also during this week.

I have a tomtom one V1 too, always working well.
Yesterday I started it and the GPS lock the wrong street 100m-150m far from my real position!! I tried everything but nothing. Any advice how to fix the problem?
More I use the tomtom for my job......I am in trobles

I got mine working again by doing this;
In TomTom HOME, go to Manage my "Whateveryouhave", Items on Device, and delete all the QuickGPSfix files.

Then disconnect, do a soft reset, and give a go. If it is going to show the right location after that (but would take a bit longer), you've got the culprit.

Found this on the tomtom forum

kidicarus wrote:I got mine working again by doing this;
In TomTom HOME, go to Manage my "Whateveryouhave", Items on Device, and delete all the QuickGPSfix files.

Then disconnect, do a soft reset, and give a go. If it is going to show the right location after that (but would take a bit longer), you've got the culprit.

Found this on the tomtom forum

Hi Kidicarus,
I did the same. Instead of my previous ~300m now I have ~6km distance between my real and the pointed position by my device.

After the posts on this subject started piling up, I booted my GO & had/have the same problem. As Downunder pointed out, it is a satellite issue not a device issue.

Apparently the soft reset is the key to get it working as it gets the satellite positions itself rather than from the file, hopefully they'll release another quickgps fix and we'll be back to normal again

kidicarus wrote:1. Apparently the soft reset is the key to get it working as it gets the satellite positions itself rather than from the file,
2. hopefully they'll release another quickgps fix and we'll be back to normal again

1. No reset, 15 second soft reset or 30 second hard reset makes no difference in fixing the issue..
2. QuickGPSfix is updated every day.

I got mine working (for now) too by doing a soft reset. Was a little surprised when it magically had the correct position again.
I wonder why this issue isn't more widely reported.. It can't be affecting only users of this forum.. right? Especially if it is a satellite issue.
Maybe TomTom is conspiring with the US Government to disable older GPS devices of NaviTotal users?? =p

It's not affecting my NOT-TomTom device either. Therefor a satellite issue is doubtable. Unless we are talking about other continents. I am in Europe.

nabi wrote:It's not affecting my NOT-TomTom device either. Therefor a satellite issue is doubtable. Unless we are talking about other continents. I am in Europe.

Hum, we have a half a dozen or so members with the same problem at the same time. Would that not indicate a system problem rather than a unit problem? I'm not in Europe!!

tendriver wrote:Hum, we have a half a dozen or so members with the same problem at the same time. Would that not indicate a system problem rather than a unit problem? I'm not in Europe!!

Yep, a TomTom system failure, like the recent bug was ([Please Register or Login to download file] , [Please Register or Login to download file] , etc), no satellite failure.

nabi wrote:Yep, a TomTom system failure

Yep, as I said in post 24.

Yep, same problem here.
Only on my TT ONE V1 with the 9.450 navcore and the 890.4222 map.
All showing position 200m too much to the west and a few meters to the north.

I have 2 exactly the same devices and the one with navcore 8.412 (and 885 map) is NOT affected.


what did NOT help:

- deleting the ephem-folder
- using the resetbutton (single-click & 30 sec. hold)
- using clearflashtool 3 times
- deleting "currentmap.dat" & "mapsettings.cfg"
- restore factory settings in preferences
- sync clock
- switched to another map

Just got a call, my friends GO630 with NC 9.430 and 890.4222 map has it too.

Going to swap SD-cards, navcores and maps to isolate the problem.

After putting the same navcore (9.450 w memory boost) and the same map, fresh from their RAR's, on another SD-card, the problem is gone.
When I put in the other SD-card the problem is back.

So it must be possible to delete something on the SD-card / internal flash memory to solve this issue.

You can check what files are created after the first start.
Compare that list with the files on the "faulty" system and replace them one at a time.
Do a check after each file and once the position error is back we know what file is involved.