Startup GPS Lock Wrong

Yes, that would be the next logic thing to do. However, I got some drifting on the fresh install aswell, but only a little, so I did a clean install again. The satellite fix is OK again. Today I will do a lot of driving for work, so I will test if this is a long term solution.

My friend wich has a GO630 was very catious/reticent about upgrading his device, worried that it might "get broke". Of all the devices I upgraded, of course, this one has this positioning problem.... oh the irony...

Today the fresh install worked fine all day, +/- 80 KM total.

I 've been busy for hours now trying to figure out wich file could be the crulpit, but I got nothig but inconsistend results.

After deleting "settings.dat", the gpsfix was fine, but after a reset with reset-button the problem came back one time. The other time it stayed OK.


Files I also deleted:

• clmdata
• currentmap.dat
• reflush.log
• ttgo.bif
• temporary.iti
• swap
• userpatch.dat
• watchdogtrace.dat
• disallowtrip.dat
• mapsettings.cfg

I also changed the map (again) on the "faulty" SD-card and the issue was gone sometimes, but sometimes it stayed!

This is taken up way too much time, I 'm gonna use the fresh install from now on and sees how it holds up.

Thanks for the testing anyway!
The settings.dat might be one reason, rest of the files (to my knowledge) does not contain enough info on the topic to cause problems.
But I start to think it must a combination of things, maybe device/NC or even map/quickfix.
For a general problem there are not enough reports.

All,
I too had this problem, in Ontario - Canada. I left the house at 0700 EDT and TomTom (GO910) didn't get an accurate fix for over 20 mins.

It did have a fix but always 200-500m out.

The day before I had just rebuilt the 910 with 9.405 and v885 of USA/Canada/Mexico.

Driving back today (about 200km) it never got an accurate fix at all. This is still the case now, as I type this.

I'm about to restore from a v9.026 backup and see what happens.

S

Good timing, just finnished another search at the TT home base and found several discussions about the same problem.
People from Europe, US and basically the rest of the world have the problem.
Many devices are affected by the looks and TT claims to have a fix.
The QuickFix data must be removed and after that re-installed by Home.
They even included instructions : [Please Register or Login to download file]

So if you're affected check the link, follow the instructions exactly and report back if it is fixed now for good.

Working!

Thanks for finding the solution :)

It's interesting to think that a small error with TomTom can affect many users so easily...

DeviceVersionHW=GO 910
DeviceSerialNumber= ***

ApplicationVersionVersionNumber=9405
TTSystem 2303757 bytes, modified 25/03/2012 23:06
PNDNavigator 8105388 bytes, modified 25/03/2012 23:06
BootLoaderVersion=55259
RDS/TMC 'mctx.dat' size 212 bytes
CurrentMap=USA_Canada_and_Mexico_P_885_4097
CurrentMapVersion=885.4097

At least now we know that there is a problem with the QuickFix and that it is known to TT.
Seems to be similar to the mess they created for TMC users with the 9.430 update.
For both problems you have to deeply search the TT support forum.
Best way IMHO would be to include such problems into TT Home/MyTT in a similar way as the optional downloads.
But focus stays on the new devices and so it is up the owner of device to solve the problems one way or the other.

LOL, just updated the QuickFix this morning, as a last resort, indeed its the only easy way to fix this issue!

The suggestion that it was in the QuickFix data was already done on saturday on alot of forums and also my first assumption, but (as many, aperrantly) I assumed also that removing the QuickFix files or even the complete ephem-folder on the device, followed by a reset (resetbutton) was enough to "start from zero" regarding the GPS-position. How wrong I was.

Aperrantly TomTom stores somewere else, on the SD-card/internal flash, also GPS-positioning data, wich can not (easely) be reset.
So the QuickFix files change something at other places in the device and therefore deleting the QuickFix files doesnt make their changes undone!

I have many questions regarding the functioning of QuickFix, tried alot of googling months ago, but more detailed then "Quickfix stores files on the device in which the position of the satellites is stored, so the device doesnt have to "search" long for them" it never got.
For instance:

• Is it possible to transfer the QuickFix files from one device to another, or are they device specific?
• The QuickFix files are only a few KB's in size, they are valid for 7 days. Why not offer them for a month or even a year? The files wouldnt be larger them some 10-20 MB for year?

