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.socialEnglish
    261·
    7 months ago

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

    • th3raid0rOPAEnglish
      12·
      7 months 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.comEnglish
        1·
        7 months 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.worldEnglish
      14·
      6 months ago

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

    • th3raid0rOPAEnglish
      3·
      7 months ago

      I’m on the Verizon variant of the software - so same version but with an .A1 tacked on.

      Edit: Oh, also, Pixel 7 Pro here.

  • Appoxo@lemmy.dbzer0.comEnglish
    3·
    7 months ago

    Mine is a Pixel7Pro from Germany with UP1A.231105.003
    My AP is from Unifi. WPA3 works without issues.

  • random65837@lemmy.worldEnglish
    22·
    6 months ago

    I’m also on a 7Pro with no issues with WPA3, when it comes to stuff like this, and you’re running a Telco/Cable provided access point, my blame would start there as those things are never the way they’re supposed to be, they run screwed with firmware that you can’t control the updates on and never know if they’re doing everything the way their supposed to or not.

    I’m sure this has been resolved, but years ago when I installed for Comast, our Arris eMTA’s were the go-to modem we’d use in both Residential and Commercial settings, but in commericial accts, the commercial billing codes would automatically disable the wireless portion of them, we were told they constantly screwed up and they were sick of dealing with the complaints as they had to deal with that when the acct was commercial vs with residential where they’d just blame the customer eq. So for commericial accts they had to use their own access points.

    • th3raid0rOPAEnglish
      1·
      6 months ago

      I’m also on a 7Pro with no issues with WPA3, when it comes to stuff like this, and you’re running a Telco/Cable provided access point, my blame would start there as those things are never the way they’re supposed to be, they run screwed with firmware that you can’t control the updates on and never know if they’re doing everything the way their supposed to or not.

      Wha? Where did I say I was using the ISP provided modem? Oh, no-no. I buy all my equipment outright and my AP is the current top-of-the-line Netgear Docis3.1 modem/router combo.

      I’ve double checked this issue as well. As soon as I enable WPA-3 my pixel just refuses to connect, but no other device in my entire home does. Pretty sure it’s the Pixel somehow.