Traccar Client 9.4.1

A new version is out. It's available to download as an APK, but should also be available on Google Play and App Store soon.

This version basically brings back an option for very accurate reporting at the expense of battery life. When you select "highest" accuracy, Traccar Client will keep GPS always on (except when stationary). And it also includes the distance/interval/angle configuration, like the old app.

There are some other small fixes, like filtering too frequent updates. Also localization updates.

Please try and provide feedback. Hopefully basic tracking works well for most people and we can move on to actually adding new features.

Many thanks Anton.

Hi Anton, I would like to inform you that this latest version 9.4.1 of Traccar Client is excellent, in my case it is extremely reliable. The many configurations make it very flexible and should meet many scenarios. Thank you and good luck!

Tested 9.4.0, worked the whole evening yesterday.

Sending a Datapoint almost every second, used as much battery as usual, no complaints.

Will use 9.4.1 from now on, and report back if i notice something.

Good evening, I installed the latest version, 9.4.1.
Everything works, I will test it tomorrow to use the battery.

One problem - the phone's battery level, altitude are not transmitted to the server. Android. All permissions are given. On the old version (7) everything was transmitted.

Another question.
What is the idle time interval?
Am I right in thinking that after a specified time the app will go into idle mode and use less battery?

https://www.traccar.org/client-configuration/

Hi, I have also tested the new 9.4.1 version but speed register still doesn't work. Have you any plans to solve this issue? Thanks a lot for all your work Anton.

What speed register?

Hello Anton, today I did test drives with Traccar-Client 9.4.1 with different settings (interval and angle 0, heartbeat 300s, offline, WakeLock and stop always on).

1. position highest, distance 20m, fastest interval 30s
   This gives the best results, update interval between 1-2s, matching the speed ridden. Fastest interval seems to have no influence.
2. position high, the rest as point 1
   There is a new position every 54s regardless of the speed. Driven speeds between 0 and 100 km/h. Quite implausible at a maximum of 27 m/s, the interval here should also be 1-2 seconds. Perhaps twice as much due to the lower accuracy.
3. position high, distance again 20m but fastest interval 5s
   Here the interval is considerably reduced. Speed (0 - 140km/h) 80% every 5s, the rest an update every 10s.
4. distance 50m, the rest like Pos 3
   Update almost 100% after 18s. Speeds between 0 and 180km/h (up to 50m/s so theoretically an update is necessary every second)

How does the fastest interval work?
respectful René

Translated with DeepL.com (free version)

If we to follow strictly to GPS hardware trackers default recommended setup parameters should be as follows ... Distance (Meters) 1 for sensing movement or move mode. Stationary heartbeat (seconds) 300 or 5 minutes. Fastest interval (seconds) 10 , nothing less that it else undesireable results. Which is microcontroller hangs and goes to cordinates 0:0. That is my observation study and usage of hardware gps trackers behaviour for serveral years now.

How does the fastest interval work?

If you select highest accuracy, we completely ignore fastest interval. With other accuracy we pass it to the SDK, which passes it to Google. How Google uses it internally is not super clear, but this is what their documentation says:

https://developers.google.com/android/reference/com/google/android/gms/location/LocationRequest.Builder#setMinUpdateIntervalMillis(long)

With the previous app, all the positions sent to server had a speed attached. Even with the latest improvements on server visualization, when a rute report was generated, the speed was represented by a color gradient on every point represented on the polygon. Now, every point on the report has a 0 km/h attached, so the color of the line in the report is completely black. Did I explain myself? Thank you very much in advance.

This is the JSON that client 9.4.1 sent using a Samsung phone:

{
	"location":
	{
		"timestamp":"2025-06-19T09:39:50.931Z",
		"coords":
		{
			"latitude":-6.xxxxxxx,
			"longitude":106.xxxxxxx,
			"accuracy":4.24,
			"speed":0.32,
			"heading":1.63,
			"altitude":21.8
		},
		"is_moving":true,
		"odometer":246471.9,
		"battery":
		{
			"level":0.58,
			"is_charging":false
		},
		"activity":
		{
			"type":"walking"
		},
		"extras":
		{
		},
		"_":"&id=xxxxxxxxx&lat=-6.xxxxxxx&lon=106.xxxxxxx&timestamp=2025-06-19T09:39:50.931Z&"
	},
	"device_id":"xxxxxxxxx"
}

The speed indeed exist there. It's now in meter per second instead of km/h as on the old client. If you're using proprietary backend like me, you need to adjust or convert its value.

Thank you very much for your response Buaya! Could you please tell me where can I modify that on the server?