The wait for software updates is a constant for technology enthusiasts, a moment that usually brings with it promises of greater security and new features.
However, for owners of Google Pixel smartphones, the release of the January 2026 patches is turning into a decidedly frustrating experience.
Nevertheless, Google took its time distributing this update, announcing it in the second week of the month, and the final result seems far from the required stability standards, triggering a series of malfunctions that are making life difficult for many users.
Google Pixel: Bluetooth and Wi-Fi issues with the latest update
The heart of the problem lies in a serious bug that affects the basic connectivity of the devices. Numerous reports appearing on Reddit and Google’s official support forums paint a worrying picture: the update seems to completely disable the operation of the Wi‑Fi and Bluetooth modules.
Users report software switches that refuse to activate, leaving the phones in a forced isolation state, similar to a permanent “airplane mode” that cannot be turned off.
The severity of the situation is amplified by the fact that this bug affects indiscriminately several supported models, including the recent Pixel 8 Pro, the Pixel 9 series and the very new Pixel 10 Pro and XL.
For those on a limited data plan or in areas with poor cellular coverage, the device becomes practically unusable for most daily activities, unable to rely on home network or the connection to external accessories such as headphones and smartwatches.
Has the rollout already been halted?
There is, however, one aspect that deserves particular attention and could suggest immediate awareness by Mountain View. As complaints multiply online, it is very likely that Google has already identified the critical issue and blocked the server-side distribution of the update to limit damage.
To support this claim, we share our firsthand experience: the Google Pixel 10 Pro XL provided to our editorial team, at the time of writing this article, has not yet received the notification for the January update, remaining on December 2025 security patches.
This delay, decidedly abnormal considering we are now at the end of the month, is an unequivocal signal.
If your device has not yet prompted you to install it, it is likely that Google has pulled the emergency brake to prevent further spread of the problem while its engineers work on a solution.
Beyond connectivity, an unstable system
Unfortunately, connectivity issues are only the tip of the iceberg. Those who have unfortunately installed the incriminated build report a compromised user experience on multiple fronts.
Reports mention a search function within the Settings menu that is completely unusable and options related to ‘Network & Internet‘ that do not load the correct screens.
Even more alarming are reports of abnormal standby battery drain, which drains the battery much faster than expected, and sporadic but annoying malfunctions in the camera system, with the Camera app sometimes refusing to start.
It seems the update has introduced a systemic instability that goes well beyond a simple network bug.
No easy solution on the horizon
User frustration is exacerbated by the lack of effective ‘do-it-yourself’ solutions. The classic troubleshooting steps, such as rebooting the device or booting into Safe Mode, have proven useless.
Nor does a factory reset, often considered the last resort to resolve software conflicts, seem to have any effect, forcing users to reconfigure the phone from scratch without solving the root problem.
At the moment, the only viable path seems to be technical and complex: some expert users have managed to restore proper operation by manually reinstalling the previous build using ADB commands by connecting the phone to a computer. However, this is a procedure that requires specific skills and is not advisable for the average user.
Although the official Made by Google account on X has acknowledged the existence of the problem, no precise timelines have been provided for the release of a corrective fix.
The recommendation, for now, is not to force any update and to patiently await official news.
