All builds (regardless of VR supported) asking me to place device into GearVR...

Unity Engine
1

Hey everyone,

I have an app that was originally built for the GearVR on Android, using Unity 5.6.
I have a need to deploy it to Cardboard (not oculus), and when I switch it in the build settings, it still asks for the GearVR.

What is SUPER strange is that If I take the Cardboard APK and build it to my Google Pixel, it launches just fine. Taking that SAME apk and installing it on my Samsung Galaxy S7 Edge results in the “Insert into GearVR” message.

Anyone have any ideas what could be causing this? Literally the same APK (which is configured for Cardboard) works on the pixel as a cardboard build, but on the S7 it asks for the Gear…

2

What does the manifest in the apk look like? I would think that would be what causes this.

Is there an entry that looks like below?

<meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only"/>
3

Will check in the morning.

However, what would be generating that, if the boxes aren’t ticked and the SDK isn’t enabled?

Rather, if it is like you say, how can I prevent that?

4

It’s just something to check further down the pipeline that would explain it, to perhaps steer you in the right direction, and that can be manually compensated for until the root cause is found.

5

Yes - The android manifest (despite being Google VR ONLY in the player settings) has that samsung VR line…

What could be adding this? Some of the older scenes still have some of the OVR prefabs in them (like the manager and such) but they are never even opened…

6

Hmm - Seems to have been something with the Oculus Utilities version i was running. I removed the OVR folder and it now works? How could that be…

7

I’d scan their code and see if they do anything to the manifest, or if they place anything in the normal spot under plugins. Last time I checked it was actually the opposite that the google sdk was messing with the manifest but maybe that’s changed. In either case you should be able to compensate for that to get the behavior to stop.

8

Are you using version 1.14 of the oculus utilities? There’s a bug in it where it was forcing all VR projects to add the gearvr line to the manifest file. Update to the latest version of oculus utilities and it should work again.

9

Actually, this seems to be happening in the 1.15 version of the utilities (from asset store) as well.