#42, yes earlier today I had the situation where Bluetooth on my Pixelbook was greyed out and I had to reboot.

Since the issue reporter isn't working for my Pixelbook (I still think this may be because I have two Chromebooks and it only works for the first one I got, the Pro), let me know if you need me to attach anything else next time this happens.

Hi wpwoodjr@gmail.com, please submit a feedback report and send me the device logs next time you see the bluetooth button greyed out. I will check what happens. Thank you for filing the feedback reports!

Ref  issue #781882 , here I am connected to Bose Bluetooth headphones but no sound is coming out.  Volume is at midpoint, and volume controls on headphones and on Pixelbook appear to work but no sound comes out of the headphones.  Disconnecting and reconnecting the headphones does not help.  Was working until I went into standby and back out again.  Will have to reboot now.

Device log attached. Feedback issue also filed.

Deleted: Device Log2.zip 52.5 KB

Device Log2.zip 52.5 KB Download

Re #45 actually now the headphones are working again, no reboot necessary.  I went into standby and then back out, and also turned the headphones off then on again.

Ref issue # 781882, now the Pixelbook will not connect to my Bose headphones.  They are visible as a paired device, but when I click on them the Pixelbook will not connect to them, even after turning them off then on again.

Deleted: Device Log3.zip 50.6 KB

Device Log3.zip 50.6 KB Download

#47 actually this was my fault.  I had another device connected to the headphones, preventing them from connecting to the Pixelbook.  Sorry!

FWIW, I just got the i7 Version of the PixelBook, and Bluetooth has been flawless for the past couple of days.

#49 seldnp...@gmail.com that's great, maybe the issue is resolved on your device build.

Test: setup smart lock with your android phone and pixelbook. Lock your device and ensure smartlock works to unlock your device. Then allow your device to automatically sleep. When you wake it up, double check that bluetooth is still enabled and working, and try to use smart lock to unlock your device.

Report: Once you are able to login then submit a support ticket (SHIFT-ALT-i) and include  issue #781882 . This will allow the developers to have proof that it's working along your hardware info.

Just filed a couple of reports on this from the i7. Hopefully they made it through. Whatever's happening here is really working.

I just filed a report. I have the same issue with Bluetooth deactivating during/after sleep. 

Just filed a report for Pixelbook i5:
Was listening to Youtube, when Bluetooth headphones disconnected.  Sound now coming from speakers.  Yet Pixelbook Bluetooth status shows BT enabled, and is showing the headphones as still connected.  Also there is no option on volume control to switch from internal speakers to Bluetooth headphones.  

Tried turning headphones off and back on, Pixelbook shows headphones connected, but no sound.

Turned Bluetooth off on Pixelbook, headphones still show as connected!?

Turned BT back on, still no sound from headphones, as they are not really connected.

Deleted: Device Log5.zip 43.4 KB

Device Log5.zip 43.4 KB Download

After reporting comment #53, went into standby and came back out.  Bluetooth  has disappeared from status tray and BT is grayed out in settings.  Filed a report, also see device log attached.

Deleted: Device Log6.zip 43.2 KB

Device Log6.zip 43.2 KB Download

Sane thing as comment 54 just happened to me. I filed a report as well.

#44, josephsih@chromium.org do you have what you need now?

Just filed feedback (see text below) for my Pixelbook.  Also see attached device log.

Ref  issue #781882 . Bluetooth just died and is greyed out in settings, cannot enable it.  Bluetooth not visible at all in shelf settings slideout.

Deleted: Device Log.zip 45.8 KB

Device Log.zip 45.8 KB Download

See attached image of shelf settings screen with no Bluetooth shown

Deleted: ink (1).png 358 KB

	ink (1).png 358 KB View Download

-- BETA --
Status:  Resolved
Release:  10176.54.0 (Official Build) beta-channel eve
Device:  Pixelbook
Comment:  

-- STABLE --
Status:  Issue still Exists
Release:  10032.86.0 (Official Build) stable-channel eve
Device:  Pixelbook
Comment:  The bluetooth still continues to be disabled automatically when device sleeps.

