Forum Discussion
Pixel 7 Security Update
My Pixel 7 will not receive the January 2023 security update . Tried doing it manually and no luck, have heard it's a T-Mobile issue but that's just hearsay. Heard you can just pull your sim out and put another one in and it will update haven't tried that one yet.
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.
magenta8617201 wrote:
syaoran wrote:
The updates come directly from Google. If you put another carrier SIM in your device, it will update the firmware and carrier aggregation to that carrier until you return to the T-Mobile update path, which might make a coue.of updates if the version numbers are dated the same.
Not true T-Mobile can delay the update. It's listed on the Google community. It's all over YouTube and Reddit. They have no right holding back on updates. Which Google approved and the phones used are unlock phones. Purchase from Google.
I purchased an unlocked Google Pixel 7 Pro directly from Google. I was surprised that T-Mobile could block an update, but if there is an issue, I probably don't want it.
raisinbrann wrote:
I was contacted by a T-Mobile customer support manager today regarding a complaint I had filed related to this issue.
He confirmed that T-Mobile has indeed delayed the roll-out of the January Andriod Security-Feature update due to a “bluetooth” issue.
He anticipates a fix may be available in the February Android Security-Feature Update. So there probably won't be a January Update for Pixel owners.
I suggested he post an annoucement or note on T-Mobile's website announcing the roll-out delay and reason why so Pixel customers will stop guessing and becomng upset. He agreed…. but I'm not holding my breath if we'll ever see anything posted.
Yup. I'm actually currently in the process of installing the QPR2 beta and this is why.
A tiny number of people using Android auto are having music issues so I'm months behind on the security updates that protect my banking info. Not a great priority set and I don't want T mobile controlling my updates. Half the reason to own a pixel
I love that answer because a service tech told me that T-Mobile doesn’t block any updates, another fricking lie she must be to far down the food chain to be told about the hold.
pixel12a wrote:
Both my wife and I are on the January update.after forcing it. Pixel 6a and 7. No issues with Bluetooth. Android auto is fine Ford pickup and Honda. And Anker headphones and Anker sound bar.
...
I have a feeling it has to do with visual voicemail. I had lots of issues with this. It always worked fine going all the way back to my Nexus 6. It only stopped when upgrading to the pixel 7. I had to call in many times. To get it to work they finally had to provision my account to a older plan??
...
I forced the January update to my Pixel 7 as well yesterday (see above). Experience thus far:
- No issues with Bluetooth (Volvo, Mazda, Android Auto, office access, smart watch, ear buds, etc.)
- Visual Voicemail (T-Mobile app) has stopped syncing after the update. Last sync is from Monday January 16 before I forced the update. I uninstalled the app and will try to use the Google visual voicemail service. Not that important for me (I get very few voicemails).
Bobaloo wrote:
I love that answer because a service tech told me that T-Mobile doesn’t block any updates, another fricking lie she must be to far down the food chain to be told about the hold.
Well technically they don't block it. They send a request to Google. To stop the update to phones on the network.
T-Mobile does not appear to be holding up the update. I have an unlocked Pixel 6a purchased from Google, not T-Mobile. I removed my T-Mobile SIM, restarted the phone on Wi-Fi, and it still would not update. Thus, it's more likely that Google has paused updates, probably because of issues that have arisen.
JNavas wrote:
T-Mobile does not appear to be holding up the update. I have an unlocked Pixel 6a purchased from Google, not T-Mobile. I removed my T-Mobile SIM, restarted the phone on Wi-Fi, and it still would not update. Thus, it's more likely that Google has paused updates, probably because of issues that have arisen.
Buddy everyone is able to pull the t mobile sim card and install one from another carrier (a step you seem to have skipped) and factory reset the phone (another step you seem to have skipped) and it updates lol. This also effects all phones connected to t mobile and connected networks so the fact that your phone is purchased straight from Google means nothing. They also didn't have a pause in the betas or pull the update for any other carrier worldwide, there's also nobody on other carriers who can't get the December update.
T mobile did hold it up. Why do people keep coming to defend T mobile. Google doesn't pull updates from a single carrier. If Google pulls it, it's pulled for everyone. If it's only happening on one carrier, it's the carrier.
No, without the SIM, T-Mobile is not in the update path. The connection is directly to Google over Wi-Fi and the Internet without T-Mobile. It's Google that's not providing the update. That might be due to a T-Mobile request, but it's still Google doing the updates.
JNavas wrote:
No, without the SIM, T-Mobile is not in the update path. The connection is directly to Google over Wi-Fi and the Internet without T-Mobile. It's Google that's not providing the update. That might be due to a T-Mobile request, but it's still Google doing the updates.
Your phone doesn't lose all network data the second you pull the SIM.
You can't even follow basic instructions to force the update but act like an expert in here. It's not Google LMFAO for the fiftieth time Google doesn't pull updates from one carrier.
Oh yea t mobile has also confirmed they have it held to others here in this thread
JNavas wrote:
No, without the SIM, T-Mobile is not in the update path. The connection is directly to Google over Wi-Fi and the Internet without T-Mobile. It's Google that's not providing the update. That might be due to a T-Mobile request, but it's still Google doing the updates.
"The updates might be held at t mobile request but it's title that does the updates"
So if t mobile makes Google block it, we still call it a Google issue?
Nah seriously all you guys defending this sound paid. Just making up weird reasons to take the blame off t mobile when nobody is asking for that. Nobody in this thread who's actually trying to get to a fix for their problem cares to sit here listening to randoms defend t mobile and not contribute.
So again, please, to everyone, if you are just here to try to get people not to blame t mobile for what they're doing just save it. We don't care. Nobody cares. Y'all are just disrupting this forum coming in to defend a giant corporation for no reason when nobody asked. It's weird and annoying.
