Maybe it's something similar to this:
https://www.traccar.org/forums/topic/new-app-a-catastrophe/#post-111659
I've just switched off the WiFi (which also uses IPv6) and the phone is now on 5G. I've tapped on "Send location" several times over the past few minutes, and when looking at the log in the app I see:
Aquired current position
INSERT: <random guid>
HTTPService is busy with an existing request
....
Location[fused <coordinates>
....
Aquired current position
INSERT: <random guid>
HTTPService is busy with an existing request
....
Then a bit further down:
HTTP service (count: 7)
Locked 1 records
HTTP POST: <random guid>
Yet I look at the Traccar web interface and it shows the device last updated 22 minutes ago.
The Traccar server's domain name is only available via IPv4, I will try creating an AAAA DNS record since the server does accept IPv6 connectivity.
There's definitely something strange going on though, it worked flawlessly before the client update.
Do you see location upload timeouts?
Also can you try with another server? For example one of the demo servers.
I did see one timeout, but I suspect that was due to very low 5G signal inside the house. The other 3 times I tapped 'send location' there was no timeout.
Just tried a demo server and saw no differences in behaviour (while at home) but will try testing it when the device is moving around more. Another thing I'll do is watch the server logs when I know the device is moving, so I can get a better idea of what is going on.
The entire days history of movements is perfect during playback, but as I mentioned previously - when the device is actively moving, it shows up in the web interface as "4 hours ago" and often the last position reported was here at home, when the device is easily 15km away from here.
That's kind of what is making me think that the device is saving the history offline and then uploading it all in one hit when it gets back in WiFi range at home.
I have two Android handsets, both running Traccar Client version 9.4.3 from the Play Store.
One is a Google Pixel 9 Pro XL and the other a Samsung S24 Ultra.
The settings are identical on each app. I also went into the logs and tapped the share icon and emailed myself the logs, then compared them side by side in Notepad++. Both are identical other than the device type, ID and odometer.
The Samsung does not seem to update when it's away from home, it can go several hours without any location update showing up in the Traccar web interface. However it seems when the device is at home connected to WiFi, it checks in and uploads everything. I can see where the device has been all through the day by looking at the replay history. The device has full internet access via 4G/5G so there is no issues with the internet connection.
The Pixel is fine and it sends regular heartbeats. When I check the server logs, I don't see any heartbeats coming from the Samsung at all. The server was recently updated to 6.7.3.
It seems really strange, the permissions are set the same on both devices to allow the app to run in the background. I'm really not sure what else I can check from here. Would providing more app or server logs be useful?