Sign in

Sign in to confirm

Have you forgotten your password?

... or login with Facebook:

Don't have an AndroidPIT account yet? Sign up

Android 4.4.3 being tested, coming soon to Nexus 5

Kris Carlon

A new build of KitKat, Android 4.4.3, is currently being tested by Google for the Nexus 5 with a build number of KTU72B. The incremental update is only destined for the Nexus 5 and addresses one core issue that has been increasingly plaguing the device: the mm-qcamera-daemon issue we have discussed here previously. This will be the third update to KitKat that only addresses Nexus 5-specific problems.

Nexus 5 camera sensor 443
Android 4.4.3 coming soon to a Nexus 5 near you! / © AndroidPIT

The bug, which first surfaced a long time ago, basically causes the CPU to go into overdrive when the camera app is launched, either on its own or via another app like Skype, and the resulting runaway CPU use drains the battery. The problem lies in the fact that the CPU chewing and battery drain continues even after the camera app has been closed. The issue is affecting other devices too, but the Android 4.4.3 update is purely to fix the Nexus 5. There's no word as to whether the update will also bring the new KitKat camera API we've been waiting for too.

Not where you want the already problematic Nexus 5 battery investing its energy. / © WonderHowTo

Google confirmed the problem as a known issue several weeks ago, but its impact seems to have picked up in intensity in the last few weeks. Android 4.4.2 (the initial cause of the problem) has been out for months now, but most fingers are pointing to a recent Skype update as the cause for the increased appearance of the problem, and many stop-gap solutions have centered around uninstalling Skype until a proper patch is implemented (rebooting also works, at least until a background process triggers the bug again). If you have another device suffering from the same bug, which is ultimately linked to Qualcomm chips, Google advises you contact your manufacturer directly.

Have you been suffering from this issue? Have you found any other solutions to fix it?