I'm on 10176.54.0 and Bluetooth still disables automatically when the Pixelbook sleeps. 

Submitted another report just now. 

#61 where does that info come from?

Just submitted a feedback report referencing this issue for my Pixelbook:
My Bluetooth mouse was working fine, then stopped working even though it is still showing as connected.

Then I turned the Bluetooth mouse off, and it is STILL showing as connected!

Updated to the official beta build a couple days ago. 10176.54.0    This bluetooth issue is still happening, it is not resolved, it just occured again today, after a wakeup the bluetooth will not turn back on and is greyed out. 

I was listening to Bluetooth headphones on my Samsung Chromebook Pro for a couple of hours.  During that time the headphones disconnected and reconnected several times even though I was only a foot or two away from the Chromebook.  Put Chromebook Pro into standby, and resumed about 4 hours later.  Bluetooth has disappeared from the shelf settings, and is grayed out in Chrome settings.

See attached device log.  I also filed a feedback report and referenced this issue.

Deleted: Device Log.zip 43.6 KB

Device Log.zip 43.6 KB Download

Forgot to say in # 67 that I was running Version 64.0.3282.110, platform 10176.58.1 (Official Build) beta-channel caroline

I submitted feedback and included the Issue # in the description of problem.  Hopefully it helps.  Usually I'm able to turn bluetooth back on in the quick settings after manually logging myself in.  This is the second time I was not able, with it greyed out in the settings.  Both of those happened recently.  I also powerwashed yesterday to resolve a problem with the automatic backlight not properly working, so I don't even know.

Let me know if there's any further assistance I can provide!  Thanks!

Hi, what's the status on this?  Do you need more feedback reports or do you have enough now?  It seems clear this is not just a bug in eve, but is more widespread, as it affects caroline too (#67).

My i7 PixelBook is also experiencing this issue now since the last milestone (64.0.3282.122), which is very disappointing. 

Happens on my Pixelbook (stable channel) as well.

I see this is blocked on 779206, but I don't have permission to view that.  I'm guessing it's security related or something along those lines.  At any rate, it would at least be good to know if you need more feedback reports or other user information.  We'd like to help you get it fixed!

Same issue here with Pixelbook on the beta channel

Same issue here now too. On latest stable channel. I am having to restart to get access to the bluetooth button, otherwise it is greyed out.

Issue remains (as described above), only to be resolved by hard reset and solution is very short term.  Issue was on my old chromebook pixel (2015), spent time with support them too, guessing it's a deep issue.

From the comments, it sounds like the beta versions have the same issue.

PixelBook i5 Version 63.0.3239.140 (Official Build) (64-bit)

Happy to help!

I tend to agree. Bluetooth is all shades of fucked up on the Pixelbook as well as in the 2013 Chromebook Pixel. It always took ages and a lot of patience to pair simple periphery like keyboards to the Chromebook Pixel and the Pixelbook hasn't improved on that.

I am experiencing this issue as well (with latest build).  Bluetooth works for some time then becomes disabled and can't be restarted without a reboot.  I will upload logs the next time the issue occurs.

I bought my Pixelbook 3 days ago, along with a Logitech M535 mouse.  I noticed BT connectivity issue as others have mentioned.  However, the issue always occurred when the mouse was connected.  I tried to play music over my BT speaker (Aiwa Exos 9) with the mouse turned off, and have not experienced any issues so far today.  I'm beginning to suspect it has something to do with the M535--at least in my brief experience.  

I'm not sure if there is any running list of devices with known issues. 

Connectivity issues with device:
Logitech M535 (Bt mouse)

No connectivity issues with device:
Aiwa Exos 9 (BT speaker) 

I have one other BT speaker and one BT headphones to test in the coming days and will make note of my observations.  

If anyone has used a BT mouse without any issues, please let me know as I might be looking for a replacement if I go a couple of days w/o issues when the M535 is not connected.  

A reddit thread was started on this about a week ago, I went to reddit looking for the solution to this issues. https://www.reddit.com/r/PixelBook/comments/7z249i/my_biggest_complaint_about_the_pixelbook_smart/

