Jump to commentsRelated Stories

Android 4.4.2: KitKat Still Has Atleast 27 Issues, Bug Fix Imminent?

Android 4.4.2: KitKat Still Has Atleast 27 Issues, Bug Fix Imminent? Android 4.4.2 BugsIssues 300x199Android 4.4 Kit Kat was one of the most expected updates of 2013, and while Google created the smoothest and best experience we’ve seen on a mobile device, Kit Kat is not perfect. This new iteration of Android, introduced a bunch of new features, but along with them came several new bugs and issues that Google is yet to fix.

Android 4.4.1 is born

Back in October 31 we got the first official glimpse at Android 4.4 Kit Kat, sadly at that time it was only available for the Nexus 5. A few weeks later, Google began rolling out the update for the rest of the Nexus family, including the Nexus 4, Nexus 7, and the Nexus 10. However, soon after users received the update to Android 4.4 Kit Kat, a huge wave of issues were discovered by the community. Google addressed some of these problems and released a new bug fix update, Android 4.4.1 was born.

Android 4.4.2 fixes bugs in 4.4.1

This new build of Kit Kat solved many issues specific to the Nexus 5 and some small bugs. But it was still far from perfect, as it also had several security flaws that many users were afraid about. So Google launched a new update, Android 4.4.2. This fixed most of the major security issues with Kit Kat. This is currently the latest version of Android, and is the one that is getting pushed by OEMs to their devices.

Android 4.4.2 has at least 27 known issues/bugs

Android 4.4.2 is still not a perfect update, as there have been numerous reports on Google’s Product Forums, pointing out a wide number of issues on Nexus devices. This led Reddit user, and Nexus 4 owner lazy_elf to identify and explain as many issues with Android 4.4.2 as he could find. In total he found 27 issues and detailed every single one of them. Some of them are fairly minor bugs that could be ignored, but there are some that you might call severe. In addition to the 27 issues detailed by lazy_elf, more users have begun listing their own issues, creating a really extensive list.

Most common issues in the current build

Some of the problems that many Nexus owners have been facing include a poor battery life, several issues with the UI, less than optimal connectivity, and many more. These issues have pushed many Nexus owners to almost beg Google for a new Android bug fix update. Sadly Google hasn’t addressed these issues nor has said anything to their upset users.

Android 4.4.2: KitKat Still Has Atleast 27 Issues, Bug Fix Imminent? Android 4.4.2 KitKat 168x300Still… everything is not dark at the end of the tunnel, earlier this week we spotted a new version of Android 4.4.2 Kit Kat, but it is unknown if this is only a test build and if it’s ever going to be released to users. The guys over at Android Police have stated that a fix for an audio issue on Android 4.4.2 Kit Kat is coming, perhaps it is the new build we found?

The only thing we can do at the moment is wait and hope for a new update in the near future, although Google has not said a word about this. Meanwhile if your device is plagued with issues you can try out custom ROMs or temporary fixes to these issues.

Have you faced any problems on your Nexus device? If so, please tell us in the comments below.

Want to share this story?

Comments

  1. dave conner says

    Lots of problems with my nexus 7 since kitkat opdate. Very slow to charge. Fast battery drain.Programmes stop for no reason even with very strong wifi signal. When i bought the tablet it had jelly bean and had no problems.
    Incidentaly my partner also got a nexus 7 at the same time and is experiencing the same problems apart from the slow charge, hers charges twice as fast. Have tried Factory reset but no change.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>