Pfew, I’m really glad about this and worth all the hazzle, posting and uploading projects 
It’s indeed really strange that a not-working app did work at your device, but not on mine. I really would like to hear what caused all this if you are able to find the problem. Thanks a lot for looking into this issue so far.
Don’t know if this is useful, but I have encountered this a few times myself, and up to now it seems to happen after I have moved the OVRPlayerController inside the editor (although not every time).
Deleting the OVRPlayerController and adding a new copy of it to the scene has, at least up to now, solved the issue.
The issue should be resolved in Patch-release 4.6.3p1: Download Archive
I fixed a build settings error for a similar issue and have since not been able to reproduce this issue. Can anyone confirm the issue is resolved? @JDMulti @Perrynow @justlike
I have definitely seen the problem while using 4.6.3p1 - working with a project that was already having the issue. In the process of trying to fix the problem I had uninstalled all copies of Unity then re-installed 4.6.3p1. The problem persisted. Yesterday I saw Adam Baily’s post (#22 above) and deleted my OVRCameraController and replaced it in my scene. The problem disappeared and I’ve been working with it for 24 hours with no problems.
Using WIndows 8.1, Unity Pro (subscription) and Android free.
I’ll try as soon as possible. Sorry I can’t test it right now, because the server where my test project is on ( at work ) has crashed. But today or tomorrow I’ll have it restored and I’ll reply for sure. Sorry for not being able to answer it now =(
@Don-Whitaker If this happens to you again, please post what you changed/did in the editor before building.
For sure. I have been keeping a close eye on it. So far so good.
I did try a fresh project to test and it is working, too. I will tinker with that tonight and see if I can break it.
I’ve tested the Gear VR example project I uploaded to Dropbox, and it works now. I’ve been checking it a couple of times and haven’t had a failing APK again. For now I keep trying to build with Android Free and see if it breaks in the couple of weeks. But for now, it seems to be fixed. Thanks for the support and sorry I couldn’t test it earlier.
It works for me too on Unity 4.6.3p3 free and pro without android pro, thanks !
At the time Unity 5 was released I tested the personal edition with the mobile SDK 0.4.3 and it did not work. Any idea why ? Maybe the same reasons. I know the plan is to support natively the Oculus SDK in Unity 5 but in the meantime it would be wonderful if it works the same way it does on the 4.6.3.
Unity 5.0.0f4 has an issue that causes all GearVR applications built with this version to crash on startup. We have resolved the issue and a fix will be included in 5.0.0p2.
Ok thanks ! Can’t wait for the 5p2 release then
I have followed every single step described in this thread and in the official oculus forum to no avail, i already installed the 5p2 patch and have the correct version of the SDK running, i have tried everything, ive followed every single step to the point and i still get any new project and any new scene configured and signed to crash right after the freaking unity splash screen. its utterly frustrating to see how many people are getting this same issue and having a patch that still doesn’t fix it for some. anyone has any other ideas why it would still be crashing even after patching and redoing everything to the smallest detail?
I’m having the exact same problem. Tried with 4.6 and p2 (even p3) version. change the splash screen (I have android pro). Nothing help : logo and then Crash
My OS is windows 8 but the same problem occurred on a OSX…
As soon as I remove the OVR camera and put a regular one it works.
It seem definitively link to OVR integration in unity for me. as idding a OVR camera crash the app 100% of the time and changing it for a regular camera does not.
We need help (and consistency too !)
Hi,
same problem here. Splash screen, then displays Gear VR homescreen instead.
Edit #2:
Solved by forcing OpenGL ES 2.0 in Unity and editing the Manifest file.
See here:
Edit #1:
I did not install the oculussig file. When installing the left eye displays what it should, but the right eye flickers between a “correct” right eye and a stretched splashscreen including a logo.
Tech details:
Unity 5.0.0p2 (Unity Pro, Android Pro)
ovr_mobile_sdk_0.4.3.1
Galaxy Note 4 (SM-N910F, 4.4.4)
Windows 7 64 bit
See the attached logfiles run with the following options: adb logcat -s Unity ActivityManager PackageManager dalvikvm DEBUG
After installing the signature file:
debug_7.txt = Unity 5.0.0p3 after having installed sigfile
Before installing the signature file:
debug_install_run_dump.txt = Unity 5.0.0p3 Install and initial run with dump/stack trace
debug.txt = Unity 5.0.0p2
debug_5.0.0p3.txt = Unity 5.0.0p3
2043405–132656–debug.txt (11.3 KB)
2043405–132683–debug_5.0.0p3.txt (10.6 KB)
2043405–132757–debug_install_run_dump.txt (80.2 KB)
2043405–132759–debug_7.txt (16.8 KB)
Hi!
i have the same problem. The app crashes on the startup. I have Unity 5.0.1f1 with Unity pro and Android pro. I have tried to change the android manifest and force OpenGL 2, but the problem continues.
any solution for this?
Same issue here. I have sent links to the Oculus boards with small Android projects but I was told that the people on the boards for Oculus do not have access to Samsung HMD’s so they could not see the issue. I worked on this isssue for the better part of week. My partners and I decided to not show any more clients Oculus Mobile possibilities (less the one we already have) untill both Unity and Oculus resolve this issue. We have enough client work to keep bussy and will just wait.
OS X 10.10.2
Unity 5 Pro 5.0 Patch 3
Unity 5 Pro 5 Android
Oculus runtime 0.5.1
Oculus Mobile 0.5.0
Samsung Note 4
Samaung Gear HMD
So I was running into an issue where, after the splash screen, the Unity logo was in the right eye, while the expected VR view was in the left eye.
I isolated the problem down to this setting:
Edit/Project Settings/Player - “Other Settings” - Graphics Level
Setting the graphics level to 3.0 causes the problem for me (I know the internet says 3.0 is right).
I set it to ES 2.0 instead, exported, worked!
It’s worth noting that in Build/Android/Texture compression, I have that set to GLES 3.0.
Hope that helps. I’ve attached a screen shot to illustrate what settings I’m talking about. On the far right is also my distilled workflow for setting up a new project to samsung VR. This process is a huge pain in the ass in general.
*Unity 5.0.1f1 (pro), Android free, mobile SDK 0.5.0
Hi there,
I’m experiencing the same error as well. I do a build/run to the Note 4, see the splash screen (which looks like the eyes are flipped, Unity logo is on the right and there is a split down the middle), and then the app crashes. Everything is set up according to the provided standards in the documentation, and the XML file is edited appropriately. I’m running Unity 5 Personal, with Android 5.0 Free. Anybody come up with a solution?
I’ll throw in one more thing to try: Help → Manage Licenses → Check for Updates. I don’t know if that’s what fixed the issue for me, as I was trying multiple things simultaneously. Unity 4.6.3f1, was stuck on splash screen with audio playing in background.
Hey, anyone experiencing this still? It keeps going to Gear Hub after unity logo
1 Like