No synchronization with the client 5.15

Emeric V6 years ago

Hello!

After an upgrade to the last version (5.15), the Android client doesn't synchronize the position any more and still blocked on the step "Network online".
After an downgrade to the version 5.14 I have "Localization up to date" as expected

Anton Tananaev6 years ago

Check troubleshooting guide. If it doesn't help, you need to provide some more information. Just saying that it doesn't work is not enough to determine what your problem is.

Emeric V6 years ago

With adb logcat and the version 5.14:

10-28 22:34:48.587 13545 13545 I TrackingService: service create
10-28 22:34:48.605 13545 13545 D TrackingController: read
10-28 22:34:48.632 13545 13545 I NetworkManager: network on
10-28 22:34:48.710 13545 13545 I PositionProvider: location new
10-28 22:34:48.713 13545 13545 D TrackingController: write (id:0 time:1540762488 lat:XX.XXXXXXX lon:XX.XXXXXXX)
10-28 22:34:48.766 13545 13545 D TrackingController: read
10-28 22:34:48.787 13545 13545 D TrackingController: send (id:424 time:1540762488 lat:XX.XXXXXXX lon:XX.XXXXXXX)
10-28 22:34:48.916 13545 13545 D TrackingController: delete (id:424 time:1540762488 lat:XX.XXXXXXX lon:XX.XXXXXXX)
10-28 22:34:48.934 13545 13545 D TrackingController: read

It's OK

and now with the version 4.15

10-28 22:38:18.728 14983 14983 I TrackingService: service create
10-28 22:38:18.757 14983 14983 D TrackingController: read
10-28 22:38:18.785 14983 14983 I NetworkManager: network on

but no position sent...

With the version 5.15 there are this lines in addition:

10-28 22:37:49.082 14983 15002 I FA      : App measurement is starting up, version: 13001
10-28 22:37:49.082 14983 15002 I FA      : To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
10-28 22:37:49.082 14983 15002 I FA      : To enable faster debug mode event logging run:
10-28 22:37:49.082 14983 15002 I FA      :   adb shell setprop debug.firebase.analytics.app org.traccar.client
10-28 22:37:49.267 14983 15010 D ApplicationLoaders: ignored Vulkan layer search path /data/app/com.google.android.gms-2/lib/arm64:/data/app/com.google.android.gms-2/base.apk!/lib/arm64-v8a for namespace 0x7f8e8870f0
10-28 22:37:49.437 14983 15007 W art     : Long monitor contention with owner Answers Events Handler1 (15010) at boolean android.os.BinderProxy.transactNative(int, android.os.Parcel, android.os.Parcel, int)(Binder.java:-2) waiters=0 in io.fabric.sdk.android.services.common.AdvertisingInfo io.fabric.sdk.android.services.common.IdManager.getAdvertisingInfo() for 416ms
10-28 22:37:49.438 14983 15014 W art     : Long monitor contention with owner Answers Events Handler1 (15010) at boolean android.os.BinderProxy.transactNative(int, android.os.Parcel, android.os.Parcel, int)(Binder.java:-2) waiters=1 in io.fabric.sdk.android.services.common.AdvertisingInfo io.fabric.sdk.android.services.common.IdManager.getAdvertisingInfo() for 413ms
10-28 22:37:49.488 14983 15007 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
10-28 22:37:50.109 14983 15017 W art     : Long monitor contention with owner Measurement Worker (15002) at long com.android.org.conscrypt.NativeCrypto.RSA_generate_key_ex(int, byte[])(NativeCrypto.java:-2) waiters=0 in com.google.firebase.iid.zzar com.google.firebase.iid.zzaq.zzc(java.lang.String, java.lang.String, java.lang.String) for 793ms
10-28 22:37:50.921 14983 15017 D FirebaseInstanceId: topic sync succeeded
Anton Tananaev6 years ago

If you don't see location update on the status screen it means that your device doesn't report location. What accuracy are you using?

Emeric V6 years ago

with adb shell setprop log.tag.FA VERBOSE:

