Abstract created by Good Solutions AI
In abstract:
- Tech Advisor stories widespread Wi-Fi connectivity points affecting Google Pixel gadgets working Android 17, with telephones showing linked however dropping web entry in apps.
- The bug impacts Pixel 7 by way of Pixel 10 fashions, affecting each Google’s personal apps and third-party functions like TikTok.
- Customers might quickly resolve the problem by enabling IPv6 settings on their dwelling routers whereas Google prepares an official repair.
Android 17 has solely simply began its roll-out this week, and a few customers are already reporting points with Wi-Fi connectivity.
Google’s new cell OS is coming to to Pixel telephones around the globe, including new multi-tasking Bubbles, content material creator-friendly Display Reactions, and extra.
In fact, including a bunch of latest options and behind-the-scenes tweaks will inevitably introduce a number of gremlins, and essentially the most outstanding of these seems to have an effect on Wi-Fi connectivity.
Numerous Pixel customers have taken to Reddit to notice a wierd Android 17 bug. Whereas affected handsets initially seem like completely linked to Wi-Fi, they’re really dropping connectivity in sure apps.
Even stranger is that Google’s personal apps appear to be the first culprits right here, although third occasion apps corresponding to TikTok are additionally implicated.
Chris Martin / Foundy
Can I get your Wi-Fi?
The difficulty appears to be affecting a variety of gadgets, from the Pixel 7 proper by way of to the Google Pixel 10 collection.
There’s no apparent rationalization for this glitch at current – once more, Android 17 has solely been out for a day or two. Nevertheless, as Android Authority notes, one attainable perpetrator is the IPv6 settings.
If a consumer’s dwelling router has IPv6 assist toggled off, then fixing this Android 17 situation could possibly be a easy matter of flipping it on. It’s removed from a nailed-on repair although, seemingly.
We’ll simply have to attend for Google to talk on the matter. We all know that growth of the primary main replace, Android 17 QPR1, is effectively underway, with public betas already accessible forward of an anticipated September rollout.
Nevertheless, we’d anticipate a serious bug like this to be addressed in a smaller replace effectively earlier than then. Keep posted.