if upgrade traccar can solve BUG MTK 2503D ?

ghiltea 4 months ago

help can
any solve my case
if i upgrade traccar 3.6 to traccar 4.0 can solve bug MTK 2503D chip (with a built-in MT3333 positioning chip) ?
because my device posisition traccar is missing

thanks

Anton Tananaev 4 months ago

You should upgrade to 6.9.0.

Helio Soares 4 months ago

Do any of these options solve the problem? Without having to update the entire traccar?
Option 1 — Use server time
Add this to <entry key='server'>...</entry> or directly to <config>:

<entry key='location.enableServerTime'>true</entry>

This causes Traccar to ignore the device time and use the server time.

— Manual offset (if only UTC is incorrect)
Add this to traccar.xml:

<entry key='server.timeOverride'>3</entry>

This only adjusts the time zone, without affecting the coordinates.

Option 2 — Filter (Traccar 5.13+)
Add this to traccar.xml:

<entry key='location.time.override'>server</entry>

This corrects the time only for the affected devices, without affecting others.

Option 3 — Full Server Fix
Add traccar.xml:

<entry key='location.timeFix'>619315200</entry>

This automatically fixes the time of all packages on affected MTK devices.

Anton Tananaev 4 months ago

Please read the official documentation first.

Helio Soares 4 months ago

Do any of these options solve the problem? Without having to update the entire traccar?
Option 1 — Use server time
Add this to <entry key='server'>...</entry> or directly to <config>:

<entry key='location.enableServerTime'>true</entry>

This causes Traccar to ignore the device time and use the server time.

— Manual offset (if only UTC is incorrect)
Add this to traccar.xml:

<entry key='server.timeOverride'>3</entry>

This only adjusts the time zone, without affecting the coordinates.

Option 2 — Filter (Traccar 5.13+)
Add this to traccar.xml:

<entry key='location.time.override'>server</entry>

This corrects the time only for the affected devices, without affecting others.

Option 3 — Full Server Fix
Add traccar.xml:

<entry key='location.timeFix'>619315200</entry>

This automatically fixes the time of all packages on affected MTK devices.

Helio Soares 4 months ago

I'm a bit of a layman, could you point me to the link that talks about the subject? I couldn't find it.

Anton Tananaev 4 months ago