I also have the issue of it asking for my pin, I type in my pin, and it says it can't be verified and I have to type in my password. So smart unlock isn't working at all.

It's still an issue on Beta after the latest update to Version 65.0.3325.107 (Official Build) beta (64-bit).  

I'm pretty surprised that this has gone unfixed for so long given how impactful it is to users.  To have your mouse stop working and require a reboot to resolve is crazy annoying.

Especially since it affects users who paid at least a thousand dollars for a premium device. I'm really disappointed this doesn't seem to have proper priority.

Over the past monnth since I got the pixelbook, the bluetooth bug is really the most frustrating.

Why is this not prioritised?

I've had my bluetooth headphones dropped during calls. really bad.

I've been on the Beta channel eagerly awaiting a fix for these bluetooth issues for the past 2 months. The smart lock features are unusable (although fantastic on those rare occasions when they choose to work) and I've also had multiple bluetooth audio devices spontaneously drop out requiring a restart - I resorted to just turning bluetooth off on my Pixelbook which is disappointing.

I've had my bluetooth mouse disconnected randomly several times during a session, or trouble connecting to the mouse since I got this Pixelbook 1 month ago. This is seriously frustrating. 

I thought this was just an issue with the mouse I was using since it was an Apple bluetooth mouse, but it turns out that this is an issue with the Pixelbook's bluetooth because I'm also having trouble enabling bluetooth on Pixelbook at all.

My problematic Pixelbook experiences with multiple Bluetooth failures mirror those above; in fine grain detail, they are threefold...

1. Getting Connected Failure
I use Bluetooth to connect to a Bluetooth-equipped speaker system, namely a Trust Tytan 2.1 Bluetooth Speaker System with Subwoofer [1]. On three Android devices [2], it takes one screen tap to establish a Bluetooth connection to this speaker system - but on my Pixelbook, at around one screen tap per second, it takes between 5 and 25 screen taps to get the Pixelbook to establish a Bluetooth connection. On the myriad failed attempts, I see "Connecting..." for under a second before it vanishes, prompting yet another screen tap connection attempt.

2. Sporadic Connection Dropping Failure
After having eventually connected to the Trust Tytan Bluetooth Speaker System, then part way through watching video (in, eg: YouTube in the Chrome browser, or with the 'MX Player Pro' Android app), the Pixelbook-speaker Bluetooth connection will cut out sporadically, with the video's audio output switching from the speaker system back to the Pixelbook's speakers. Occasionally, before I am forced to pause playback and manually re-establish the Pixelbook-speaker Bluetooth connection, the Pixelbook spontaneously reconnects to the speaker system, and the video's audio output switches back to the speaker system again; but usually, I'm forced to manually re-establish the Pixelbook-speaker Bluetooth connection. My three Android devices have never suffered from any Bluetooth connection dropping to the speaker system.

3. Bluetooth Setting Vanishes Failure
About once a fortnight, the whole Bluetooth system appears to vanish from the Pixelbook. On the status panel, between the WiFi control and the volume control, where the Bluetooth setting control usually appears, there's now nothing but whitespace, as illustrated in the attached screenshots from 14 and 22 Mar 2018. Only shutting down and booting up my Pixelbook will restore the Bluetooth setting control to visibility again.

What Ought To Happen Instead?
1. One Tap Connection: it should only take ONE tap on a paired Bluetooth device, such as my speaker system, to immediately establish a Pixelbook-speaker Bluetooth connection in Chrome OS - as indeed it does with my three Android devices.
2. Consistent Bluetooth Connection: once a Pixelbook-[device] Bluetooth connection has been established by Chrome OS, it should MAINTAIN a rock solid connection, rather than sporadically dropping the connection; again, all three of my Android devices flawlessly maintain such a consistent Bluetooth connection.
3. Persistent Bluetooth Setting Control: the Chrome OS status panel's Bluetooth setting control should ALWAYS be present and available to use, rather than intermittently disappearing, thereby requiring a system reboot to restore it.

