Google Pixel 8 WiFi issues?

[James_B]

We're aware of reports from Google Pixel 8 users who are having difficulties connecting their phones to the new Smart Hub 7 Plus.

When trying to connect your Pixel 8 to the hub's WiFi, you may find that it fails to connect at all, or connects very briefly before disconnecting.

We've established that this is a recent problem following the big December Pixel update - Android 16’s new updates

Our engineers have raised the issue with Google and we're hopeful the problem will be resolved in a future Android update.

In the meantime, you can work around the problem by having your Pixel 8 device use the Compatible Wi-Fi network. Steps for activating and using this feature can be found here - Set up and use Compatible WiFi | Broadband Help | EE

[Elyndys]

I've just got a Smart Hub 7 and have found this problem with my Pixel 8 Pro. I can't even try the workaround because the app is down. Absolutely unacceptable that this is still a problem 7 months later! 

[Tonksie]

Similar issue having just switched to EE broadband. My Pixel 9a connects intermittently with the router and when it does the speeds are well below that of other devices in the house. Whenever I leave the house and return my phone fails to reconnect with the WiFi. I didn't have this issue with my previous broadband provider. After 3hrs of online chat to EE I was given the compatible Wi-Fi work around which has worked. I asked what was causing the issue and was told "it can sometimes happen with busy connections..."

I've noticed that my daughters 7a, which connects fine and gets speeds of 500+Mbps, connects over 5Ghz whereas when my Pixel 9a connects (before the compatible Wi-Fi workaround) it is always 2.4Ghz. No idea if that's indicative of any issue.

7 months on from the OP and it's clearly still an issue.

[JimM11]

@Tonksie There is a few issues in general with EE and the Google pixel range just not your specific one, until EE/Google engineers bang heads together there will be no fix until that time. Turn the 5Gb/s on for the comp network, there is just no need for it NOT TO be on and give it a try.

[jak26]

It's best not to assume all these issues are Hub issues rather than some being Pixel issues or even general WiFi / range issues.

My Pixel 7 is reluctant to re-connect on return on 6GHz to a new Asus router - not showing the 6GHz SSID which then suddenly pops up as an available network after opening a WiFi analyser app for instance. No issues with other devices or on 5GHz. 

[pounzer]

I'm on a Google Pixel 9 Pro and I've got the same issue. Annoying, as we only just got the connection installed. I would appreciate a permanent fix as well.

[JimM11]

@pounzer Is it only your pixel phone to the EE Hub with the problem?

[pounzer]

As far as I've noticed (the network has only been running for 2 days), it's only the phone.

[Ozzie1989]

@James_B  can we get an official update? It's been radio silence since December.

I've contacted Google who have said they know nothing of this issue and there is no fix planned.

[bobpullen]

---

@Ozzie1989 wrote:

I've contacted Google who have said they know nothing of this issue...

---

I wouldn't be so sure of that. This isn't the only one, but see the bug report here that describes a similar (the same?) problem. Those reports are from customers of the French ISP 'Free' whose routers use WPA3-Personal-Compatibility. Probably no coincidence that the EE 7 Plus does too (which is where I think people are having problems?) 🤔

[Ozzie1989]

To clarify, they said they know nothing of the BT issue in terms of they've promised a fix to BT or similar.

I spent a month back and forth with their support team providing developer level logs and trying different settings (phone and router), full reset of the phone etc. the case got escalated to a higher level as well before it was closed, to the point they offered me a replacement device which didn't help.

I can only tell you what they told me which is they don't believe it's their issue to fix and they can successfully connect to many other implementations/combinations and their phones are compliant with the WiFi standards.

A friend who has a Samsung also has issues with the main WiFi and connects to my compatible network also, so it does point towards a potentially wider issue.

In any case, regardless of who's at fault, an update to the original alert would be welcomed, especially as it didn't really confirm a fix was being implemented.