Still no update here. But I'm wondering from an earlier post, if they're having Bluetooth issues, maybe they pulled it till they figure it out. I'm on Fi in California.Two P7's here, one on beta, both on Fi, no updates yet.
Sent from my Pixel 7 using AC Forums mobile app
That seems very likely, but good manners and common decency would dictate that they tell us what is going on.Still no update here. But I'm wondering from an earlier post, if they're having Bluetooth issues, maybe they pulled it till they figure it out. I'm on Fi in California.
Sent from my Pixel 7 Pro using AC Forums mobile app
They can’t possibly do what you propose.Silence is golden...at least when you're an OEM and screwed something up! The last thing Google needs is more negative talk concerning their Pixel series phones. Yes they deserve the criticism but they are doing what nearly every other OEM does when they hose things up...it's called CYA! So they just stop the release, "try" to fix the issue(s), and then let it flow again. What bothers me the most is that it's clearly evident that most of these OEM's DO NOT truly test every possible aspect of the software they are releasing! Now if that sounds too difficult then I guess a multi-billion dollar company should either HIRE MORE QUALIFIED TESTERS.....or, STOP making phones!
In the case of a provider, “testing” means adding all of their bloatware to the release, if it isn’t already there in their version of the OS.Just an FYI; Android updates are released by their OEM then tested by each cell company. Example, they go from Google to Verizon or Google to TM or to At&t, etc. Then it is up to that cell company to release the update to the phones. Some are notoriously later than others.
Sent from my SM-S908U using AC Forums mobile app
My theory Verizon pass the certification didn't see a bug and TMobile during its certification seen a bug and halted it .
Definitely agree on Google or the carrier giving explanation but they just don't care unless the Media reaches out to them and they pass information to us .That makes sense. I thought I saw somewhere on Reddit, someone saying switching between 5G and other networks was crashing their phone on TMO. If that's the case, then I can understand why they halted it. Hopefully this gets sorted quickly. It would be nice if Google would be forthcoming with info, but they never are, so hopes aren't really high.
Just an FYI; Android updates are released by their OEM then tested by each cell company. Example, they go from Google to Verizon or Google to TM or to At&t, etc. Then it is up to that cell company to release the update to the phones. Some are notoriously later than others.
Sent from my SM-S908U using AC Forums mobile app
Google FI runs T-Mobile network right?Sure, but in the case of us Fi customers our "carrier" is actually Google (that's who we pay the bill to) so it's perplexing that we don't have the update unless they're waiting on T-Mobile to approve even though we don't get T-Mobile's forced apps...
Google FI runs T-Mobile network right?
Sent from my SM-F721U1 using Tapatalk
Yeah your in same boat as us T-Mobile peopleNow that Sprint is gone T-Mobile is the predominant carrier, yes. That's why I mentioned Fi waiting on T-Mobile approval in my post.
Yeah your in same boat as us T-Mobile people
Sent from my SM-F721U1 using Tapatalk
Same thing with me being on T-Mobile never missed a beatI didn't think we usually were. Usually we have the update on release day or within a week.
Wonder if Verizon pulled it or it just going get to you late after Verizon users .I have Straight Talk which is a Verizon MVNO I haven't gotten the January Security patch yet either. Unlocked Pixel 7 Pro.
Sent from my Pixel 7 Pro using Tapatalk