- Nov 9, 2017
- 406
- 0
- 0
Anyone know why the the 302 and the Pixel 2 XL won't pair via Bluetooth? I've seen folks claim on reddit that they've paired other chromebooks with Pixels, but I've also seen a number of people on Google forums complain about not being able to pair chromebooks with either of the 2017 Pixels.
I've tried a ridiculous number of times to pair them. The 302's BT address never seems to show up in the list of available devices on the 2 XL; the 2 XL always shows up in the chromebook's list. Both devices display pairing toasts and identical pairing codes each time, and the 302 even claims it's connected when it's not. But the bottom line is that they will not actually connect & stay connected.
I've updated the 302 to version 62, and I've tried switching to the Beta channel, but that was a dead end, too. I'd try the Dev channel if I knew it was a sure thing, but I don't really want to powerwash the 302 yet again for no good reason.
The 2 XL is currently running the November security update, build OPD1.170816.025, on Project Fi.
I've tried a ridiculous number of times to pair them. The 302's BT address never seems to show up in the list of available devices on the 2 XL; the 2 XL always shows up in the chromebook's list. Both devices display pairing toasts and identical pairing codes each time, and the 302 even claims it's connected when it's not. But the bottom line is that they will not actually connect & stay connected.
I've updated the 302 to version 62, and I've tried switching to the Beta channel, but that was a dead end, too. I'd try the Dev channel if I knew it was a sure thing, but I don't really want to powerwash the 302 yet again for no good reason.
The 2 XL is currently running the November security update, build OPD1.170816.025, on Project Fi.