GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations

Here some experiences via email with Jeanet which also has the same TomTom One XP, with chipset GL1 FFFF.
Navcore is the old trusted 9.510 with a modified bin folder file borrowed from 9,541 the glgps file.

While I was of the opinion that everything was fine with the clock, Jeanet taught me that that was not the case as I thought

Indeed after a few minutes back to finish to call it that.
I had put a demo route in it to Hoek van Holland, it started well but suddenly the clock went back to now at 00:00

The route is well indicated and also the duration of the ride and distance
So it is quite possible to work with it, only I am now watching if the clock is still counting, only the duration of the ride counts down, I am now on the A20 and have already driven 9 minutes.

Speeds are well displayed at the bottom left of the screen, but the clock is always at 00:00.

I interrupted the demo for a moment and let the clock synchronize with the satellites and it now shows the correct time and I restarted the demo.
Arrival time is now 12:51 PM and the duration is also indicated correctly.
It looks like the clock continues to run well.

After a hard reset, the clock is still running
But when there is satellite again, it is back at 00:00
Using QuickFix does not help, remains 00:00
Now tried setting via clock and then synchronizing that also does not work without a route
If I put the route to Hoek van Holland back in and go back to the clock setting, the correct time will be shown after synchronization.

[Login or Register to remove this advertisement]

Solution:
Set your route first
Go to clock setting
Synchronize
and just drive

Conclusion:
As long as you don't give a hard reset or the battery runs out without using the device, it looks like the TomTom One Xl is working normally.

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Have the same issue with my go630 / 9.702, as mentioned earlier.

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

I can confirm that this worked on my ONE 30 Series PB with GL1 and NC8.010

I see now the ephem files now the date of creation is year 2120 in the beginning of week is 2019
Perhaps they solved the 7 days problem
Some one have feedback

No the bootloader is not the solution.

I cannot confirm above mentioned results on my One 3rd Edition (v6) first two digits of device are Y2 (device-HW readout: GL1 FFFF) , NC9510 and changed \bin content with new "glgps" file. Yesterday evening QuickFix downloaded from TTHome2. Practical drive-experience this morning:
- it took about 3 min before GPS was active
- accuracy of GPS is less then before 6 April
- action in #141 done; synchronized time, but on display Estimated Arrival Time still equal to drive-time.
My conclusion: it is not only the GPS-chip (GL1 FFFF) but also rest of HW?