We develop an accessibility-focused Android application that is designed for the Galaxy S10 and GearVR Headset. Part of our provisioning process is to disable the native GearVR application that comes preloaded on S10’s; this is to prevent the GearVR application from launching when the S10 is docked into the GearVR Headset. We also disable any system updates via Samsung Knox.
We began seeing a problem with a recent batch of S10’s that we received. The problem is that our app gets closed whenever the S10 is docked into any GearVR Headset. Upon comparison with our older S10’s, we notice these devices have the later Android 10 update that is coupled with One UI 2.5 (our older devices run One UI 2.1).
After viewing the logs, I think I can pinpoint the difference between the two devices and how they are treating the GearVR Headset.
Normal S10 when inserting into GearVR (One UI 2.1)
5-03 13:57:21.331 1272 1272 V GearVrManagerService: notifyDockEventChanged event=1(1) ids=04e8:a500
05-03 13:57:21.331 1272 1272 V GearVrManagerService: setDockState prevIsDock=false event=1 ids=04e8:a500
05-03 13:57:21.331 1272 1272 I GearVrManagerService: setDockState ignored.
Problematic S10 when inserting into GearVR (One UI 2.5)
05-03 09:52:06.668 1238 1238 V GearVrManagerService: notifyDockEventChanged event=1(1) ids=04e8:a500
05-03 09:52:06.668 1238 1238 V GearVrManagerService: setDockState prevIsDock=false event=1 ids=04e8:a500
05-03 09:52:06.670 1238 1238 V GearVrManagerService: vr service now force enabled!