Forum Discussion
Pixel 7 Security Update
- Hace 2 años
pixel12a wrote:
So that only leaves something behind the scenes. Something tmo and google are hashing it out. Its got to be something that the two cant agree on. I highly suspect something feature related. I keep saying I think tmo wants something removed or blocked?
We're just going to have to wait it out. Once we do get a update. I'm pretty sure it will be a specific android build for tmo. We can pick it apart then and look for whats different.
- It’s more likely the time necessary to modify and fully test code, which is significant,
- It won’t be a specific T-Mo build for factory unlocked phones (like mine).
- It’s more likely a functional issue specific to the T-Mo network than something T-Mo wants removed or blocked.
As I said before if people believed it was T-Mobile they can take out the sim and factory reset their unlocked device. Connect to WiFi and the update should be there. If it isn't then it can't be carriers as the phone is unlocked and not associated with a carrier in anyway and is missing the carrier partition. None are willing to do it because it's easier to blame the carrier than it is to blame Google. Google has a lot of strong fanboys thinking they can do no wrong.
As I said before Google has Always staggered the release of their OTAs. The ones that are unwilling to wait they offer the OTA file for people do download and install. Doesn't matter which version they are all the same unless specified by Google before the release of the update. They are marked as such but subsequently the next version gets rolled back into one afterwards. Just side load it if you want it now. It's actually safer than doing it OTA to boot.
Contenido relacionado
- Hace 2 meses
- Hace 8 meses
- Hace 6 meses