Arcore-android-sdk: Exception running helloAR_java on OnePlus 5 ONEPLUS A5000

Created on 24 Feb 2018  路  8Comments  路  Source: google-ar/arcore-android-sdk

Hello, I built and try to run the helloAR_java project on my oneplus 5
ONEPLUS A5000(a supported device), but it displayed a "device unsupported" message. I looked into the code and find the exception with adb. Please help!

02-23 15:51:23.029 14916 14928 W native : helpers.cc:890 Property calibration_cad is not defined.
02-23 15:51:23.030 14916 14928 E native : device_profile_database_helpers.cc:134 Device profile for OnePlus/OnePlus5/OnePlus5:8.0.0/OPR6.170623.013/01120216:user/release-keys does not exist in /data/user/0/com.google.ar.core/files/device_profile_database
02-23 15:51:23.030 14916 14928 E native : calibration_jni.cc:74 No device profile available for build fingerprint OnePlus/OnePlus5/OnePlus5:8.0.0/OPR6.170623.013/01120216:user/release-keys
02-23 15:51:23.032 15976 15976 E native : session_create_implementation.cc:190 Device is not supported.
02-23 15:51:23.032 15976 15976 E native : session_create_implementation.cc:486 Failed to create calibration provider
02-23 15:51:23.032 15976 15976 W native : session_create_implementation.cc:487 ArSession_createImplementation returning ArStatusErrorSpace::AR_UNAVAILABLE_DEVICE_NOT_COMPATIBLE: .
02-23 15:51:23.053 15976 15976 E HelloArActivity: Exception creating session
02-23 15:51:23.053 15976 15976 E HelloArActivity: com.google.ar.core.exceptions.UnavailableDeviceNotCompatibleException
02-23 15:51:23.053 15976 15976 E HelloArActivity: at com.google.ar.core.Session.throwExceptionFromArStatus(Session.java:361)
02-23 15:51:23.053 15976 15976 E HelloArActivity: at com.google.ar.core.Session.nativeCreateSession(Native Method)
02-23 15:51:23.053 15976 15976 E HelloArActivity: at com.google.ar.core.Session.(Session.java:100)
02-23 15:51:23.053 15976 15976 E HelloArActivity: at com.google.ar.core.examples.java.helloar.HelloArActivity.onResume(HelloArActivity.java:155)

bug device support duplicate fixed in upcoming release

Most helpful comment

It seems several devices are hitting this bug. Log from my Samsung S8 SM-G950F:

02-25 14:26:45.375  9326  9342 W native  : helpers.cc:913 Defaulting to persistent calibration file.
02-25 14:26:45.375  9326  9342 W native  : helpers.cc:890 Property calibration_cad is not defined.
02-25 14:26:45.376  9326  9342 I native  : device_provider.cc:715 Identified device type: kDreamltexxDreamlte
02-25 14:26:45.382  9326  9342 E native  : device_profile_database_helpers.cc:134 Device profile for samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU1CRB7:user/release-keys does not exist in /data/use
r/0/com.google.ar.core/files/device_profile_database
02-25 14:26:45.382  9326  9342 E native  : calibration_jni.cc:74 No device profile available for build fingerprint samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU1CRB7:user/release-keys
02-25 14:26:45.386  9229  9254 E native  : session_create_implementation.cc:190 Device is not supported.
02-25 14:26:45.386  9229  9254 E native  : session_create_implementation.cc:486 Failed to create calibration provider
02-25 14:26:45.386  9229  9254 W native  : session_create_implementation.cc:487 ArSession_createImplementation returning ArStatusErrorSpace::AR_UNAVAILABLE_DEVICE_NOT_COMPATIBLE: .
02-25 14:26:45.386  9229  9254 E ArPresto: ArPresto::ArCore session creation failed.
02-25 14:26:45.386  9229  9254 E native  : session_c_api.cc:183 ArConfig_setUpdateMode: session was passed NULL.
02-25 14:26:45.386  9229  9254 E native  : session_c_api.cc:166 ArConfig_setPlaneFindingMode: session was passed NULL.
02-25 14:26:45.386  9229  9254 E native  : session_c_api.cc:148 ArConfig_setLightEstimationMode: session was passed NULL.
02-25 14:26:45.387  9229  9254 E native  : session_c_api.cc:207 ArSession_configure: session was passed NULL.

