Android Q Beta out now
Discussion
Corso Marche said:
Yeah, I'll see what happens over the next few weeks re. the May OTA security update. I'd found a convenient way around the charging issue myself when it arose, so that's not much of a worry.
Late last night (after midnight), I picked up my phone as part of tidying up before bed only to see a notification on it re. a pending update. And lo and behold there was the April security update ready for installation.
Just as well I chose not to take Google up on their suggestion of returning it for a paid repair! I'd queried what they would do with an obvious software or firmware issue and if their repair centres had different versions of software available to the OTA's but they avoided answering that question.
Indications are there's more going on behind the scenes and the left hand doesn't always know what the right hand is doing.
Charging bug still isn't resolved, but at least I have a no hassle workaround for that which doesn't cause any hindrance.
Interesting update on this, for anybody who is interested.
The May security patch also failed to automatically install on my P2XL, so I waited until the 12th May to see if I would receive it late. No signs of anything, so on the 12th May I began to intermittently perform manual checks for the update. Still nothing, only the same extra long "Preparing System Update" message eventually followed by a message 15-20 minutes later saying my phone was up to date (which it wasn't).
All my Nexus and Pixel devices have been bought in the US since 2011 and used internationally. When Google Support suggested returning it for paid repair it was no issue returning it to a repair centre in Europe, even though it was bought in the US.
I'm currently in Asia though, and probably won't be home in the near future due to the current virus crisis.
Last night I checked again, and it failed. So then I switched to a VPN in the US, hit the manual update, et voila! Instant installation of the May security patch.
So then, what gives? My phone's DNS has always been set to 1dot1dot1dot1.cloudflare-dns.com in recent years, so it shouldn't be a DNS issue identifying the update servers. But the update kept failing until I went through a VPN node in the USA. What gives? Any ideas folks? 9 years of receiving updates when they were issued no matter what country I was in, and now as of April this year this weird issue has arisen.
The May security patch also failed to automatically install on my P2XL, so I waited until the 12th May to see if I would receive it late. No signs of anything, so on the 12th May I began to intermittently perform manual checks for the update. Still nothing, only the same extra long "Preparing System Update" message eventually followed by a message 15-20 minutes later saying my phone was up to date (which it wasn't).
All my Nexus and Pixel devices have been bought in the US since 2011 and used internationally. When Google Support suggested returning it for paid repair it was no issue returning it to a repair centre in Europe, even though it was bought in the US.
I'm currently in Asia though, and probably won't be home in the near future due to the current virus crisis.
Last night I checked again, and it failed. So then I switched to a VPN in the US, hit the manual update, et voila! Instant installation of the May security patch.
So then, what gives? My phone's DNS has always been set to 1dot1dot1dot1.cloudflare-dns.com in recent years, so it shouldn't be a DNS issue identifying the update servers. But the update kept failing until I went through a VPN node in the USA. What gives? Any ideas folks? 9 years of receiving updates when they were issued no matter what country I was in, and now as of April this year this weird issue has arisen.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff