Android 5.0 Lollipop OTA delayed to November 12
Google had previously announced that the Android 5.0 Lollipop OTA should begin its rollout to the Nexus 4, Nexus 5, Nexus 7 and Nexus 10 on Monday. While many were eagerly awaiting the arrival of the update to their devices, it never showed. It seems that the Mountain View-based company has delayed the Android 5.0 Lollipop OTA rollout to November 12 so that they can fix some bugs and issues discovered in the OS.
November 12 is the official release date for the Nexus 6, so pairing the Android 5.0 Lollipop OTA release with the brand new handset isn’t such a bad idea. It seems a bit old-fashioned though. Anyway, the Android 5.0 Lollipop OTA was delayed because developers have allegedly encountered a series of bugs that would negatively impact the experience of new users with the brand new OS. It might be the right choice, since Google wouldn’t like to rollout the Android 5.0 Lollipop OTA like Apple rolled out iOS 8. When iOS 8 was launched, there were a ton of bugs present, and the subsequent release of iOS 8.0.1 and 8.0.2 only made things worse. While iOS 8 did stabilize with version 8.1, the bad feedback the OS got when users first received it wasn’t pleasant. We’re sure that Google would not like that to happen with the Android 5.0 Lollipop OTA.
While some users and Nexus owners who are more than impatient say that it was a below-the-belt move from Google to announce Android 5.0 Lollipop OTA and then delay it, it might be for the best. Google has responded to users complaining about how the company had had the opportunity to fix the bugs in previous developer versions of the OS, saying that the Android 5.0 Lollipop OTA should roll out in the following few weeks. We hope that “few weeks” is an extended margin and the November 12 date is accurate, because we are anxious to see the Android 5.0 Lollipop OTA on older Nexus devices, too. In any case, we are still wondering what kind of bugs we are talking about here and why the company hasn’t addressed them in previous versions of the OS. Maybe it has something to do with the new SD card functions and app permissions.