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

Issue 895105 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
zalcorn@chromium.org
abodenha@chromium.org
r...@chromium.org
█ igo@chromium.org
alemate@chromium.org
jdufault@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Resurface Bluetooth dialog if device is rebooted during OOBE and has no input devices

Project Member Reported by kuscher@google.com, Oct 13 

Google Chrome	70.0.3538.58 (Official Build) beta (64-bit)
Platform	11021.45.0 (Official Build) beta-channel fizz-unibuild

What steps will reproduce the problem?
(1) Connect a new Fizz device to power
(2) Turn it on with a monitor plugged in
(3) Do not have mouse or keyboard connected

What is the expected result?
I get to see the Bluetooth screen trying to connect to devices

What happens instead?
No such screen showed. I had to find a wired mouse from 1956 to get going

Potential ideas what is at fault?
(1) I also connected the Monitors USB hub. That had nothing else connected to it but maybe it was misdetected as input? (would be a bug)
(2) This device was enterprise enrolled. Maybe our logic got snitched?

Comment 1 by abodenha@google.com, Oct 13

Components: UI>Shell>OOBE

Comment 2 by zalcorn@chromium.org, Oct 15 

Almost certainly due to enrollment - chromestop would have connected keyboard for that step. 
alemate@, do we have logic to re-surface the bluetooth screen in this case?

Comment 3 by zalcorn@chromium.org, Nov 13

Cc: alemate@chromium.org jdufault@chromium.org
Labels: -Type-Bug Hotlist-OOBE-polish Type-Feature
Status: Available (was: Untriaged)
Summary: Resurface Bluetooth dialog if device is rebooted during OOBE and has no input devices (was: Fizz did not ask me to connect Bluetooth devices)
Updating to reflect the particular request here.
►

Sign in to add a comment