04-02-2025 21:33 - edited 04-02-2025 21:38
04-02-2025 21:33 - edited 04-02-2025 21:38
Been with o2 for years with the same number.
New Pixel 9 Pro that I've set up and used for a few weeks.
But when trying to connect to the 'WifiExtra' hotspots on the underground (or anywhere for that matter), it does not auto-connect.
It doesnt allow me to 'setup' as a new device via the o2 site (which I think instructions say. I remember this happening on my prior phone years ago when I first set it up).
When I do click the wif name,
it comes up with this:
Why do I need to fill this info in? How would/should I know what to put?
Now, with a bit of googling, I found I have to set the EAP to AKA, and lo-and-behold, it connected.
Am I doing this right? Missing something obvious?
on 05-02-2025 07:35
on 05-02-2025 07:35
That is down to the Pixel Phone not negotiating the connection correctly with the SSID provided by the 3rd party provider, as it should be using AKA as the authentication method with the Authentication centre.
Bear in mind EAP-AKA has been around since UMTS (3G 1st Gen).
I would report it as a bug to the Pixel Community, as o2 cant do anything about the client authentication methods it is defaulting to.
on 05-02-2025 09:25
on 05-02-2025 09:25
Thanks for the message.
Can I ask, what specifically is this 'bug'? What is it not doing exactly?
I migrated my phone data/settings from my Oneplus 6 to the Pixel 9 Pro (using that Pixel migrate feature). Maybe I should do the 'reset network settings' feature? To atleast start that fresh?
Cheers
on 05-02-2025 13:23
on 05-02-2025 13:23
If I recall its network authentication negotiation, hence I said to report it via the Pixel Community,
Try a network refresh, but it will log you out of WiFi etc
08-02-2025 14:42 - edited 08-02-2025 14:46
08-02-2025 14:42 - edited 08-02-2025 14:46
Hmm are you sure it's a Pixel issue? I've now found a number of posts (reddit, EE website) where people saying London underground hardly every (auto) connects for any providers in the last few years...?