User Profile
xblackvalorx
Transmission Trainee
Joined 6 years ago
User Widgets
Contribuciones
Re: Pixel 7 Security Update
pixel12a wrote: xblackvalorx wrote: 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. I agree but this is a tmo forum. So we should only expect some defending of tmo. I have been with tmo since 2003. Back when bring your own phone was something you had to ask about in the store. Just to get special pricing. Tmo is the better of the 3 by far. But I'm 100 percent sure this block is at tmo request. And tmo requested it as the december update was going out. That's why some are stuck on november. So it couldn't be because of the supposed bluetooth bug. That didn't pop up until the January update. If this was a issue with network interference or e911 incompatibility. We would see bug issues on the android developer site. It would be a work in process to get it fixed. Its quite on the android developers forum. Just unrelated bug discussions in progres for february update So that only leaves something behind the scenes. Something tmo and google are hashing it out. Its got to be something that the twocant 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. For what it's worth the beta is solid, and largely takes tmo out of the update process for real. I'm very happy I updated and have a fully featured build because I share the same suspicion1Ver0likes0ComentariosRe: Pixel 7 Security Update
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.2Visto0likes0ComentariosRe: Pixel 7 Security Update
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 thread1Ver0likes0ComentariosRe: Pixel 7 Security Update
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.0Visto0likes0ComentariosRe: Pixel 7 Security Update
raisinbrann wrote: I was contacted by a T-Mobile customer support managertoday regarding a complaint I had filed related tothis 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 anticipatesa fix maybe available in the February Android Security-Feature Update. Sothere probably won't be aJanuary Update for Pixel owners. I suggested he post an annoucement ornote onT-Mobile's website announcing the roll-out delay and reason why so Pixel customers will stop guessing and becomngupset. 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 pixel2Visto0likes0ComentariosRe: Pixel 7 Security Update
syaoran wrote: xblackvalorx wrote: syaoran wrote: xblackvalorx wrote: fireguy_6364 wrote: xblackvalorx wrote: Bobaloo wrote: Spoke with a technical rep from T-Mobile and was told they do not block updates and that December is the latest update that they have. So my guess now is that it's a Google issue as they tried to connect me to Google and they were closed. Must have MLK day off so really nothing more to add to the story! That's a flat lie from them. Literally only one carrier and it's connected carriers are having this issue. I can't find one singular t mobile phone that has updated to the January update without outside assistance across here, Reddit and xda. Literally every other carrier anyone who goes to check it's there. it was also literally mentioned above that it was reported that Google Fi devices were having issues after the update and they run on TMOs network. gonna go out on a limb and say if the Google Fi devices are having issues then so is whatever update variant they have for TMO devices..if this is the case then theres your delay. If it was the image from Google having issues they'd pull it and we couldn't side load. Why are you all so desperate to take the blame off t mobile? Google it. Every Android focused news sources has been reporting it as a t mobile issue for days. Some t mobile phones aren't even updating past November. Stop trying to protect t mobile and hold them accountable I don't see any proof offered.that clearly shows that T-Mobile is to blame. Why are you so insistent on blaming T-Mobile when others have pointed out that it also affects Google Fi? Google Fi is t mobile LMAO And I'm just being factual. If the issue is isolated to t moving devices, yes it's a t mobile issue. As I've said, there's a reason every single Android media source is reporting it as such. You can track every platform and at this point nearly all other devices have auto updated, and t mobile (and it's smaller carriers) users still have nothing. Google Fi uses multiple carriers. T-Mobile is just one of their service partners. 1 of 2 "not t mobile employee" They're also the primary one with US Cellular only being used in a few Midwest areas.0Visto0likes0ComentariosRe: Pixel 7 Security Update
fireguy_6364 wrote: peer to peer site..you wont see any posts from any TMO peeps. only mods and admins to keep the site in order only.. Pretty hard to believe a bunch of people are taking time out of their days to defend a company and disrupt legitimate discussion of an issue for free. If you guys don't have anything to say about the actual problem, or anything actually contributory to the topic maybe put down the keyboard? Just saying it isn't a t mobile issue when it's only happening to t mobile users, across multiple pixel gens and even some still being stuck on the November update isn't contributing anything. It just seems like weird defense of t mobile. As another user pointed out, for all intents and purposes it seems as if T mobile for some reason began blocking updates sometime even before the January update given there's still some users who right now can't pull the December feature update even and it's finally being pointed out and discussed everywhere, but only on a t mobile owned forum are there a bunch of random white knights totally blocking discussion and just insisting it isn't T mobile. Little weird, seems like PR damage control at this point, especially given all the defensiveness appeared after literal news articles about the issue. This has shady T mobile shenanigans written all over it.0Visto0likes0ComentariosRe: Pixel 7 Security Update
fireguy_6364 wrote: xblackvalorx wrote: fireguy_6364 wrote: so why not test this out yourself? go toss in another carriers sim card..do your download..then test away..if its issue free then its TMO holding things up..if it downloads and when you switch back to your TMO sim and you start running into network issues..well..you were told this was happening and cant exactly blame TMO Also given t mobile hasn't said anything for weeks I could definitely blame them lol. Seriously, defending a mega corp for no reason is peak cringe dude where exactly are you expecting them to say anything? Usually if there's something worth blocking an update for there's a known issue, usually if there's a known issue a carrier could tell you. I mean it's not like tech reporters are literally reaching out for comment from t mobile and getting silence or anything?0Visto0likes0ComentariosRe: Pixel 7 Security Update
fireguy_6364 wrote: so why not test this out yourself? go toss in another carriers sim card..do your download..then test away..if its issue free then its TMO holding things up..if it downloads and when you switch back to your TMO sim and you start running into network issues..well..you were told this was happening and cant exactly blame TMO Also given t mobile hasn't said anything for weeks I could definitely blame them lol. Seriously, defending a mega corp for no reason is peak cringe dude0Visto0likes0ComentariosRe: Pixel 7 Security Update
fireguy_6364 wrote: so why not test this out yourself? go toss in another carriers sim card..do your download..then test away..if its issue free then its TMO holding things up..if it downloads and when you switch back to your TMO sim and you start running into network issues..well..you were told this was happening and cant exactly blame TMO Esim No network issues reported in any of the Google forums, and no issues with the beta that has the January 5th update. Seriously bruh is t mobile paying you? This is sad lol.1Ver0likes0Comentarios