Android 17 Is Breaking 5G on Some Pixel Phones
Google's Android 17 stable rollout has officially begun, and while many Pixel owners are celebrating the arrival of new features and performance improvements, not everyone is having a smooth experience. A growing number of users are reporting that the update appears to have broken 5G connectivity entirely on their devices, leaving them stuck on slower LTE or even 4G speeds — with no obvious fix in sight.
If you've recently updated your Pixel phone to Android 17 and noticed your 5G signal has vanished, you're far from alone. Here's everything we know about the bug so far, which devices seem to be affected, and what steps you can take while waiting for an official fix from Google.
What Exactly Is Happening?
According to multiple user reports surfacing on Reddit, Google's own support forums, and various tech communities, a segment of Pixel owners are experiencing a complete loss of 5G connectivity following the Android 17 update. In most cases, the issue presents itself as the phone simply refusing to connect to a 5G network, even in areas with strong 5G coverage. Some users report seeing the 5G icon briefly before it drops back to LTE, while others say the 5G option has effectively disappeared from their network settings altogether.
The problem doesn't appear to be carrier-specific. Reports are coming in from users on multiple major carriers, which strongly suggests the root cause lies within the Android 17 software update itself rather than a network-side issue. This points toward a bug in the modem firmware, radio settings, or network stack introduced during the update process.
Which Pixel Models Are Affected?
The bug appears to be casting a fairly wide net across Google's Pixel lineup. Reports indicate that the issue is not isolated to a single device, with owners of several different Pixel generations experiencing similar connectivity problems after installing Android 17. While the full scope of affected models is still being confirmed as more users update their phones, the problem seems to impact:
- Pixel 9 series devices
- Pixel 8 and Pixel 8 Pro
- Pixel 7 and Pixel 7 Pro
- Pixel 6 series, in some reported cases
It's worth noting that not every user on these models is experiencing the issue. The bug appears to be affecting a subset of devices, which could mean it's tied to specific hardware configurations, carrier profiles, or how the update was installed. Still, the number of reports is significant enough that it's clearly a widespread problem requiring Google's attention.
Why Does This Kind of Bug Happen?
Connectivity bugs following major Android updates are not entirely unheard of. When Google ships a significant OS update, it often includes changes to modem firmware and radio access layers — the low-level software responsible for managing cellular connections. Even small unintended changes in these components can cause a device to improperly negotiate connections with 5G towers or completely fail to switch from LTE to 5G under certain conditions.
In some cases, the issue can also stem from corrupted or misconfigured carrier settings that get overwritten or reset during the update. If the update process doesn't cleanly preserve existing network configuration data, the phone may lose the correct parameters it needs to establish a 5G connection on a given carrier's network.
This is particularly frustrating because 5G connectivity is one of the primary selling points of modern Pixel hardware. Having that capability stripped away by a software update — even temporarily — is a significant quality-of-life regression for affected users.
What Can You Try in the Meantime?
While an official patch from Google is the only real solution, there are a few troubleshooting steps that some users have reported as helpful in restoring 5G functionality on a temporary basis. These are not guaranteed fixes, but they're worth attempting before waiting indefinitely for a software update.
- Toggle Airplane Mode: Switching Airplane Mode on and then off again forces your phone to re-establish its connection to the network and can sometimes restore 5G access temporarily.
- Reset Network Settings: Navigate to Settings, then System, then Reset Options, and select Reset Wi-Fi, Mobile & Bluetooth. Be aware this will also reset your saved Wi-Fi networks and Bluetooth pairings.
- Manually select network mode: Go to Settings, then Network & Internet, then SIMs, and look for Preferred Network Type. Make sure 5G is selected if it's available as an option.
- Update carrier settings: Check for any pending carrier settings updates, which can sometimes be found under Settings, then About Phone, then SIM Status.
- Restart the device: A simple restart won't always solve the problem, but it's worth trying before diving into more complex steps.
Some users have also reported that performing a factory reset resolves the issue — but this is an extreme step that should only be considered as a last resort, as it will erase all data on the device.
Has Google Responded?
As of the time of writing, Google has not issued an official public statement specifically acknowledging the Android 17 5G connectivity bug. However, given the volume of reports and the visibility of the issue across major tech platforms, it's reasonable to expect that Google's engineering team is aware of the problem and actively investigating it. Google has a track record of releasing targeted bug-fix updates relatively quickly when high-impact connectivity issues emerge — so a patch could arrive within the next few weeks.
Users are encouraged to report their issues directly through the Android Feedback tool built into their Pixel phones, as these reports help Google identify and prioritize bugs for resolution.
The Bottom Line
Android 17 brings a lot of compelling improvements to the Pixel experience, but for a notable group of users, those upgrades have come at the cost of their 5G connectivity. The bug appears to affect multiple Pixel models across various carriers, strongly suggesting it's a software-level issue introduced by the update itself. While Google has yet to officially acknowledge or address the problem, the community-driven troubleshooting steps above may offer some temporary relief. In the meantime, keep an eye out for a point update from Google — and if you haven't yet updated to Android 17 and rely heavily on 5G, it may be worth waiting a little longer before making the jump.