While a rollout date for the Android 4.4.3 KitKat update was leaked and later debunked, there is an indication that the new software version may still be released soon.
A source originally told Android Geeks that Google had plans to begin rolling out Android 4.4.3 onto the Nexus 4, Nexus 5, Nexus 7, and Nexus 10 starting Friday, but now the publication says the update has been delayed. There are no details on why the Android 4.4.3 update has been delayed.
Meanwhile, there have been many sightings that suggest the Android 4.4.3 update is real. Most recently, the software was spotted by name in an AOSP change log and within an informational video for the newly launched Motorola Moto E smartphone.
Though actual mentions of Android 4.4.3 are still scarce, there are others, such as the Edu Device Setup, listing software support for its app as Android 4.4.3 on the Play Store. Other sightings include the surfacing of several build numbers, which are not associated with currently released Android operating systems.
Rumors about Android 4.4.3 first surfaced when tech website Myce discovered the build number KTU65, which it quickly connected to Android 4.4.3. Later, Italian tech website TuttoAndroid discovered the build number KUT72B, and LlabTooFeR indicated that the build was being tested by Google. Android Police also got its hands on a prospective change log for Android 4.4.3 in addition to a capture of Android 4.4.3 running on a Nexus 5.
Will Android 4.4.3 KitKat Affect Rooting Ability?
As users await the Android 4.4.3 KitKat update, a well-known developer has detailed that the new version could actually hinder the tech-savvy rooting devices to their preferred specifications. The developer Chainfire has looked within the Android Open Source Project (AOSP) code for indicators of what changes can be expected with the Android 4.4.3 update. According to the developer, such root access protocols as SuperSU, SELinux and ART are among those that may suffer from the Android 4.4.3 update.
Android initially adopted the SELinux, a protocol that exists to enhance security on Linux-based systems such as Android. Google’s continued development of SELinux blocks how apps gain root access on Android. According to Chainfire AOSP code indicates that Android 4.4.3 might negate old ways of executing root access. This could in turn affect protocols such as SuperSU, a management tool, which allows users to select which applications get root access, and which does not, and Android Runtime (ART), which is the basis of app execution for the Android operating system.
Chainfire notes that AOSP code is not stock Android 4.4.3 and that there is no indication that these changes will actually make it into a released version of the new operating system. Chainfire has updated his root guide to include the new methods for software exploits. Additionally, Chainfire recommends that developers switch to using the old Android processing protocol, Dalvik, temporarily upon the release of Android 4.4.3 until root apps are compatible with ART.
Fixes Expected To Be Addressed With Android 4.4.3 KitKat
Users have been awaiting the Android 4.4.3 update since the current Android 4.4.2 version has a number of bugs, which have plagued devices since December. Nexus users appear to report the most issues with the firmware. Android 4.4.3 will reportedly address more than three dozen bugs brought on by Android 4.4.2.
Many hope to see a resolution to issues with the Nexus 5 camera: the lens’ inability to focus and a bluish tint in the presence of white light. Other glitches users hope to see resolved include Bluetooth and data connection problems as well as various battery draining issues.
One issue having to do with battery drain caused by the Nexus 5 camera is localized within the mm-qcamera-daemon system code, which allows third-party apps (like Snapchat or Skype) access to a device’s camera. The mm-qcamera-daemon process continues to run even when those apps are closed and contributes to battery drain.
So far, Google has not indicated any plans to roll out an Android 4.4.3 update.