I never botherd much about updating the QuickFix, since it only lasts a week, but this incident got me thinking of never updating it again at all.
The QuickFix data wich caused the problem on saturday (30-6) was already downloaded at tuesday (26-6) and had been functioning fine for four days.
They must have forgot to correct for the the GPS leap-second at midnight 29-6/30-6.

Very glad this issue is solved! Sloppy from TomTom! This leap-second was already announced in January this year.

They have a link now on their support page:
[Please Register or Login to download file]

RJ45 wrote:1. LOL, just updated the QuickFix this morning, as a last resort, indeed its the only easy way to fix this issue!

2. The suggestion that it was in the QuickFix data was already done on saturday on alot of forums and also my first assumption, but (as many, aperrantly) I assumed also that removing the QuickFix files or even the complete ephem-folder on the device, followed by a reset (resetbutton) was enough to "start from zero" regarding the GPS-position. How wrong I was.

3. Apparantly TomTom stores somewere else, on the SD-card/internal flash, also GPS-positioning data, wich can not (easely) be reset.
So the QuickFix files change something at other places in the device and therefore deleting the QuickFix files doesnt make their changes undone!

4. I have many questions regarding the functioning of QuickFix, tried alot of googling months ago, but more detailed then "Quickfix stores files on the device in which the position of the satellites is stored, so the device doesnt have to "search" long for them" it never got.
For instance:

• Is it possible to transfer the QuickFix files from one device to another, or are they device specific?
• The QuickFix files are only a few KB's in size, they are valid for 7 days. Why not offer them for a month or even a year? The files wouldnt be larger them some 10-20 MB for year?

5. I never botherd much about updating the QuickFix, since it only lasts a week, but this incident got me thinking of never updating it again at all.
The QuickFix data wich caused the problem on saturday (30-6) was already downloaded at tuesday (26-6) and had been functioning fine for four days.
They must have forgot to correct for the the GPS leap-second at midnight 29-6/30-6.

6. Very glad this issue is solved! Sloppy from TomTom! This leap-second was already announced in January this year.

They have a link now on their support page:
[Please Register or Login to download file]

1. Not the last resort, but the only resort, since it was a system issue, rather than a unit issue.
2. You were closer to being right than you realize.
3. It's all in the ephem folder.
4. The sats move around, so QuickGPSfix updates your unit to the new locations, so it doesn't have to "hunt" for them.
You can transfer them, if you wish, but the files downloaded today for unit X are the same as the files downloaded for unit y. So nothing would be gained.
After 7 days the data is so old that your unit starts having problems getting a lock on.
With a monthly or annual update, your unit would take forever or never get a lock on.
5. Not updating is a direct result of not knowing how the system works.
6. We don't know that a leap second caused the problem.

thanks for your response,

1. Since a clean navcore install, also solves the problem, replacing the Quickfix data is not the only resort to solve the issue. Has to be said that it is definatly the best, especially when you want to keep your device as much the same as possible.
2. 1% away from being right, is still wrong ;)
3. If that was the case, how do you explain that removing of the faulty Quickfix files not solved the issue?
4. The reason I asked if they where the same is because, then I would be able to e-mail them to my friend, the one from the GO630, and instruct him by telephone to replace them on his device. Without having to install another piece of bloatware, excuse me, TomTomHome.
5. I honestly dont understand. Lots of people never update the quickfixdata for even years and their devices, although (much) slower, posistions fine.
6. Well, since the same QuickFixdata (as said) functioned fine for four days and devices with that data started to fail exactly after the night of the leap-second, I would say it had something to do with it.

regards

RJ45 wrote:thanks for your response

If you are not satisfied with the answers that you received here, then I suggest that you call TT Tech Support.

MInes been working fine today, used it all day for work, was drifting about a bit yesterday and the clock wouldn't sync to the correct time.
I havent updated the quickgps file on mine yet tho, will try and do it later if I can.

kidicarus wrote:MInes been working fine today, used it all day for work, was drifting about a bit yesterday and the clock wouldn't sync to the correct time.
I havent updated the quickgps file on mine yet tho, will try and do it later if I can.

Apparently this position issue would have solved itself, without any interaction at all.
My friend's GO630 worked fine again, since yesterdayevening, wich is the moment his QuickFixdata was more then 7 days old. He hadn't put the new QuickFix files on his device at that moment and didnt change anything.