Force Samsung S8 to use Daydream, not Gear VR

@Percy-Pea (without seeing your project) The Oculus SDK may have a manifest file that is being merged in automagically by our Android build system. Can you check to see if that is the case and then remove the AndroidManifest.Xml file (or any AAR/JAR that might also be part of the SDK)? You should also watch out for the menu item they provide under Tools/Oculus/Create store-compatible AndroidManifest.xml as that would re-create the manifest file.

@WendlinReich When you target Gear VR/Oculus, there is a required manifest entry that is injected into your APK. This manifest entry causes the device to IMMEDIATELY drop into the Gear VR transition screen before the application is even run. This means that Unity is unable to do anything for this as we are not even running when this happens. This is a deep, system level issue that Unity can do nothing about at this time. Resolving that issue is something we are working with Samsung and Oculus on, but there isn't much we can do till they fix the issue own their end. The current recommendation is that you script your builds and generate separate APKs for each platform as there is really no other way to handle this at this time.

Even when that issue is resolved, there are still issues around code signing and packaging that make this an extremely difficult thing to maintain. In order to be supported in each store you will most likely have to generate separate APKs with separate signing properties and package names. This would still lead you to require some scripted/multi-APK build for your application even if you could support both SDKs int he same app at the same time.

 

That's actually what we are working with them on as that is also the solution that could potentially allow forced Daydream execution (if we can get over all the other hurdles).