The Android 5.1 Lollipop update for the Nexus 5 is finally starting to roll out to additional owners of the smartphone almost a month after being initially announced by Google.

It appears that the rollout of the Android 5.1 Lollipop update for the Nexus 5 smartphone is finally taking shape after a select number of users received the update in March after Google's official announcement of the update. The Android 5.1 update not only offers improvements and fixes for issues that have been plaguing owners of the smartphone, but also some additional features.

The move is buoyed by the new Android 5.1 LMY47I build from Google. The build that was pushed out to select Nexus 5 smartphones following Google's announcement was a different build number, not LMY47I, which has additional features including SIM card improvements. Nexus 5 owners have been experiencing numerous issues with the initial Lollipop rollout and it appears that a further push to the Nexus 5 was halted until the issues could be addressed within a new build.

Verizon recently pushed out an Android 5.0 Lollipop update to users of Samsung's former flagship smartphone, the Galaxy S5, and then suddenly halted the update, only to re-release it recently. Though no official announcement was made as to why, it is suspected that issues experienced by users with the initial version were severe and widespread enough to call a halt to the rollout until the problems were addressed and fixed. Presumably, the same scenario is in effect with Google and the Nexus 5, which is why an entirely new build number is now being rolled out.

With many Nexus 5 users now finally receiving their upgrade over the air, Google is now slated to begin Android 5.1 updates for the Nexus 9, Nexus 7 2013, Nexus 7 (cellular), and Nexus 4. While the updates have been confirmed by Google for all 4 devices, no specific time frame has been announced, and it's not clear if the Nexus devices will actually receive Android 5.1 or Android 5.1.1, which will likely contain a bug fix for the memory leak problem that has been affecting some Android 5.1 users.

ⓒ 2021 All rights reserved. Do not reproduce without permission.