WiFi connectivity problems since update to 20250520000

rpupkin

Sorry for double-posting (I already mentioned it in the 20250520000 OS update thread), but this is sort of urgent.

I've been experiencing severe problems with WiFi connectivity since the update to 20250520000.
My phone constantly loses WiFI internet connectivity. Out of nowhere, the WiFi logo will disappear. If I check the WiFi status on my Pixel, it will say Connected - No internet connection.

None of my other devices have any problem with my WiFi router, and nothing has changed since last week other than this OS update, so I'm fairly certain the issue lies there.

Some examples of problems I get related to this:

Normally, I use my phone as an FTP server and access it from my desktop via FileZilla, but since last week even establishing a local connection has been difficult. I get this in FileZilla: Connection attempt failed with "ECONNREFUSED - Connection refused by server". After making sure phone is connected to the WiFi router, I need disconnect and reconnect my desktop computer to it as well for it to eventually connect to my Pixel's FTP server.

Also, if I try to run a speed test on my Pixel (using WiFi only, SIM disabled), I get a socket error, whereas it runs just fine on my computer on the same WiFI network.

Signal and Telegram are barely usable when on WiFi: Telegram just says "Connecting..." and won't refresh, and any messages I try to send on Signal get stuck with a spinning wheel. Switching to SIM only fixes all those issues.

user

Maybe you could try to use per-network randomized mac option instead of per-connection.

rpupkin

user Does not seem to make a difference. Tried all the different MAC settings.

rpupkin

I may have found why. I was using a static IP address for that specific WiFi network. Setting it back to DHCP, the issues seem to have gone away. This is fine but a bit annoying for my FTP purposes, meaning that I have to double-check the server's IP in FileZilla whenever I want to access my phone's content remotely.

GrapheneOS

rpupkin Your router likely has a way to make the DHCP reservation for a device permanent. That's the correct way to do this whether or not you use DHCP on the device to obtain that IP. It's best to still use DHCP to obtain it so the IP that's reserved can be changed on the router side alone rather than needing to keep both configurations in sync.

jackFang

If you set static for one device but dhcp for others its possible there will be conflict. You probably have to create separate subnet just for your static addresses

It also depends if you do it using device or router

rpupkin

I literally only have 3 devices connected to my router. Not sure what happened but my laptop (which for years was also set to a static IP) suddenly reverted back to using DHCP, so that's probably what was causing the conflict. So I guess this has nothing to do with the update, just a timing coincidence.

GrapheneOS

rpupkin There are frequent OS updates. Any issue people experience will be shortly after an OS update.