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

Issue 600949 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Apr 2016
Cc:
omrilio@chromium.org
█ pstew@chromium.org
x...@chromium.org
ajha@chromium.org
abodenha@chromium.org
█ kavvaru@chromium.org
pucchakayala@chromium.org
tbuck...@chromium.org
kathrelk...@chromium.org
steve...@chromium.org
songsuk@chromium.org
█ merkulova@chromium.org
█ durga.behera@chromium.org
█ jleong@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Bluetooth is seen enabled by default in OOBE

Project Member Reported by sandeepk...@techmahindra.com, Apr 6 2016 
Version: 51.0.2699.0/8155.0.0 (Official Build) dev-channel Daisy, Peppy, Quawks
<b>OS: <please tell me it's not XP></b>

What steps will reproduce the problem?
(1) Try to recover the OS via usb>> go to uber tray>> and observe the Bluetooth option

Expected: Bluetooth should not be enabled by default 
Actual: Instead Bluetooth is seen enabled by default (Refer screenshot)

This is a Regression issue as issue is not seen in M50: 50.0.2661.57/7978.36.0 beta-channel Daisy

Issue is not applicable to Linux and Windows

@tbuckley: Please help me in reassigning if the issue is not related to you
IMG_0595.JPG
953 KB View Download

Comment 1 by kavvaru@chromium.org, Apr 6 2016

Cc: songsuk@chromium.org pucchakayala@chromium.org
Able to reproduce the issue on Peppy using chrome version 51.0.2699.0/8155.0.0

Comment 2 by pbath...@chromium.org, Apr 6 2016

Cc: jleong@chromium.org kathrelk...@chromium.org
Components: UI>Shell>OOBE
I was able to reproduce the issue on 51.0.2699.0/ 8155.0.0 peppy and daisy

1.The Bluetooth stays enabled by default in the OOBE screen after recovery install, once we login the Bluetooth is disabled by default.It stays disabled if we logout or try to add another user.

2.On daisy , this issue doesn't happen on 51.0.2693.2/8133.0.0 and happens on 51.0.2694.1/8134.0.0

Comment 3 by tbuck...@chromium.org, Apr 8 2016

Cc: tbuck...@chromium.org
Owner: steve...@chromium.org
@stevenjb, could you take a look at this?

Comment 4 by steve...@chromium.org, Apr 8 2016

Labels: Needs-Feedback
Can you confirm whether or not Bluetooth appears enabled in the system tray? i.e. is Bluetooth actually enabled, or is the Settings UI incorrect?

Comment 5 by frankt3...@gmail.com, Apr 8 2016 

#CBC-RS/TC-watchlist

Comment 6 by pbath...@chromium.org, Apr 8 2016

Labels: -Needs-Feedback
Bluetooth is actually enabled....we can scan and connect to BT devices

Comment 7 Deleted

Comment 8 by steve...@chromium.org, Apr 8 2016

Summary: Bluetooth is seen enabled by default in OOBE (was: Bluetooth is seen enabled by default in Chrome://settings)

Comment 9 by steve...@chromium.org, Apr 8 2016 

Also, are we sure this is not intentional behavior so that devices can be paired to a mouse or keyboard during OOBE?

Comment 10 by pbath...@chromium.org, Apr 8 2016 

As mentioned in 1st point in #2, BT is disabled once we login. So devices connected in OOBE screen do not function once we login

Comment 11 by steve...@chromium.org, Apr 8 2016

Cc: abodenha@chromium.org
I guess step one is to determine what the expected behavior is here.

Comment 12 by kathrelk...@chromium.org, Apr 20 2016

Cc: merkulova@chromium.org omrilio@chromium.org
any update on whether this is a OOBE feature gone wrong or just broken?

Comment 13 by omrilio@chromium.org, Apr 20 2016

Cc: x...@chromium.org
Status: WontFix (was: Untriaged)
This is working as intended. 
Bluetooth should be enabled when OOBE starts to allow the bootstrapping process to happen. If user continues with the screens Bluetooth will be disabled.

See issue 537354 for more details.
►

Sign in to add a comment