Whenever a new version of Android is released there always seem to be a couple of bugs that come along with it and, it’s pretty unavoidable when writing software. The team behind the releases could have done all the testing in the world but if they miss out one little thing then they have a bug on their hands. It’s hard to think of absoilutely everything when testing, which is why we have “point releases” of software, the smaller updates in life that fix a few issues here and there and squash some bugs. Google have had a history of releasing point release after point release in order to fix issues and Gingerbread got all the way up to 2.3.7 on some devices. It’s by no means a bad thing, it’s good to see that Google are releasing fixes but, I’m sure a lot of you out there would like to see Google get things right the first time around.
For those of you on Android 4.2 – the second release of Jelly Bean – you might have come across a few bugs here and there and while it’s unfortunate to see, it’s perhaps the curse of having first access to the latest updates. We’ve heard that Android 4.2.2 was on its way and that it might be fixing bugs concerning Bluetooth audio and we’ve seen Nexus 4s roll out of Brazil running the latest and greatest from Google. Now, we’ve seen another Nexus running the latest and greatest, a Galaxy Nexus has been spotted running Android 4.2.2 and it could well hint at a fairly imminent release.
More interestingly this could be a sign that Google are plugging all the holes left in Android 4.2 to focus on Android 5.0, which is pegged to be named Key Lime Pie. If that’s the case then I could see why Google would want to get the release out sooner rather than later, with Google I/O scheduled for the summer, it’d be a good idea to get your latest release all fixed up before you move on to something new.
What bugs are you experiencing from Android 4.2 that you still need fixing?
Category: Android News