Bluetooth & Chrome 84
Discussion
On Chrome OS 84, or Chrome 84 on another OS?
I've been using a Microsoft Bluetooth mouse with my Pixelbook and never had any issues all through the 84 releases, and am currently on some version of an 85 release. (I switched to the beta update channel in 2018 for a specific reason at the time, and just never moved back to stable - yet).
That's not to say there haven't been issues, but I didn't/haven't encountered any.
I've been using a Microsoft Bluetooth mouse with my Pixelbook and never had any issues all through the 84 releases, and am currently on some version of an 85 release. (I switched to the beta update channel in 2018 for a specific reason at the time, and just never moved back to stable - yet).
That's not to say there haven't been issues, but I didn't/haven't encountered any.
Corso Marche said:
On Chrome OS 84, or Chrome 84 on another OS?
I've been using a Microsoft Bluetooth mouse with my Pixelbook and never had any issues all through the 84 releases, and am currently on some version of an 85 release. (I switched to the beta update channel in 2018 for a specific reason at the time, and just never moved back to stable - yet).
That's not to say there haven't been issues, but I didn't/haven't encountered any.
It's Version 84.0.4147.110 (Official Build) (64-bit) on Acer Spin Chromebooks, one of which was fine until I updated to current version. The other (new) has only ever had the latest version which won't recognised anything other than Soundsticks. I've been using a Microsoft Bluetooth mouse with my Pixelbook and never had any issues all through the 84 releases, and am currently on some version of an 85 release. (I switched to the beta update channel in 2018 for a specific reason at the time, and just never moved back to stable - yet).
That's not to say there haven't been issues, but I didn't/haven't encountered any.
Sony/Logitech and Apple devices are simply unrecognised while Soundsticks is recognised and pairs with ease. Their both behaving the same so I'm guessing it's a OS glitch.
I think I can roll back the old machine, but not sure about the new one, any ideas?
Thanks.
You could try rolling back the new machine too, there's a remote chance it was assembled with an earlier version and received the most recent update during final QA on the line before packaging. It's worth a try, but may not be possible either -- only one way to find out!
One suggestion would be to try switching the newer machine to the beta channel and see if the problem persists. (I'm on 85.0.4183.59)
If it does then hit <Alt>+<Shift>+<i> and fill in the pop-up dialog to report the bug to the developers.
I've not had any issues, but only use the mouse regularly. Out of interest today I connected one of my Bluetooth speakers and it connected instantly and stayed working without issues. No issues with the mouse either. I could connect a few more headphones and a soundbar to complete testing, but the fact I never experienced any issues and successfully had an instant connection today with a speaker it had never seen before is probably an indication I was lucky enough to not be affected by any bug. So I'm of little help to you - sorry.
One suggestion would be to try switching the newer machine to the beta channel and see if the problem persists. (I'm on 85.0.4183.59)
If it does then hit <Alt>+<Shift>+<i> and fill in the pop-up dialog to report the bug to the developers.
I've not had any issues, but only use the mouse regularly. Out of interest today I connected one of my Bluetooth speakers and it connected instantly and stayed working without issues. No issues with the mouse either. I could connect a few more headphones and a soundbar to complete testing, but the fact I never experienced any issues and successfully had an instant connection today with a speaker it had never seen before is probably an indication I was lucky enough to not be affected by any bug. So I'm of little help to you - sorry.
Corso Marche said:
You could try rolling back the new machine too, there's a remote chance it was assembled with an earlier version and received the most recent update during final QA on the line before packaging. It's worth a try, but may not be possible either -- only one way to find out!
One suggestion would be to try switching the newer machine to the beta channel and see if the problem persists. (I'm on 85.0.4183.59)
If it does then hit <Alt>+<Shift>+<i> and fill in the pop-up dialog to report the bug to the developers.
I've not had any issues, but only use the mouse regularly. Out of interest today I connected one of my Bluetooth speakers and it connected instantly and stayed working without issues. No issues with the mouse either. I could connect a few more headphones and a soundbar to complete testing, but the fact I never experienced any issues and successfully had an instant connection today with a speaker it had never seen before is probably an indication I was lucky enough to not be affected by any bug. So I'm of little help to you - sorry.
Thanks for your thoughtful response. I've swapped to beta on the new machine, nada,.One suggestion would be to try switching the newer machine to the beta channel and see if the problem persists. (I'm on 85.0.4183.59)
If it does then hit <Alt>+<Shift>+<i> and fill in the pop-up dialog to report the bug to the developers.
I've not had any issues, but only use the mouse regularly. Out of interest today I connected one of my Bluetooth speakers and it connected instantly and stayed working without issues. No issues with the mouse either. I could connect a few more headphones and a soundbar to complete testing, but the fact I never experienced any issues and successfully had an instant connection today with a speaker it had never seen before is probably an indication I was lucky enough to not be affected by any bug. So I'm of little help to you - sorry.
I'll hope over to the Acer community boards and see if anyone else has the issue.
Thanks again.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff