Pixel 8 Pro: Wi-Fi Turns Off & Won’t Scan Until Reboot (All Users)

enthusiast

hi,
I just installed GrapheneOS on my Google Pixel 8 Pro, and I’m running into a weird Wi-Fi issue that affects every user profile on the device:

– Wi-Fi will randomly turn itself off.
– When I manually re-enable Wi-Fi, it shows “No networks available” and doesn’t scan or list any SSIDs, as if all nearby APs are hidden.
– The only temporary workaround is to restart.... but the problem always comes back after a while.

and no, the problem isn't the router... since I live in a densely populated area with dozens of routers within range, so it’s virtually impossible that they all have the same issue. On stock Android, I never experienced this issue.

• What I’ve tried so far:

Switched MAC settings between “Use per-network randomized MAC” and “Use device MAC”
Toggled Airplane Mode on/off
Verified the OS is fully up to date
Tested in multiple user profile, same behavior each time

I didn't test on a physical SIM, only Wi-fi.

de0u

enthusiast How long did you have the device before putting GrapheneOS on it? If the device is newly acquired, perhaps there is a problem with the Wi-Fi hardware.

enthusiast

de0u I have pixel 8 for 2 weeks but it was used for 1 year (so it's not new). Before Graphene, I used stock OS and I never encountered this issue.

de0u

enthusiast Does this seem relevant? https://github.com/GrapheneOS/os-issue-tracker/issues/5711

enthusiast

de0u Now I switched to Beta and updated the system, I will let you know the outcome

de0u

enthusiast Now I switched to Beta and updated the system, I will let you know the outcome

To be clear, I think the "please try the beta channel" request in the issue was so that the user could get A16, which at the time was not in the stable channel. If you are already running A16 (2025063000 or newer) then it's not clear that's still relevant.

enthusiast

de0u Unfortunately, the problem still persists. It's extremely frustrating; I waited a long time to get a Pixel in order to upgrade to Graphene. I can tolerate many bugs, but this one is too severe.

enthusiast

de0u I opned an issue on github with the hope that they will fix it, if not, then sadly I have to switch to stock bloat OS.

Lagged4228

I have the same issue. It's what promoted me to try out graphene os. I started after the most recent update on stock pixel software.

It still persists on graphene.

Lagged4228

I spoke with Google support via phone who said they will talk with engineering, but that I am out of warranty. Which seems messed up since it was their software push that fucked it. It's looking like my very expansive new phone is now a mobile data only device. Insane.

enthusiast

Lagged4228 update : I reset the settings related to Wi-fi and Bluetooth and now it seems like it's working fine (no crash, at least for now).The strange part is... I already did it before publishing this issue and I got the same problem, not sure why it works.