Arcore-android-sdk: GetRecentDevicePose failed — ARCore stopped working at all on Samsung Galaxy S8

[alekostsom]

Hello,

ARCore was working really well on my device (Galaxy S8). Last time i checked was almost 1 month ago. Today, I updated to ARCore 1.5 and all the apps that use ARCore are not working anymore. None of them. Seems that tracking never starts. I cannot see the blue point cloud dots in the sample, nor a surface is ever detected. I checked the logs with adb logcat and noticed that i am indeed getting the following error as soon as ARCore tracking launches in the app:

10-02 14:29:18.845 25027 25266 W native : pose_manager.cc:80 GetRecentDevicePose failed. generic::invalid_argument: Passed timestamp is invalid. Latest VIO t:nan, latest IMU t:nan, query t:1209.90166236

I reset to factory settings, installed ARCore again (even older versions through adb), but i am still facing the above troubles. My device's fingerprint is:
samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU4CRI5:user/release-keys

[inio]

Thanks for the report. We'll look into it.

[alekostsom]

Hi, do you have any updates on this issue?

[inio]

No, we've received a couple reports of regressions like this with 1.4 and 1.5 and we're still trying to reproduce this on our devices.

[EmmaNaty]

Hi,

I'm getting the same error but I'm testing an AR app with Motorola G6. Any news?

[Daemroot]

I received a message "failure to iniciaklize ! Your hardware does not support this application, sorry !"
I tried the app helloAR with ARcore 1.5 and Unity ver 2017_4_0. When I use Unity remote 5 everything is ok but when I try to launch helloAR direct at Samsung Galaxy S8 I received error message :-(.

[inio]

@Daemon0x0 Do you mean the Unity helloAR? If so, please post issues/questions for the Unity integration on the google-ar/arcore-unity-sdk issues board.

[Daemroot]

@inio Yes, thank you very much.

[Th3MrKill3r]

Any updates on the issue, i got last version and still crashing

[Lukasenko22]

I just bought Xiaomi POCOPHONE F1 for my project to develop ARCore app, and I got this Error too. Every time when I have this bug, device restart is needed and then ARCore is working again, but it has to be fixed, because it is really slowing me during my app development.

[inio]

@Lukasenko22 Do you have a Chinese version of the POCOPHONE F1? Only versions of this device that ship with the Play Store are supported.

[inio]

@alekostsom @Th3MrKill3r Could either of you capture a logcat from session create through to this failure?

[SyntaxError403]

Having the same issue with S9. Worked for the first run of my app then second time gave me "This Device does not support ARCore."

[Lukasenko22]

@inio I installed ARCore from Play Store, but In China, devices do not ship with the Google Play Store. I guess I dont have Chinese version, but how do I determine for sure?

[inio]

@syntax-error404 Could you file a separate issue and capture a logcat?

@Lukasenko22 What is the build fingerprint of your device? You can find this with adb shell getprop ro.build.fingerprint

[synthercat]

My Mi8 stopped working ARCore too. It happened during the production of an ARCore through Unity. Weird. Now not even the Google measure app works anymore. It can't find a ground plane.

EDIT: I just erased data+cache from the ARCore app, restarted my phone and all works fine now.

[richard3575]

We're seeing the same @alekostsom - ARCore used to work brilliantly, but now is useless.
We noticed this on Sony Xperia XZ Premium, and also on Samsung Tab S3 (both supported devices).
Xperia stopped after Android 9.0 update
Tab S3 is new and on Android 8.0 but has the same effect.

Tested using Unity HelloAR world, Ikea AR app, Google Measure app - all of them are giving very poor surface detection. Some of them will not get anything, others get something, but drift and are wildly out.

[inio]

@synthercat Probably just the restart that fixed it. We don't keep any dynamic data in the ARCore app.

@richard3575 for Sony devices watch #639. For the Tab S3, if you could report the build fingerprint (adb shell getprop ro.build.fingerprint) and capture a logcat that could be helpful.

[richard3575]

Thanks @inio for the Samsung Tab S3 this has Android 8.0.0
samsung/gts3lltexx/gts3llte:8.0.0/R16NW/T825XXU2BRG3:user/release-keys
And here's a logcat
Let me know if there's anything else you need.
logtcat.txt

[richard3575]

HI @inio any update on this issue? We have bought a Samsung Tab S3 specifically for use with ARCore as it is listed as a supported device, yet at the moment it is not functioning. We'd really appreciate an update on what the issue might be and when we can expect it to be fixed.
Let us know if there's any other information you require to help resolve the issue and we'll glad assist. Thank you

[sauldelabrida]

I had the same problem using a S7 Edge Android 8.0 and ARCore SDK 1.6 for Unity. It works changing the Unity ARCore SDK to 1.4 :)

