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

Double Vision Samsung S7 — distortion wrong when resolution is not WQHD #421

Closed
justinwasilenko opened this Issue Dec 26, 2016 · 60 comments

Comments

Projects
None yet
@justinwasilenko

justinwasilenko commented Dec 26, 2016

I just updated Minos Spacefighter to use the new GVR 13 Unity build. This has caused a tonne of issues for everyone using a Samsung S7 and has caused a serious drop in the ratings of the game.
Last time I updated the game using Unity 5.4.3 and the GVR 0.85 which also have issues with the Samsung S7.

So I'm stuck again with bad reviews on my app due to problems with the GVR plugin.

I have instructed people to rescan their QR codes and delete the local cache and data of both the Cardboard app and the Minos Spacefighter app but that hasn't solved the issues.

Is this a known issue? I also had one report with the Asus Zenphone 2 of having the same problem.

@justinwasilenko

This comment has been minimized.

Show comment
Hide comment
@justinwasilenko

justinwasilenko Dec 26, 2016

Sorry the issue with the Asus Zenphone 2 is the gyroscope doesn't work.

justinwasilenko commented Dec 26, 2016

Sorry the issue with the Asus Zenphone 2 is the gyroscope doesn't work.

@nathanmartz

This comment has been minimized.

Show comment
Hide comment
@nathanmartz

nathanmartz Jan 3, 2017

Sorry for the issues. We'll take a look with our friends at Unity.

nathanmartz commented Jan 3, 2017

Sorry for the issues. We'll take a look with our friends at Unity.

@nathanmartz

This comment has been minimized.

Show comment
Hide comment
@nathanmartz

nathanmartz Jan 3, 2017

Can you post a play store link to your game?

nathanmartz commented Jan 3, 2017

Can you post a play store link to your game?

@justinwasilenko

This comment has been minimized.

Show comment
Hide comment
@MrDelegateCB

This comment has been minimized.

Show comment
Hide comment
@MrDelegateCB

MrDelegateCB Jan 4, 2017

Hey, I'm also having the same issue. I think it has something to do with dpi of the device. Because in the review, reported dpi was 640 while in actual device has dpi of 577.

MrDelegateCB commented Jan 4, 2017

Hey, I'm also having the same issue. I think it has something to do with dpi of the device. Because in the review, reported dpi was 640 while in actual device has dpi of 577.

@MephestoKhaan

This comment has been minimized.

Show comment
Hide comment
@MephestoKhaan

MephestoKhaan Jan 8, 2017

Same problem here with S7s. Sometimes it is more extreme when disabling distortion and doing it in the vertex-shader.

MephestoKhaan commented Jan 8, 2017

Same problem here with S7s. Sometimes it is more extreme when disabling distortion and doing it in the vertex-shader.

@Saraceni

This comment has been minimized.

Show comment
Hide comment
@Saraceni

Saraceni Jan 21, 2017

I am having this exact same problem with my Galaxy S7 Flat. I am using Unity 5.5.of3 Personal and Google VR SDK 1.0. It works fine in the majority of devices, but in the Galaxy S7 the offset between left and right eyes are too big, making it impossible to have an immersion using any headset.

Saraceni commented Jan 21, 2017

I am having this exact same problem with my Galaxy S7 Flat. I am using Unity 5.5.of3 Personal and Google VR SDK 1.0. It works fine in the majority of devices, but in the Galaxy S7 the offset between left and right eyes are too big, making it impossible to have an immersion using any headset.

@Saraceni

This comment has been minimized.

Show comment
Hide comment

Saraceni commented Jan 21, 2017

double-vision-gvr

@miraleung

This comment has been minimized.

Show comment
Hide comment
@miraleung

miraleung Jan 22, 2017

Contributor

Thanks for the report, we'll look into this.

Contributor

miraleung commented Jan 22, 2017

Thanks for the report, we'll look into this.

@kasradzenika

This comment has been minimized.

Show comment
Hide comment
@kasradzenika

kasradzenika Jan 24, 2017

I'm having the same issue, screenshot:

screenshot

kasradzenika commented Jan 24, 2017

I'm having the same issue, screenshot:

screenshot

@tomihr

This comment has been minimized.

Show comment
Hide comment
@tomihr

tomihr Mar 3, 2017

screenshot_20170303-140506
I also have double vision problem on Samsung Galaxy S7 flat.

Any news about this?

tomihr commented Mar 3, 2017

screenshot_20170303-140506
I also have double vision problem on Samsung Galaxy S7 flat.

Any news about this?

@gaffkins

This comment has been minimized.

Show comment
Hide comment
@gaffkins

