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
Samsung Tab S3: not able to find stable surfaces in ARCore #701
Comments
Hi @fredsa any thoughts on this issue? We've done as you requested and attached the logs - we're really perplexed - we need a tablet that can work with ARCore. |
Thank you @richard3575. Forwarding to our certification and QA team to reproduce. |
@richard3575 Would you be able to attach a video recording of the problematic plane finding on your Samsung Tab S3, using |
hi @fredsa We’ve been trying to capture the issue, however, I have to say the Tab is now performing much better. Not perfect, and when we run it next to the Sony Xperia it’s clear the Sony is faster and more stable. However, the Samsung Tab is now again usable and finding surfaces. I’m not sure what has changed, I know we updated ARCore to 1.7 recently, I’m not sure if there was any other updates. Thanks for your help. |
Tested on:
Sony ZX premium – (working well) pointing to the floor within seconds finds the floor and puts the white grid on it.
Samsung S3 Tab (listed as supported device) – (not working well) same floor, it takes near a minute sometimes to find the floor and then only shows purple or red gird, which then swims away or disappears. It is not stable enough to use.
The Issue – we saw this happen on the Sony ZX, it was working awesome, then an OS update from Nougat to PIE made it totally unusable.. However that has since been rectified with an OS patch from Sony. The Samsung S3 is still unusable.
Devices: Samsung S3 Tab SM-T825, Android 8.0.0
Samsung S3 Tab Build fingerprint:
samsung/gts3lltexx/gts3llte:8.0.0/R16NW/T825XXU2BRL2:user/release-keys
Android Studio: 3.3
ARCore 1.6 Packages: versionName=1.6.181112096
Note: the original app was developed in Unity, however with no changes to the app and only a change to the OS (from 8.0 to 9.0) on the Sony ZX it appears that that was the issue. We have since done tests on the Android Studio HelloAR package with similar results
Sequence of events:
Sept 2018
Mid-Oct 2018
Dec 2018
End-Dec 2018
End-Jan 2018
Reading github there are a number of other reported similar issues.
Similar issues: #639 #659 #419 #590 (not sure about the last 2, but they sound similar)
Also, if you look at the reviews for https://play.google.com/store/apps/details?id=com.google.tango.measure&showAllReviews=true
You’ll see there’s a lot of negative reviews about the app not finding surface (yeah, I know a good 60% of those will be on unsupported devices, or bad surfaces and user error, but still there’s a lot of “not working” issues there).
@fredsa requested we do the following:
Please try running the unmodified HelloAR sample project. When doing so:
Download the latest ARCore for Android SDK (releases page)
Connect an ARCore supported device
Make sure you device is up to date (running the latest available version of the o/s)
Verify that the latest version of ARCore is installed
I have done this and still get the same results – the Sony ZX is very good and the Samsung is poor (whilst it can find surfaces, they are not stable)
Logcat’s from both devices for both for “HelloAR” are attached
log-samsungS3Tab_HelloAR.txt
log-sonyZXPremium_HelloAR.txt
Please advise as this is listed as a support device and we have a client looking to purchase a number of them, however due to the stability we can not deliver a viable solution.
Thank you
-Richard
The text was updated successfully, but these errors were encountered: