Arcore-android-sdk: LG V30 is not yet supported

Created on 18 Apr 2018 · 15Comments · Source: google-ar/arcore-android-sdk

1.Call _ArCamera_getViewMatrix_ result always identity matrix.
2.Call _ArFrame_acquireCameraImage_ always return AR_ERROR_NOT_YET_AVAILABLE.

Below is the log:

04-18 17:36:45.157 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.189 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.223 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.255 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.288 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.322 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.357 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.390 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.423 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.458 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.491 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.497 1146-2842/? E/LG-3A-AWB: lg_awb_always_gain_logging: main log - final output_gain(2.174281/1.000000/1.608720), out_cct(5231), out_type(1)
04-18 17:36:45.526 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.560 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.597 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.624 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.659 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.693 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.728 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.759 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.793 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.822 1146-2842/? E/LG-3A-AWB: lg_awb_always_gain_logging: main log - final output_gain(2.180208/1.000000/1.604891), out_cct(5253), out_type(1)
04-18 17:36:45.827 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.858 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.891 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.922 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.957 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:45.991 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:46.025 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:46.059 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:46.094 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE: 
04-18 17:36:46.127 1811-2761/com.meitu.arcoredemo E/native: status.cc:175 ArStatusErrorSpace::AR_ERROR_NOT_YET_AVAILABLE:

device support fixed in upcoming release

Source

01098996

Most helpful comment

@mxxcon This forum is intended to support developers creating ARCore applications. User issues can be handled through the contact email on the ARCore Play Store listing.

The issue blocking ARCore rolling to the V30 should be fixed by a regular monthly security update. LG is very aware of this and anxious to have ARCore support on this device.

inio on 10 May 2018

👍5 ❤1

All 15 comments

The LG H930 is not a supported device.

inio on 18 Apr 2018

Duplicate of #89

inio on 18 Apr 2018

https://developers.google.com/ar/discover/?hl=zh-cn
Indicates that LG H930 is supported @inio

01098996 on 19 Apr 2018

Oops! I didn't realize the H930 was a model of the V30.

As you discovered, we encountered a driver issue very late in enabling the V30 that causes it to never start tracking in some situations. It will be supported soon.

I'll make sure the supported device list is updated.

inio on 19 Apr 2018

Please support as soon as possible.Thanks!

01098996 on 19 Apr 2018

👍2

What does it mean that you removed all the issue tags? It won't be fixed and there's no work being done to add support for V30?

mxxcon on 9 May 2018

😕1 👍1

I'd also like to know why the V30 was removed from the list of supported devices. It used to state that you needed Oreo, now the device is not listed at all. Please help!

justinmyersm on 10 May 2018

I removed the "fixed in upcoming release" tag in preparation for the 1.2 release to avoid confusion on the meanings of "upcoming" vs. "next". We're still blocked on a driver bug on this device. Calibrations are in 1.2 and it may work if side-loaded, but we cannot fully support the device and enable it on Play Store because there are too many devices in the field that don't have the driver update yet.

inio on 10 May 2018

👍1

I'm just a user, not a developer, so I don't know what exactly is involved in fixing such a bug.
Would we need to wait for LG+carriers to release next Android 8.x update or can this be fixed with a monthly security update or even an apk download?
Do you know if LG is aware of this? Should end-users bug them about this to get things moving or is this being handled and we just need to wait?

mxxcon on 10 May 2018

@mxxcon This forum is intended to support developers creating ARCore applications. User issues can be handled through the contact email on the ARCore Play Store listing.

The issue blocking ARCore rolling to the V30 should be fixed by a regular monthly security update. LG is very aware of this and anxious to have ARCore support on this device.

inio on 10 May 2018

👍5 ❤1

When will Huawei mate 10 pro be supported? It should be technical feasible to support AR.

widovanheemstra on 30 May 2018

@widovanheemstra Please post your request in #89. We cannot comment on upcoming support before it is announced.

inio on 30 May 2018

Hello @inio
Do you have any updates on this issue?

forcewake on 1 Jun 2018

@forcewake Nope.

inio on 2 Jun 2018

This should be fixed! Users with V30 devices should now be able to see ARCore and AR-Required apps in the Play Store. If you experience poor functioning or tracking oddities, please make sure you don't have any pending security/system updates before reporting.

inio on 11 Jun 2018

👍2

Was this page helpful?

0 / 5 - 0 ratings