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

Device calibration unavailable #14

Closed
ArthurSav opened this issue Aug 30, 2017 · 8 comments
Closed

Device calibration unavailable #14

ArthurSav opened this issue Aug 30, 2017 · 8 comments

Comments

@ArthurSav
Copy link

I have galaxy s8+(G955F) and i get this message "Device calibration unavailable".
What exactly is lacking from the other s8 devices?

@xiazdong
Copy link

You can see SupportedDevices.deviceCalibrationAvailable()

@jguomoto
Copy link
Contributor

@ArthurSav Your device's SKU is not on the supported device list. We only support certain SKUs of Galaxy devices.

@ArthurSav
Copy link
Author

Well what do you know, someone stripped the device check and it works.
https://github.com/tomthecarrot/arcore-for-all

@jguomoto
Copy link
Contributor

I just wanted to mention that you may encounter drastic motion tracking quality degrading if you run ARCore on currently unsupported device.

@janerivi
Copy link

I used th arcore-for-all and .. it works, but with frequent catastrophic drift of planes/anchors. If I don't continously observe the same area where the anchor or plane was registered and at similar angle it tends to be unstable and you will frequently see that the anchors or planes slides away form you. I would assume an employe at google could fix this for S8+ by spending a few minutes settings a handful of parameters for camera lens distortion of S8+ that may differ slightly from the supported S8. And then Google could add it to the list of supported devices... Why not add support for different devices incrementally instead of postponing to the official 1.0 launch?

@inio
Copy link

inio commented Dec 15, 2017

Duplicate of #89

@inio inio marked this as a duplicate of #89 Dec 15, 2017
@aakhans
Copy link

aakhans commented Feb 14, 2018

i am still getting Device calibration unavailable on my S8+,
when i look into the code it turns out that my build.fingerprint is samsung/dream2ltexx/dream2lte:7.0/NRD90M/G955FXXU1AQJ5:user/release-keys which is some thing not expected by HellorAR code, it should be some thing containing dreamqlteue ?? when we suppose to get an update build for that -- although S8+ is on supported device list - my device model is SM-G955F https://developers.google.com/ar/discover/

@inio
Copy link

inio commented Feb 20, 2018

That is rather odd. I see "samsung/dream2ltexx/dream2lte:7" in our calibration database prior to the DP2 branch. Are you sure you're using DP2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants