New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 732945 link

Starred by 2 users
Status: Fixed
Owner:
█ bshe@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
Cc:
vsupruniuk@google.com
█ leilei@chromium.org
mthiesse@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression
Proj-VR
Proj-XR



Sign in to add a comment

Resetting pose doesn't work

Project Member Reported by dbbrooks@chromium.org, Jun 13 2017 
Chrome Version: 61.0.3129.0
OS: Android N
Device: Pixel
VRCore: 1.6.156467194
Daydream: 1.6.170509033

* This does not occur if Chrome beta 60.0.3112.20 is used

What steps will reproduce the problem?
(1) With Daydream set as default headset
(2) go to https://webvr.info/samples/03-vr-presentation.html and press enter VR
(3) Follow DON flow to start presentation
(4) Press and hold bottom remote button to reset the pose

What is the expected result? Pose resets

What happens instead? The pose does not reset

Comment 1 by ddorwin@chromium.org, Jun 13 2017

Cc: mthiesse@chromium.org
Components: UI>Browser
Labels: -Pri-3 -Proj-VR Proj-VR-Daydream M-61 Pri-1
Status: Available (was: Untriaged)

Comment 2 by ddorwin@chromium.org, Jun 13 2017

Labels: -Type-Bug Type-Bug-Regression

Comment 3 by dbbrooks@chromium.org, Jun 13 2017 

BTW, resetting does work within the Daydream app itself.
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 15 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7

commit 9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7
Author: bshe <bshe@chromium.org>
Date: Thu Jun 15 20:52:27 2017

Reland "Upgrade gvr library to 1.60.1"" and fix recentering(as a byproduct)

It was reverted at 2f7ee461cdd933ac5ed72f737b9ea65c5b19a28c due to
black screen after presentation.

The root cause was the we didn't call onResume when presenting. This
works fine with old GVR version somehow. The fix is in VrShellImpl.
It also fixed recentering issue as described in 732945

Bug: 706842,  732945 
Change-Id: I32dcb0d69e37a9456056d3cc9c4abab2c3527342
Reviewed-on: https://chromium-review.googlesource.com/537393
Commit-Queue: Biao She <bshe@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#479821}
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/DEPS
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/chrome/android/java/src/org/chromium/chrome/browser/vr_shell/VrShellImpl.java
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/BUILD.gn
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/README.chromium
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/common_library.aar.sha1
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/gvr_api_jni.h
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/libgvr_shim_static_arm.a.sha1
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/libgvr_shim_static_arm64.a.sha1
[modify] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/native_callbacks_jni.h
[add] https://crrev.com/9d3ddcc4abeab5c79537dfd0ec8758924f74c5e7/third_party/gvr-android-sdk/proguard-gvr-chromium.txt

Comment 5 by vollick@chromium.org, Jul 10 2017

Owner: bshe@chromium.org
Status: Assigned (was: Available)
Biao, is this fixed?

Comment 6 by vollick@chromium.org, Jul 10 2017

Status: Fixed (was: Assigned)
Looks like this is working. Checked for both the VR browser and WebVR.

Comment 7 by btebbs@chromium.org, Jul 4

Components: Blink>WebXR
►

Sign in to add a comment