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

Issue 883012 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Bluetooth disappearing on Lenovo devices

Project Member Reported by vkhabarov@chromium.org, Sep 11

Issue description

ChromeOS version: 
68.0.3440.118 
69.0.3497.35 
70.0.3532.8 
ChromeOS device model: Reks (they also report Lenovo 100E, but I've seen logs only from Reks)
Case#: 16830033

Description:
The Bluetooth option cannot be turned on (disappears from settings), in some other devices it is on but it will randomly disconnect 

Steps to reproduce: 
1) Turn on the device 
2) Sign in with any account, public session or guest mode 
3) Try to turn on the Bluetooth 


Current Behavior / Reproduction: 
The option will be grayed out or it will disconnect after a few seconds 

Expected Behavior: 
Bluetooth works

Drive link to logs: 
Policies - 
https://drive.google.com/open?id=18yNyDY5OQYH8KWFLzWHW91GJ8BToy-mA
Debug logs
https://drive.google.com/open?id=1PbKARxUFVelZkLBR_bFJp7PcT9t7YS6G
https://drive.google.com/open?id=1XmtBdj-nVuvoEUjSHNKdG-E31kPs8i2O
https://drive.google.com/open?id=1mZ9CNa_KeytRfYwCIaPgKaAe7wXvjV8n
https://drive.google.com/open?id=18olQH1NL1F75UugctVn8UXehZ1Wm5lpf
https://drive.google.com/open?id=1DIFRvWaS8h81UErgPexOWuPYoZjLwvsR

In newer version logs I see messages about usb over-current and then btusb device reconnect, which might be indication of hardware issue, but customer says this issue affects all of their devices (N22 and 100e ones)

 
Cc: shijinabraham@chromium.org
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Comment 3 by sylcat@google.com, Jan 17 (5 days ago)

Status: Archived (was: Untriaged)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment