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

Issue 804375 link

Starred by 2 users
Status: WontFix
Owner:
█ asimjour@chromium.org
Last visit > 30 days ago
Closed: Aug 27
Cc:
vsupruniuk@google.com
dougman@chromium.org
█ bshe@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-XR
Proj-XR-VR



Sign in to add a comment

After granting microphone permissions for voice input, Chrome VR isn't always automatically re-started

Project Member Reported by dbbrooks@chromium.org, Jan 22 2018 
Chrome Version: OS: Android N
Device: Samsung Galaxy S8+

What steps will reproduce the problem?
** This doesn't repro every time. I find it often right after upgrading Chrome.
(1) Make sure Chrome does not have microphone permissions
(2) Open Chrome and put the device in the Daydream headset
(3) In Chrome VR, click on the Voice input button
(4) Confirm prompt to allow Chrome access to the microphone and follow prompt to remove device from headset.
(5) Click Allow in 2D Chrome

What is the expected result? 
Chrome VR is supposed to automatically restart. 

What happens instead? 
I've found that often time, the first time this is done on a fresh upgrade of Chrome, Chrome VR doesn't automatically restart. It's not 100% reproducible but I see it often.

If you immediately follow the process again, it will work.
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 22 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/a48ebb2f88bb29f76001d9da52b420ab25fbdc41

commit a48ebb2f88bb29f76001d9da52b420ab25fbdc41
Author: David Riley <davidriley@chromium.org>
Date: Mon Jan 22 18:01:13 2018

som_alerts_dispatcher: Handle failed build look ups.

Change 5465002a "Add mst Android PFQ Configuration for master-arc-dev
Android branch" broke SoM dispatcher because it was searching for a
master build which does not exist until there is a waterfall restart.

BUG= chromium:804375 
TEST=som_alerts_dispatcher

Change-Id: I9c9b0fa56f2af0326d614f3348689c52b099b846
Reviewed-on: https://chromium-review.googlesource.com/879107
Commit-Queue: David Riley <davidriley@chromium.org>
Tested-by: David Riley <davidriley@chromium.org>
Trybot-Ready: David Riley <davidriley@chromium.org>
Reviewed-by: Jacob Kopczynski <jkop@chromium.org>

[modify] https://crrev.com/a48ebb2f88bb29f76001d9da52b420ab25fbdc41/scripts/som_alerts_dispatcher.py

Comment 2 by tiborg@chromium.org, Jan 23 2018

Labels: -Pri-2 -Proj-VR-Shell Proj-VR M-66 Pri-1
Owner: asimjour@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by dbbrooks@chromium.org, Feb 23 2018 

This just repro'd for me on Pixel 66.0.3350.12

Comment 4 by sko...@chromium.org, Feb 27 2018

Labels: -Pri-1 Pri-2

Comment 5 by ericde@google.com, Mar 21 2018

Cc: bshe@chromium.org
any updates on this one?

Comment 6 by ericde@chromium.org, May 1 2018

Labels: -M-66
removing milestone as M66 is already on stable, and no new milestone has been established.

Comment 7 by asimjour@chromium.org, Aug 27

Status: WontFix (was: Assigned)
I don't think this is reproducible now. Feel free to file a new bug if it starts happening again.
►

Sign in to add a comment