this post was submitted on 15 Dec 2023
78 points (96.4% liked)

Android

27903 readers
349 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

[email protected]


founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -1 points 10 months ago (1 children)

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.

[–] [email protected] 1 points 10 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.