User Profile
JNavas
Transmission Trainee
Joined 4 years ago
User Widgets
Contribuciones
Re: June Pixel security update delayed
Bobaloo wrote: I'm content to wait but not so happy with my modem as sometimes my calls will not go through and have to dial more than one time, very frustrating. Yes, Pixel does have some annoying calling problems, but I found that restarting the phone weekly largely eliminates them. You might want to give that a try.11Visto0likes0ComentariosRe: June Pixel security update delayed
fireguy_6364 wrote: Bobaloo wrote: Guess Google is going to have to make a special update for T- Mobile like last time or T-Mobile is going to have to change things to be compatible with Google. Either way someone needs to change things up T-Mobile. you change the car to work on the road..not the road to work with the car. fully on G to fix. I'm afraid that's not a valid analogy. Wireless communications is extremely complex, both on the carrier side and on the device side. Devices (esp. modems) are not perfect, and carriers have to make allowances for device imperfections. Carriers (esp. T-Mo) have the challenge of juggling standards and frequencies, and refarming spectrum, so devices have to make allowances for carrier imperfections. Hence it's quite possible that it's more practical for Google to patch its device to be compatible with T-Mobile than vice versa. Regardless, my Pixel 6a is still happily on the May update, and I'm quite content to wait until the June update is rolled out. "If it ain't broke, don't fix it."9Visto0likes0ComentariosRe: Pixel 7 Security Update
pixel12a wrote: Plus the silence speaks volumes. If Tmobile was protecting us or its network. You would think there would be a official response."Hey our Tmo engineers found a issue with E911. Expect a slight delay while we work with google" Or "We noticed that your not getting your updates. Were working with google to get to the bottom of this" Something, anything its just silence. Not commenting on reworking a security update is normal. This is no big deal. Disclosure is only necessary when there is a widespread problem, which isn't the case here.13Visto1like0ComentariosRe: Pixel 7 Security Update
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 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. It's more likely the time necessary to modify and fully test code, which is significant, It won'tbe 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.307Visto1like0ComentariosRe: Pixel 7 Security Update
Yes, because Google delivers updates, it's a Google issue. Has it not occurred to you that there are likely issues in the update that are unique to the T-Mobile network? Because 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.15Visto0likes0ComentariosRe: Pixel 7 Security Update
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.12Visto0likes0ComentariosRe: Pixel 7 Security Update
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.11Visto0likes0Comentarios