Obviously this is still a Pixel issue - but at least I can connect to my home Wifi again.

I previously posted saying that Wifi was broken in general, but I mistook my ongoing Xfinity outage as being unable to connect to any wifi. Thus I removed the post.

When the outage ended, I could connect to some other networks and couldn’t figure out why.

It wasn’t until after a painful factory reset process that I tried going from WPA3/WPA2 mode to just WPA2 on both of my APs and suddenly everything is able to connect again.

It seems that the recent OTA update borked WPA3-Personal in a way that doesn’t allow it to navigate the “compatibility mode” of WPA3/WPA2 either.

Edit - Looks like this might even be something Verizon specific - UQ1A-20231205.015.A1

Edit2 - Also mine is a Pixel 7 Pro - a Pixel 6 Pro user reports no such issue - YMMV.

  • Exec@pawb.social
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    1
    ·
    1 year ago

    What about Google just releasing a stable and unbroken system for once?

    • th3raid0rOPA
      link
      fedilink
      English
      arrow-up
      12
      ·
      1 year ago

      No kidding, my Pixel graveyard is too damn big… I wish other phones had nearly the AI/Assistant features that Pixels had because I definitely don’t want to switch to the Apple ecosystem and found the OnePlus experience flawed, while the Samsung experience feels bloated.

      I’d go with a Fairphone, but for some reason it’s impossible to get “officially” here in the U.S.

      • imkali@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Look around for the FP, more places sell it unofficially than you might think, and some of them have their own store warranty.

        I know here in Australia I can order it from https://www.clove.co.uk/ with relatively low markup, not sure if they sell to the US though.

    • random65837@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      4
      ·
      1 year ago

      If it was a Google issue we’d all have that problem, and clearly that’s not the case.