Wrong data from my huawei g750

pme9 years ago

Hi Anton

Yesterday i saw that the time of the server and the time from the traccar client is very different, see data, i have this from my phone but also my tablet (nexus 7), but my wife her phone (wiko) works fine.
Any suggestions?

2016-03-09 12:28:32  INFO: [23F7A2D8] connected
2016-03-09 12:28:32 DEBUG: [23F7A2D8: 5055 < 91.180.173.111] HEX: 474554202f3f69643d3931393339382674696d657374616d703d31343537353036323236266c61743d35302e3739393530333333333333333333266c6f6e3d332e373630303136363636363636363636362673706565643d302e302662656172696e673d3234382e373230303031323230373033313326616c7469747564653d34332e3126626174743d38302e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f312e362e3020284c696e75783b20553b20416e64726f696420342e322e313b2048554157454920473730302d553130204275696c642f487561776569473730302d553130290d0a486f73743a206d65657273736368616572742e64646e732e6e65743a393635320d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a0d0a
2016-03-09 12:28:32 DEBUG: [23F7A2D8: 5055 > 91.180.173.111] HEX: 485454502f312e3120323030204f4b0d0a0d0a
2016-03-09 12:28:32  INFO: [23F7A2D8] disconnected
2016-03-09 12:28:32  INFO: [23F7A2D8] id: 4, time: Wed Mar 09 07:50:26 CET 2016, lat: 50.79950333333333, lon: 3.7600166666666666, speed: 0.0, course: 248.72000122070312

pme9 years ago

Ok got it working again , removed traccar client and reinstalled from the apk download and its working as before.

pme9 years ago

Oeps, thought it was working, look at this data, after 5 minutes its already 4 minutes behind.

2016-03-09 13:02:45  INFO: [6BC0801A] id: 4, time: Wed Mar 09 13:02:44 CET 2016, lat: 50.7995, lon: 3.759936666666667, speed: 0.0, course: 296.2900085449219
2016-03-09 13:03:35  INFO: [C9EAD0D3] id: 4, time: Wed Mar 09 13:02:50 CET 2016, lat: 50.79937333333334, lon: 3.759946666666666, speed: 1.3137086826589106, course: 292.7099914550781
2016-03-09 13:04:20  INFO: [1F4EF502] id: 4, time: Wed Mar 09 13:02:56 CET 2016, lat: 50.79936666666667, lon: 3.759895, speed: 0.0, course: 319.3500061035156
2016-03-09 13:05:07  INFO: [953D841C] id: 4, time: Wed Mar 09 13:03:02 CET 2016, lat: 50.79936666666667, lon: 3.759895, speed: 0.0, course: 319.3500061035156
2016-03-09 13:05:52  INFO: [7F8C32AA] id: 4, time: Wed Mar 09 13:03:08 CET 2016, lat: 50.799348333333334, lon: 3.759751666666667, speed: 0.0, course: 249.47999572753906
2016-03-09 13:06:38  INFO: [FA2CE0CA] id: 4, time: Wed Mar 09 13:03:14 CET 2016, lat: 50.799348333333334, lon: 3.759751666666667, speed: 0.0, course: 249.47999572753906
2016-03-09 13:07:23  INFO: [A427F8AF] id: 4, time: Wed Mar 09 13:03:19 CET 2016, lat: 50.799348333333334, lon: 3.759751666666667, speed: 0.0, course: 249.47999572753906

Anton Tananaev9 years ago

There must be some problem on the device side. Decoding works correctly as far as I can see.