GPS Week Number Rollover (WNRO) issue with IGO Primo under WINCE

**CYK** · 26th July 2019, 10:02 PM

Originally Posted by ScorpionSX

[...]

I actually managed to change the time on my unit. However, it is really only changed - not correct. Or, to be precise, it's correct when I start iGO and there is clock which shows correct time. When I close it, the stereo interface shows wrong time.

[...]

ScorpionSX,

I solved the same problem on my GPS (iGo Primo 2.0.1 with Ultimate skin) by leaving the time zone to manual and setting my time zone in iGo Primo settings and using the following setting in "sys.txt":

[regional.timezone]
reset_os_timezone=0
sync_os_timezone=0
sync_time=0

Although the above setting does not sync the time of the GPS device, it is updating with the correct time. Hope this can solve your problem.

Greetings,
CYK

**hermierf** · 18th June 2019, 02:07 PM

Any update with this issue, I'm also encountering same problem with my car GPS using IGO Primo... regards...

**Boki** · 18th June 2019, 04:42 PM

IT IS ONLY UP TO DEVICE. To its FIRMWARE, to be precise. Nothing can be really done with iGO software

My device is 14 years old, currently using KIA Primo, no problems at all. Also tested a lot Chinese, "branded" and no-name, all is OK at all of them.

**hermierf** · 20th June 2019, 01:18 PM

Thanks for the info Boki, but how can I fix my problem, any Firmware update for IGO, or some tweak on my sys.ini files ? regards....

**xcv** · 23rd June 2019, 10:27 AM

Hello!

We have a problem with the GPS Week Number Rollover (WNRO). We use a Wayteq X980BT with Primo 2.0 9.6.5.278914. As long as the Primo doesn’t have a GPS connection, then the time and date will be displayed correctly (using the data from Wayteq). But as soon as the GPS connection is established the date will jump to 1999-11-01 and the time will also be wrong/changed.

Is there a possibility to stop Primo from using the GPS provided data and let it use it the data provided from Wayteq instead? This would hopefully bring my Primo to display the right date and time.

The settings in the sys.txt

[timezone]
sync_os_timezone=0
sync_time=0
use_auto=0

were tested and changed, but that sadly didn’t help.

Due to this problem (wrong time and date) the change from day to night display will also probably happen at the wrong time.

We sent a request for help to Fa. Wayteq about this problem with the Week Number Rollover (WNRO), but their answer only was that the X980BT won’t be receiving any more updates.

Regards
Team xcv

**BIBUOT** · 23rd June 2019, 10:55 AM

Hi

must look here at the link WayteQ xRider

[Only registered and activated users can see links. ]

Worked on my WayteQ-X985BT

Thanks costas3850

**freund** · 23rd June 2019, 01:24 PM

@ xcv

This is interesting, because I have the WayteQ X960BT (older than yours) with IGO Primo v2.0.1 (9.6.5.245577 - 6.7.2012) on it.
Yesterday I made a ride over 600 km - no problems!
GPS, time, date correct as always!

**xcv** · 23rd June 2019, 02:50 PM

Hello!

@ BIBUOT:
After inquiry to the company Wayteq the update of the x985BT can not be used for the x980BT.

@ Friend:
My son has a x960BT with Primo 2.01 (9.6.5.278914). These problems do not occur. The settings in Primo are completely the same as on my x980BT.
The problem is likely to occur only with the x980BT.

**nik4m** · 25th June 2019, 10:17 PM

Two possible solutions are verified for NextGen on Android OS. It is possible that it will work for WinCE or/and Primo as well. In sys.txt to add
Solution #1:
[time_provider.gps_time_provider]
enable=0
priority=0

Solution #2:
[time_provider.local_time_provider]
priority=200

[regional]
timezone_providers=1