FWIW, I think I saw this message in logs when using developer-preview-2 on the same device, but it didn't actually stop it working.

For me:
adb shell getprop ro.build.fingerprint

samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU1CRB7:user/release-keys

I believe all of these are duplicates (same bug, different phones), and these build.fingerprints need adding to the supported device profiles by google in a bugfix release of ARCore?:

Samsung Galaxy S8 & OnePlus5 also reporting the same problem in this thread: https://forum.unity.com/threads/arcore-1-0-samsung-galaxy-s8-no-longer-working.519024/

@alchemz The 5T A5010 is NOT listed under supported devices, and you can't download from google play (whereas the other phones can), so I think that's a different issue, #185.

All 8 comments

I only have a OnePlus 5T(A5010), and found it is incompatible to download ARCore 1.0 from the play store.

Could you check to see you could down it https://play.google.com/store/apps/details?id=com.google.ar.core&rdid=com.google.ar.core ?

BTW, Yes, I was able to download ARCore 1.0 from google play

@handymoby Thx, and what's wrong with OnePlus 5T?

It seems several devices are hitting this bug. Log from my Samsung S8 SM-G950F:

02-25 14:26:45.375  9326  9342 W native  : helpers.cc:913 Defaulting to persistent calibration file.
02-25 14:26:45.375  9326  9342 W native  : helpers.cc:890 Property calibration_cad is not defined.
02-25 14:26:45.376  9326  9342 I native  : device_provider.cc:715 Identified device type: kDreamltexxDreamlte
02-25 14:26:45.382  9326  9342 E native  : device_profile_database_helpers.cc:134 Device profile for samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU1CRB7:user/release-keys does not exist in /data/use
r/0/com.google.ar.core/files/device_profile_database
02-25 14:26:45.382  9326  9342 E native  : calibration_jni.cc:74 No device profile available for build fingerprint samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU1CRB7:user/release-keys
02-25 14:26:45.386  9229  9254 E native  : session_create_implementation.cc:190 Device is not supported.
02-25 14:26:45.386  9229  9254 E native  : session_create_implementation.cc:486 Failed to create calibration provider
02-25 14:26:45.386  9229  9254 W native  : session_create_implementation.cc:487 ArSession_createImplementation returning ArStatusErrorSpace::AR_UNAVAILABLE_DEVICE_NOT_COMPATIBLE: .
02-25 14:26:45.386  9229  9254 E ArPresto: ArPresto::ArCore session creation failed.
02-25 14:26:45.386  9229  9254 E native  : session_c_api.cc:183 ArConfig_setUpdateMode: session was passed NULL.
02-25 14:26:45.386  9229  9254 E native  : session_c_api.cc:166 ArConfig_setPlaneFindingMode: session was passed NULL.
02-25 14:26:45.386  9229  9254 E native  : session_c_api.cc:148 ArConfig_setLightEstimationMode: session was passed NULL.
02-25 14:26:45.387  9229  9254 E native  : session_c_api.cc:207 ArSession_configure: session was passed NULL.

FWIW, I think I saw this message in logs when using developer-preview-2 on the same device, but it didn't actually stop it working.

For me:
adb shell getprop ro.build.fingerprint

samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU1CRB7:user/release-keys

I believe all of these are duplicates (same bug, different phones), and these build.fingerprints need adding to the supported device profiles by google in a bugfix release of ARCore?:

Samsung Galaxy S8 & OnePlus5 also reporting the same problem in this thread: https://forum.unity.com/threads/arcore-1-0-samsung-galaxy-s8-no-longer-working.519024/

@alchemz The 5T A5010 is NOT listed under supported devices, and you can't download from google play (whereas the other phones can), so I think that's a different issue, #185.

@Crashthatch Thanks for the reply, OnePlus 5T is a new release/upgrade of the 5 series, if OnePlus 5 is on the supported list, how could 5T not be on the list? Do you know who should I contact with about this issue?

No. I am not affiliated with google. Please keep that separate issue in your own thread, #185.

@Crashthatch thank you so much for the work aggregating those reports!

Duplicate of #198

Was this page helpful?
0 / 5 - 0 ratings