Search Issue Tracker

Won't Fix

Votes

1

Found in

2017.2.0f3

Issue ID

964738

Regression

No

[Android][GearVR] Input from headset touch pad is ignored when controller with pressed button is disconnected from the device

XR SDK

-

To reproduce:

1. Download and open attached "repro964738.zip" project.
2. Add Oculus Signature File (osig) of the device which will be used to the Project->Plugins->Android->assets.
3. Build and run the project.
4. Insert the device into GearVR headset.
5. Make sure GearVR controller is connected to the device.
6. When application loads, use GearVR controller trigger button to select the cube in the left side of the scene and drag it.
7. Notice when trigger button is held cube can be moved and when released cube is left stationary.
8. Select the cube again. While cube is selected and trigger button on controller is held, disconnect the GearVR controller by removing batteries from the controller.
9. Wait till GearVR controller fully disconnects from the application.
10. Try to select that same cube again by using touch pad on GearVR headset.

Expected result: Cube can be selected and dragged across the scene when using GearVR headset touch pad.
Actual result: Input gets stuck. It is not possible to select the cube with GearVR headset controls.

Reproduced with: 2018.1.0a4, 2017.3.0b9, 2017.2.0p1.

Devices Under Test:

Samsung SM G928F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zenltexx/zenlte:7.0/NRD90M/G928FXXU3CQG2:user/release-keys

Verizon SM G930V*, OS:6.0.1, CPU:arm64-v8a, GPU:Adreno (TM) 530,
Build:Verizon/heroqltevzw/heroqltevzw:6.0.1/MMB29M/G930VVRU2APG3:user/release-keys

Samsung SM G950F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-G71,
Build:samsung/dreamltexx/dreamlte:7.0/NRD90M/G950FXXU1AQH3:user/release-keys

Notes: Could not test on earlier versions due to code errors caused by change from VR to XR. In the scene there is a text box which represents Input class and returns true if there is any Input from "fire1" button. After disconnecting GearVR controller while holding its trigger, it can be seen that the Input is always returned as true, even though none of the buttons are pressed afterwards. Could not reproduce with GearVR Developer mode turned on and without headset.

  1. Resolution Note (2018.1.X):

    XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.