mm-qcamera-daemon to be fixed in the next android update

Since the start of the nexus 5 launch there was a major bug reported by many users the 'mm-qcamera-daemon' bug which drained the battery because of its high CPU usage and caused the device to heat up and when the camera is launched it cant open the camera
many forums and sites said that the apps like skype, viber, snapchat are causing this bug but many users who didnt installed these apps also reported this bug. The only solution for the time being is restarting the phone

google has released various OTA updates but nothing seems to work for this bug users still have the bug in the 4.4.4 kitkat version. the 4.4.3 did include the tweaks to the camera code but it failed to resolve this problem
well th good news now is that this problem will not appear in the android L update
Just a few notes on this bug.

developer at explains what is the cause of this bug and its solution

- mm-qcamera-daemon is a key part of the camera subsystem. It needs to run for the camera to operate on the N5.  The problem occurs when it gets stuck in a state where it uses large amounts of CPU, preventing camera use and draining the battery. 

Simply disabling the daemon does no good, since that also prevents the camera from working.

- This bug is for the Nexus 5.  Other Android devices may also have a process called 'mm-qcamera-daemon', but it will be based on different source code, customized for that device. Problems seen with it on other Android devices such as the Samsung S5 or the Moto G aren't going to be solved by fixes to the N5. Please reach out to the manufacturer of your device, if it is not a Nexus device.

- We've identified additional fixes to the N5 camera code, which we hope resolve the remaining 100% CPU usage cases.  We've also added a watchdog which tries to clean things up if the daemon gets stuck like this, in case there are still unaddressed issues. Again, these fixes will only affect the Nexus 5; other devices do not share the same source code at these lower layers of the camera stack, and the codebase for those devices is only available to the device makers themselves, not to us at AOSP.

I'm marking this bug as FutureRelease, which means we've put fixes in place in our internal builds, and the fixes will be included in the next major update for the N5.