10-28 22:46:13.543 15944 15963 V FA      : Collection enabled
10-28 22:46:13.543 15944 15963 V FA      : App package, google app id: org.traccar.client, 1:39016471396:android:b1c7194c699bfa25
10-28 22:46:13.545 15944 15963 I FA      : App measurement is starting up, version: 13001
10-28 22:46:13.545 15944 15963 I FA      : To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
10-28 22:46:13.545 15944 15963 I FA      : To enable faster debug mode event logging run:
10-28 22:46:13.545 15944 15963 I FA      :   adb shell setprop debug.firebase.analytics.app org.traccar.client
10-28 22:46:13.545 15944 15963 D FA      : Debug-level message logging enabled
10-28 22:46:13.553 15944 15963 V FA      : Persisting first open: 1540763173302
10-28 22:46:13.633 15944 15963 V FA      : Updating deferred analytics collection: false
10-28 22:46:13.682 15944 15971 D ApplicationLoaders: ignored Vulkan layer search path /data/app/com.google.android.gms-2/lib/arm64:/data/app/com.google.android.gms-2/base.apk!/lib/arm64-v8a for namespace 0x7f8e8870f0
10-28 22:46:13.866 15944 15975 W art     : Long monitor contention with owner Answers Events Handler1 (15971) at boolean android.os.BinderProxy.transactNative(int, android.os.Parcel, android.os.Parcel, int)(Binder.java:-2) waiters=0 in io.fabric.sdk.android.services.common.AdvertisingInfo io.fabric.sdk.android.services.common.IdManager.getAdvertisingInfo() for 380ms
10-28 22:46:13.866 15944 15965 W art     : Long monitor contention with owner Answers Events Handler1 (15971) at boolean android.os.BinderProxy.transactNative(int, android.os.Parcel, android.os.Parcel, int)(Binder.java:-2) waiters=1 in io.fabric.sdk.android.services.common.AdvertisingInfo io.fabric.sdk.android.services.common.IdManager.getAdvertisingInfo() for 374ms
10-28 22:46:13.920 15944 15965 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
10-28 22:46:14.125 15944 15963 V FA      : Checking service availability
10-28 22:46:14.143 15944 15963 V FA      : Service available
10-28 22:46:14.143 15944 15963 V FA      : Setting useService: true
10-28 22:46:14.151 15944 15963 V FA      : Connecting to remote service
10-28 22:46:14.236 15944 15963 V FA      : Connection attempt already in progress
10-28 22:46:14.236 15944 15963 D FA      : Connected to remote service
10-28 22:46:14.239 15944 15963 V FA      : Processing queued up service tasks: 2
10-28 22:46:15.281 15944 15944 W art     : Before Android 4.1, method android.graphics.PorterDuffColorFilter android.support.graphics.drawable.VectorDrawableCompat.updateTintFilter(android.graphics.PorterDuffColorFilter, android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would have incorrectly overridden the package-private method in android.graphics.drawable.Drawable
10-28 22:46:15.283 15944 15944 V FA      : onActivityCreated
10-28 22:46:15.446 15944 15963 I FA      : Tag Manager is not found and thus will not be used
10-28 22:46:15.480 15944 15979 D FirebaseInstanceId: topic sync succeeded
10-28 22:46:15.489 15944 15963 D FA      : Logging event (FE): screen_view(_vs), Bundle[{firebase_event_origin(_o)=auto, firebase_screen_class(_sc)=MainActivity, firebase_screen_id(_si)=5218507939479353951}]
10-28 22:46:15.499 15944 15995 I Adreno  : QUALCOMM build                   : 8209866, I528a81912f
10-28 22:46:15.499 15944 15995 I Adreno  : Build Date                       : 04/01/17
10-28 22:46:15.499 15944 15995 I Adreno  : OpenGL ES Shader Compiler Version: XE031.14.00.02
10-28 22:46:15.499 15944 15995 I Adreno  : Local Branch                     :
10-28 22:46:15.499 15944 15995 I Adreno  : Remote Branch                    :
10-28 22:46:15.499 15944 15995 I Adreno  : Remote Branch                    :
10-28 22:46:15.499 15944 15995 I Adreno  : Reconstruct Branch               :
10-28 22:46:15.503 15944 15995 I Adreno  : PFP: 0x005ff087, ME: 0x005ff063
10-28 22:46:15.506 15944 15995 I OpenGLRenderer: Initialized EGL, version 1.4
10-28 22:46:15.506 15944 15995 D OpenGLRenderer: Swap behavior 1
10-28 22:46:15.856 15944 15963 V FA      : Activity resumed, time: 2514401051
10-28 22:46:20.861 15944 15963 V FA      : Inactivity, disconnecting from the service
10-28 22:46:24.317 15944 15944 I TrackingService: service create
10-28 22:46:24.347 15944 15944 D TrackingController: read
10-28 22:46:24.374 15944 15944 I NetworkManager: network on
10-28 22:46:25.868 15944 15963 V FA      : Session started, time: 2514411495
10-28 22:46:25.889 15944 15963 D FA      : Setting user property (FE): _sid
10-28 22:46:25.957 15944 15963 V FA      : Connecting to remote service
10-28 22:46:25.976 15944 15963 D FA      : Logging event (FE): session_start(_s), Bundle[{firebase_event_origin(_o)=auto, firebase_screen_class(_sc)=MainActivity, firebase_screen_id(_si)=5218507939479353951}]
10-28 22:46:26.028 15944 15963 V FA      : Connection attempt already in progress
10-28 22:46:26.031 15944 15963 D FA      : Connected to remote service
10-28 22:46:26.033 15944 15963 V FA      : Processing queued up service tasks: 2
10-28 22:46:31.104 15944 15963 V FA      : Inactivity, disconnecting from the service
Emeric V6 years ago

The accuracy is Medium (same accuracy for the tests with the version 5.14 and 5.15)

Emeric V6 years ago

With the version 5.15: with the Low accuracy I have the same result.

Anton Tananaev6 years ago

It might work differently on new version. Medium now only uses network location provider. Is it enabled in settings?

Emeric V6 years ago

On the authorization list, I have the two: approximative (Network) and precise (GPS)
On the global settings: I have selected "High precision" (containing GPS, Nework mobile, WiFi, etc...)

Anton Tananaev6 years ago

For some reason your Android system doesn't provide network location. I can only guess why. It can be anything from lack of network connection to disabled provider in general (e.g. you haven't accepted it somewhere in terms and conditions).

