Android 5.0.1 Lollipop update coming soon

Summary:Owners of Nexus 4, Nexus 5, Nexus 7, and Nexus 10 should be seeing Android 5.0.1 update for Lollipop landing on their devices soon which should squash the unpleasant bugs that have been plaguing Lollipop early adopters.

Owners of Nexus 4, Nexus 5, Nexus 7, and Nexus 10 should be seeing Android 5.0.1 update for Lollipop landing on their devices soon.

Google has released the source code for the update to the Android Open Source Project (AOSP) and this is good sign that the update will be pushed to Nexus devices imminently.

This will come are a relief to those who have been suffering from Lollipop bugs. Users have been complaining of poor battery life (a problem that appears to be widespread on the Nexus 5), overheating (Nexus 9) and storage related issues (Nexus 6).

Some users claimed that the update rendered their devices unusable.

If you're not yet moved up to Android 5.0 Lollipop then don't worry. You're lucky since you're missed out on the problems.

You can if you want download the Android 5.0.1 (build LRX22C) direct from Google for the Nexus 9, Nexus 7 (2013), and Nexus 10.

See also:

Adrian Kingsley-Hughes is an internationally published technology author who has devoted over a decade to helping users get the most from technology -- whether that be by learning to program, building a PC from a pile of parts, or helping them get the most from their new MP3 player or digital camera.Adrian has authored/co-authored technic... Full Bio

zdnet_core.socialButton.googleLabel Follow @@the_pc_doc Contact Disclosure All opinions expressed on Hardware 2.0 are those of Adrian Kingsley-Hughes. Every effort is made to ensure that the information posted is accurate. If you have any comments, queries or corrections, please contact Adrian via the email link here. Any possible conflicts of interest will be posted below. [Updated: February 23, 2010] - Adrian Kingsley-Hughes has no business relationships, affiliations, investments, or other actual/potential conflicts of interest relating to the content posted so far on this blog.

View the original article here

Google quietly pushes out Android Lollipop 5.0.1 images

Summary:An update to Lollipop should fix the issues that Nexus 7 users have had with video playback.

After a less-than-smooth rollout three weeks after it began to roll out Android Lollipop to users, Google has begun the process of getting Lollipop 5.0.1 out the door.

The Android maker quietly updated its factory images page to reveal a 5.0.1 build for the Nexus 9, Nexus 7, and Nexus 10. Installing images from this page does require the flashing of devices in order to update them, and does not carry user data across in the process, unless backed up and restored by the user.

Among the changes in this version is an increase to the amount of memory allocated for video playback on Nexus 7 users, which often manifested itself on YouTube as the now-infamous "There was a problem while playing the video. Touch to retry" error.

Users on the bug have reported that the update has fixed the issue.

Another issue fixed in this release is avoiding accidentally factory resetting a device configured to wipe itself after a number of failed access attempts. Lollipop now does not count password or patterns with less than four elements as attempts to access the device.

"If we do, we risk resetting the device due to stray input," the relevant commit message said.

A Google spokesperson told CNET News that the factory reset bug was not widespread.

Lollipop is yet to be provided to Android users en masse. In the latest statistics provided by Google on which versions of Android users are running when accessing its Play Store, Lollipop fails to rate a mention.

According to Google, 34 percent of Android users now run Android 4.4 KitKat, 49 percent run a version of Jelly Bean, while 9 percent are stuck on Android 2.3 Gingerbread.

Chris started his journalistic adventure in 2006 as the Editor of Builder AU after originally joining CBS as a programmer. After a Canadian sojourn, he returned in 2011 as the Editor of TechRepublic Australia, and is now the Australian Editor of ZDNet.

View the original article here