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

Issue 892985 link

Starred by 7 users

Issue metadata

Status: Duplicate
Merged: issue 904571
Owner: ----
Closed: Dec 1
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Bluetooth forcefully disables after some time in Sleep Mode

Reported by scamdyn@gmail.com, Oct 7

Issue description

Chrome Version       : 71.0.3567.0
OS Version: 11135.0.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. Make sure Bluetooth can be toggled. 
2. Put the Chromebook in sleep mode for a few minutes. 
3. Bluetooth will be forcefully disabled after being in sleep mode. 

What is the expected result?
Bluetooth should be able to be toggled. 

What happens instead of that?
Bluetooth is forcefully disabled and cannot be toggled. 

Please provide any additional information below. Attach a screenshot if
possible.

Google Chrome	71.0.3567.0 (Official Build) canary (64-bit)
Revision	7c7bc73fc5f252e28f2308c81de4760e49990542-refs/branch-heads/3567@{#1}
Platform	11135.0.0 (Official Build) canary-channel wolf
Firmware Version	Google_Wolf.4389.24.62

First screenshot shows Bluetooth is forcefully disabled (greyed out) and Bluetooth does not show up in the System Menu. 

Second screenshot shows Bluetooth can be enabled after a full restart. Scenario in screenshot one happens after some time in sleep mode. 

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 11135.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3567.0 Safari/537.36



 
Screenshot 2018-10-07 at 12.50.20 PM.png
97.1 KB View Download
Screenshot 2018-10-07 at 1.19.54 PM.png
73.9 KB View Download
This also happens to me on eve using 11021.34.0 / 70.0.3538.41 beta after coming out of sleep or hibernation.

I have enabled & disabled the #newblue flag and neither setting makes a difference.

I also tried enabling & disabling 'newblue' in crosh with no effect.

I'll be happy to provide more data, just let me know what's needed.
Components: OS>Systems>Bluetooth
Components: IO>Bluetooth
Labels: -Pri-3 Hotlist-ConOps-CrOS M-71 Pri-2
Labels: Hotlist-ConOps-Source-Forum
Cc: josephsih@chromium.org
Components: -IO>Bluetooth
Same exact issue on the Pixelbook
Screenshot 2018-11-09 at 13.45.28.png
26.3 KB View Download
Cc: adlr@chromium.org
Cc: khorimoto@chromium.org urbanvili@google.com kbleicher@chromium.org
Still seeing user reports on recent M71 Beta builds about bluetooth turning off after sleep and being unable to re-enable it.

From Pixelbooks on 71.0.3578.71 beta: 
- https://listnr.corp.google.com/report/85817086469
- https://listnr.corp.google.com/report/85816098743
- https://listnr.corp.google.com/report/85816094350
- https://listnr.corp.google.com/report/85810261504

Mergedinto: 904571
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment