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

Issue 655425 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Bluetooth mouse/keyboard can't wake up the hp chromebox from sleep.

Reported by qs1...@gmail.com, Oct 13 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Platform: Platform version: 8530.96.0

Steps to reproduce the problem:
1. wait the chromebox to sleep;
2. use the logitech M337 bluetooth mouse and K380 bluetooth keyboard to activate chromebox;
3. finally you will find can't wake up the chromebox.
4. after press the power button, both of the bluetooth devices can't connect to the chromebox.

What is the expected behavior?
There is no problem until chrome version 53.
I hope the bluetooth mouse/keyboard allways connect to the chromebox and work.

What went wrong?
I suspect when the chromebox sleeps, turned off the Bluetooth function.

Did this work before? Yes about 52.0.2743.116 or before, too detailed I can not remember.

Chrome version: 53.0.2785.154  Channel: stable
OS Version: 53.0.2785.154
Flash Version: Shockwave Flash
 
Components: OS>Systems>Bluetooth

Comment 2 by qs1...@gmail.com, Nov 18 2016

Until now the Bluetooth mouse and keyboard can not activate chromebox!
I checked on M-56 build on Zako ( HP chromebox) and i could see that the BT mouse and keyboard wer able to wake the device from sleep.

I used logitech M337 mouse and k830 keyboard.

qs1028@ --  can you update to the latest build and check whether the issue is still happening
Labels: Needs-Feedback

Comment 5 by qs1...@gmail.com, Dec 18 2016

Thanks your comments.
I'v already update my hp chormebox to the latest version 55.0.2883.87, as before it works in a couple of hours but can't wake up the chomebox use logitech M337 K380 the next day !
Cc: st...@chromium.org mcchou@chromium.org
 Issue 652093  has been merged into this issue.

Comment 7 by mcchou@google.com, Dec 19 2016

pbathini@, can you help with reproducing the issue and collecting /var/log/messages with debug logging enabled? In order to enable the debug flag, please add "-d" option in /etc/init/bluetooth.conf and reboot the DUT. Thanks.

Comment 8 by qs1...@gmail.com, Dec 21 2016

Oh! This is too hard for me,I'm just a regular user!and I in China, not
through vpn data is not transmitted...
Project Member

Comment 9 by sheriffbot@chromium.org, Dec 28 2016

Labels: -Needs-Feedback Needs-Review
Owner: kathrelk...@chromium.org
Thank you for providing more feedback. Adding requester "kathrelkeld@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by qs1...@gmail.com, Dec 31 2016

This morning,i found press power button to active the chromebox from sleep
state first then the logitech bluetooth mouse/keyboard can connect to it
and effective!
But as before can not be activated by the logitech bluetooth mouse/keyboard
!
Chromeos version number: 55.0.2883.87(64bit)
The chromeos is being upgraded to 55.0.2883.103(64bit),then I will feedback
!


​

Comment 11 by qs1...@gmail.com, Dec 31 2016

This morning,i found press power button to active the chromebox from sleep state first then the logitech bluetooth mouse/keyboard can connect to it and effective!
But as before can not be activated by the logitech bluetooth mouse/keyboard !
Chromeos version number: 55.0.2883.87(64bit)
The chromeos is being upgraded to 55.0.2883.103(64bit),then I will feedback !
217545209072603793.jpg
48.8 KB View Download
566888773968594648.jpg
48.9 KB View Download
I was on 55.0.2883.103 build on HP chromebox for last few days

I was using Logitech k830 keyboard and logitech M535 BT mouse. 

I was able to wake the chromebox from sleep .

qs1028@ --  Did you see the issue still on 55.0.2883.103 build.

Comment 13 by qs1...@gmail.com, Jan 12 2017

This morning,i found press power button to active the chromebox from sleep
state first then the logitech bluetooth mouse/keyboard can connect to it
and effective!
But as before can not be activated by the logitech bluetooth mouse/keyboard
!
Chromeos version number: 55.0.2883.87(64bit)
The chromeos is being upgraded to 55.0.2883.103(64bit),then I will feedback
!


​
Cc: kathrelk...@chromium.org
Owner: mcchou@chromium.org
Status: Untriaged (was: Unconfirmed)
Re #7, 

Able to reproduce the issue on 55.0.2883.105/8872.76.0 (Official Build) stable-channel zako.

Connected BT keyboard (k830) and left the machine idle to go to sleep overnight.
In the morning when i clicked the BT keyboard, the Chromebox didn't wakeup. I used the USB mouse to wake it up. After wakeup , when i see the BT devices, the BT keyboard still shows as connected but is not functional. We need to remove it and connect again to use it again.

Attached logs and /var/log/messages with Bluetooth debug log enabled.
messages.txt
710 KB View Download
log-012417-110232.tar.gz
1.9 MB Download
Cc: r...@chromium.org
Cc: -st...@chromium.org
Labels: -Needs-Review
Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]
Status: Assigned (was: Untriaged)

Comment 19 by fles...@gmail.com, Oct 17 2017

I have been getting this on 
Google Chrome	61.0.3163.120 (Official Build) (64-bit)
Revision	0
Platform	9765.81.0 (Official Build) stable-channel zako
Firmware Version	Google_Zako.5219.30.0

for the past week or so. When I leave the HP Chromebox idle for say an hour and come back, my Kenesis bluetooth keyboard is no longer connected. Checking the system tray shows the 'Bluetooth enabled' label greyed out; clicking it had no effect. 

Today I tried signing out and signing in, and that resolved the issue.
Cc: -kathrelk...@chromium.org rjahagir@chromium.org kobbad@chromium.org
Status: WontFix (was: Assigned)
This issue is being tracked in b/64035404

Sign in to add a comment