Gregorian paradox

Gregorian.info is behaving differently on this particular watch. It's a Fenix5X belonging to a yacht racing colleague who is running my raceQs app. He has reported that the app is incorrectly displaying the time.

I now have his watch in my lab and indeed it's misbehaving.

Gregorian.info is returning a time 1:22 (82 seconds) slow!

 

Here's the code:

function GPSData(positionInfo){
	   timeSecs = Position.getInfo().when.value();// work-around for 1024 GPS time issue
....


formattedReportTime = formatToReportTime(	timeSecs);


function formatToReportTime(timeSecs){
		local_TZ = 0; // so I can use local_TZ in the Engine without having to use :debug
		var timestruct = Gregorian.info((new Time.Moment(timeSecs )), Time.FORMAT_SHORT);
	  	return timestruct.hour.format("%02u")
	    	+ ":" + timestruct.min.format("%02u")
	    	+ ":" + timestruct.sec.format("%02u");		 
	}

I'm getting the GPS time with Position.getInfo()...

Then passing the timestamp to formatToReportTime.

It works fine on all my devices, in the Sim and none of my thousands of users is reporting an issue.

I thought it may have been an issue with the phone's timezone, but I  have connected the 5X to my iPhone and it's still wrong.

The watch's Settings>System>Time is set to Auto and I have run "Sync with GPS"

I have rebooted the watch.

Any suggestions?

  • Yes, from Position.

    I'm pretty certain if it was the antenna getting the wrong time (88 seconds wrong) then the location would be wrong, by hundreds of miles! But the location is correct, just the time is wrong! 

    I'm uncomfortable about going back to my colleague without a better answer.

  • you compare two different things - 2 gps samples on 2 different watches (you can assume that at one moment readings should be the same but they are probably not) so you can't excepted they will be the same

    it simply means GPS position was fetched 1:22 later on one of watch

    gps can be the same 'now' and 1:22 later if both watches are in the same place

    of course it also means GPS doesn't work the same on both devices or doesn't transmit data to ciq app the same way (2 processors on f5x makes a lot of problems - I don't remember exactly what  but I had similar issues with sensors and gps is the sensor, do maybe sensor hub bug or by design synchronisation has a lag)

  • A factory reset fixed the problem.
    I think that confirms my suspicion that the problem was a data corruption in the OS.
    The user reported that it took 5.5 hours for the sync to complete.