Android Mobile APP - device data refreshing problem on server 5.2
Hi,
I have had a few people mention this to me as well. If they have the traccar manager app open on their phone, minimise it and open another app for a period of time then go back to the traccar manager app none of the device positions will have updated.
They have to minimise the app and open it again and the positions will have updated.
Note then are only minimising the app not closing it from the app drawer.
good morning, this was corrected with the new update of traccar 5.5
Hi everybody!, I have my server with traccar v5.6 and I have the same problem. I attach a video of the behavior:
-I enter the app.
-A new position update appears.
-It takes 3 minutes before a new position is observed.
-In route playback shows that there were positions recorded in the previous 3 minutes (every almost 30 seconds).
Video
Any idea how to fix it?
What troubleshooting have you done? Have you checked logs? Have you checked reporting order? Have you checked timestamps? Have you checked WebSocket connection? Hopefully you did all those basic things before asking for help. Please share all the details.
Apologies in advance for not being so good at this, I have checked the logs and marked in bold where the gps id shown in the video appears (id: 9172016101). As far as I can see the coordinates are received in order although all at once from the server timestamp 2023-04-11 19:33:36. I don't know if with this you can see what is going on. I don't know how to check WebSocket connection but I will investigate if the log doesn't help yet. Thanks in advance.
...
2023-04-11 19:29:32 INFO: [T348e4e42: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303239333223
2023-04-11 19:29:32 INFO: [T348e4e42] id: 9172016101, time: 2023-04-11 19:27:55, lat: 21.14157, lon: -86.85502, course: 336.0
2023-04-11 19:29:32 INFO: [T348e4e42: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303239333223
2023-04-11 19:29:32 INFO: [T348e4e42] id: 9172016101, time: 2023-04-11 19:28:25, lat: 21.14157, lon: -86.85502, course: 336.0
2023-04-11 19:29:32 INFO: [T348e4e42: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303239333223
2023-04-11 19:29:32 INFO: [T348e4e42] id: 9172016101, time: 2023-04-11 19:28:55, lat: 21.14157, lon: -86.85502, course: 336.0
2023-04-11 19:29:32 INFO: [T348e4e42: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303239333223
2023-04-11 19:29:32 INFO: [T348e4e42] id: 9172016101, time: 2023-04-11 19:29:24, lat: 21.14157, lon: -86.85502, course: 336.0
...
2023-04-11 19:30:25 INFO: [T268cbca9: h02 < 200.68.161.163] 2a48512c393137323031363130312c56312c3030333032342c412c323130382e343934302c4e2c30383635312e333030392c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c323839343823
2023-04-11 19:30:25 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303330323523
2023-04-11 19:30:25 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:30:24, lat: 21.14157, lon: -86.85502, course: 336.0
...
2023-04-11 19:33:36 INFO: [T268cbca9: h02 < 200.68.161.163] 2a48512c393137323031363130312c56312c3030333035342c412c323130382e343934302c4e2c30383635312e333030382c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c3238393438232a48512c393137323031363130312c56312c3030333132342c412c323130382e343934302c4e2c30383635312e333030362c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c3238393438232a48512c393137323031363130312c56312c3030333135332c412c323130382e343933392c4e2c30383635312e333030362c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c3238393438232a48512c393137323031363130312c56312c3030333232332c412c323130382e343933392c4e2c30383635312e333030352c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c3238393438232a48512c393137323031363130312c56312c3030333235332c412c323130382e343933382c4e2c30383635312e333030342c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c3238393438232a48512c393137323031363130312c56312c3030333332332c412c323130382e343933392c4e2c30383635312e333030322c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c323839343823
2023-04-11 19:33:36 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303333333623
2023-04-11 19:33:36 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:30:54, lat: 21.14157, lon: -86.85501, course: 336.0
2023-04-11 19:33:36 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303333333623
2023-04-11 19:33:36 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:31:24, lat: 21.14157, lon: -86.85501, course: 336.0
2023-04-11 19:33:36 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303333333623
2023-04-11 19:33:36 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:31:53, lat: 21.14157, lon: -86.85501, course: 336.0
2023-04-11 19:33:36 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303333333623
2023-04-11 19:33:36 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:32:23, lat: 21.14157, lon: -86.85501, course: 336.0
2023-04-11 19:33:36 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303333333623
2023-04-11 19:33:36 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:32:53, lat: 21.14156, lon: -86.85501, course: 336.0
2023-04-11 19:33:36 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303333333623
2023-04-11 19:33:36 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:33:23, lat: 21.14157, lon: -86.85500, course: 336.0
...
2023-04-11 19:33:54 INFO: [T268cbca9: h02 < 200.68.161.163] 2a48512c393137323031363130312c56312c3030333335322c412c323130382e343933382c4e2c30383635312e333030332c572c3030302e30302c3333362c3132303432332c46464646424246462c3333342c30322c373733332c323839343823
2023-04-11 19:33:54 INFO: [T268cbca9: h02 > 200.68.161.163] 2a48512c393137323031363130312c56342c56312c323032333034313230303333353423
2023-04-11 19:33:54 INFO: [T268cbca9] id: 9172016101, time: 2023-04-11 19:33:52, lat: 21.14156, lon: -86.85501, course: 336.0Please don't post massive logs directly into the forum comment. It's really hard to read it.
I see in your log that the device hasn't reported for those 3 minutes, so it seems to me that your issue is with the device and it's completely unrelated to this topic.
Thank you for your help. I commented in this topic because the behavior was similar to the one posted here. It only remains to add that it was not a problem of the device either since the GPS ST-902 does not have SD slot and does not save positions, so the problem is because of the cellular network that in the area in question is not stable. Thank you very much.
Hi. This fix is not working for me. Probably the session is not closed, but I don't have enough knowledge to investigate it.
Thanks for your support anyway.