Pixelbook Bluetooth: Persistently Problematic
These Pixelbook Bluetooth failures have been consistent and persistent across four months usage and three iterations of Chrome OS:
1. Chrome OS 62 - factory default version, as delivered on Thu 23 Nov 2017:
● Chrome 62.0.3202.97 (Official Build) (64-bit)
● Platform 9901.77.0 (Official Build) stable-channel eve
2. Chrome OS 63 - from Fri 12 Jan 2018 to Mon 25 Feb 2018:
● Chrome 63.0.3239.140 (Official Build) (64-bit)
● Platform 10032.86.0 (Official Build) stable-channel eve
3. Chrome OS 64 - current up-to-date version, on Thu 22 Mar 2018:
● Chrome 64.0.3282.190 (Official Build) (64-bit)
● Platform 10176.76.0 (Official Build) stable-channel eve
Now I've learnt (in this thread) that reporting each Bluetooth failure instance via the "shift-alt-i" 'Report an issue' mechanism, citing 'Issue Number 781882', helps the developers "to triage the problem with logs", I will in future file multiple Bluetooth failure issue reports.

Please Get This Bug FIXED! 
I thought that in paying £1,100 for a Google Pixelbook and Pen, and after SIX years of Chromebook development (alongside TEN years of Bluetooth  speakers being available), then I'd be assured of a premium convertible PC that worked perfectly out of the box. But these Bluetooth failure reports date back to 06 Nov 2017, have been voted up by 52 users, and haven't even been raised to Priority 1 for developing a bug FIX for the currently wildly  problematic Chrome OS Bluetooth implementation (as attested to by the user comments above).

Google have already proved that a properly functional Bluetooth implementation is entirely possible with Android OS, as demonstrated by my three Android devices, from KitKat 4.4.2 to Oreo 8.0.0, persistently making consistent and flawless Bluetooth connections to my Bluetooth speaker system. So on behalf of the vast number of Chrome OS users who are adversely affected by this seriously annoying bug, my plea to the Chrome OS Development Team is:
1. Please demonstrate that this widespread and long-standing Bluetooth bug it's getting the serious developer attention it deserves by raising its Priority to Level 1.
2. Please devote sufficient development team time, attention, and resources to making the Chrome OS Bluetooth implementation works as flawlessly as  Android Bluetooth already does.
3. Please roll out a bug-FIXED version of the Chrome OS Bluetooth implementation as soon as possible.

Thanks in advance for getting these troublesome problems ironed out of Chrome OS with alacrity.

[1] Trust Tytan 2.1 Bluetooth Speaker System with Subwoofer:
» https://www.amazon.co.uk/gp/product/B00H4ZRFPM

[2] Three Android devices - all of these devices, each of which is running a stock Android version, connect to my Trust Tytan Bluetooth Speaker System on the FIRST attempt, every time (cf. Pixelbook's 5 to 25 attempts to make ONE connection), and all three STAY connected (cf. Pixelbook's sporadic connection dropping):
1. OnePlus 3T A3003 smartphone, Android Oreo 8.0.0
2. Samsung Galaxy Note Pro 12.2 SM-P900 tablet, Android Lollipop 5.0.2
3. ASUS Fonepad Note FHD 6 ME560CG smartphone, Android KitKat 4.4.2

Deleted: Pixelbook Bluetooth Bug.png 757 KB

	Pixelbook Bluetooth Bug.png 757 KB View Download

Can verify this issue on pixelbook through 65 beta at least. Recurrent problem that requires hard restart.  

I have updated chrome to current version, tried restarting several times, unpair and repair to phone and can not get a consistent bluetooth connection with my phone.  The auto unlock with phone feature will not work.  When I power up the chromebook it says bluetooth is disabled so it won't try to connect.  Then when I check settings bluetooth is enabled.  What is going on.  This bluetooth connectivity issue is enough to make me give up on my chromebook and just go back to MS.  When will this be resolved?

