Ian Muldoon

Good catch. At least we should return UNKNOWN_TIMED_OUT after a while. Under the hood, our compatibility check works by checking for the visibility of ARCore itself. Without a signed-in account,...

In general the checkAvailability() API should not produce any user-facing side-effects except for enabling AR-entering user interface elements when the device is supported. The additional state is provided to provide...

Thanks for the feature request. That does sound useful.

Indeed, that's a really neat feature, isn't it? It's among the many potential additions we're looking at.

That sounds like a pretty reasonable request. I've recorded it.

Sorry, none of those are supported with the developer preview.

@Thaina: Right now we can't commit to supporting any specific devices other than the Google Pixels and some models of the Samsung S8.

@wynwas4 Currently the Play store only offers a pre-DP2 version of ARCore for Pixel devices running O MR1 to support AR Stickers. For development with ARCore DP2, all developers (including...

ARCore 1.0 released today now supports (newly supported devices in bold): * Google’s Pixel, Pixel XL, Pixel 2 and Pixel 2 XL * Samsung’s Galaxy S8, **S8+, Note8, S7 and...

@KnIfER What is your device fingerprint? Capture it with: adb shell getprop ro.build.fingerprint Posted this as a separate issue #197. Respond either there or here.