[Help Wanted]: GPS stuck on for days despite being stationary with confidence of 100 in logs

[antonymikhael]

Required Reading

• Confirmed

Plugin Version

4.18.2

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

Samsung s25 Ultra, xiaomi redmi note 8 pro, Nokia 3.4, mi a1 and others

Device operating-systems(s)

Android 15, Android 11, pixel experience rom, Android 7

What do you require assistance about?

Every once in a while traccar ( which uses this library https://github.com/traccar/traccar-client ) on almost all of my Android devices whether samsung , Xiaomi, pixel experience rom, etc will end up having the gps stuck constantly on even while being stationary for days. I don't know what causes the bug but what I know is that everytime it happens the only way to fix it is to uninstall play services and clear the play store's data and uninstall traccar then re update the play store and play services and reinstalling traccar. Noting that on all devices affected they are always in highest accuracy mode. It happens after weeks so I am not sure what is the trigger honestly for the bug. This obviously leads to excessive battery usage having the gps constantly on. The logs shows activity type is still with confidence of 100 but strangely enough isMoving is set to true despite having stop detection enabled and working for weeks just fine before the issue happening. Logs are too long to paste in the logs section so will upload it and share its link directly, I have only edited the logs masking the coordinates as per the user's request. Let me know if there is anything I can provide to help you pinpoint the root cause of the issue

The traccar developer mentioned it is a bug with this library here
https://www.traccar.org/forums/topic/2-bugs-in-traccar-for-android/

[Optional] Plugin Code and/or Config

╔═════════════════════════════════════════════
║ TSLocationManager3.7.0 (444)
╠═════════════════════════════════════════════
╟─ samsung SM-S928B @ 16 (flutter)
{
  "activityRecognitionInterval": 10000,
  "allowIdenticalLocations": false,
  "authorization": {},
  "autoSync": false,
  "autoSyncThreshold": 0,
  "backgroundPermissionRationale": {
    "title": "Allow {applicationName} to access this device's location in the background",
    "message": "For reliable tracking, please enable {backgroundPermissionOptionLabel} location access.",
    "positiveAction": "Change to {backgroundPermissionOptionLabel}",
    "negativeAction": "Cancel"
  },
  "batchSync": false,
  "configUrl": "",
  "crashDetector": {
    "enabled": false,
    "accelerometerThresholdHigh": 20,
    "accelerometerThresholdLow": 4.5,
    "gyroscopeThresholdHigh": 20,
    "gyroscopeThresholdLow": 4.5
  },
  "debug": false,
  "deferTime": 0,
  "desiredAccuracy": -1,
  "desiredOdometerAccuracy": 100,
  "disableAutoSyncOnCellular": false,
  "disableElasticity": true,
  "disableLocationAuthorizationAlert": false,
  "disableMotionActivityUpdates": false,
  "disableProviderChangeRecord": false,
  "disableStopDetection": false,
  "distanceFilter": 0,
  "elasticityMultiplier": 1,
  "enableHeadless": true,
  "enableTimestampMeta": false,
  "extras": {},
  "fastestLocationUpdateInterval": 0,
  "foregroundService": true,
  "geofenceInitialTriggerEntry": true,
  "geofenceModeHighAccuracy": false,
  "geofenceProximityRadius": 1

[Optional] Relevant log output

https://wormhole.app/6YAYjO#Qn9t8eoqhHXDUJYZ6mBRQg

[christocracy]

On some devices, the play-services geofencing api is incorrectly firing an exit event on the "stationary geofence" when entering the stationary state (the 200 meter geofence the plug-in creates around the location where the device became stationary), even though the device is clearly still inside that geofence. This causes the plug-in to immediately re-enter the "moving" state.

This is a play-services bug.

GeofencingService b]
╔═════════════════════════════════════════════
║ GeofencingService: Stationary geofence EXIT
╠═════════════════════════════════════════════

The latest 5.0.0-beta version has guards against these spurious, incorrect geofence exits.

#1595

[antonymikhael]

Thanks for the response. Hopefully it will be out of beta soon

[christocracy]

Why don't you try the beta now. It's not going to come out of beta until I get feedback.

[antonymikhael]

I am not the developer of the app (traccar) and I don't have the time to build it and compile it from source myself for the time being to be honest, but hopefully soon maybe after the Christmas holidays ( Merry Christmas by the way ). However I will let the app developer know for now about it and this way we can get you the feedback needed

[christocracy]

How do you get a license key?

[antonymikhael]

I didn't. We just use the traccar client app which I am sure has the license key

[tananaev]

Yes, we have a key for Traccar Client. @christocracy where can I find Migration Guide to 5.0.0? The documentation refers to it, but I couldn't find any link.

[christocracy]

See the "Discussions" tab in this repo.

[tananaev]

For me it's failing on this:

Project with path ':background_fetch' could not be found in root project 'android'.

Migration guide doesn't mention anything about it.

[christocracy]

Custom maven urls are no longer required in android/build.gradle.

Delete them.

[antonymikhael]

I had a test device with the gps stuck on with the library's version 4.18.2 and even when uninstalling traccar and reinstalling it (the stable production version) , the moment I turn the continuous tracking on, the GPS will come on and stay on indefinitely unless I clear the play services data and so on as previously mentioned. But with this beta version. It doesn't happen. Taking into consideration that I didn't get enough time to actually test the tracking itself while moving yet to see if it still works as good. But so far looks promising in regards to that bug.