gaffkins Mar 6, 2017

The same problem Galaxy s7 after update system to 7.0 :(
The cameras looks like 1/4 view compare to view in unity or view before I upgrade my samsung to android 7.0.
I will try to find the bug in library code but I'm to confused to find the problem. Please fix it.

gaffkins commented Mar 6, 2017

The same problem Galaxy s7 after update system to 7.0 :(
The cameras looks like 1/4 view compare to view in unity or view before I upgrade my samsung to android 7.0.
I will try to find the bug in library code but I'm to confused to find the problem. Please fix it.

@JOESIDinc

This comment has been minimized.

Show comment
Hide comment
@JOESIDinc

JOESIDinc Mar 11, 2017

My Google VR app got a case of split eye vision after Android 7.0 updated to my Samsung S7. Worked great on Android 6.0. The screen is looking too far to each side, on each eye on almost every previous build of Unity up till 5.5f2. The 5.6 beta has very poor results. Google VR version is 1.3. My Android SDK supports up to target build 24.
Please fix this soon.
screenshot_20170310-222258

JOESIDinc commented Mar 11, 2017

My Google VR app got a case of split eye vision after Android 7.0 updated to my Samsung S7. Worked great on Android 6.0. The screen is looking too far to each side, on each eye on almost every previous build of Unity up till 5.5f2. The 5.6 beta has very poor results. Google VR version is 1.3. My Android SDK supports up to target build 24.
Please fix this soon.
screenshot_20170310-222258

@ninjingames

This comment has been minimized.

Show comment
Hide comment
@ninjingames

ninjingames Mar 11, 2017

Samsung apparently reduced the screen resolution of the Galaxy S7 from its native 2560x1440 to 1920x1080 with the update to Android 7. This article is about a beta build, but I believe it's in the final as well.

Could we please get an update on the situation from somebody at Google? The SGS7 is probably one of the most popular phones for VR applications and if it doesn't work correctly with the GVR SDK it's really tough for us developers dealing with all the bad ratings and complaints from users.

ninjingames commented Mar 11, 2017

Samsung apparently reduced the screen resolution of the Galaxy S7 from its native 2560x1440 to 1920x1080 with the update to Android 7. This article is about a beta build, but I believe it's in the final as well.

Could we please get an update on the situation from somebody at Google? The SGS7 is probably one of the most popular phones for VR applications and if it doesn't work correctly with the GVR SDK it's really tough for us developers dealing with all the bad ratings and complaints from users.

@Saraceni

This comment has been minimized.

Show comment
Hide comment
@Saraceni

Saraceni Mar 11, 2017

I'm having this problem in a S7 running 6.0.1 Marshmallow. I think the resolution is not the problem.

Saraceni commented Mar 11, 2017

I'm having this problem in a S7 running 6.0.1 Marshmallow. I think the resolution is not the problem.

@kasradzenika

This comment has been minimized.

Show comment
Hide comment
@kasradzenika

kasradzenika Mar 11, 2017

@Saraceni resolution is the cause of the problem. This is, I think, how unity creates VR frames (black borders):

  1. unity first creates bottom and middle frames to fit the virtual resolution (which is bigger than then the actual), so the frames appear zoomed in on the device towards the bottom-center of the screen
  2. then it creates frames on the top and at the left and right edges of the screen which get created... I don't know how...

again, this is just a guess based on the screenshots

kasradzenika commented Mar 11, 2017

@Saraceni resolution is the cause of the problem. This is, I think, how unity creates VR frames (black borders):

  1. unity first creates bottom and middle frames to fit the virtual resolution (which is bigger than then the actual), so the frames appear zoomed in on the device towards the bottom-center of the screen
  2. then it creates frames on the top and at the left and right edges of the screen which get created... I don't know how...

again, this is just a guess based on the screenshots

@JOESIDinc

This comment has been minimized.

Show comment
Hide comment

JOESIDinc commented Mar 11, 2017

screenshot_20170311-141242

@JOESIDinc

This comment has been minimized.

Show comment
Hide comment
@JOESIDinc

JOESIDinc Mar 11, 2017

Just as I thought this worked. I rooted my Samsung S7 and downgraded back to Marshmallow 6 0.1 and kept Google VR current to 1.3 and Unity3D 5.5.2f1 and the Google VR worked just as it always had. The problem is Android 7.0. Please fix this guys. It's the android build and I lost my apps to figure it out . The sacrifices I make because of you Unity3D or Google.

JOESIDinc commented Mar 11, 2017

Just as I thought this worked. I rooted my Samsung S7 and downgraded back to Marshmallow 6 0.1 and kept Google VR current to 1.3 and Unity3D 5.5.2f1 and the Google VR worked just as it always had. The problem is Android 7.0. Please fix this guys. It's the android build and I lost my apps to figure it out . The sacrifices I make because of you Unity3D or Google.

@tomihr

This comment has been minimized.

Show comment
Hide comment
@tomihr

tomihr Mar 12, 2017

Yes now when you take screenshot it is 1920xx1080, why Samsung did that?

tomihr commented Mar 12, 2017

Yes now when you take screenshot it is 1920xx1080, why Samsung did that?

@JOESIDinc

This comment has been minimized.

Show comment
Hide comment
@JOESIDinc

JOESIDinc Mar 12, 2017

This the VR game in action on Samsung Galaxy S7 for GoogleVR. Marshmallow 6.0

https://youtu.be/AsO8nVP2Auc

http://www.joesid.com

JOESIDinc commented Mar 12, 2017

This the VR game in action on Samsung Galaxy S7 for GoogleVR. Marshmallow 6.0

https://youtu.be/AsO8nVP2Auc

http://www.joesid.com

@tomihr

This comment has been minimized.

Show comment
Hide comment
@tomihr

tomihr Mar 12, 2017

Guys solution is to change screen resolution in display settings. Just done this on my Samsung S7 and it works, you need to change it to wqhd.

tomihr commented Mar 12, 2017

Guys solution is to change screen resolution in display settings. Just done this on my Samsung S7 and it works, you need to change it to wqhd.

@JOESIDinc

This comment has been minimized.

Show comment
Hide comment
@JOESIDinc

JOESIDinc Mar 12, 2017

@tomihr Thank you for the heads up. This is why I posted here. :)

JOESIDinc commented Mar 12, 2017

@tomihr Thank you for the heads up. This is why I posted here. :)

