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

Android

27905 readers
290 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:

!android@lemmy.ml


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.

all 16 comments
sorted by: hot top controversial new old
[–] breadsmasher@lemmy.world 60 points 11 months ago

“Reduce your security to fix the issue”

Wonderful.

[–] Exec@pawb.social 26 points 11 months ago (2 children)

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

[–] th3raid0r@tucson.social 13 points 11 months ago (2 children)

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.

[–] Lukario@sh.itjust.works 1 points 11 months ago (1 children)

Are they Pixels all after the 5? I've been rocking my Pixel 5 for so long and both my parents have Pixels (6 & 7) and the only one who really complains is my mom with her 6.

[–] daq@lemmy.sdf.org 1 points 11 months ago

I have pixel 7 pro. Total piece of shit. Spam blocking is nice and camera is great but everything else sucks. I'm definitely upgrading to oneplus as soon as 12 comes out now that they brought back wireless charging.

[–] imkali@lemmy.dbzer0.com 1 points 10 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.world -4 points 10 months ago

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

[–] MangoPenguin@lemmy.blahaj.zone 5 points 11 months ago

That is one hell of a bug

[–] Appoxo@lemmy.dbzer0.com 3 points 10 months ago

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

[–] FutileRecipe@lemmy.world 3 points 10 months ago

I'm on UQ1A.231205.015.2023121200 (GrapheneOS) on a Pixel 7 Pro and connected via WPA3-Personal.

[–] SpezCanLigmaBalls@lemmy.world 2 points 10 months ago

I think I'm lucky with not really running into bugs with my P8 so far

[–] algorithmae@lemmy.sdf.org 0 points 10 months ago

This is one reason why I don't update, I despise things breaking for no good reason

[–] random65837@lemmy.world -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.

[–] th3raid0r@tucson.social 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.