Problems with Continuous Tracking
The log you provided seems to indicate that you're in a stationary mode.
OK, I tried a few more things.
Disabled stop detection, then I don't see the three states on main screen as described here: https://www.traccar.org/client-configuration/
Tried also to use heartbeat, still nothing. What I see is that when I hit the continuous tracking, it immediately cuts off while the button is still in the ON state. I will see the notification about continuous tracking but then it immediately disappears.
(By the way, I was getting "Too many requests" from your web, so unable to respond immediately).
Have you actually tried to take the device for a ride or something to see what happens?
Sorry for the late reply. To clarify — yes, once I start moving it works fine, but that's not how it behaved before. Previously it would track me even while stationary.
Config I'm testing with:
- Interval: 15
- Stationary heartbeat: not sending any data regardless of the value (tried 0 and 60)
- Offline buffering: Enabled
- Stop detection: tried both Enabled and Disabled — same result either way
Stationary tracking seems broken no matter the configuration.
When previously? Which version are you comparing to?
Version 9.6.5, it worked perfectly, all version above, broken for me.
What exact configuration worked? Because some of the parameters you're talking about should have never worked. For example, heartbeat interval on most devices will be 10 minutes minimum.
- Distance: Disabled
- Interval: 15s
- Angle: Disabled
- Stationary heartbeat: 0
- Fastest interval: Disabled
- Offline buffering: Enabled
- Wake lock: Enabled
- Stop detection: Disabled (but it actually didn't matter before)
This way I have accomplished to get position every 15 seconds no matter what.
Sounds like maybe stop detection parameter stopped working.
Have you checked logs if you get into a stationary state even with it disabled?
I think I'm not getting in stationary.
03-20 21:04:26.851 DEBUG [AbstractService onDestroy]
TrackingService stopped
03-20 21:04:26.850 DEBUG [AbstractService f]
TrackingService.stopSelfResult(1): true
03-20 21:04:26.845 DEBUG [AbstractService onDestroy]
LocationRequestService stopped
03-20 21:04:26.844 DEBUG [AbstractService f]
LocationRequestService.stopSelfResult(5): true
03-20 21:04:26.718 INFO [BackgroundTaskManager$a m] stopBackgroundTask: 2
03-20 21:04:26.714 INFO [HttpService$e onResponse]
Response: 200
03-20 21:04:26.714 DEBUG [EventManager c] http
03-20 21:04:26.714 DEBUG [d0 a]
DESTROY: bf96dbac-50c1-469d-b914-b6b543247153
03-20 21:04:26.655 DEBUG [d0 first]
Locked 1 records
03-20 21:04:26.655 INFO [HttpService a]
HTTP POST: bf96dbac-50c1-469d-b914-b6b543247153
03-20 21:04:26.653 INFO [BackgroundTaskManager$a a] startBackgroundTask: 2
03-20 21:04:26.647 DEBUG [AbstractService a]
FINISH [TrackingService startId: 1, eventCount: 0, sticky: false]
03-20 21:04:26.646 DEBUG [AbstractService a]
motionchange [TrackingService startId: 1, eventCount: 1]
03-20 21:04:26.646 INFO [TrackingService l]
╔═════════════════════════════════════════════
║ TrackingService motionchange: false
╠═════════════════════════════════════════════
03-20 21:04:26.643 INFO [HttpService flush]
╔═════════════════════════════════════════════
║ HTTP Service (count: 1)
╠═════════════════════════════════════════════
03-20 21:04:26.641 DEBUG [AbstractService a]
FINISH [LocationRequestService startId: 5, eventCount: 0, sticky: false]
03-20 21:04:26.640 DEBUG [AbstractService b]
STOP [LocationRequestService startId: 5, eventCount: 1]
03-20 21:04:26.639 DEBUG [EventManager c] motionchange
03-20 21:04:26.639 DEBUG [TSGeofenceManager startMonitoringStationaryRegion]
Start monitoring stationary region (radius: 150.0m 52.3721,4.8363713 hAcc=12.584)
03-20 21:04:26.638 INFO [d0 a]
bf96dbac-50c1-469d-b914-b6b543247153
03-20 21:04:26.638 DEBUG [EventManager c] location
03-20 21:04:26.637 DEBUG [AbstractService a]
FINISH [LocationRequestService startId: 4, eventCount: 0, sticky: false]
03-20 21:04:26.634 INFO [TSLocationManager onSingleLocationResult]
MOTIONCHANGE isMoving=false df=0.0 — resetting short-term filter state
03-20 21:04:26.634 INFO [TSLocationManager onSingleLocationResult]
Acquired motionchange position, isMoving: false
03-20 21:04:26.633 DEBUG [AbstractService a]
1:2 [LocationRequestService startId: 4, eventCount: 1]
03-20 21:04:26.633 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ motionchange LocationResult: 2 (2936ms old)
╠═════════════════════════════════════════════
╟─ Location[fused 52.372100,4.836371 hAcc=12.584 et=+9d12h58m37s677ms alt=64.5999984741211
vAcc=0.88707495 vel=0.21178788 sAcc=1.5 bear=8.362612 bAcc=45.0], time: 1774037063697
03-20 21:04:26.623 INFO [LocationRequestService b]
Location availability: true
03-20 21:04:26.623 DEBUG [AbstractService a]
FINISH [LocationRequestService startId: 3, eventCount: 0, sticky: true]
03-20 21:04:26.622 DEBUG [AbstractService a]
1:2 [LocationRequestService startId: 3, eventCount: 1]
03-20 21:04:23.976 DEBUG [AbstractService onDestroy]
ActivityRecognitionService stopped
03-20 21:04:23.975 DEBUG [AbstractService f]
ActivityRecognitionService.stopSelfResult(1): true
03-20 21:04:23.958 INFO [TSScheduleManager cancelOneShot]
Cancel OneShot: TERMINATE_EVENT
03-20 21:04:23.958 DEBUG [LifecycleManager d] onWindowFocusChanged: true
03-20 21:04:23.951 DEBUG [TSLocationManagerActivity onDestroy] locationsettings
03-20 21:04:23.914 INFO [TSScheduleManager oneShot]
Scheduled OneShot: TERMINATE_EVENT in 10000ms (jobID: -1708771588)
03-20 21:04:23.913 DEBUG [LifecycleManager d] onWindowFocusChanged: false
03-20 21:04:23.882 DEBUG [TSLocationManagerActivity a] locationsettings
03-20 21:04:23.774 DEBUG [AbstractService a]
FINISH [ActivityRecognitionService startId: 1, eventCount: 0, sticky: false]
03-20 21:04:23.773 DEBUG [AbstractService a]
start [ActivityRecognitionService startId: 1, eventCount: 1]
03-20 21:04:23.773 DEBUG [ActivityRecognitionService a]
DetectedActivity [type=STILL, confidence=100]
03-20 21:04:23.753 DEBUG [AbstractService a]
FINISH [LocationRequestService startId: 2, eventCount: 0, sticky: true]
03-20 21:04:23.752 DEBUG [AbstractService a]
1:2 [LocationRequestService startId: 2, eventCount: 1]
03-20 21:04:23.752 INFO [LocationRequestService b]
Location availability: false
03-20 21:04:23.691 DEBUG [AbstractService a]
start [LocationRequestService startId: 1, eventCount: 1]
03-20 21:04:23.691 INFO [SingleLocationRequest startUpdatingLocation]
[SingleLocationRequest start, action: 1, requestId: 2]
03-20 21:04:23.691 DEBUG [AbstractService a]
FINISH [LocationRequestService startId: 1, eventCount: 0, sticky: true]
03-20 21:04:23.686 DEBUG [LocationAuthorization withPermission]
LocationAuthorization: Permission granted
03-20 21:04:23.685 DEBUG [SingleLocationRequest trySatisfyLastLocation]
╟─ age: 9426ms
╟─ maximumAge: 30000
╟─ desiredAccuracy: 20.0
╟─ meetsAccuracy: false
╟─ meetsStaleness: true
03-20 21:04:23.679 DEBUG [EventManager c] connectivitychange
03-20 21:04:23.678 DEBUG [HttpService a]
╔═════════════════════════════════════════════
║ Connectivity change: connected? true
Then what is this?
03-20 21:04:26.639 DEBUG [TSGeofenceManager startMonitoringStationaryRegion]
Start monitoring stationary region (radius: 150.0m 52.3721,4.8363713 hAcc=12.584)
OK, I'm idiot. With heartbeat 60s (or 0) and stop detection disabled, it works. Thanks!
However, I can't see notification that I'm being tracked, I think before I could. Maybe when I start moving it appears, I would need to test but then it is strange, as I'm being tracked, so I would like to see it.
I will just squeeze one question here, any plans on something like buffering positions offline and then send it to server in bulk (i.e. no real-time tracking, just tracking)?
Thanks a lot, and sorry for my stupidity.
We already have buffering. No sure I understand the question.
The switch is still green, shows that it supposed to be running.