Thread: Time

The incorrect time on your phone? That is a well know issue on the internet.
Or the calculated driving time by NextGen?
On what route? Compared to? Is the route set logically or set different from the one you have in mind?
Routing is always approximately. Traffic circumstances permitting, Primo/NextGen is IMHO quite accurate. Not to the minute, but the differences between estimated time of arrival and expected time always were limited for me (and I use them for many years) and a consequence of in reality driven speed. (primo never calculates time lost at red lights, for primo it's always green light )
Are your parameters set up properly? Like driving a car while calculation is made for truck or your normal speed is set at bicycle speeds :D

Its only when i starts igo

What is? Be more precise. You are speaking in riddles.

When i starts igo many times the time of the clock is not correct. Some times its more than 2 hours different and some times day is night.

The igo clock? The device clock? And what is the device? You keep beating around the bush

The igo clock

Originally Posted by goud

The igo clock

I had similar problem years ago,I solved but now I don't remember how. In my archive I've found theese strings for sys.


[timezone]
patch_dst=1
sync_time=1
use_auto=1
sync_os_timezone=0
reset_os_timezone=0

[timezones]
use_timezone_setting_fix=1
use_new_timezone_ini=1
timezone_key="Time Zones"

Try them

i will give it a try

Igo time is determined by the time zone that is set in the regional settings and also the GPS satellites will update yhe IGO time. A GPS receiver works by measuring the time satellite signals take to arrive. This is a small fraction of a second, so the receiver's clock must be very accurate. ...........the receiver's clock is an atomic accuracy clock and will be the most accurate timepiece you own. Everything else should be set by it. As the time is calculated you cannot usually set it on the receiver, only the time zone. Time must be correct after you have a satellite lock

As in sys:


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