Here’s What To Expect In Android 4.4.3
It has been more than two months since Google released their 4.4.2 update, which, for the most part, resolved numerous camera-related issues on the Nexus 5. However, since that time, some residual bugs have persisted, and new ones have emerged, prompting numerous users to repeatedly inquire on issue tracking platforms for an estimated timeframe for resolution. The most prevalent issue, to which I am personally privy and have experienced firsthand, is the mm-qcamera-daemon mm-qcamera-daemon process’s detrimental impact on battery life.
It appears that the aforementioned fixes will be included in a forthcoming release of Android 4.4.3, which is anticipated to become available imminently. The individuals at Android Police have obtained a screenshot of a Nexus 5 device operating on the Android 4.4.3 platform, with certain portions redacted for reasons of privacy. A comprehensive changelog will not be accessible until the build is disseminated by Google engineers to the AOSP repositories. However, the following information has been made available to Android Police thus far:
- frequent data connection dropout fix
- mm-qcamera-daemon crash and optimization fixes
- camera focus in regular and HDR modes fixes
- Power Manager display wakelock fix
- multiple Bluetooth fixes
- fix for a random reboot
- app shortcuts sometimes got removed from launcher after update
- USB debugging security fix
- app shortcuts security fix
- Wi-Fi auto-connect fix
- other camera fixes
- MMS, Email/Exchange, Calendar, People/Dialer/Contacts, DSP, IPv6, VPN fixes
- stuck in activation screen fix
- missed call LED fix
- subtitle fixes
- data usage graph fix
- Internet telephony fix
- FCC compliance fix
- miscellaneous fixes
It is noteworthy that Myce has identified a Nexus 5 build fingerprint that indicates a KTU83 build. According to their findings, this build was created on March 24th, which is a relatively recent date. It seems reasonable to conclude that this is the same build that is redacted in the aforementioned screenshot, thereby confirming its authenticity.