It looks like steps to reproduce are:
1. Connect Pixelbuds to both Chromebook and phone
2. Listen to music on phone (and stop)
3. Try to move Pixelbuds to listen to music on Chromebook

Expected behavior:
Music from Chromebook are heard on Pixelbuds

Actual behavior:
Can't transfer Pixelbuds

Looking for more info from user

looks like we both edited at the same time and it removed kobbad@ - fixed

Another related bug: https://buganizer.corp.google.com/issues/69476097
Version : 10124.0.0 Eve

1.Pair and connect apolo headphones to eve
2.Change audio input to apolo headphones.
3.Open a new tab in chrome and click on "search by voice"

Expected : Audio should change to HSP mode

Observed: The apolo headphone is disconnected from the chromebook.

assigning to pbathini@ for repro following steps in comment 2.

some added context from the user who originally reported the problem: "I paired the Pixel Buds with the Pixelbook, got audio for a few seconds, then it cut out, then it came back, etc...  I'm not 100% sure whether it had switched back to being paired with the phone when it was no longer playing audio from the Pixelbook, but it did seem like it was cycling through connected/disconnected, as sometimes the Pixelbook audio would start playing from the main Pixelbook speakers."

I think at this point it's pretty unclear whether this has anything to do with the Pixel phone. It might be useful to see if we can repro it without the pixel phone as well. Thanks.

Re #6 , I tried on eve and pixel XL phone to connect the pixel buds. I was able to connect to either the chromebook or the phone at a time but not both simultaneously. If i am connected to the phone and the try to connect to chromebook , i get the connection error and vice-versa

Re #9,

A2DP profile only allow one A2DP connection at a time, unless Pixelbuds has special handling for switching connection, simultaneous does not work as expected.

mcchou@ and pbathini@ I got another pair of pixel buds. Would either of you find it useful? 

Thanks.

Hi all,

I'm going to close this bug since it seems this is intended behavior.