Search Issue Tracker
Fixed in 2019.1.X
Votes
1
Found in
2017.3.0b3
Issue ID
956911
Regression
Yes
[Android][Daydream] Black screen after disabling and enabling VR mode at runtime with newest Google VR Services update
This appears to have been fixed in the Google VR Services version 1.17.2017118074
To reproduce:
1. Download and open attached "repro956911.zip" project.
2. Build and run on a Daydream compatible phone.
3. When application loads go to VR settings and change headset from Daydream View to Google Cardboard(I/O 2015)
4. Go back to the application.
5. Press the button to exit VR mode.
6. Press the button again to enter VR mode.
Expected result: After re-entering VR mode everything renders correctly in VR view.
Actual result: After re-entering VR mode screen goes black and sometimes app crashes.
Reproduced with: 2018.1.0a1, 2017.3.0b4, 2017.2.0f3, 2017.2.0b3.
Not reproduced with: 2019.1.0a1, 2018.3.0b1, 2017.2.0b2, 2017.1.2p1, 5.6.4p1.
Regression introduced in: 2017.2.0b3.
Devices under test:
Reproduced with:
Google Pixel*, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 530,
Build:google/sailfish/sailfish:8.0.0/OPR3.170623.007/4286350:user/release-keys
Google Pixel XL*, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 530,
Build:google/marlin/marlin:O/OPP2.170420.019/4021594:user/release-keys
Not reproduced with:
Samsung SM G950F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-G71,
Build:samsung/dreamltexx/dreamlte:7.0/NRD90M/G950FXXU1AQEB:user/release-keys
Notes: This only happens with newest Google VR services version, after uninstalling newest Update everything worked as expected.
Google VR Services version : 1.10.170928015. After uninstalling the newest Update everything works as expected.
-
dustinkerstein
Feb 24, 2018 05:36
FYI - this issue is also tracked here - https://github.com/googlevr/gvr-unity-sdk/issues/766#issuecomment-345030172
-
dustinkerstein
Feb 24, 2018 05:11
This appears to be fixed in 2017.3.1p1 but another major GVR issue is present in this release that entirely breaks Cardboard devices (Daydream works fine):
https://answers.unity.com/questions/1456999/google-vr-had-a-fatal-issue-while-loading.html
https://fogbugz.unity3d.com/default.asp?990993_b5v2n79co80u7ia6
https://fogbugz.unity3d.com/default.asp?991127_jhl7ggsi3gon4ip4If anyone has a workaround or knows of a release where both of these issues aren't replicable please let me know.
-
rrrus
Dec 14, 2017 21:09
A fix in Google VR Services is on the way.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The PlayableDirector Component properties are not being updated when the "Bindings" section is expanded
- "Trying to read value of type Dimension while reading a value of type Enum" is thrown when the system language is set to Turkish
- Win32Exception error is thrown when Android dependencies are resolving due to the Ads Mediation package
- Symlinks are broken when a package which contains .xcframework + symlinks is added through Unity Package Manager.
- Crash on ApplyMaterialPass when opening a specific scene
Resolution Note (fix version 2019.1):
Fixed by Google.