So it seems that recently, an update to the Google Cardboard SDK introduced its own sensor API with automatic drift correction and stuff like that. For VR apps, it's now the advised way to access the sensors, instead of the android.hardware.Sensor API.
The bug was first spotted with Cmoar Cinema Pro (not the Free, it doesn't use the Cardboard API) but it can easily be reproduced using VRTV Video Player Free: this app provides an option "Orientation Provider" with 4 choices:
- Google Cardboard SDK (default): this produces the aforementioned bug.
- Manual touch input: use the touch screen to move the screen instead of the sensors. It also bypasses our module but that's normal.
- Improved Orientation Sensor: no problem, the module works.
- Calibrated Gyroscope: no problem also.
It seems this Cardboard sensor API is quite new so I don't have much more info.
So it seems that recently, an update to the Google Cardboard SDK introduced its own sensor API with automatic drift correction and stuff like that. For VR apps, it's now the advised way to access the sensors, instead of the android.hardware.Sensor API.
The bug was first spotted with Cmoar Cinema Pro (not the Free, it doesn't use the Cardboard API) but it can easily be reproduced using VRTV Video Player Free: this app provides an option "Orientation Provider" with 4 choices:
It seems this Cardboard sensor API is quite new so I don't have much more info.