"Phantom" coordinates with the wrong time

APanfilov

I often see an error recently: coordinates with the wrong time. The time is always about the same: 13.10(+-5min) Moscow time. If unit start moving, you start receiving notifications about the start of movement and exit-entry of their geofences. I deleted my unit and created it again. The problem is not fixed. I have the screenshots. What are your tips for solving this problem?

APanfilov

ashe

APanfilov Hello!
The message you specify in the Toolbox came at 10:12 (server.timestamp), but with an indication of the future time 13:12 (timestamp). The application works with the data that your tracker sends, if the data is sometimes sent incorrectly, then this is not related to the application.
Maybe you have a wrong timezone (it should be 0 (UTC)), or some other settings do not work correctly.

APanfilov

ashe The message you specify in the Toolbox came at 10:12 (server.timestamp), but with an indication of the future time 13:12 (timestamp)

You should see that the message “10:12″ server.timestamp(!) came between 12:57 and 12:58. Don’t you think that’s strange?

APanfilov

This problem appeared about 2 months ago. Before that, there were no problems. There were also no problems with the old version of your app. At the same time, when requesting coordinates via SMS, the time shows correctly. Can you do ignoring this error? Previously, You solved the problem of ignoring empty data.
The settings were always set to +3 UTC (and before the problem started). Now I was doing a new setting: 0 UTC. I don’t think this is a fix my problem.

ashe

APanfilov Hello!
We examined the data coming from your tracker. The message came exactly as I wrote earlier ahead of time.
This message is always generated by the tracker immediately after connection and comes first. Perhaps right after the connection, your tracker still does not have time to correctly establish communication with the satellites and does not properly take into account the time zone setting.

APanfilov

My tracker is always ON and doesn’t have sleep mode. But I noticed that when an incoming call to the tracker(for example, a SPAM-call), the GPRS disappears for a second. Is there any way to make Your service ignore this error?

ashe

APanfilov Hello!
Unfortunately, for the moment, this is not possible, since it is not directly related to the operation of the application, but to the operation of the platform that processes messages.
However, we will take into account that such a problem may arise and perhaps we can change something in the future.