Certain Google Pixel units are incompetent to implement a Jul Android Security Update that Google started rolling out on Wednesday, as countless owners of a 5-inch flagship took to a company’s central product forums to protest about their smartphones unwell a designation process. The Alphabet-owned association is distributing a latest set of confidence rags as an over-the-air (OTA) update, nonetheless owners of some models are presented with a “Couldn’t update” summary once they try to implement a 61.1MB package. The blunder doesn’t explain on a problem and usually provides users with a choice to “Try again,” that reportedly doesn’t do anything. According to new reports, Google Pixel models from Google Fi, Rogers, and T-Mobile are a usually ones affected, indicating that a emanate is associated to a OTA build NKG47M. Google Pixel units bought from Verizon Wireless and unlocked, general versions of a handset are all clearly updating but any issues.
The Mountain View, California-based tech hulk already pronounced it’s wakeful of a problem and is operative on a fix, yet it’s now misleading how prolonged a association will take to discharge a patch. Google didn’t go into any sum per a inlet of a emanate and what caused it and it stays to be seen either a organisation does so by a time it distributes a new program package. None of a Pixel XL units are influenced by a phenomenon, with their 70.1MB OTA nearing and installing on all models but any hiccups. While some owners of a smaller Pixel-series smartphone are now still using a Jun confidence patch, a association positive them that there’s no reason to be shaken as no famous exploits are now in dissemination and their inclination are still protected as of this writing.
The latest OTA already hit a Nokia 6 in certain territories even before Google managed to pull out a images for concordant Nexus and Pixel devices, that isn’t an bland occurrence and signals that HMD Global Oy is clearly critical about a guarantee of unchanging program updates for new Nokia devices. More sum on a revised chronicle of a problematic NKG47M picture should follow shortly.
Do you have an unusual story to tell? E-mail email@example.com