When Google released its February Android security build for the Google Pixel and Google Pixel XL, some owners of the said phones have started experiencing Bluetooth-related problems on their devices. Google did acknowledge the existence of the problem, saying that the company is already working on a solution to resolve it. The said fix came in a few days ago and it arrived as an automatic update. Google said that since the solution is server-side, users no longer need to download anything to get the bug-fixing update. Nevertheless, the problem about this is that the newly released update allegedly failed to resolve the entirety of the problem.

Like Us on Facebook

According to some of the most recent testimonials that Google Pixel and Google Pixel XL owners have shared on the company's forum, the Bluetooth bug still exists on their devices despite the company's new update. Nevertheless, some users have seen a change in the nature of the problem. One user shared that while his/her Pixel device no longer experiences automatic Bluetooth disabling, the user's phone disconnects from his/her smartwatch without reconnecting back. Additionally, there are also people who claim having connectivity issues when they try connecting their Pixel phones to their cars' Bluetooth. Furthermore, as of writing, the forum keeps getting more messages from Pixel owners who still face the Bluetooth problem that was allegedly caused by Googles February Android patch.

The Google Pixel and Google Pixel XL were released back in October but the Bluetooth-related problems of the devices just started getting rampant this year. Google usually addresses problems like these immediately. The company's executives have been known for being a bit generous when it comes to sharing important information to the public. In fact, Google VP of hardware Rick Osterloh has already confirmed the arrival of the Google Pixel 2 series as early as now. As for the first Pixel series however, Google has not yet issued a statement about the unresolved Bluetooth problem, Phone Arena reported. Nevertheless, the company is expected to once again address the issue in the coming days.