@baroquedub

This comment has been minimized.

Show comment
Hide comment
@baroquedub

baroquedub Mar 21, 2017

Thanks @tomihr

Now to explain this to our users :) ...

Couple of useful screenshots here: http://gadgetguideonline.com/s7/how-to-change-screen-resolution-of-galaxy-s7-and-s7-after-android-nougat-update/ (Scroll down to "How to change screen resolution of Galaxy S7 and S7 after Android Nougat update?")

baroquedub commented Mar 21, 2017

Thanks @tomihr

Now to explain this to our users :) ...

Couple of useful screenshots here: http://gadgetguideonline.com/s7/how-to-change-screen-resolution-of-galaxy-s7-and-s7-after-android-nougat-update/ (Scroll down to "How to change screen resolution of Galaxy S7 and S7 after Android Nougat update?")

@ninjingames

This comment has been minimized.

Show comment
Hide comment
@ninjingames

ninjingames Mar 24, 2017

This is really a problem that Google has to fix. We can't force all SGS7 users to go into their settings and change the resolution.

It's a problem that Google is capable to fix, since the official Google Cardboard app works correctly with the lower resolution, so Google has a code branch somewhere that works correctly. Also the SGS7 properly reports the changed dpi for the different screen resolutions you can select, so the GVR SDK should be able to work with whatever resolution the user has selected.

@miraleung You wrote "we'll look into this" two months ago. Any update on the situation?

ninjingames commented Mar 24, 2017

This is really a problem that Google has to fix. We can't force all SGS7 users to go into their settings and change the resolution.

It's a problem that Google is capable to fix, since the official Google Cardboard app works correctly with the lower resolution, so Google has a code branch somewhere that works correctly. Also the SGS7 properly reports the changed dpi for the different screen resolutions you can select, so the GVR SDK should be able to work with whatever resolution the user has selected.

@miraleung You wrote "we'll look into this" two months ago. Any update on the situation?

@dbuck

This comment has been minimized.

Show comment
Hide comment
@dbuck

dbuck Mar 29, 2017

We're also seeing the problem here, and would appreciate a fix that doesn't require the end-user to change the system resolution

dbuck commented Mar 29, 2017

We're also seeing the problem here, and would appreciate a fix that doesn't require the end-user to change the system resolution

@miraleung

This comment has been minimized.

Show comment
Hide comment
@miraleung

miraleung Mar 29, 2017

Contributor

We haven't been able to repro for recent releases - could you please try upgrading to v1.3 of the GVR Unity SDK, and Unity 5.6.0f2?

Contributor

miraleung commented Mar 29, 2017

We haven't been able to repro for recent releases - could you please try upgrading to v1.3 of the GVR Unity SDK, and Unity 5.6.0f2?

@Zoriak22

This comment has been minimized.

Show comment
Hide comment
@Zoriak22

Zoriak22 Apr 2, 2017

The resolution and Android 7.0 is NOT the problem. This issue with S7 devices was posted in 2016 august too with 6.0, same double vision issue. The problem is somehow in the SDK.

Zoriak22 commented Apr 2, 2017

The resolution and Android 7.0 is NOT the problem. This issue with S7 devices was posted in 2016 august too with 6.0, same double vision issue. The problem is somehow in the SDK.

@ninjingames

This comment has been minimized.

Show comment
Hide comment
@ninjingames

ninjingames Apr 2, 2017

@miraleung The problem still exists for GVR1.3 and Unity 5.6.0f3.

Steps I took to reproduce the problem:

  • Create new project in Unity 5.6.0f3
  • Import Google VR SDK v1.3.0
  • Open GVRDemo.scene
  • Set Build target to Android, turn on "Virtual Reality Supported" in player settings, add Cardboard to "Virtual Reality SDKs", Change Minimum API Level to Android 4.4
  • Build and deploy to Galaxy S7 with FullHD Resolution
  • Run DemoGVR => Double vision
  • Change resolution to WQHD and run again => app displays correctly
  • Switch resolution back to FullHD => fail again

Are you sure that the Galaxy S7 you've tried to reproduce the problem with is set to FullHD resolution instead of the displays native WQHD?
If you set the screen resolution to WQHD the 3D effect works correctly, but unfortunately all Galaxy S7 were changed to use FullHD by default during the upgrade to Android 7.0, so it affects the majority of all Galaxy S7 owners who didn't manually change resolution back to WQHD.

@Zoriak22 I think this issue (which was posted 26 Dec 2016, not August 2016) really is about resolution and Android 7.0, because everything works correctly with the resolution set to WQHD (which was the default and only setting on Android 6.0 and was changed to FullHD during the update to Android 7.0).

ninjingames commented Apr 2, 2017

@miraleung The problem still exists for GVR1.3 and Unity 5.6.0f3.

Steps I took to reproduce the problem:

  • Create new project in Unity 5.6.0f3
  • Import Google VR SDK v1.3.0
  • Open GVRDemo.scene
  • Set Build target to Android, turn on "Virtual Reality Supported" in player settings, add Cardboard to "Virtual Reality SDKs", Change Minimum API Level to Android 4.4
  • Build and deploy to Galaxy S7 with FullHD Resolution
  • Run DemoGVR => Double vision
  • Change resolution to WQHD and run again => app displays correctly
  • Switch resolution back to FullHD => fail again

Are you sure that the Galaxy S7 you've tried to reproduce the problem with is set to FullHD resolution instead of the displays native WQHD?
If you set the screen resolution to WQHD the 3D effect works correctly, but unfortunately all Galaxy S7 were changed to use FullHD by default during the upgrade to Android 7.0, so it affects the majority of all Galaxy S7 owners who didn't manually change resolution back to WQHD.

@Zoriak22 I think this issue (which was posted 26 Dec 2016, not August 2016) really is about resolution and Android 7.0, because everything works correctly with the resolution set to WQHD (which was the default and only setting on Android 6.0 and was changed to FullHD during the update to Android 7.0).

@Zoriak22

This comment has been minimized.

Show comment
Hide comment
@Zoriak22

Zoriak22 Apr 2, 2017

https://github.com/googlevr/gvr-unity-sdk/issues/271

Not August, July, sorry. It's a really old issue, and not connected with resolution, because the issue was already happened on 6.0 version too. Maybe changing resolution on your S7 variant can help, but on mine still no change. It's SM-G930F modell.

I try to reproduce also the problem and give you a feedback.

Zoriak22 commented Apr 2, 2017

https://github.com/googlevr/gvr-unity-sdk/issues/271

Not August, July, sorry. It's a really old issue, and not connected with resolution, because the issue was already happened on 6.0 version too. Maybe changing resolution on your S7 variant can help, but on mine still no change. It's SM-G930F modell.

I try to reproduce also the problem and give you a feedback.

@guneyozsan

This comment has been minimized.

Show comment
Hide comment
@guneyozsan

guneyozsan Apr 2, 2017

@miraleung I also confirm the view is out of focus in S7 set to Full HD both in Android 6 and 7 (you see double), but it is normal in WQHD. This is the case for all versions of Unity from 5.6.0b9 to 5.6.0f3 and Google VR SDK 1.20 and 1.30.

I was thinking Google VR SDK was incompatible with Gear VR (in cardboard mode not oculus) and had ordered a different viewer. Thanks to this topic setting to WQHD resolved the issue. Honestly I didn't even know my S7 was downsized until I find this topic. I don't think any regular user can notice and change the setting for an app/game that behaves buggy.

