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

Samsung Tab S3: not able to find stable surfaces in ARCore #701

Closed
richard3575 opened this issue Jan 28, 2019 · 5 comments
Closed

Samsung Tab S3: not able to find stable surfaces in ARCore #701

richard3575 opened this issue Jan 28, 2019 · 5 comments
Labels
device support questions/issues with device enablement

Comments

@richard3575
Copy link

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

  • ARCore app created and tested on Sony ZX Premium (Android 8.0)
  • Works great, very well in finding ground plans quickly and accurately. Mostly finding white grid surfaces.

Mid-Oct 2018

Dec 2018

  • Samsung S3 Tab purchased (as it’s listed as a support device) as Sony device not working.
  • Same app is giving the same results – it just will not find any surfaces what so ever.
  • Other apps tested on device ARMeasure, Ikea app, Measure from Google. Same results, unable to find accurate surfaces

End-Dec 2018

  • Sony ZX – gets a new OS update from Sony and is now back to how it was – working nicely, quickly and accurately.

End-Jan 2018

  • To-date – Samsung S3 Tab has all updates installed, but still giving very poor experience.

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

@richard3575
Copy link
Author

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.
Thanks in advance for your help!

@fredsa
Copy link
Member

fredsa commented Feb 14, 2019

Thank you @richard3575. Forwarding to our certification and QA team to reproduce.

@fredsa fredsa added the device support questions/issues with device enablement label Feb 14, 2019
@richard3575
Copy link
Author

Also someone else has reported on Samsung S4 Tab #720

It's been almost 3 months since this was first reported and as an issue #591 and we're still no closer. We've provided the requested logs and will provide any further details you require.
Thank you

@fredsa
Copy link
Member

fredsa commented Mar 1, 2019

@richard3575 Would you be able to attach a video recording of the problematic plane finding on your Samsung Tab S3, using adb shell screenrecord --bugreport?

@fredsa fredsa changed the title Samsung S3 Tab not able to find stable surfaces in ARCore Samsung Tab S3: not able to find stable surfaces in ARCore Mar 1, 2019
@richard3575
Copy link
Author

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.
For reference the fingerprint is: samsung/gts3lltexx/gts3llte:8.0.0/R16NW/T825XXU2BRL2:user/release-keys
We can close this issue now.

Thanks for your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
device support questions/issues with device enablement
Projects
None yet
Development

No branches or pull requests

2 participants