Bruce H6 years ago

I'm experiencing the same problem. I just installed Traccar to try it out. I have version 5.15 running on a Sony Xperia Z3+ with Android 7.1.1. The client never sends an update. I've been trying since last night. I have my location settings on "Precise". The update interval in the client is 120 seconds. I've been not only indoors, but outside driving around where I checked and I definitely had a GPS fix. The status page of the app simply has "Server started" and "Network is online" and never anything else. The server is running and I've tested it using Postman to hit it and I get the hex info for a bad request, but nothing ever gets logged from the client.

I checked the settings for the Traccar client app and it has permissions for location.

Anton Tananaev6 years ago

Have you followed client troubleshooting guide?

Bruce H6 years ago

Yes. All items checked and verified. Traccar client was not added to the exceptions for the battery optimization, so I added it. But I also did not have any of the battery optimizations on (for Sony it's Stamina and Ultra Stamina modes). I rebooted the phone, made sure I had a solid GPS fix, but still no attempted updates by the Traccar client.

Anton Tananaev6 years ago

Not sure what else could be the problem. All the common issues are included in the troubleshooting. If it doesn't work, it means that the OS just doesn't provide location updates to the app for some reason.

Bruce H6 years ago

The OP said that his problem was with only version 5.15. He said if he downgraded to 5.14 it worked again. Unfortunately, I don't have version 5.14 to test or I would do try the same. Is it possible for me to get a copy of the 5.14 apk and I can try it. If it works, then that would verify that something between the two versions is causing the issue.