We get so excited when a new Android update arrives, especially if you own a Nexus handset and we’re talking about a major overhaul of the operating system, like Lollipop for example. Google’s latest OS update definitely did change a ton of things within the OS, but that also probably means they missed a few bugs. This is actually a pattern with every OS update, it’s the way it has to be I guess. Every time we get an update, Google releases another update after that in order to fix the bugs they missed, sometimes those bugs are unnoticeable and not a big deal, but sometimes they cause major issues with your smartphone and need to be fixed ASAP. Unfortunately, I’ve seen many bugs like that and had issues with many of them myself, Lollipop included. I currently have a nasty memory leak bug on my Nexus 5 after the official Lollipop update and can’t wait for Google to patch it, luckily it seems the company has started pushing 5.0.1 update for certain devices, though Nexus 5 doesn’t seem to be included just yet.
We already reported Google started pushing the 5.0.1 update to Wi-Fi Nexus 9, Wi-Fi Nexus 7 (2013) and the Nexus 10, but we didn’t have any info when it comes to things they fixed, now we do… let’s see what this 5.0.1 update has in store for us. It seems like Google’s Android 5.0 Lollipop update came with a nasty inadvertent factory reset bug (at least in the versions for the devices listed above) which Google fixed in a 5.0.1 update. Android is a platform which can be configured to wipe the device if you fail to unlock it after the certain amount of attempts, and by unlock it I mean hit the right pattern or enter the right PIN you set up as a security feature. This is of course not a problem if you don’t use a PIN or pattern lock on your device. Every tap is basically an attempt (at least while using pattern lock, when using a PIN code you need to hit “OK” in order to trigger an attempt), or at least Android perceives it as such, some users experienced this issue and their device got wiped on its own basically.
That’s all we have thus far, if we stumble upon some additional fixes we’ll let you know, considering I don’t believe many users have experienced this issues on their device, at least it doesn’t sound like it.