this post was submitted on 15 Dec 2023
76 points (96.3% liked)

Android

27933 readers
215 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.

you are viewing a single comment's thread
view the rest of the comments
[–] 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.

[–] imkali@lemmy.dbzer0.com 1 points 11 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.

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

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.

[–] random65837@lemmy.world -3 points 11 months ago

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