Search Issue Tracker
Fixed in 5.6.0f3
Votes
7
Found in
5.5.1p2
Issue ID
881421
Regression
Yes
[GearVR] Leaving headset in standby mode causes screen to freeze
Steps to reproduce:
1. Create new project and make GearVR build
2. Take headset off
3. wait ~10 seconds and put headset back on
4. Notice that view is frozen
Workaround:
void OnApplicationPause(bool isPaused)
{
VRSettings.enabled = !isPaused;
}
Reproduced with: 5.4.4p3, 5.5.1p2, 5.5.1p4
Not reproducible: 5.4.4p1, 5.5.1p1, 5.6.0b9
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Gruguir
Feb 01, 2019 16:42
Reproduced with 2018.3.0f2
bremyBBW
Sep 27, 2018 08:01
Reproduced with 2018.3.0b1
colorteam
Mar 31, 2018 03:38
Reproduced with 2017.3.0f3
rmuk
Nov 15, 2017 19:28
I can't edit my last comment, so here's an update. It looks like this issue was not with Unity, or was a combo. I had an AT&T Galaxy S7 that was only on wifi with no SIM card. Without that card, it was stuck on the firmware that came from the factory. After updating the OS, the issue went away.
rmuk
Oct 25, 2017 17:06
Reproduced in 2017.1.2, workaround does not appear to be working either.
haico1992
Oct 13, 2017 09:51
Bug report with workaround included. The world need more man like you!
Beloudest
Sep 07, 2017 20:21
5.6.0b9 it worked
Beloudest
Sep 07, 2017 20:21
Not fixed in Unity 2017.2.0b10
keyrea1
Aug 29, 2017 06:18
Same problem in Unity 2017. This solution is works.
iniq
May 31, 2017 21:46
Still experiencing this on Galaxy S7 (US ATT) in 5.6.1p1
I do not get this issue on S7E (US TMO) with same build.
Workaround seems to work intermittently, still experimenting with it.