guneyozsan commented Apr 2, 2017

@miraleung I also confirm the view is out of focus in S7 set to Full HD both in Android 6 and 7 (you see double), but it is normal in WQHD. This is the case for all versions of Unity from 5.6.0b9 to 5.6.0f3 and Google VR SDK 1.20 and 1.30.

I was thinking Google VR SDK was incompatible with Gear VR (in cardboard mode not oculus) and had ordered a different viewer. Thanks to this topic setting to WQHD resolved the issue. Honestly I didn't even know my S7 was downsized until I find this topic. I don't think any regular user can notice and change the setting for an app/game that behaves buggy.

@miraleung

This comment has been minimized.

Show comment
Hide comment
@miraleung

miraleung Apr 2, 2017

Contributor

Could you please see if you can reproduce the issue with the NDK TreasureHunt sample (https://github.com/googlevr/gvr-android-sdk/tree/master/samples/ndk-treasurehunt)? This will help us identify where the root cause is located.

Contributor

miraleung commented Apr 2, 2017

Could you please see if you can reproduce the issue with the NDK TreasureHunt sample (https://github.com/googlevr/gvr-android-sdk/tree/master/samples/ndk-treasurehunt)? This will help us identify where the root cause is located.

@jdduke

This comment has been minimized.

Show comment
Hide comment
@jdduke

jdduke Apr 5, 2017

Another thing to try is installing the latest version of Google VR Services. The GVR SDK used a set of DPI overrides for certain devices which misreport their DPI. However, such DPI overrides only work properly when the device is configured for native resolution. The latest version of Google VR Services might have a fix for this issue.

jdduke commented Apr 5, 2017

Another thing to try is installing the latest version of Google VR Services. The GVR SDK used a set of DPI overrides for certain devices which misreport their DPI. However, such DPI overrides only work properly when the device is configured for native resolution. The latest version of Google VR Services might have a fix for this issue.

@miraleung miraleung closed this Apr 19, 2017

@baroquedub

This comment has been minimized.

Show comment
Hide comment
@baroquedub

baroquedub Apr 19, 2017

Closed as in fixed? Last build I did on Unity 5.5.1 / GVR10.3, it was still a problem.

Can you confirm whether you're closing because it's fixed in Unity 5.6's built-in GoogleVR support?

baroquedub commented Apr 19, 2017

Closed as in fixed? Last build I did on Unity 5.5.1 / GVR10.3, it was still a problem.

Can you confirm whether you're closing because it's fixed in Unity 5.6's built-in GoogleVR support?

@Zoriak22

This comment has been minimized.

Show comment
Hide comment
@Zoriak22

Zoriak22 Apr 19, 2017

The problem still exists.

Zoriak22 commented Apr 19, 2017

The problem still exists.

@miraleung

This comment has been minimized.

Show comment
Hide comment
@miraleung

miraleung Apr 19, 2017

Contributor

Following @jdduke's fix should solve the issue.

Contributor

miraleung commented Apr 19, 2017

Following @jdduke's fix should solve the issue.

@miraleung miraleung reopened this Apr 19, 2017

@helge79

This comment has been minimized.

Show comment
Hide comment
@helge79

helge79 Apr 21, 2017

We are also experiencing this issue after upgrading our Galaxy S7 to Android 7. Our configuration: Unity 5.5.2f1, GVR SDK 1.30 and latest Google VR services.

Screenshot of GVRDemo with default setting (FullHD):

screenshot_20170421-125608

Screenshot of GVRDemo with resolution changed to WQHD:

screenshot_20170421-125738

helge79 commented Apr 21, 2017

We are also experiencing this issue after upgrading our Galaxy S7 to Android 7. Our configuration: Unity 5.5.2f1, GVR SDK 1.30 and latest Google VR services.

Screenshot of GVRDemo with default setting (FullHD):

screenshot_20170421-125608

Screenshot of GVRDemo with resolution changed to WQHD:

screenshot_20170421-125738

@helge79

This comment has been minimized.

Show comment
Hide comment
@helge79

helge79 Apr 21, 2017

@miraleung The NDK TreasureHunt sample works fine. I just cloned the repository and built the APK -
find the screenshots below. Anything else we can assist you with in finding the root cause of this issue?

Screenshot of TreasureHunt (FullHD):

screenshot_20170421-135648

Screenshot of TreasureHunt (WQHD):

screenshot_20170421-135547

helge79 commented Apr 21, 2017

@miraleung The NDK TreasureHunt sample works fine. I just cloned the repository and built the APK -
find the screenshots below. Anything else we can assist you with in finding the root cause of this issue?

Screenshot of TreasureHunt (FullHD):

screenshot_20170421-135648

Screenshot of TreasureHunt (WQHD):

screenshot_20170421-135547

@andyz

This comment has been minimized.

Show comment
Hide comment
@andyz

andyz May 4, 2017

Get exactly same as helge79 with Unity 5.5.1 and GVR 1.4. Changing s7 phone res fixes, but this is not a solution (you can not ask public using your app to chnage their resolution). Have latest Google VR Services

andyz commented May 4, 2017

Get exactly same as helge79 with Unity 5.5.1 and GVR 1.4. Changing s7 phone res fixes, but this is not a solution (you can not ask public using your app to chnage their resolution). Have latest Google VR Services

@miraleung

This comment has been minimized.

Show comment
Hide comment
@miraleung

miraleung May 15, 2017

Contributor

Could you please try this with Unity 5.6 and Cardboard enabled in Player Settings?

Contributor

miraleung commented May 15, 2017

Could you please try this with Unity 5.6 and Cardboard enabled in Player Settings?

@Chris-1993

This comment has been minimized.

Show comment
Hide comment
@Chris-1993

Chris-1993 May 18, 2017

I tested it with Unity 5.6.1f1 (Cardboard enabled in Player Settings) and GoogleVR SDK 1.50.0 on a Galaxy S7 (SM-G930F) with Android 7.0.

Random Package Name & GoogleVR Services app installed: Doesn’t work
Random Package Name & WITHOUT GoogleVR Services app installed: WORKS
Package Name of a published Cardboard App & GoogleVR Services app installed: Doesn’t work
Package Name of a published Cardboard App & WITHOUT GoogleVR Services app installed: Doesn’t work.

Between all tests I killed all tasks on the phone and possibly rebooted the phone. Otherwise you won't be able to see the changes. Furthermore the phone had an internet connection.

All in all it’s the same result as in other Unity and GoogleVR SDK (except < 0.7.2) versions.

The results with GoogleVR/Cardboard SDK < 0.7.2 look like this:

Random Package Name & GoogleVR Services app installed: Doesn’t work
Random Package Name & WITHOUT GoogleVR Services app installed: WORKS
Package Name of a published Cardboard App & GoogleVR Services app installed: Doesn’t work
Package Name of a published Cardboard App & WITHOUT GoogleVR Services app installed: WORKS.
->The last point is the only solution you can publish a app without getting problems with S7 Users

Please also check out this falsely closed issues. There are more information related to this problem.
#271 (here you also find an explanation why I used different Package Names)
#315

Sorry for my Englisch. I’m not a native Englisch speaker.

Chris-1993 commented May 18, 2017

I tested it with Unity 5.6.1f1 (Cardboard enabled in Player Settings) and GoogleVR SDK 1.50.0 on a Galaxy S7 (SM-G930F) with Android 7.0.

Random Package Name & GoogleVR Services app installed: Doesn’t work
Random Package Name & WITHOUT GoogleVR Services app installed: WORKS
Package Name of a published Cardboard App & GoogleVR Services app installed: Doesn’t work
Package Name of a published Cardboard App & WITHOUT GoogleVR Services app installed: Doesn’t work.

Between all tests I killed all tasks on the phone and possibly rebooted the phone. Otherwise you won't be able to see the changes. Furthermore the phone had an internet connection.

All in all it’s the same result as in other Unity and GoogleVR SDK (except < 0.7.2) versions.

The results with GoogleVR/Cardboard SDK < 0.7.2 look like this:

Random Package Name & GoogleVR Services app installed: Doesn’t work
Random Package Name & WITHOUT GoogleVR Services app installed: WORKS
Package Name of a published Cardboard App & GoogleVR Services app installed: Doesn’t work
Package Name of a published Cardboard App & WITHOUT GoogleVR Services app installed: WORKS.
->The last point is the only solution you can publish a app without getting problems with S7 Users

Please also check out this falsely closed issues. There are more information related to this problem.
#271 (here you also find an explanation why I used different Package Names)
#315

Sorry for my Englisch. I’m not a native Englisch speaker.

@mcfn

This comment has been minimized.

Show comment
Hide comment
@mcfn

mcfn Jun 7, 2017

We have same problem for S7 in Android 7.0, any update for this issue?

mcfn commented Jun 7, 2017

We have same problem for S7 in Android 7.0, any update for this issue?

@Zagrava

This comment has been minimized.

Show comment
Hide comment
@Zagrava

Zagrava Jul 24, 2017

Same problem with S7, no solution so far?

Zagrava commented Jul 24, 2017

Same problem with S7, no solution so far?

@Zagrava

This comment has been minimized.

Show comment
Hide comment
@Zagrava

Zagrava Jul 26, 2017

P.S. Installing project in offline mode runs the game perfectly, but if you install it being online - this bug appears.
Something is synced with the google store?

Zagrava commented Jul 26, 2017

P.S. Installing project in offline mode runs the game perfectly, but if you install it being online - this bug appears.
Something is synced with the google store?

@fredsa fredsa added the bug label Aug 31, 2017

@fredsa fredsa changed the title from Double Vision Samsung S7 - Unity GVR 13 build to Double Vision Samsung S7 — distortion wrong when resolution is not WQHD Aug 31, 2017

@fredsa

This comment has been minimized.

Show comment
Hide comment
@fredsa

fredsa Aug 31, 2017

Member

Likely same issue as described in immersive-web/webvr-polyfill#273

Member

fredsa commented Aug 31, 2017

Likely same issue as described in immersive-web/webvr-polyfill#273

@jdduke

This comment has been minimized.

Show comment
Hide comment
@jdduke

jdduke Sep 7, 2017

Just wanted to share an update. We've tested a tentative fix against several apps, and the results are promising. The fix would go out as part of a Google VR Services update at the end of the month. We'll post more when the rollout starts to get confirmation of the fix. Thanks for your patience.

jdduke commented Sep 7, 2017

Just wanted to share an update. We've tested a tentative fix against several apps, and the results are promising. The fix would go out as part of a Google VR Services update at the end of the month. We'll post more when the rollout starts to get confirmation of the fix. Thanks for your patience.

@AlexanderStohr

This comment has been minimized.

Show comment
Hide comment
@AlexanderStohr

AlexanderStohr Sep 10, 2017

Samsung Galaxy S7 (SM-G930F): able to confirm the problems with too wide eye-views (clipped on the short edges) on many applications from Google Play Store. Android system version is 7.0.

now eagerly hoping for the possible global fix from jdduke right above!

AlexanderStohr commented Sep 10, 2017

Samsung Galaxy S7 (SM-G930F): able to confirm the problems with too wide eye-views (clipped on the short edges) on many applications from Google Play Store. Android system version is 7.0.

now eagerly hoping for the possible global fix from jdduke right above!

@parkitny

This comment has been minimized.

Show comment
Hide comment
@parkitny

parkitny Sep 24, 2017

Any further updates on a release date for the bug fix?

parkitny commented Sep 24, 2017

Any further updates on a release date for the bug fix?

@rpassareti

This comment has been minimized.

Show comment
Hide comment
@rpassareti

rpassareti Sep 26, 2017

even changing the resolution on my s7, the displays still be in the wrong position
seems like the circle is bigger

rpassareti commented Sep 26, 2017

even changing the resolution on my s7, the displays still be in the wrong position
seems like the circle is bigger

@fredsa

This comment has been minimized.

Show comment
Hide comment
@fredsa

fredsa Sep 28, 2017

Member

The Google VR services update @jdduke mentioned above, initially scheduled to go out this week, has been pushed to next week. Expect the staged rollout of the VrCore update to begin on Monday, October 2, 2017.

To see the current version of VrCore on your device, use:
Settings > Apps > ︙ > Show system apps > Google VR Services

Member

fredsa commented Sep 28, 2017

The Google VR services update @jdduke mentioned above, initially scheduled to go out this week, has been pushed to next week. Expect the staged rollout of the VrCore update to begin on Monday, October 2, 2017.

To see the current version of VrCore on your device, use:
Settings > Apps > ︙ > Show system apps > Google VR Services

@jonny2027

This comment has been minimized.

Show comment
Hide comment
@jonny2027

jonny2027 Oct 3, 2017

@fredsa Can you tell us what version of VRCore will have the fix in for this issue?

jonny2027 commented Oct 3, 2017

@fredsa Can you tell us what version of VRCore will have the fix in for this issue?

@jdduke

This comment has been minimized.

Show comment
Hide comment
@jdduke

jdduke Oct 3, 2017

The Google VR Services with the tentative fix should have the following version name: 1.10.170249286. Rollout will hit 25% today, and 100% be the end of the week.

jdduke commented Oct 3, 2017

The Google VR Services with the tentative fix should have the following version name: 1.10.170249286. Rollout will hit 25% today, and 100% be the end of the week.

@guneyozsan

This comment has been minimized.

Show comment
Hide comment
@guneyozsan

guneyozsan Oct 6, 2017

I can confirm this is fixed for me after receiving the Google VR Services version 1.10.170928015.

guneyozsan commented Oct 6, 2017

I can confirm this is fixed for me after receiving the Google VR Services version 1.10.170928015.

@jdduke jdduke closed this Oct 6, 2017

@helge79

This comment has been minimized.

Show comment
Hide comment
@helge79

helge79 Oct 13, 2017

I cannot confirm this is fixed for me. Our apps built with Unity 5.5.2f1 and GVR SDK 1.30 still do not work in Full HD mode after updating Google VR services to 1.10.170928015. Should this work or is Unity 5.5 and GVR SDK 1.30 the show-stopper here?

helge79 commented Oct 13, 2017

I cannot confirm this is fixed for me. Our apps built with Unity 5.5.2f1 and GVR SDK 1.30 still do not work in Full HD mode after updating Google VR services to 1.10.170928015. Should this work or is Unity 5.5 and GVR SDK 1.30 the show-stopper here?

@guneyozsan

This comment has been minimized.

Show comment
Hide comment
@guneyozsan

guneyozsan Oct 13, 2017

If it helps our versions are Unity 2017.1.1p2 and GVR 1.60.

guneyozsan commented Oct 13, 2017

If it helps our versions are Unity 2017.1.1p2 and GVR 1.60.

@fredsa

This comment has been minimized.

Show comment
Hide comment
@fredsa

fredsa Oct 16, 2017

Member

@helge79 Native integration of Google VR into Unity exists from Unity 5.6 onward, so at the moment that's Unity 5.6 and 2017.

Unity 5.5 does not have native Google VR integration, so will not be affected by the installed Google VR Services.

Member

fredsa commented Oct 16, 2017

@helge79 Native integration of Google VR into Unity exists from Unity 5.6 onward, so at the moment that's Unity 5.6 and 2017.

Unity 5.5 does not have native Google VR integration, so will not be affected by the installed Google VR Services.

@AlexanderStohr

This comment has been minimized.

Show comment
Hide comment
@AlexanderStohr

AlexanderStohr Oct 16, 2017

i feel like i got all of the latest updates - but for the S7 i see it only fixed for the low and medium resolution mode. it still does not work for the high resolution "W" mode. sorry to say.

AlexanderStohr commented Oct 16, 2017

i feel like i got all of the latest updates - but for the S7 i see it only fixed for the low and medium resolution mode. it still does not work for the high resolution "W" mode. sorry to say.

@jules43

This comment has been minimized.

Show comment
Hide comment
@jules43

jules43 Oct 19, 2017

I am working with Unity 5.3.8p2 and Google VR Unity plugin version 1.40 and an older build, and have been seeing this problem.

I can confirm that the problem occurs in FHD mode and is fixed in WQHD mode on my Samsung S7 (Android 7.0 Aug patch).

The problem still occurs when installing the 1.10.170928015 version of Google VR Services.

Full details of the problems I'm seeing are in #751

jules43 commented Oct 19, 2017

I am working with Unity 5.3.8p2 and Google VR Unity plugin version 1.40 and an older build, and have been seeing this problem.

I can confirm that the problem occurs in FHD mode and is fixed in WQHD mode on my Samsung S7 (Android 7.0 Aug patch).

The problem still occurs when installing the 1.10.170928015 version of Google VR Services.

Full details of the problems I'm seeing are in #751

@helge79

This comment has been minimized.

Show comment
Hide comment
@helge79

helge79 Oct 19, 2017

@fredsa Thanks for clarification, Fred. If updating Unity would not be an option can you think of any possible workaround we might apply?

helge79 commented Oct 19, 2017

@fredsa Thanks for clarification, Fred. If updating Unity would not be an option can you think of any possible workaround we might apply?

@fredsa

This comment has been minimized.

Show comment
Hide comment
@fredsa

fredsa Oct 19, 2017

Member

@jules43 The current Google VR SDK requires Unity 5.6 or later.
(Unity 5.3 does not include native integration of Google VR, which means the SDK is handling a lot more of the rendering implementation. For the update to Google VR Services to help, please update to Unity 5.6 and the latest Google VR SDK.)

Member

fredsa commented Oct 19, 2017

@jules43 The current Google VR SDK requires Unity 5.6 or later.
(Unity 5.3 does not include native integration of Google VR, which means the SDK is handling a lot more of the rendering implementation. For the update to Google VR Services to help, please update to Unity 5.6 and the latest Google VR SDK.)

@jules43

This comment has been minimized.

Show comment
Hide comment
@jules43

jules43 Oct 19, 2017

@fredsa Thanks for the clarification

jules43 commented Oct 19, 2017

@fredsa Thanks for the clarification

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