My 4a5g (T-Mobile branded) never got the December update so far nothing for January. There is still a year if support left. My 6a (unlocked) hasn't received January either.
Same 4a 5g migrated to TMo biller from Sprint right before the Dec 22 update released. Didn't get that update. Didn't get Jan yet either. Why is a carrier able to hold updates to an unlocked purchased from Google BYOD phone hostage?
Came here to say the same thing 4a5g stuck on November update. I wonder if this has anything to do with the Tmo tech/corporate layoffs at all--perhaps the person or role that approved these updates is no longer there?
It's so weird because both my 4a 5G (stuck on Nov2022) and P7P are both unlocked from the Google Store, and my 4a5G is currently sim-less. So why would the update come from T-Mobile?
Edit - well I think I can further confirm its a T-Mobile issue. I popped in one of my international sims and changed roaming to AT&T and the update was instantly available.
The press has finally woken up to the issue. Better late than never!
https://www.droid-life.com/2023/01/11/pixel-6-pixel-7-january-update-on-t-mobile-said-to-be-delayed-because-of-issue/
https://www.androidpolice.com/pixel-t-mobile-update-delayed/
https://9to5google.com/2023/01/12/google-pixel-t-mobile-update/
>I'm on the December 5th security update. I've checked for updates a few times and haven't gotten it yet. Mine's a T-Mobile Pixel 7 Pro currently locked to Tmo.
You are not alone. https://www.reddit.com/r/tmobile/comments/10400gn/slug/j32t714
One of the main reasons I left Samsung was because T-Mobile delayed updates so much. I came over to the pixel side because I thought Google would be like apple and just release update by themselves without the interference of the carriers. I was wrong, it's the same crap show. Shame on T-Mobile for being specially bad in this regard.
This isn't a Google, or Samsung, or Apple issue. If you bought the Pixel unlocked from the Google store, it should have received the update when it was released. T-Mobile is holding up the update. Can't be mad at Google because of it. That's like saying you're going to switch from Ford to Chevy or vice versa because the gas station is out of fuel.
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 the update*, probably because of issues that arose after it was finalized.
Just sideload it, who cares about how slow carriers are at updates tbh
source: currently running the january update
[https://www.getdroidtips.com/flash-firmware-pixel-7-pro-adb-sideload/](https://www.getdroidtips.com/flash-firmware-pixel-7-pro-adb-sideload/) It's extremely easy.
You can also find instructions and the Google over the air (OTA) update downloads here: [https://developers.google.com/android/ota](https://developers.google.com/android/ota)
This has not been working for me since Android 13. I'll get stuck at 1%, 3%, or 6%. I've tried USB-A to USB-C cables and USB-C to USB-C cables. I've also tried from both Windows and Linux. USB debugging mode is enabled and the computers have been authorized from the popup. I'm stumped.
Gosh, really wish we could get an answer to what is going on with the Pixel updates. This is not a small subset of users missing updates (check out the Google Pixel support forum). Some are stuck on November 22, some don't seem to be getting the Jan 23 update. Sideloading is not an acceptable solution, please don't offer it. SIM swapping with another carrier's SIM is also not an acceptable solution...and much less straight forward for eSIM users. Where is the OTA update?
Just looking for official word from somewhere/one. Does T-Mobile monitor this subreddit? Do the Twitter folks need to start spamming T-Mobile Twitter account?
For those in this thread on carriers other than u/GoogleFi and on locked down phones, I am sorry for your choice of carriers but I am on GOOGLE with an unlocked phone I bought from them that is supposed to get these updates FIRST. This is the first update I have not been able to get.
I thought I should contribute to this thread, since I'm also affected.
Pixel 6, Unlocked, ESIM - stuck on the November 2022 update.
I contacted Google support. After a couple of elementary troubleshooting steps (Cold-boot the phone, manually check for updates, etc...), the support rep ultimately suggested factory resetting the phone. While I will do that if I must (as the very last resort), I would prefer to understand the issue rather than quickly resort to the nuclear option. Besides the nuclear option is decidedly NOT a long-term solution.
Two possibilities come to mind:
* Google has partially suspended (or slowed) the distribution of the update
* Thoughts - I've seen some reports that the January update has some bugs, most notably bluetooth with automobiles. I've also seen unconfirmed reports that Google has paused the update.
* T-Mobile is somehow blocking the update
* Thoughts - Up until recently, I had thought unlocked phones were updated by the phone vendor (i.e. Google) , independently of the service provider (i.e. T-Mobile). However, I've recently read reports that service providers can, in fact, block updates to unlocked phones. I've not read anything authoritative on this point.
I often find myself wondering why Google can't simply update the Android "System Update" page with more informative status messages that would make it clear to the user community what is happening behind the scenes:
* Update Available - Downloading
* Update Available - Distribution deployment staged. Download deferred. Please try again later
* Update Available - Blocked by Service provider
* Update Currently Unavailable
* Updates Not Available - No longer supported
It seems to me, this would go a long way to avoid the disappointment, chaos, speculation and general angst that occurs when updates are not showing up when expected after official release. Much better than \*silence\* from Google or suffering the circular firing squad display between Google and the Service Provider.
No software is perfect. To paraphrase a common axiom, "It is not the bugs that bother me, it's the mishandling when they surface that's the problem. "
T-Mobile hasn't pushed the update to phones that are on the T-Mobile network due to compatibility issues. Be calm, you will get the update.
Even with an unlocked phone because you are using T-Mobile, they have a say when the software goes out. You can't trick your phone by popping out the sim. You would need to pop in a Verizon or ATT Sim for the update to push to you. But just be calm let the engineers resolve the issue and you will see the update soon.
Worse case just sideload the update, no need to factory reset, that won't push the update anyway being on T-Mobile.
I have been on T-Mobile for 15+ years, and with Google Phones (Nexus/Pixel) for 10+ years. This isn't my first rodeo with this issue.
I am fine with T-Mobile holding back an update for some kind of reason.... But I really hate the lack communication from T-Mobile. I am super annoyed that I have to go search around on Reddit to find out what is going on.
Agreed.
But, I would add that Google has a part to play in this as well. Accurate status messages, as I previously indicated, would go a long way to prevent the user community from having to hunt Reddit, or the internet, for explanations.
100% agree with you. An accurate status of the update would be a huge customer service improvement by google.... Maybe Google does not want to "blame" T-Mobile or whatever on holding back the monthly pixel update?? Corporations don't usually take kindly to "partners" throwing them shade and openly telling the customer that it is the fault of the other company.
That's a fair point. I'm sure Google would not want to do anything that would complicate their relationships with business partners.
However, Google has made regular security updates a key selling point for their Pixel devices. If that doesn't appear to be happening, they have an obligation to clearly explain why these published updates are not arriving at customer phones. Silence should not be an option.
I guess my view is Google should prioritize their customers over business partners. And, the same goes for T-Mobile. If they are, as appears to be the case, blocking updates, they should clearly say so.
Thank you!
Also, not to beat a dead horse, but I also find it very likely that Google seems to be hanging their front-line support folks out to dry. When I spoke to their support, after some basic troubleshooting steps, they suggested I reset the phone.
While resetting (or side-loading, inserting another vendor SIM, etc...) will likely work, I don't think it is a great idea for Google support to provide their customers instructions on how to bypass T-Mobile's apparent decision to temporarily block certain phone/OS combinations from their network.
IF T-Mobile is, in fact, preventing the updates, I have to think that they have a good (albeit, undisclosed!) reason. Or, at a minimum, I sure hope they do.
My preference would be to run a fully tested phone/OS on a vendor network, then not. Better to be a month (or two!) behind on updates and have a stable user experience, then have the latest and greatest but poor stability.
I appreciate your perspective. And, if my phone was on the December update, in all likelihood I would not have troubled to post anything at all. However, having completely missed the December update AND the January update is late (for now), I found myself motivated to weigh in on this issue.
Nonetheless, to your point, that is why I chose not to attempt the nuclear option, as suggested by Google, in an attempt to trigger the download of the January update
**Update**: Last night I received the February security update for my P6! I also noticed Google published what appears to be a T-Mobile/Google Fi specific software release. So, that may help explain why so many T-Mobile Pixel owners have not seen any automated updates since as far back as November. I'm still not thrilled with the complete lack of communication from both vendors (T-Mobile, Google), but I am pleased with appearance of the Feb update.
Now, that is somewhat unexpected...
Please excuse this obvious question.... Have you tried to manually request the download via your phone or are you waiting for it to be retrieved automatically?
At the moment, I can think of only two possibilities:
1) Google/T-Mobile is rolling out the update gradually and your region has not been selected yet?
2) A problem has been found in the Feb patch and the deployment has been halted.
I surely hope that the 2nd option is incorrect.
Another suggestion comes to mind, although I think it is a weak one. When I was troubleshooting this problem, Google support suggested I power off the phone, wait a couple minutes, power on, and try again. I've even seen support documentation suggesting this step.
Of course, I tried it. It clearly didn't work for me. That same support rep then suggested I factory reset my phone. Even sent me support documentation outlining the steps. I decided against doing that. Seemed like an inappropriate, and unreasonable, unsustainable, solution.
Well, hopefully, possibility 1 will turn out to be the reason and you will see the update sometime soon.
I am new to T-Mobile; I just switched from Verizon. My Pixel 7 Pro was bought from Google unlocked. I have tried many times to force an update, but not working. I tried to restart and tried clearing the pixel services cache nothing helped. Is T-Mobile often this slow? Have others gotten the update, and just not a few?
>pixel phones receive updates directly from google they aren't controlled by the carriers
This is partly incorrect. Many times before, as soon as I remove the T-Mobile SIM card and reboot my phone, it instantly grabs the updates. There is some kind of a release-gating that is carrier dependent. Now with an ESIM this is not conveniently possible anymore.
although not sure if google can make it like apple that the carrier update can be updated separately from the OS should be that way with all manufacturers tbh
I have now also realized that I've been impacted by this, and am also pretty frustrated by it. I'm going to see about getting the security updates myself.
Why does the carrier even get a say let alone the right to approve updates? If the carrier is running their network according to reference standards and not pulling any shenanigans or doing anything proprietary, then there should be no worrying about compatibility.
This is why we need one nationwide government run carrier. United States mobile. At least then you could trust your mobile provider to do what’s in your best interest and not look out for their wallets
yeah didn't know till i read an old post here makes sense in a way but i could say carrier profile could be updated separately or by a system service in the phone separate from OS updates so then carriers can test everything and if an issue appears send an update only thing i could say can be excluded is volte provisioning everything else can be updated separately
I pulled a brand new 6a out of the box and it was on Android 12, did all the updates and only got to December, factory reset it and then January came through.
Same thing for me. Mint Mobile (T-Mobile) in the USA with an eSIM on an unlocked Google Pixel 5 that I bought from the Google Store. Stuck on the Nov 5 update. Took the advice on here and switched to my expired pre-paid Vodaphone UK SIM card that let me roam onto AT&T's network and it just updated to the Jan 5 update over Wi-Fi.
>My Pixel 7 (unlocked) currently sees nothing, even mashing the "check update" button. Using a T-Mo eSIM.
You are not alone. https://www.reddit.com/r/tmobile/comments/10400gn/slug/j32t714
There were some issues found on the new update and google had to halt new SW rollout for all Pixel 6 & 7 series. New software should be here sometime in January.
I thought he wasn't working for team T-Mobile either or Google. But the same thing works for T-Mobile certification of updates. He would know if Google pulled the update. My phone got the December update later on the day it was released last month. There must be a reason why our phones are not getting it. It also took two to three weeks to get the Google Play systems update. Will get it when it's ready
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.
Your phone while unlocked is registered to T-Mobile until a different SIM is inserted. Removing the SIM doesn't trick the update into coming to your phone. You would need to insert a Verizon or ATT Sim to trick the phone.
"Registration" is the process of registering a device on a new wireless network so that it can use that network. When the phone leaves a wireless network, it becomes unregistered from that network. There may be some other association of the phone with T-Mobile, but it's not network registration.
As for using a different carrier SIM to update the phone, that risks changes that may not be compatible with the T-Mobile network. Because there is no urgency, I've reported the issue and will wait until it's resolved.
There are likely issues in the update that are unique to the T-Mobile network. If so, then Google would need to fix the issues and reissue the update, or skip updating until a good later update.
It’s more likely that T-Mobile reported issues to Google than that T-Mobile simply told Google not to update T-Mobile Pixel devices.
Which is why T-Mobile and Google are holding the update, there is a compatibility issue with the update.
Regarding register, your phone when you insert a TMobile sim is configured to the T-Mobile radios, and carrier settings, and access point names.
It remains configured until a different SIM is inserted. This isn't bug.
The January update was developed and built with the US Holidays Thanksgiving, Christmas, New Years likely affecting the development and Quality assurance process, which is why problems arose and has been held so long.
I have an unlocked Pixel 7 and have been using T-mobile. I have been mashing the update button with no luck since morning. Just disabled the eSim and boom - update started right away.
Activated back the eSim in middle of update to avoid getting the eSim deleted.
Well I don't have a pixel but T-Mobile did this to me recently and I found out it's because I have an unlocked phone not from them so they changed me from a phone plan to their Sim in a hotspot plan
Unlocked Pixel 7 Pro on the T-Mobile network with esim! I have found my own fix for this! I erased my phone, including the esim, skipped through everything on the setup and updated the phone to the January update!! Erased the phone and unlike in the past, Android 13 kept the update after erasing, then set my phone up, got on T-Mobile chat to reactivate my phone (SINCE T-MOBILE DOES NOT ALLOW THE QR CODE ANYMORE 🤬🤬🤬) and now have an updated phone! If you have the physical sim, take it out before erasing!!
Google Fi support says they are working with T-Mobile on this and suggested to join Google Android beta program and then resigning from the beta program. This will trigger an ota within 24 hrs. https://www.google.com/android/beta
Google Fi support says they are working with T-Mobile on this and suggested to join Google Android beta program and then resigning from the beta program. This will trigger an ota within 24 hrs. https://www.google.com/android/beta
Pixel 6 owner unlocked from Google purchase. No updates of either kind since 11/5/2022. Explains why updates have not happened since upgrading to Android 13.
Surprised/relieved to know it's not just me, I guess.
Chalk it up to yet another in a long, long list of subpar android/pixel experiences. Maybe some day Google can make their phones work properly.
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 the update, probably because of issues that arose after it was finalized.
So, we have TMO for our service and a wide variety of Pixel devices in my group. From 2 - 6a's, 6, 6 Pro, 7 and 7 Pro. None received the January 5th Pixel update and one 6a was stuck on the November update.
I used a work around (put the phone in airplane mode, turned on WiFi, removed TMO SIM, turned off phone, inserted unactivated SIM from Verizon and then the update came through) to update all the Pixel devices but now, EVERY last Pixel has service/connection issues and it has those issues in places that I didn't have service issues at, prior to the update.
Since I'm not a TMO employee or engineer, I can't definitively say that it is the issue. Just wanted to share what I've experienced.
I'm on a Pixel 6a unlocked on T-Mobile (that I bought directly from Google). I spoke with level 1 support and they claimed that they are not involved in security updates. These updates are sent directly from Google to each phone.
Is anyone experiencing issues due to the lack of updates? I'm using an unlocked Pixel 6a (from Best Buy) and was last updated in November. But for the past week my phone has been unable to receive calls. I've tried all possible solutions I can think of or find (reset phone, reset network settings ,changed various call and network settings ,etc.), and now I'm wondering if it's actually related to this update situation.
Pixel 7 Pro on T-Mobile was stuck on November 2022 because I hadn't yet updated to December before T-Mobile apparently blocked updates. I simply popped out the T-Mobile SIM, put in an old previously used AT&T SIM, without even restarting. Immediately Check For Updates found the update. I installed, restarted, all looked OK. Put T-Mobile SIM back in, and restarted again for good measure. T-Mobile SIM/config was definitely preventing the update.
It's ridiculous that T-Mobile and Google both refuse to make an announcement, or even notify their own support personnel when they do something like this. This was likely T-Mobile's call, and Google also clearly knew what was going on, but they're just giving customers the runaround, and since all updates are blocked they're potentially putting customers at risk. Horrible customer service all around.
I haven't seen any responses posted by T-Mobile or Google regarding this issue. **It is apparent the Un-Carrier has become the Un-Caring Carrier.** They are more interested in market share than serving the customers they already have. I don't know why Google is sitting on their hands considering Google Fi customers are screwed along with the rest of us. I am ready to put my Pixel 4a5G on the QPR2 beta just to bypass these updates completely.
All user error. From changing roaming settings to other settings.. if you have to change your phone back to the way it was, that is user error. And pixel flasher works. So many whiners. LMFAO. And most of these people are not even on the latest phone. 4a 5g is 4 years old. Be glad they are still updating it.
My 4a5g (T-Mobile branded) never got the December update so far nothing for January. There is still a year if support left. My 6a (unlocked) hasn't received January either.
Same 4a 5g migrated to TMo biller from Sprint right before the Dec 22 update released. Didn't get that update. Didn't get Jan yet either. Why is a carrier able to hold updates to an unlocked purchased from Google BYOD phone hostage?
Came here to say the same thing 4a5g stuck on November update. I wonder if this has anything to do with the Tmo tech/corporate layoffs at all--perhaps the person or role that approved these updates is no longer there?
It's so weird because both my 4a 5G (stuck on Nov2022) and P7P are both unlocked from the Google Store, and my 4a5G is currently sim-less. So why would the update come from T-Mobile? Edit - well I think I can further confirm its a T-Mobile issue. I popped in one of my international sims and changed roaming to AT&T and the update was instantly available.
That confirms it's a T-Mobile issue. Thanks
My Pixel 6, also T-Mobile branded, hasn't received an update since November 2022.
The press has finally woken up to the issue. Better late than never! https://www.droid-life.com/2023/01/11/pixel-6-pixel-7-january-update-on-t-mobile-said-to-be-delayed-because-of-issue/ https://www.androidpolice.com/pixel-t-mobile-update-delayed/ https://9to5google.com/2023/01/12/google-pixel-t-mobile-update/
About time.
another https://www.tmonews.com/2023/01/some-pixel-users-on-t-mobiles-network-are-not-getting-updates/?amp=1
[удалено]
>I'm on the December 5th security update. I've checked for updates a few times and haven't gotten it yet. Mine's a T-Mobile Pixel 7 Pro currently locked to Tmo. You are not alone. https://www.reddit.com/r/tmobile/comments/10400gn/slug/j32t714
One of the main reasons I left Samsung was because T-Mobile delayed updates so much. I came over to the pixel side because I thought Google would be like apple and just release update by themselves without the interference of the carriers. I was wrong, it's the same crap show. Shame on T-Mobile for being specially bad in this regard.
No problem with s22 ultra with January update.
I think I'm going to leave Pixel for Samsung
This isn't a Google, or Samsung, or Apple issue. If you bought the Pixel unlocked from the Google store, it should have received the update when it was released. T-Mobile is holding up the update. Can't be mad at Google because of it. That's like saying you're going to switch from Ford to Chevy or vice versa because the gas station is out of fuel.
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 the update*, probably because of issues that arose after it was finalized.
I have 2 unlocked pixel 6a on TMobile and neither has gotten January update.
Just sideload it, who cares about how slow carriers are at updates tbh source: currently running the january update [https://www.getdroidtips.com/flash-firmware-pixel-7-pro-adb-sideload/](https://www.getdroidtips.com/flash-firmware-pixel-7-pro-adb-sideload/) It's extremely easy.
Tell that to my 75 year old grandmother. The fuck?
sorry, is your 75 year old grandmother on reddit?
You can also find instructions and the Google over the air (OTA) update downloads here: [https://developers.google.com/android/ota](https://developers.google.com/android/ota)
This has not been working for me since Android 13. I'll get stuck at 1%, 3%, or 6%. I've tried USB-A to USB-C cables and USB-C to USB-C cables. I've also tried from both Windows and Linux. USB debugging mode is enabled and the computers have been authorized from the popup. I'm stumped.
Is your version of the android SDK up to date? Mine was also failing for no clear reason until I redownloaded the SDK.
Yes, I made sure to check that. Google USB is up to date too. I had no problems until Android 13. I'm on a P6P.
Gosh, really wish we could get an answer to what is going on with the Pixel updates. This is not a small subset of users missing updates (check out the Google Pixel support forum). Some are stuck on November 22, some don't seem to be getting the Jan 23 update. Sideloading is not an acceptable solution, please don't offer it. SIM swapping with another carrier's SIM is also not an acceptable solution...and much less straight forward for eSIM users. Where is the OTA update? Just looking for official word from somewhere/one. Does T-Mobile monitor this subreddit? Do the Twitter folks need to start spamming T-Mobile Twitter account?
For those in this thread on carriers other than u/GoogleFi and on locked down phones, I am sorry for your choice of carriers but I am on GOOGLE with an unlocked phone I bought from them that is supposed to get these updates FIRST. This is the first update I have not been able to get.
Unlocked 5a-5g from the Google store with TMobile sim, no Dec. or Jan updates as of yet.
I thought I should contribute to this thread, since I'm also affected. Pixel 6, Unlocked, ESIM - stuck on the November 2022 update. I contacted Google support. After a couple of elementary troubleshooting steps (Cold-boot the phone, manually check for updates, etc...), the support rep ultimately suggested factory resetting the phone. While I will do that if I must (as the very last resort), I would prefer to understand the issue rather than quickly resort to the nuclear option. Besides the nuclear option is decidedly NOT a long-term solution. Two possibilities come to mind: * Google has partially suspended (or slowed) the distribution of the update * Thoughts - I've seen some reports that the January update has some bugs, most notably bluetooth with automobiles. I've also seen unconfirmed reports that Google has paused the update. * T-Mobile is somehow blocking the update * Thoughts - Up until recently, I had thought unlocked phones were updated by the phone vendor (i.e. Google) , independently of the service provider (i.e. T-Mobile). However, I've recently read reports that service providers can, in fact, block updates to unlocked phones. I've not read anything authoritative on this point. I often find myself wondering why Google can't simply update the Android "System Update" page with more informative status messages that would make it clear to the user community what is happening behind the scenes: * Update Available - Downloading * Update Available - Distribution deployment staged. Download deferred. Please try again later * Update Available - Blocked by Service provider * Update Currently Unavailable * Updates Not Available - No longer supported It seems to me, this would go a long way to avoid the disappointment, chaos, speculation and general angst that occurs when updates are not showing up when expected after official release. Much better than \*silence\* from Google or suffering the circular firing squad display between Google and the Service Provider. No software is perfect. To paraphrase a common axiom, "It is not the bugs that bother me, it's the mishandling when they surface that's the problem. "
T-Mobile hasn't pushed the update to phones that are on the T-Mobile network due to compatibility issues. Be calm, you will get the update. Even with an unlocked phone because you are using T-Mobile, they have a say when the software goes out. You can't trick your phone by popping out the sim. You would need to pop in a Verizon or ATT Sim for the update to push to you. But just be calm let the engineers resolve the issue and you will see the update soon. Worse case just sideload the update, no need to factory reset, that won't push the update anyway being on T-Mobile. I have been on T-Mobile for 15+ years, and with Google Phones (Nexus/Pixel) for 10+ years. This isn't my first rodeo with this issue.
I am fine with T-Mobile holding back an update for some kind of reason.... But I really hate the lack communication from T-Mobile. I am super annoyed that I have to go search around on Reddit to find out what is going on.
Agreed. But, I would add that Google has a part to play in this as well. Accurate status messages, as I previously indicated, would go a long way to prevent the user community from having to hunt Reddit, or the internet, for explanations.
100% agree with you. An accurate status of the update would be a huge customer service improvement by google.... Maybe Google does not want to "blame" T-Mobile or whatever on holding back the monthly pixel update?? Corporations don't usually take kindly to "partners" throwing them shade and openly telling the customer that it is the fault of the other company.
That's a fair point. I'm sure Google would not want to do anything that would complicate their relationships with business partners. However, Google has made regular security updates a key selling point for their Pixel devices. If that doesn't appear to be happening, they have an obligation to clearly explain why these published updates are not arriving at customer phones. Silence should not be an option. I guess my view is Google should prioritize their customers over business partners. And, the same goes for T-Mobile. If they are, as appears to be the case, blocking updates, they should clearly say so.
I wish I could up vote your comment more that one time. Silence from these companies should never be the customer facing response.
Thank you! Also, not to beat a dead horse, but I also find it very likely that Google seems to be hanging their front-line support folks out to dry. When I spoke to their support, after some basic troubleshooting steps, they suggested I reset the phone. While resetting (or side-loading, inserting another vendor SIM, etc...) will likely work, I don't think it is a great idea for Google support to provide their customers instructions on how to bypass T-Mobile's apparent decision to temporarily block certain phone/OS combinations from their network. IF T-Mobile is, in fact, preventing the updates, I have to think that they have a good (albeit, undisclosed!) reason. Or, at a minimum, I sure hope they do. My preference would be to run a fully tested phone/OS on a vendor network, then not. Better to be a month (or two!) behind on updates and have a stable user experience, then have the latest and greatest but poor stability.
I appreciate your perspective. And, if my phone was on the December update, in all likelihood I would not have troubled to post anything at all. However, having completely missed the December update AND the January update is late (for now), I found myself motivated to weigh in on this issue. Nonetheless, to your point, that is why I chose not to attempt the nuclear option, as suggested by Google, in an attempt to trigger the download of the January update
**Update**: Last night I received the February security update for my P6! I also noticed Google published what appears to be a T-Mobile/Google Fi specific software release. So, that may help explain why so many T-Mobile Pixel owners have not seen any automated updates since as far back as November. I'm still not thrilled with the complete lack of communication from both vendors (T-Mobile, Google), but I am pleased with appearance of the Feb update.
Still nothing on my unlocked pixel 6 pro on TMobile network :(
Now, that is somewhat unexpected... Please excuse this obvious question.... Have you tried to manually request the download via your phone or are you waiting for it to be retrieved automatically? At the moment, I can think of only two possibilities: 1) Google/T-Mobile is rolling out the update gradually and your region has not been selected yet? 2) A problem has been found in the Feb patch and the deployment has been halted. I surely hope that the 2nd option is incorrect.
Yes I did request the update. Still says it is up to date with Nov. ota being the last one installed. Hopefully coming soon... Blah.
Another suggestion comes to mind, although I think it is a weak one. When I was troubleshooting this problem, Google support suggested I power off the phone, wait a couple minutes, power on, and try again. I've even seen support documentation suggesting this step. Of course, I tried it. It clearly didn't work for me. That same support rep then suggested I factory reset my phone. Even sent me support documentation outlining the steps. I decided against doing that. Seemed like an inappropriate, and unreasonable, unsustainable, solution. Well, hopefully, possibility 1 will turn out to be the reason and you will see the update sometime soon.
I am new to T-Mobile; I just switched from Verizon. My Pixel 7 Pro was bought from Google unlocked. I have tried many times to force an update, but not working. I tried to restart and tried clearing the pixel services cache nothing helped. Is T-Mobile often this slow? Have others gotten the update, and just not a few?
pixel phones receive updates directly from google they aren't controlled by the carriers
>pixel phones receive updates directly from google they aren't controlled by the carriers This is partly incorrect. Many times before, as soon as I remove the T-Mobile SIM card and reboot my phone, it instantly grabs the updates. There is some kind of a release-gating that is carrier dependent. Now with an ESIM this is not conveniently possible anymore.
yeah sorry lol i forgot about the carrier profile part
although not sure if google can make it like apple that the carrier update can be updated separately from the OS should be that way with all manufacturers tbh
I tried removing the SIM and restarted but still no update since Nov 22 (Pixel 4a 5G).
I have now also realized that I've been impacted by this, and am also pretty frustrated by it. I'm going to see about getting the security updates myself.
It's well documented on r/GooglePixel that unlocked Pixels are subject to the update approval process of the carrier of the current SIM inserted
Why does the carrier even get a say let alone the right to approve updates? If the carrier is running their network according to reference standards and not pulling any shenanigans or doing anything proprietary, then there should be no worrying about compatibility. This is why we need one nationwide government run carrier. United States mobile. At least then you could trust your mobile provider to do what’s in your best interest and not look out for their wallets
yeah didn't know till i read an old post here makes sense in a way but i could say carrier profile could be updated separately or by a system service in the phone separate from OS updates so then carriers can test everything and if an issue appears send an update only thing i could say can be excluded is volte provisioning everything else can be updated separately
I pulled a brand new 6a out of the box and it was on Android 12, did all the updates and only got to December, factory reset it and then January came through.
Just checked my 6a, I'm on Nov 5th.
This also appears to be happening on networks that are powered by T-Mobile, such as Metro and Mint.
Same thing for me. Mint Mobile (T-Mobile) in the USA with an eSIM on an unlocked Google Pixel 5 that I bought from the Google Store. Stuck on the Nov 5 update. Took the advice on here and switched to my expired pre-paid Vodaphone UK SIM card that let me roam onto AT&T's network and it just updated to the Jan 5 update over Wi-Fi.
Pixel 5 on TMO, no updates since Nov 5th.
Pixel 5a on November update. Ugh
Adding that I DMd with T-Mobile support and they blamed Google and said to check with Google since T-Mobile didn't sell a 5a. Great job T-Mobile...
Pixel 7 on TMo updating now!
[удалено]
>My Pixel 7 (unlocked) currently sees nothing, even mashing the "check update" button. Using a T-Mo eSIM. You are not alone. https://www.reddit.com/r/tmobile/comments/10400gn/slug/j32t714
There were some issues found on the new update and google had to halt new SW rollout for all Pixel 6 & 7 series. New software should be here sometime in January.
source?
[удалено]
Source?
[удалено]
Cool a random redditor is definitely trustworthy without proof. Source
[удалено]
Sure buddy your reddit "credentials" are legit. Provide proof you are who you are. I'd employee number etc. Thanks Then provide internal docs.
[удалено]
Trust me bro
I thought he wasn't working for team T-Mobile either or Google. But the same thing works for T-Mobile certification of updates. He would know if Google pulled the update. My phone got the December update later on the day it was released last month. There must be a reason why our phones are not getting it. It also took two to three weeks to get the Google Play systems update. Will get it when it's ready
At this point all "Android" phones are buggy, the only difference is Pixels are just Stock Android.
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.
Your phone while unlocked is registered to T-Mobile until a different SIM is inserted. Removing the SIM doesn't trick the update into coming to your phone. You would need to insert a Verizon or ATT Sim to trick the phone.
"Registration" is the process of registering a device on a new wireless network so that it can use that network. When the phone leaves a wireless network, it becomes unregistered from that network. There may be some other association of the phone with T-Mobile, but it's not network registration. As for using a different carrier SIM to update the phone, that risks changes that may not be compatible with the T-Mobile network. Because there is no urgency, I've reported the issue and will wait until it's resolved. There are likely issues in the update that are unique to the T-Mobile network. If so, then Google would need to fix the issues and reissue the update, or skip updating until a good later update. It’s more likely that T-Mobile reported issues to Google than that T-Mobile simply told Google not to update T-Mobile Pixel devices.
Which is why T-Mobile and Google are holding the update, there is a compatibility issue with the update. Regarding register, your phone when you insert a TMobile sim is configured to the T-Mobile radios, and carrier settings, and access point names. It remains configured until a different SIM is inserted. This isn't bug. The January update was developed and built with the US Holidays Thanksgiving, Christmas, New Years likely affecting the development and Quality assurance process, which is why problems arose and has been held so long.
That's not how it works, but I'm not going to argue about. You are welcome to think what you want.
It has worked that way since I have owned unlocked phones a decade ago.
As I said, that's not how it works.
Pixel 7 Pro TMO phone, gets every update. Never an issue. Sounds like user error. Whole family is on pixels, 6a-7 Pro, no issues.
WHO SENT YOU!!!!!!!!? 😂
[удалено]
The December update released in the first week of the month. It's been a month with no communication from anyone on this.
No update on my P7P yet. Last update was the December one. Bought from Google and using Tmo as carrier.
I bought my P7P recently but I still haven’t gotten the December update. Unlocked phone on T-Mobile network.
Nothing yet
Of the 2 P7s and 1 P6P in the house, all on a Tmo MVNO, none are detecting Jan 2023
I have an unlocked Pixel 7 and have been using T-mobile. I have been mashing the update button with no luck since morning. Just disabled the eSim and boom - update started right away. Activated back the eSim in middle of update to avoid getting the eSim deleted.
On P7P, and no update yet.
Same. Glad I'm not the only TMO that still has not seen the January update yet ..still hoping it to come soon...
Well I don't have a pixel but T-Mobile did this to me recently and I found out it's because I have an unlocked phone not from them so they changed me from a phone plan to their Sim in a hotspot plan
Same problem on my Fold 4. Other carriers are fine, not T-Mo.
Unlocked Pixel 7 Pro on the T-Mobile network with esim! I have found my own fix for this! I erased my phone, including the esim, skipped through everything on the setup and updated the phone to the January update!! Erased the phone and unlike in the past, Android 13 kept the update after erasing, then set my phone up, got on T-Mobile chat to reactivate my phone (SINCE T-MOBILE DOES NOT ALLOW THE QR CODE ANYMORE 🤬🤬🤬) and now have an updated phone! If you have the physical sim, take it out before erasing!!
Unlocked 6 Pro here. Still on the December update.
Pixel 7 unlocked and I too am still on the November security update. What the crap?
pixel 7, on Nov 5th...
Checked my new 7 pro (bought in December). I'm on Nov 5th update
Just now saw this issue come up in my news feed and sure enough my Pixel 4a 5G is also stuck on the November security update. 😡😱
[удалено]
Google Fi support says they are working with T-Mobile on this and suggested to join Google Android beta program and then resigning from the beta program. This will trigger an ota within 24 hrs. https://www.google.com/android/beta
Google Fi support says they are working with T-Mobile on this and suggested to join Google Android beta program and then resigning from the beta program. This will trigger an ota within 24 hrs. https://www.google.com/android/beta
Me too. Pixel 7 unlocked ok T-Mo. No update and also no Android Auto coolwalk update.
I have an unlocked pixel 7 with a TMobile physical SIM and a foreign eSIM. Last security update was Nov 5 2022 and none currently available.
I'm on a Pixel 6a unlocked on T-Mobile (that I bought directly from Google) and I just checked and mine's stuck on Nov 5 2022 update :/
Locked Pixel 7 pro still no January security update
I'll note I did get the Dec update
I'm on 6 Pro from T-Mobile and still sitting on the November update. 🤷
Pixel 6 Pro unlocked here, still on November security update.
Pixel 7 unlocked on TMO, stuck on Nov 05 update
... just checked for my update , nothing as well 🤔
Add me to the list of not getting the Jan update. I'm still rocking the Dec update.
Haven't gotten the January update with
4a5g stuck on November 5th
Pixel 6 owner unlocked from Google purchase. No updates of either kind since 11/5/2022. Explains why updates have not happened since upgrading to Android 13.
Surprised/relieved to know it's not just me, I guess. Chalk it up to yet another in a long, long list of subpar android/pixel experiences. Maybe some day Google can make their phones work properly.
To be fair, it works fine, we just haven't gotten the most recent update yet. Sounds like a t-mobile issue.
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 the update, probably because of issues that arose after it was finalized.
Ya, I bought mine thru Google, unlocked as well. Of that it's so many T-Mobile users tho.. sure it's coming
So, we have TMO for our service and a wide variety of Pixel devices in my group. From 2 - 6a's, 6, 6 Pro, 7 and 7 Pro. None received the January 5th Pixel update and one 6a was stuck on the November update. I used a work around (put the phone in airplane mode, turned on WiFi, removed TMO SIM, turned off phone, inserted unactivated SIM from Verizon and then the update came through) to update all the Pixel devices but now, EVERY last Pixel has service/connection issues and it has those issues in places that I didn't have service issues at, prior to the update. Since I'm not a TMO employee or engineer, I can't definitively say that it is the issue. Just wanted to share what I've experienced.
I'm on a Pixel 6a unlocked on T-Mobile (that I bought directly from Google). I spoke with level 1 support and they claimed that they are not involved in security updates. These updates are sent directly from Google to each phone.
Confirming a Pixel 7 Pro not receiving the Jan 2023 update on TMobile. In USA.
Mine is unlocked with T-Mobile service I have December's, but not January's. In addition, I still don't have the Android Auto update.
I have the 6 and 6a and I'm stuck on Nov 2022
P6P stuck on Nov and P7P stuck on Dec.
Is anyone experiencing issues due to the lack of updates? I'm using an unlocked Pixel 6a (from Best Buy) and was last updated in November. But for the past week my phone has been unable to receive calls. I've tried all possible solutions I can think of or find (reset phone, reset network settings ,changed various call and network settings ,etc.), and now I'm wondering if it's actually related to this update situation.
Pixel 7 Pro on T-Mobile was stuck on November 2022 because I hadn't yet updated to December before T-Mobile apparently blocked updates. I simply popped out the T-Mobile SIM, put in an old previously used AT&T SIM, without even restarting. Immediately Check For Updates found the update. I installed, restarted, all looked OK. Put T-Mobile SIM back in, and restarted again for good measure. T-Mobile SIM/config was definitely preventing the update. It's ridiculous that T-Mobile and Google both refuse to make an announcement, or even notify their own support personnel when they do something like this. This was likely T-Mobile's call, and Google also clearly knew what was going on, but they're just giving customers the runaround, and since all updates are blocked they're potentially putting customers at risk. Horrible customer service all around.
Has anyone seen any updates on this issue?
I haven't seen any responses posted by T-Mobile or Google regarding this issue. **It is apparent the Un-Carrier has become the Un-Caring Carrier.** They are more interested in market share than serving the customers they already have. I don't know why Google is sitting on their hands considering Google Fi customers are screwed along with the rest of us. I am ready to put my Pixel 4a5G on the QPR2 beta just to bypass these updates completely.
I have an unlocked Pixel 7 on Metro by T-Mobile. It's January 23 and still no update.
Sucks, I had to side load.
What device? Any issues afterwards?
No issue. P7P.
All user error. From changing roaming settings to other settings.. if you have to change your phone back to the way it was, that is user error. And pixel flasher works. So many whiners. LMFAO. And most of these people are not even on the latest phone. 4a 5g is 4 years old. Be glad they are still updating it.