Packet timestamp mismatch - Samsung A70

[roonskipp]

SPECIFIC ISSUE ENCOUNTERED

Randomly upon app start it will not launch correctly. I have tried it on a pixel 2, and it launches correctly every time, but on my Samsung A70 it randomly does not launch correctly roughly 9/10 times.

VERSIONS USED

• Android Studio: Android Studio 3.6.3 Build #AI-192.7142.36.36.6392135, built on April 14, 2020 Runtime version: 1.8.0_212-release-1586-b04 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Windows 10 10.0 GC: ParNew, ConcurrentMarkSweep Memory: 1237M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: google-sceneform-tools
• ARCore SDK for Android:
• Device manufacturer, model, and O/S:
• ARCore: Google_Play_Services_for_AR_1.17.apk

>adb shell pm dump com.google.ar.core | findstr /i "packages: versionName" Packages: versionName=1.17.200420086 Hidden system packages: versionName=0 Active APEX packages: Inactive APEX packages: Factory APEX packages:

• Output of adb shell getprop ro.build.fingerprint: adb shell getprop ro.build.fingerprint samsung/a70qeea/a70q:10/QP1A.190711.020/A705FNXXU5BTC2:user/release-keys

• Error showing in log while app is running and the error appears

  E/native: aimatter_landmarks_3Dmesh.cc:304 generic::invalid_argument: Graph has errors: 
  Packet timestamp mismatch on a calculator receiving from stream "model_select". Current minimum expected timestamp is 475890972022 but received 475890841663. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
  Packet timestamp mismatch on a calculator receiving from stream "model_select". Current minimum expected timestamp is 475890972022 but received 475890841663. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.

The error above keeps repeating for every frame.

STEPS TO REPRODUCE THE ISSUE

1. Launch app, sometimes there is a timestamp mismatch, sometimes there is not. Cannot reproduce consistently, apart from the fact that it happens roughly 9/10 times.

WORKAROUNDS (IF ANY)

Use a pixel phone instead of a Samsung A70

ADDITIONAL COMMENTS

This happens using augmented faces, front camera, trying to use the helloar sample code.

[abkoradiya]

Hi, Have you found any solutions? Same issue occurring in Redmi note 7 Pro.

[roonskipp]

Hi, Have you found any solutions? Same issue occurring in Redmi note 7 Pro.

Hi, I am sorry. I did not find a solution to this problem. I have not fiddled with google-ar since june. I never found a workaround. I am getting back into google-ar and android, this time with Unity. If I encounter the problem again and I find anything, I will update this issue. Let me know if you find a solution.

[dkmoon]

Hi, any update regarding this issue?

I tried the vanilla Augmented Face Java test app and my smartphones intermittently experience the issue. I'm testing with Redmi note 10 pro, Galaxy S8, Galaxy A32 and Galaxy J7. It seems this is issue happens regardless of smartphone model.

[roonskipp]

Hi, any update regarding this issue?

I tried the vanilla Augmented Face Java test app and my smartphones intermittently experience the issue. I'm testing with Redmi note 10 pro, Galaxy S8, Galaxy A32 and Galaxy J7. It seems this is issue happens regardless of smartphone model.

I am no longer working on this project, but I will leave the issue open in case anyone else knows a fix and wants to comment on it (or even fix it).