I must be quite lucky as the only issue I have is when resuming from sleep. I'm on a Samsung CB Plus and connect to a Jabra Pulse headset, Multiple Aether Cone speakers, a Naim Muso QB and a Plantronics 975 Headset (not all at the same time!) and this happens without issue, from a cold boot. I've never had any dropouts, I use Smart unlock with a Galaxy S8+, which works fine... I say it al works, it works until I've closed the lid and the CB has slept. As soon as I open the lid, Bluetooth is off message and although it's generally there in the options (I've also occasionally experienced the missing BT option, only once or twice and again only once resuming from sleep) it's impossible to enable it, the toggle does nothing.  

Just performed an alt-vol up-x. I too experience this pretty regularly. 

Eve/Pixelbook i7

Chrome:  66.0.3359.102 (Official Build) beta (64-bit)
Platform:  10452.54.0 (Official Build) beta-channel eve

I too have Bluetooth reliability issues (Samsung Chromebook Pro) which are very annoying. Aside from the Bluetooth option under Settings occasionally disappearing, or turning itself off, the connection to my Lindy BNX-60 BT headphones continually drops in and out. Sometimes it'll reconnect automatically after a few seconds, other times it requires a reboot etc.. I'm guessing from this thread that this is a know issue and there's a fix planned??

I can confirm I am having the exact same issues

Bluetooth disconnects and reconnects itself to my Bose Headphones

on opening Pixelbook Bluetooth is disabled (roughly half the time) - have to turn device on and off to be able to enable it.

have to try and connect the headphones to the PB multiple times before it will actually connect.

Having the same issue. Effecting the ability to instant tether which has always been flakey. Perhaps related to Bluetooth all along? Please fix 

Version 66.0.3359.137 (Official Build) (64-bit)
Platform
10452.74.0 (Official Build) stable-channel eve
Firmware
Google_Eve.9584.107.0

...same...

I was having this issue on my Chromebook Plus and needed a reboot to fix. I'm now on a Pixelbook on Dev channel and it's still turning off, but does not need a reboot to fix.

I've moved over to the dev channel (68) and enabled the new Bluetooth stack... still having the same exact issue. It seems as if there's been no movement in getting this highly annoying issue resolved.

I have to admit that in the near decade of using Google software (Android user since 2009) and now their own hardware, Google-branded anyway, I have had troublesome Bluetooth issues. 

Bluetooth and Wifi implementation is very less than ideal on the Pixelbook. I have seen bluetooth randomly disabling itself and could not really pinpoint a reason why. It could happen at any time. 

The worst bluetooth issue for me is that it causes wifi slowdown. I could barely get unstable 30mbit down speed when bluetooth is on, full wifi speed with bluetooth off.

(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.

Just received my Pixelbook (June 2017) and also having an issue with this.

Bluetooth controller gone after coming back from sleep.

bt_console:

[bluetooth]# list
[bluetooth]# power on
No default controller available

system log:

2018-06-21T13:42:19.705498-04:00 ERR kernel: [16710.138853] Bluetooth: btusb.c:btusb_setup_intel() hci0 sending initial HCI reset command failed (-110)

Today is my 2nd day with my pixelbook and i started seeing this  issue 4  hrs after opening the box last night. issue occurs 90% when unlocking pixelbook with my phone.and at times the pixelbook tries to reconnect with my speaker but end up connecting then disconnecting over and over.now im not using anything.and im not sure if this is related but in my experiences with this issue i would have problems using the unlock with phone feature.so i just type in my password.

Different bugid but seems to be the same issue. Temp fix in place on Beta channel. 

arc_bluetooth_bridge: Increase Android power intent timeout

Android takes 3-4 seconds to fulfill power state change, so the timeout
of 5 seconds is too close that the probability of the timeout hit is
high enough to happen to users. As a result, users often encounter
Bluetooth turned off by itself. This CL changes the timeout to 8 seconds
to provide safer buffer, if there is no response from Android after 8
seconds it is considered as lost (will never respond).

Future larger work is needed to avoid relying on timeout to make it more
robust, but at this moment we need a low-risk solution to be merged to
stable channel.

BUG= 843650 
TBR=sonnysasaka@chromium.org

(cherry picked from commit d680078aa1a35778a523c23f2ea9a6d5243ac9cb)

Change-Id: I9aded127e3eb510ff58b1167900bda9546226aa5
Reviewed-on: https://chromium-review.googlesource.com/1062773
Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Commit-Queue: Sonny Sasaka <sonnysasaka@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#559315}
Reviewed-on: https://chromium-review.googlesource.com/1077076
Cr-Commit-Position: refs/branch-heads/3396@{#713}
Cr-Branched-From: 9ef2aa869bc7bc0c089e255d698cca6e47d6b038-refs/heads/master@{#550428}

Sony mdr-xb950N1 not connecting.. current Dev channel chromebook... says unknown error.. they work great with pixel phone.. c'mon Google get this Bluetooth thing straightened out!Tried resetting each... No success!

For a few weeks now I haven't been unable to do a smart login by unlocking my pixelbook via my Pixel 2 XL.  I haven't tried any other bluetooth devices, but it's been pretty good lately.  Is anyone still having issues with this?

I'm still having this issue constantly. A reboot will re-enable Bluetooth but then once I go to standby by and resume later, Bluetooth is off and I can't turn it back on. This is frustrating because I use my Pixel to unlock the device and use a Bluetooth mouse. I'm even thinking of just giving up and returning to my Macbook as a result. I love the pen functionality, though. I have a Samsung Chromebook Plus.

I have been observing the behavior on my Pixelbook. It is intermittent. Bluetooth may work for 30 to 45 minutes before cutting out and reconnecting several times with it eventually failing completely requiring a reboot. It doesn't matter what device I have connected (I use several) the symptoms are always the same. 

This has been going on for years on multiple devices including PixelBooks. It just seems like an issue that Google is ignoring and not treating it seriously enough and fix.

This issue seems to occur with increasing frequency, thus becoming increasingly disruptive. Please address.

The frequency of this issue does seem to have increased lately. Increasing priority.

Thank you. My Bluetooth keyboard and mouse is unreliable as ever. I hope these issues are not existent in the new pixelbooks

Me personally I'm getting this less on my Pixelbook than I used to get it.

I would love a resolution to the bluetooth being disabled after the device goes to sleep and comes back on after a period of time. Bluetooth toggle isn't even in the quick settings until a reboot then things work well. Becoming increasingly annoying as, what's the point of letting the device fall asleep if you gotta restart it for it to function correctly?

This seemed to go away for a while...now it's back.

We noticed that this issue seems to become more severely than before. Our team is looking into it. Thanks!

I have been using my Pixel book for more than year now. The Bluetooth issue is the most annoying. It randomly switches off. On the quick settings panel it shows Bluetooth is ON but when you actually go to the setting it is turned off and grayed our. Every time I have to completely reboot for it to become OK. With version 70 the problem has increased and it is more frequent. I have talked to Google support innumerable number of times, they have escalated the issue and every time I get a response that the update which will be coming one week after will resolve this issue. 

Deleted: Screenshot 2018-10-06 at 7.39.39 PM.png 148 KB

	Screenshot 2018-10-06 at 7.39.39 PM.png 148 KB View Download

I finally contacted support about the bluetooth issue on the Pixelbook. They tell me it's software not hardware.  If that's the case wouldn't all Pixelbooks have this issue??  Bluetooth disconnects randomly, grays out after going to sleep etc.  It has literally been almost a year with this problem, and I know I'm not alone which makes it even more frustrating.  It makes it almost useless to use an audio bluetooth device (I have 3 different and all disconnect randomly) because you never know when it will disconnect and everyone around you is disturbed. So over this.  I to truly hope the new Slate doesn't have this issue.

Exact same issue on a brand new Pixelbook. Bluetooth just disappears. No solution found via Googling. That's why you need a headphone jack!

I'm having the same issue with my brand new pixelbook. Rediculous software bug for an overpriced piece of hardware.

Can confirm this issue. Brand new Pixelbook. Fully updated. Bug still exists. Bluetooth headphones randomly disconnect. Randomly grayed out. Need to restart to fix the issue.

Color me ignorant, but if it's software wouldn't all Pixelbooks have this issue?  Does anyone know of someone who has a Pixelbook that doesn't have this bug and bluetooth actually works?

I have a 2017 pixelbook. When using a bluetooth mouse, and I put the device to sleep, upon return, bluetooth is disabled and cannot be re-enabled without restarting.

Unacceptable.

Fix this please.

Still experiencing disappearing bluetooth on my Pixelbook with Chrome OS 70 stable. I've experienced it on all my Chromebooks for years (Pixel 2013, Pixel 2015 included), so it seems it's not Pixelbook-specific.

Bluetooth bug still persist in build from yesterday, Version 71.0.3578.49 (Official Build) beta (64-bit).

Also here Bluetooth Bug in Version 70.0.3538.76 (Official Build) (64-bit)

It's shocking that this issue hasn't been taken seriously, and can only harm Google and the OS's reputation.  The bug reports from users, especially rsigler@gmail.com, are a developer's dream, and reproducing the issue must be pretty straightforward - I've had my Pixel Book for about a week and this bug has manifested itself every day (but not each time) when the device is woken from sleep.

So frustrated by this bug and the lack of resolution!

i wonder sometimes if it's related to having work and personal accounts, and which account was active at suspend, and which used to resume.  Haven't fully explored the idea yet.

Version 70.0.3538.76 (Official Build) (64-bit) FWIW - but I see above the problem is unresolved STILL! in 71.

Also. I've tried with chrome://flags/#newblue but even switching bluetooth stacks doesn't seem to affect this bug. 

Thanks for the recent comments and feedback reports.

This Bluetooth problem is due to firmware bugs on the Intel Stone Peak 2 Bluetooth controller, which is the chip that powers Bluetooth on a variety of laptops including the Pixelbook. We are unifying several related bugs under issue 904571, which tracks progress of bugs specific to Stone Peak 2.

The Chrome OS Bluetooth team will continue meeting with Intel's engineers to work toward a solution.

Its happening for me too. same as above

Same for me, Version 71.0.3578.71. Mainly, just the setting grayed out after sleep.

Same here, woke up to this issue with the BT button greyed out.

A reboot (not sleep/wake) turned it back on.

Deleted: about_chromeos.txt 2.1 KB

about_chromeos.txt 2.1 KB View Download

Same issue for me. Brand  new pixelbook, Stable Channel, Bluetooth greys out almost every time i use the computer without fully resetting. Smart unlock only work reliably the first login after a reset as well.

Wow, this problem has existed without a fix for over a year???

I just got a new Pixelbook and used BT headphones for the first time. Then I put the computer to sleep and a couple of hours later I can't connect anything to BT because it is grayed out and I can't turn it on.

So I'm returning this thing ASAP because I use BT headphones a lot and this is a deal breaker. And it's clear that this issue is never going to be fixed.

I'm going to pretend that Google is listening and report that rebooting brought the BT back. But that is not an acceptable workaround.

I just found this article from late November 2018 stating that Google is testing a new BT stack for chromebooks. The author said it worked for him but several of the comments stated it made things worse. So I guess YMMV but here is the link with instructions if anyone wants to try it out. I just did it but too soon to tell if it fixes anything.

https://www.howtogeek.com/fyi/how-to-instantly-improve-your-chromebooks-bluetooth-performance/

I've tried both old and new bluetooth stacks.  It doesn't seem to affect this problem.  (Without a careful analysis, my impression is some things get better e.g. bluetooth audio, but other things like phone unlock seem to get worse, depending on which stack is enabled)

I have a sense (again, not carefully tested) that I don't get the disappearing bluetooth problem when the pixelbook is running on external power.  Do others also see that - is it just that the computer never really sleeps when running on external power?

Is it really impossible with the pixelbook hardware platform to do a full chip reset (or whatever) from within the OS.  Even a special chrome://reset-bluetooth-hardware page or some other interim solution would go a long way to making the situation less painful.