Google's next Android expansion has been spotted running on Nexus 4, Nexus 5, Nexus 6, LG G4, HTC One M7 and Moto G XT1033 in the previous days which translates that the update would be rolled out anytime soon.

Various information have been leaked by different sources since February. Android issue tracker Chromium reveals that the latest firmware update is already available for Nexus 6 smartphones with build number LMY40. The Nexus 5 devices with build number LMY47E was also spotted on the issue tracker last February 16. Screenshots published in a website also points out the same update shows up last February 5 on Nexus 4 smartphones with build number LMY36B. Leakster named Artem Russakovskii also has just confirmed that Lollipop Maintenance Release 1 update or Android 5.1 will hit Nexus 7 2013 devices before this week ends.

Meanwhile, another website discovers an HTML5 test for Chrome browser a possible G4 variant with model number LG-H818 running with the same Lollipop update. The website stresses that the future G4 smartphone with build number LMY29F is bound for Asia. The same report says LG-H818 is likely to sport as 2560 x 1440 pixel QHD screen resolution.

Leaked photos of the first-generation of Moto G smartphone with model number XT1033 have surfaced online via Google Plus user Damian Junior. The user told XDA-Developers Google+ community that a friend working from Motorola have shared him the information. The Moto G model sports a dual-SIM slot, which is said to enable users to change the dialer color for each SIM.

Motorola's Moto X 2013 has not received the Android 5.0 update yet due to issues on the architecture on the device.

According to several news reports, Android 5.1 Lollipop update will resolve some issues with battery life. It will also bring in silent or mute mode, bug fixes, better RAM management and some changes for Material Design. The update is also apparently supposed to "make Android buttery smooth again."

Based on Google's usual code naming process, all the individual builds are determined with a short build code, which suggests the build date of that particular software.

Google, however, states that the date code is not guaranteed to be the exact date the build was made and minor variations added to an existing build re-use the same date code.