Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ArCore does not find surface any more on Moto Z2 force Android 8.0 #659

Closed
chriswattz opened this issue Dec 1, 2018 · 6 comments
Closed
Labels
bug device support questions/issues with device enablement

Comments

@chriswattz
Copy link

I bought an Motorola Z2 force to develop with ArCore. It worked for 3 Days (surface was found in seconds) , now all apps using ARCore stopped working including my Unity Apps (HelloAR) that i tested on the device. The apps do start (IKEA and others) but they do not find any surface. No error messages. The camera access for the ARcore apps are granted. Any idea why Arcore does not work any more? I reinstalled the ARCore software from App store but no change. I can see the particles very shortly coming up and disappearing but no surface found. I did not change something on the phone...what can i do ?

@chriswattz
Copy link
Author

After additional testing i think this issue is a performance problem. Is there a way to push the ARCore excecution up ? Are there any performance tools in ArCore to use the full power of the system?

@fizixman83
Copy link

fizixman83 commented Dec 4, 2018

Might be crazy, but try restarting your device and see if tracking picks up better. See: #419

@inio inio added bug device support questions/issues with device enablement labels Dec 7, 2018
@inio
Copy link

inio commented Dec 7, 2018

Thanks for the report. Could you try updating to ARCore 1.6 (released yesterday) and checking if you still see this behavior? If you are still seeing it, please respond with your build fingerprint, accessible by running adb shell getprop ro.build.fingerprint.

@chriswattz
Copy link
Author

Thanks for the advice. What i did the last days was resetting my phone (hard reset) and i recognized that first time run of an ARCore App was fine but the second run was problematic again. So i checked the App and saw that it seems to be running still (i forced quit). Tracking was a bit better but not really fast. Now i checked with ARCore 1.6 and i think it is better than before. Still i have to force quit (before restart of an ARCore app) and it is working quiet well now. I will go on testing the next days to see how it does behave.

@inio
Copy link

inio commented Jan 3, 2019

We can't attempt to reproduce without knowing what firmware you're running. Could you provide the output of adb shell getprop ro.build.fingerprint?

@devbridie
Copy link
Member

As a part of ongoing efforts to maintain ARCore repositories, I’m closing this issue as stale since it hasn’t had activity in more than 6 months. If this issue is still relevant, please feel free to file a new bug using the latest version of the SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug device support questions/issues with device enablement
Projects
None yet
Development

No branches or pull requests

4 participants