[richard3575]

Hi @inio Happy New year and all that - any update on this issue? It's been over 3 months this issue was raised and it's still a problem. We're going to have to return the device (at cost to us) as it is not able to do what Google said it could. It would be great to get some indication if this is an ARCore issue, or an OS issue and if it's Google or Samsung - but given the wide spread issues across a range of devices I'm guessing it's a Google issue. Some confirmation of this and when we might expect a resolution would be greatly appreciated.

[richard3575]

@inio I appreciate you have a lot of issues, but we would really like and update on this one. It sounds like there’s a number of people with the same issue across flag ship Android devices. Listed devise on the Google Dev site as support ARCore are NOT working. We have provided information to you, but not heard back. We have clients waiting for apps and have purchased devices to support them. You have S9’s S8s and S3 Tabs not working – core Android devices – this feels pretty significant, yet it’s been 3 months without any clear update from Google. We respectfully request to understand if ARCore is a viable solution or not. (our next step is to return all the devices and switch to ARKit and Apple devices – which we don’t want to do!). Please can you provide an estimation on when this will be fixed. Thank you.

[fredsa]

Changing issue title to reflect that this issue is about the original pose_manager.cc:80 GetRecentDevicePose failed issue reported by @alekostsom on a Samsung Galaxy S8.

[fredsa]

@richard3575 Thank you for the logcat output. since you mentioned seeing the same issue across multiple devices (S9, S8, S3 Tab) I suspect there's an issue with the app and/or build process, rather than an ARCore platform issue.

Please try running the unmodified HelloAR sample project. When doing so:

• Download the latest ARCore for Android SDK (releases page)
• Connect an ARCore supported device
• Make sure you device is up to date (running the latest available version of the o/s)
• Verify that the latest version of ARCore is installed

If this does not work, feel free to file a new issue in this issue tracker. Please provide the requested information as defaulted in after clicking "New issue", as well as attaching the output of adb logcat when running the HelloAR sample.

[fredsa]

Closing this issue for now.
@alekostsom — if you are still seeing the pose_manager.cc:80 GetRecentDevicePose failed issues on the S8 using the latest ARCore SDK for Android, please include attach the output of adb logcat using the above steps to run an unmodified HelloAR app, and we can reopen. If you're experiencing other issues, please file a new issue.

[richard3575]

@fredsa - thanks for getting back to me Fred, I'll do as you outlined. However, just for clarity, I'm not personally seeing the issue on all the devices listed, I was referring to other peoples posts. If you look through the list of issues from myself and others it's clear there's a bigger issue across different devices where the surfaces detection just isn't working - no changes to the .apk, was working awesome, then can't find a surface at all.

Also, I can confirm that we had the same problem on a Sony ZX Premium #639 - however that is now working correctly again after a Sony update. We have the same .apk builds running on both devices.
So same .apk went in this sequence

1. Sony ZX working fine
2. .apk stopped being able to detect surfaces
3. bought Samsung S3 tab - same results as on Sony - not detecting surfaces.
4. Sony update
5. same .apk with no changes is now working very well on Sony, as it did before
6. Samsung S3 Tab .apk - still not detecting surfaces.

Reading other messages from other users this appears to be a common thing happening across a range of devices
I will continue as you suggested, but fear that the issue will still remain.

I hope that clarifies it - and if anyone else out there is experiencing anything similar, please back me up (or I'll think it's just me!)

Thanks

[alekostsom]

@fredsa - Thanks for getting back to me. Unfortunately the issue is still occuring. I run both the Google Measure app and the HelloAR sample, built with Unity. ARCore 1.6 installed:
Measure Google App-logcat.txt
HelloAR Unity build-logcat.txt

And still no other installed ARCore app is working. I guess the issue should be reopened.

Thank you.

[richard3575]

I agree with @alekostsom we're still seeing the issue. @fredsa as requested I've run the tests and created a new ticket #701 with logcat.txt
Any help would be much appreciated as it's unclear why a supported device isn't giving good results, we're now a long way behind on our development.
Thank you

[fredsa]

Note that this issue is closed. The best place to follow up is on the relevant open issue, or file a new issue if yours is related to a different device than the one covered by the issue.