GPS Week Rollover affecting T800x and some GT02 (dates show 2006) — temporary decoder workaround

unfiltered logs as follows

oejsi.HttpChannelState$HttpChannelSerializedInvoker@5b85558d{name=HttpChannelState_writeInvoker,tail=oejut.SerializedInvoker$Link@4bb8c96d{Queued by qtp1047187138-49 at org.eclipse.jetty.server.internal.HttpChannelState$ChannelResponse.write(HttpChannelState.java:1312)[BLOCKING] -> null},invoker=null}
2025-08-20 15:22:41 DEBUG: Running oejut.SerializedInvoker$Link@4bb8c96d{Queued by qtp1047187138-49 at org.eclipse.jetty.server.internal.HttpChannelState$ChannelResponse.write(HttpChannelState.java:1312)[BLOCKING] -> null} of oejsi.HttpChannelState$HttpChannelSerializedInvoker@5b85558d{name=HttpChannelState_writeInvoker,tail=oejut.SerializedInvoker$Link@4bb8c96d{Queued by qtp1047187138-49 at org.eclipse.jetty.server.internal.HttpChannelState$ChannelResponse.write(HttpChannelState.java:1312)[BLOCKING] -> null},invoker=null}
2025-08-20 15:22:41 DEBUG: onWriteComplete(true,null) s=CLOSING,api=BLOCKED,sc=false,e=null,wb=oeju.Blocker$Shared@22ded0f3[c=null]->s=CLOSED,api=BLOCKING,sc=false,e=null,wb=oeju.Blocker$Shared@22ded0f3[c=null] c=null cb=Callback@a65124c{NON_BLOCKING, org.eclipse.jetty.ee10.servlet.ServletChannel$$Lambda/0x00007fc5747c5c80@6eedd25d,org.eclipse.jetty.ee10.servlet.ServletChannel$$Lambda/0x00007fc5747c4c00@1f35db30} w=false
2025-08-20 15:22:41 DEBUG: completed oeje10s.ServletChannelState@59a3ff83{s=HANDLING rs=COMPLETING os=OPEN is=IDLE awp=false se=false i=false al=0}
2025-08-20 15:22:41 DEBUG: Next link is null, execution is over in oejsi.HttpChannelState$HttpChannelSerializedInvoker@5b85558d{name=HttpChannelState_writeInvoker,tail=null,invoker=null}
2025-08-20 15:22:41 DEBUG: unhandle oeje10s.ServletChannelState@59a3ff83{s=HANDLING rs=COMPLETED os=OPEN is=IDLE awp=false se=false i=false al=0}
2025-08-20 15:22:41 DEBUG: nextAction(false) TERMINATED oeje10s.ServletChannelState@59a3ff83{s=IDLE rs=COMPLETED os=OPEN is=IDLE awp=false se=false i=false al=0}
2025-08-20 15:22:41 DEBUG: action TERMINATED oeje10s.ServletChannel@368c503c{s=oeje10s.ServletChannelState@59a3ff83{s=IDLE rs=COMPLETED os=OPEN is=IDLE awp=false se=false i=false al=0},r=0,c=true/false,a=IDLE,uri=http://mydomain.com:8082/api/media/7301033780/device.heic,age=28}
2025-08-20 15:22:41 DEBUG: onCompleted for /api/media/7301033780/device.heic written app=0 net=451
2025-08-20 15:22:41 DEBUG: consumeAvailable: true oejsi.HttpChannelState@4bb40539[:handling=Thread[#49,qtp1047187138-49,5,main],handled=false,send=LAST_COMPLETE,completed=true,request=GET@54475296 http://mydomain.com:8082/api/media/7301033780/device.heic HTTP/1.1] 
2025-08-20 15:22:41 DEBUG: succeeded: failure=null needLastStreamSend=false org.eclipse.jetty.server.internal.HttpChannelState$ChannelCallback@77554c68
2025-08-20 15:22:41 DEBUG: No action on succeeded org.eclipse.jetty.server.internal.HttpChannelState$ChannelCallback@77554c68
2025-08-20 15:22:41 DEBUG: !handle TERMINATED oeje10s.ServletChannel@368c503c{s=oeje10s.ServletChannelState@59a3ff83{s=IDLE rs=COMPLETED os=COMPLETED is=IDLE awp=false se=false i=false al=0},r=0,c=true/true,a=IDLE,uri=http://mydomain.com:8082/api/media/7301033780/device.heic,age=29}
2025-08-20 15:22:41 DEBUG: handler invoked: completeStream=true failure=null callbackCompleted=true oejsi.HttpChannelState@4bb40539[:handling=null,handled=true,send=LAST_COMPLETE,completed=true,request=GET@54475296 http://mydomain.com:8082/api/media/7301033780/device.heic HTTP/1.1]
2025-08-20 15:22:41 DEBUG: stream=org.eclipse.jetty.session.AbstractSessionManager$SessionStreamWrapper@69ed5524, failure=null, callbackCompleted=true, completeStream=true
2025-08-20 15:22:41 DEBUG: completeStream(org.eclipse.jetty.session.AbstractSessionManager$SessionStreamWrapper@69ed5524, null)
2025-08-20 15:22:41 DEBUG: Complete called with session oejs.ManagedSession@36a8e808{id=node01b6o8twc2v6b111kenqzjecloc1,x=node01b6o8twc2v6b111kenqzjecloc1.node0,req=1,res=true}
2025-08-20 15:22:41 DEBUG: Session node01b6o8twc2v6b111kenqzjecloc1 complete, active requests=0
2025-08-20 15:22:41 DEBUG: Session node01b6o8twc2v6b111kenqzjecloc1 is immortal && no inactivity eviction
2025-08-20 15:22:41 DEBUG: Not starting timer for session node01b6o8twc2v6b111kenqzjecloc1
2025-08-20 15:22:41 DEBUG: Store: id=node01b6o8twc2v6b111kenqzjecloc1, mdirty=true, dirty=false, lsave=1755692405077, period=0, elapsed=156449
2025-08-20 15:22:41 DEBUG: Non passivating SessionDataStore, session in SessionCache only id=node01b6o8twc2v6b111kenqzjecloc1
2025-08-20 15:22:41 DEBUG: succeeded org.eclipse.jetty.server.internal.CompletionStreamWrapper@69121d7e
2025-08-20 15:22:41 DEBUG: recycle oeje10s.HttpInput@393724005 cs=oeje10s.ServletChannelState@59a3ff83{s=IDLE rs=COMPLETED os=COMPLETED is=IDLE awp=false se=false i=false al=0} cp=org.eclipse.jetty.ee10.servlet.BlockingContentProducer@71ece002 eof=true
2025-08-20 15:22:41 DEBUG: recycling org.eclipse.jetty.ee10.servlet.BlockingContentProducer@71ece002
2025-08-20 15:22:41 DEBUG: recycling oeje10s.AsyncContentProducer@1fd1df4b[c=null]
2025-08-20 15:22:41 DEBUG: recycle oeje10s.ServletChannelState@59a3ff83{s=IDLE rs=COMPLETED os=COMPLETED is=IDLE awp=false se=false i=false al=0}
2025-08-20 15:22:41 DEBUG: succeeded oejsi.HttpConnection@2ce257b0::oeji.SocketChannelEndPoint@4d62da4b[{l=/192.168.1.8:8082,r=/XX.XX.XX.XX:56977,OPEN,fill=-,flush=-,to=7/30000}{io=0/0,kio=0,kro=1}]->[oejsi.HttpConnection@2ce257b0[p=oejh.HttpParser{s=END,0 of -1},g=oejh.HttpGenerator@10df25eb{s=END}]=>oejsi.HttpChannelState@4bb40539[:handling=null,handled=true,send=LAST_COMPLETE,completed=true,request=GET@54475296 http://mydomain.com:8082/api/media/7301033780/device.heic HTTP/1.1]]

I don't know if it's a joke, but I obviously expect logs at the standard level.

for sure it is a device side issue , but I was asking if you know the fix as multiple peoples experience the same issue.
below are the logs you asked for (I guess)

2025-08-20 15:50:09  INFO: [Taa3299a0: h02 < 37.186.33.156] *HQ,7301033850,V1,124914,V,2515.0983,N,05125.6788,E,000.00,000,200825,FFFFFBFF,427,02,0,0,6#
2025-08-20 15:50:09  INFO: [Taa3299a0: h02 > 37.186.33.156] *HQ,7301033850,V4,V1,20250820125009#
2025-08-20 15:50:09  INFO: Event id: 7301033850, time: 2025-08-20 15:50:09, type: deviceOnline, notifications: 0
2025-08-20 15:50:10  INFO: [Taa3299a0: h02 < 37.186.33.156] *HQ,7301033850,V1,124915,V,2515.0983,N,05125.6788,E,000.00,000,200825,FFFFFBFF,427,02,0,0,6#
2025-08-20 15:50:10  INFO: [Taa3299a0: h02 > 37.186.33.156] *HQ,7301033850,V4,V1,20250820125010#
2025-08-20 15:50:13  INFO: [Taa3299a0] id: 7301033850, time: 2025-08-20 15:49:14, lat: 25.25164, lon: 51.42798, course: 0.0
2025-08-20 15:50:14  INFO: [Taa3299a0] id: 7301033850, time: 2025-08-20 15:49:15, lat: 25.25164, lon: 51.42798, course: 0.0
2025-08-20 15:50:25  INFO: [Tb9f926a5] connected
2025-08-20 15:50:25  INFO: [Tb9f926a5: h02 < 212.70.112.47] *HQ,7301033885,V1,125019,A,2517.4702,N,05124.9923,E,000.00,000,040106,FFFFFBFF,427,02,0,0,6#
2025-08-20 15:50:26  INFO: [Tb9f926a5: h02 > 212.70.112.47] *HQ,7301033885,V4,V1,20250820125026#
2025-08-20 15:50:26  INFO: Event id: 7301033885, time: 2025-08-20 15:50:26, type: deviceOnline, notifications: 0
2025-08-20 15:50:26  INFO: [Tb9f926a5: h02 < 212.70.112.47] *HQ,7301033885,V1,125020,A,2517.4702,N,05124.9923,E,000.00,000,040106,FFFFFBFF,427,02,0,0,6#
2025-08-20 15:50:26  INFO: [Tb9f926a5: h02 > 212.70.112.47] *HQ,7301033885,V4,V1,20250820125026#
2025-08-20 15:50:27  INFO: [Tb9f926a5: h02 < 212.70.112.47] 2473010338851250210401062517470206051249923e000000fffffbffff00140a00015ae301ab0200000000008700
2025-08-20 15:50:30  INFO: [Taa3299a0: h02 < 37.186.33.156] *HQ,7301033850,V1,124935,V,2515.0983,N,05125.6788,E,000.00,000,200825,FFFFFBFF,427,02,0,0,6#
2025-08-20 15:50:30  INFO: [Taa3299a0: h02 > 37.186.33.156] *HQ,7301033850,V4,V1,20250820125030#
2025-08-20 15:50:30  INFO: Skipping notifications for old event
2025-08-20 15:50:30  INFO: [Tb9f926a5] id: 7301033885, time: 2025-08-20 15:50:19, lat: 25.29117, lon: 51.41654, course: 0.0
2025-08-20 15:50:31  INFO: [Tb9f926a5] id: 7301033885, time: 2025-08-20 15:50:20, lat: 25.29117, lon: 51.41654, course: 0.0
2025-08-20 15:50:32  INFO: [Tb9f926a5] id: 7301033885, time: 2025-08-20 15:50:21, lat: 25.29117, lon: 51.41654, course: 0.0
2025-08-20 15:50:34  INFO: [Taa3299a0] id: 7301033850, time: 2025-08-20 15:49:35, lat: 25.25164, lon: 51.42798, course: 0.0
2025-08-20 15:50:43  INFO: [Tb9f926a5: h02 < 212.70.112.47] *HQ,7301033885,V19,125036,A,2517.4702,N,05124.9923,E,000.00,000,040106,,,8942702111601138093F,FFFFFBFF#
2025-08-20 15:50:47  INFO: [Tb9f926a5] id: 7301033885, time: 2025-08-20 15:50:43, lat: 25.29117, lon: 51.41654, course: 0.0
2025-08-20 15:50:55  INFO: [Tb9f926a5: h02 < 212.70.112.47] 2473010338851250490401062517470206051249923e000000fffffbffff00140a00015ae301ab0200000000008801
2025-08-20 15:50:59  INFO: [Tb9f926a5] id: 7301033885, time: 2025-08-20 15:50:49, lat: 25.29117, lon: 51.41654, course: 0.0
2025-08-20 15:51:25  INFO: [Tb9f926a5: h02 < 212.70.112.47] 2473010338851251190401062517470206051249923e000000fffffbffff00150a00015ae301ab0200000000008902
2025-08-20 15:51:29  INFO: [Tb9f926a5] id: 7301033885, time: 2025-08-20 15:51:19, lat: 25.29117, lon: 51.41654, course: 0.0
2025-08-20 15:51:55  INFO: [Tb9f926a5: h02 < 212.70.112.47] 2473010338851251490401062517470206051249923e000000fffffbffff001f0a00015ae301ab0200000000008a03
2025-08-20 15:51:59  INFO: [Tb9f926a5] id: 7301033885, time: 2025-08-20 15:51:49, lat: 25.29117, lon: 51.41654, course: 0.0
2025-08-20 15:52:02  INFO: [Taa3299a0: h02 < 37.186.33.156] 2473010338501251082008252515098306051256788c000000fffffbffff00180a0001a3a701ab0200000000007a2a
2025-08-20 15:52:06  INFO: [Taa3299a0] id: 7301033850, time: 2025-08-20 15:51:08, lat: 25.25164, lon: 51.42798, course: 0.0

OK, so the summary is that the location is updated correctly in Traccar. It's just the device reports the same coordinates. I don't think we can do anything about that on the server side.

Hi Bro
Before the GPS week rollover, there were no issues. Does this mean the device can no longer obtain accurate location?

It's very possible.

@Richard let me know if you find a solution at any time, I now tried to send restart command to my devices and it sends updated coordinate the first time then repeat the same coordinate with new time .

@Sulfy I just found the solution, and it's quite simple. Enable sensors for devices with the GT06 protocol, such as SENSOR,xx,xx,xx#, and other protocol devices that are experiencing a stop reporting. I used this method, and it worked.

@ Richard can you guide me how you did it?
my device responded as follows for the command
status#

BAT:6, GPRS:1, GSM:2,GPS:0,ACC:0,oil:0,Power:1,S:0

help me if you have any fix

@sulfy Which device are you using?

please see the attached

This device is still experiencing issues after GPS week rollover. Btw so that there is no confusion, my name is now Richard ID, because another Richard is also here

I have attached the response from device for SMS commands too for better understanding , I have around 10 Devices all experiencing the same and all reporting a location once (sometimes) the device is restarted then keep sending the same

I get one successful location update to my server when I send begin123456 to the device