[Q] mm qcamera issue - Nexus 5 Q&A, Help & Troubleshooting

Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755

koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.

Lethargy said:
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Click to expand...
Click to collapse
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?

koszor said:
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
Click to expand...
Click to collapse
I doubt it, it might be a hardware driver issue, nobody knows what the real cause is. Personally I don't have this issue, I don't think another ROM or kernel will change anything much, although it's worth a shot if the drain applies to you.

It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!

koszor said:
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
Click to expand...
Click to collapse
Depends where you are in the world.. 10:46pm here in Australia. :angel:
But yeah, I have no idea if another ROM would fix the issue in any way. If it helps a little it's more likely because it's a clean flash, not because of the ROM itself, but who knows. Kernel won't affect this at all.

well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.

koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.

simms22 said:
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
Click to expand...
Click to collapse
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
bblzd said:
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
Click to expand...
Click to collapse
Its gotta be snapchat, it used to lock up and soft boot my nexus 4 from a 'bug' or something like that ><
oh well, ill just have to keep an eye out for it.. I will try CM for a month or so and post my results back tho!

koszor said:
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
Click to expand...
Click to collapse
do you have any apps that use the camera? and i mean any, there are many. if you used that app, and iy continued running in the background, the the camera daemon would also run in tbe background. if it is the old camera daemon issue that youre experiencing, then it would happen every time the camera is used, not occasionally. if its only once in a while, something else is causing your issue. i had the issue before, every single time i used the camera, not occasionally.

Related

Nexus S Freezing - How big a problem is this?

I'm on the verge of buying a Nexus S but I am now reading about many freezing issues where the phone loses all responsiveness after the backlight goes out on occasion - the only solution being to pull the battery and reboot, only to have it happen again.
This thread shows that some people are returning their phones to Samsung and are seeing a fault diagnosis of 'bad BGA' and a fix of 'PBA replaced'
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
BAD BGA COMPONENT
WARRANTY, REPLACE PART
Solution:
Replaced PBA
Passed All Functional Testing
Just how wide a problem is this, is it something that will affect pretty much everyone at some point or are these cases failry isolated?
edit: I am buying from someone who has this phone on contract so I am wondering also if I will be able to get support from Samsung should I run into this problem. Are warranty issues dealt with by Samsung direct or are they passed through the carrier when originally obtained on contract?
Any thoughts?
never experienced any of these problems. you have a 30 day return policy (maybe less now)
zephiK said:
never experienced any of these problems. you have a 30 day return policy (maybe less now)
Click to expand...
Click to collapse
Unfortunately not, see my edit above.
Also, it seems users are running into this problem after owning the device for a while, taking them beyond their 28 day / 30 day return
i've had mine since it was first available and never had any problem like this.
I've also never seen this.
milkham said:
i've had mine since it was first available and never had any problem like this.
Click to expand...
Click to collapse
same. ive had it maybe like a 1.5 week after release date
It happens to me if i mess around with custom kernels and o/c speed but so far if i use netarchy's stable CFS, it'll be fine. No freezing and having to pull my batt.
It happens if i use hornity or some BFS kernels. Haven't tried Jame Bond yet to test it out.
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
the thread the OP linked is Nexus S
only time that has happened to me is when i overclock to 1.4 ghz and the phone can not handle it
Ok, it's encouraging that this isn't affecting everyone but still a bit worrying.
AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
Wrong - as zephiK has pointed out, the link is to a whole load of people having issued with the Nexus S, NOT the Galaxy S.
I believe the most problems with smartphones are in software, not hardware. And software could/should be patched/updated.
and this is one of the reasons that preventing me from walking into cpw and buying it tomorrow.
I am Having this exact issue with my phone. it is unusable the phone freezes every 20 minutes. Hope Samsung finds a fix for this soon.
I just got my nexus s the other day but I haven't had any freezing either I hope those with the issue get it sorted out though
loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange
AllGamer said:
loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange
Click to expand...
Click to collapse
Happens in stock rom, and many other custom roms too. So I dun think its the rom problem
oh dear, this is exactly what I'm concerned about. Any pattern as to which are affected by this, ie just slcd or just samoled? Only a thought.
I shall soon receive my second nexus s and I really don't want to have this problem!
I'm using the i9023 if that info helps.
Yes thanks but it's not what I wanted to hear as the chances are that this is the one I will receive.
I've heard of people reporting successfully fixing this with a full reflash, others say it's a hardware issue.
Keep us posted.

How to install init to fix froyo freeze ?

hello xda members
i have install froyo fx06 bundle here
my problem is sometimes the phone freeze. i read the entire post to find the solution to fixed that. then i found the only solution is to install init at here . can someone make a tutorial how to install that. i mean the step by step tutorial.
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
R^7Z said:
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
Click to expand...
Click to collapse
i don't know how to use ADB or terminal. actually this is my first time heard that. hehe
Some say it isn't that difficult while others have a difficult time trying to understand English, much less speak/type it(like myself ). If you feel up to it, you can start by reading HERE. Unless someone else has this simplified elsewhere. If that were the case and I knew of it, I woldn't be pointing you in this direction.
Thank you for trying to help me.
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
hotsmusic said:
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
Click to expand...
Click to collapse
and i think it's not because flax cable because this problem only happen when i use froyo fx06.
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
R^7Z said:
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
Click to expand...
Click to collapse
Thank you for trying to help me. actually i have try to set my phone in airplane mode to test if the problem because operator/service provider , but the problem still the same. it's not freeze because i still can fell it vibrate when i touch the screen only the display not show up.
about gingerbread. i have read that gingerbread is android 2.3 and froyo is 2.2 right? but why many people like to use froyo then gingerbread? if gingerbread have any problem. sorry if i asking to many question.
I'm not 100% on this but I think it has something to do with the fact that the porting is still in alpha phase for our devices. If anything, this can be looked at as good or bad. Good, that we have gotten this far and it seems our devices are pretty much stable. Bad, that this might be as good as it gets for a while. You have to weight the options of a faster port(in terms of stability) but less complete(in terms of functionality) or a more complete port but not quite as fast. I remember when we first got FroYo, it seemed like a complete mess. It took till the third release (FRX03) for stability to take place(noticable) because the devs were trying to figure out what caused the instability. When it's all said and done, the end user experience is all that most are looking for. When this is the case, it's difficult to say what should be done. Wait till it becomes more stable or try to come up with work arounds. Troubleshooting can get you so far until you require more understanding of what affects what. Hopefully, I have bored you out of your mind and that this makes things clearer as to what you can do to help!
thank you for your kind to help me. i have change to gingerbread but it have same problem like froyo. then i tried to hard reset then reinstall froyo and change the kernel. now it working great without problem except camera not working . maybe because i change the kernel htc-msm-linux-20110214_200559-package.tar . but it's ok for me. i will wait till new release.
You must have the similar issues some others have (on foreign carriers/other than USA based) Now, I'm not saying this is the problem just that others that have a similar issue, are on those carriers. There have been updated kernel packages that include the camera fix but I would suggest a little more reading into what you need to do, to ensure that you aren't causing the issue you are experiencing now.

[Q] New Google Maps flickers on CM10.1

Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
emi.bu said:
Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
Click to expand...
Click to collapse
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
PsychoPhreak said:
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
Click to expand...
Click to collapse
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
emi.bu said:
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
Click to expand...
Click to collapse
Sorry, saw someone mention it, thought it was you! Glad to hear it was sorted, I'll be sure to avoid a map update if I see one pop, but I haven't yet. Maybe it was causing issues outside of custom roms and google stopped pushing it until they got it sorted.
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Tampoon said:
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Click to expand...
Click to collapse
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
PsychoPhreak said:
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
Click to expand...
Click to collapse
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Tampoon said:
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Click to expand...
Click to collapse
Unfortunately it seems to me to be an issue with all of the 10.1's at least, and from my googling before, it seems likely specific to our device, just not sure why
Anywho, I'm pretty OK with maps 6, it works, and still has separate navi app, and is what anyone with earlier than android 4.0 is stuck with anyway.
UPDATE: So I tried the 7/22 update that I got hit with, and it's weird. Initially it seemed OK, aside from the menu button still being half off screen. After fooling around for a bit with menus and settings, it got all flickery again. It seems like it heavily had to do with overlays/prompt dialogues showing up. The box would kind of disappear aside from the outline, but still respond. After fooling around quite a bit and disabling boxes from asking again, eventually everything seems to have evened out. Now I haven't actually done any kind of navigation or heavy use, but I've been using v 7.0.2 now on and off for a few days, and the stutter hasn't come back. Wish I had a more definitive way of what I did to get rid of it, or if it eventually just smoothes out on it's own, but for now it seems like I'm good with the new maps on a CM10.1 rom.
Bump for update, anyone else experiences with new maps?
PsychoPhreak said:
Bump for update, anyone else experiences with new maps?
Click to expand...
Click to collapse
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
greiland said:
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
Click to expand...
Click to collapse
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
j1232 said:
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
Click to expand...
Click to collapse
Im running PACman ROM v22.4.0, same issue as you guys with the new maps, and navigation is a stutterfest.
I'm on jellykang 1.8 and that's definitely happening to me. especially in the navigation app
Since others are now finding this thread outside of just us DS users, I figure I'll share this idea from a dev thread:
Originally Posted by pyro9219
"Have you tried Settings > Developer Options > Disable HW Overlays?
I had to do that for several games that were causing screen tearing / artifacts."
I hadn't, but that's a wonderful suggestion, wonder if anyone else has?
Edit: So after learning how to re-enable dev options, I just tried this, and it definitely seems to WAY help. Is there any downside to leaving this checked all the time?
So something for others to try/chime in on?
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
anitgandhi said:
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
Click to expand...
Click to collapse
Hrm, I'll try it. Just loaded maps now, it was sketchy, disabled and seemed fine. Turned back on, and it was still fine, this one seems to be crazy inconsistent.
It wotk fine on my device
Gesendet von meinem GT-I9505 mit Tapatalk 2
possible workaround?
I found another workaround that seems to work for me:
Turn on the "Extended Desktop" (or "Expanded"? I'm on German here). And it's gone. Strangely the flickers don't return when I turn it off again.
Extended Desktop Option has to be activated in the settings, if it's not available in the power switch menu.
Counter perspective
I've just been working with the newest CM builds for the MT4GS, and I don't encounter any flickering. This is with a complete wipe prior to installing however.
same issue with HTC G2 on CM10.1
Hello,
I experienced the same issue on my HTC G2 with CM10.1. I had to revert to Maps v6...the v7 would sometime work fine, but most of the time I had some part of the screen flickering and the navigation feature was not usable at all (the animation would not work). I first thought it might be because of the overclocking. but I tried with stock frequency and the issue persisted.
My wife's Sony Ericsson Mk16a also has the same issue but on a custom stock rom..

mm-qcamera-daemon

I am running a stock Nexus 5 with 4.4.2. and mm-qcamera-daemon has been significantly lowering my battery life and I do not know which app is causing it. Does anyone know where this originated from or what it is?
doomjuice20 said:
mm-qcamera-daemon has been significantly lowering my battery life and I do not know which app is causing it. Does anyone know where this originated from or what it is?
Click to expand...
Click to collapse
it comes from the camera, when you take hdr+ photos.
Are you using any battery saving apps? If so, get rid of them.
Always swipe the camera away from recents when you finished
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Always swipe the camera away from recents when you finished
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
WOuld Killall -HUP /system/bin/mm-qcamera-deamon by shell script fix the camera crash without reboot?
I had the same thing I deleted most things that I recently downloaded that used the camera and I rebooted the phone and it worked
Sent from my Nexus 5 using Tapatalk
I'm having this problem too. I don't have snapchat or any of the other applications that have been claimed to cause it.
I haven't installed any new camera using apps so it's probably due to some update. Stock rom, was happening on stock kernel, is still happening on linaro.
doomjuice20 said:
I am running a stock Nexus 5 with 4.4.2. and mm-qcamera-daemon has been significantly lowering my battery life and I do not know which app is causing it. Does anyone know where this originated from or what it is?
Click to expand...
Click to collapse
I'm not sure if this helps or relates to your situation but I had that problem about a month after installing jishnu's camera...kinda came out of nowhere one day. I deleted the app/ mod, rebooted and reinstalled it and haven't had the problem since.
this is a nightmare, as it is unpredictable, with no solution, and not addressed by google.. Even after a factory reset, it ends up coming back.
I got this 2 days ago, first time ever. And I have been using my camera consistently.
First when I start my camera, I get Unable to connect to camera, so I rebooted, and camera works again, but at the end of the day, I saw the high memory usage. I rebooted the phone again yesterday and it seems fine again. Buggy...
And this process have no "Report" button like Google Search or Google Maps have, so I have no way of reporting this issue to Google.
One of the culprit is Yahoo! Messenger's voice/video plugin... Or any other apps that will use the camera..
If you were trying to upload a picture but failed in the mid way... this might occured as the app will always trying to upload the pic eventhough it got failed..
Per my similar topic here: http://forum.xda-developers.com/showthread.php?t=2564457 the culprit for me seems to be an update to Skype pushed out a few days ago.
Gaffadin said:
Per my similar topic here: http://forum.xda-developers.com/showthread.php?t=2564457 the culprit for me seems to be an update to Skype pushed out a few days ago.
Click to expand...
Click to collapse
hmm, now you mentioned it, I did install skype on my phone a while ago.
Let me uninstall it!
Since I removed Skype I've had zero more black screens; I'm pretty confident that this is the cause for me.
Negative Guys....
I'm sure that is not third party apps that is causing that drainage,
Why in the world suddenly all people are experiencing this batt drainage with many different apps and blaming them?
I have the problem with weather channel and the mm-qcamera-daemon, others with skype, others with yahoo messenger and so on, this problem suddenly?
I believe that google is working on that problem but not saying anything about it.
Please read all these reports in these 2 links and after that tell me that I'm wrong.
https://productforums.google.com/forum/#!topic/nexus/c__1mTUbOIE%5B101-125-false%5D
https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=60058
hmm.... for me, it was skype, uninstalled and back to normal. i only had skype for a week, was wondering why my battery was so messed up so i googled and landed here, took off skype and wallah.
stealthj said:
hmm.... for me, it was skype, uninstalled and back to normal. i only had skype for a week, was wondering why my battery was so messed up so i googled and landed here, took off skype and wallah.
Click to expand...
Click to collapse
I know that some people just uninstall an application and then it works again as before, but later on the problem shall arise in a few days or something, I've read this. Let me uninstall it and let you know, maybe it was an update that caused the problem but I got The Weather Channel that said it was something similar to mm-qcamera.daemon and I uninstalled it and the same problem, I deleted the cache and davlik cache as well and it did not work, I have rebooted several times and it seems that I have to do a nandroid restore and see what happens after that.
rayosx said:
I'm sure that is not third party apps that is causing that drainage,
Why in the world suddenly all people are experiencing this batt drainage with many different apps and blaming them?
Click to expand...
Click to collapse
I am not actually blaming them, just want to find out HOW to make sure this doesn't happen to me. If it involves uninstalling Skype, then let it be.
This is definitely a OS process, its whether there's a bug in the OS, that was triggered by Skype, OR its that Skype is not using the API correctly, either way, the "solution" for now is just to uninstall Skype.
/Skype/any other apps that's reported here/
Gaffadin said:
Per my similar topic here: http://forum.xda-developers.com/showthread.php?t=2564457 the culprit for me seems to be an update to Skype pushed out a few days ago.
Click to expand...
Click to collapse
I would agree with this. I've frozen Skype with TiBackup to see what happens.
reboot with clearing cache did the job for me

[Q] What's up with the N5?

I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Using my N5 in germany and it's the best phone I've ever held in my hands Running CM12 (based on Lollipop) for now. Have also been using stock Lollipop for a few months. Both run extremely stable. To be honest: I never heard about your issues. I'm not that big of a fanboy. Never owned a Nexus device before, but I guess I'll never move away from Nexus
Just my honest opinion about the device
By the way: I've got a moto 360, too. And the connection is great - up to 10 meters at least and no random disconnects
I have zero issues with mine, but I'm on stock 4.4.4 so that may have something to do with it. I'm not a fan of Lollipop at all. Too many bugs, and I don't like the look of it.
After one year with my Nexus 5, running stock no root, never a problem. I'm a former owner of HTC flagships phones, never a problem with them.
Sent from my Nexus 5 using Tapatalk
Using Stock 5.0.1 rooted and with ElementalX kernel is good for me and have been using that setup for over a month now. No issues like what you're describing at all. :S
No problems here like that. Bug report issue is normally a poorly fitting case
Hmm... So it seems that the only people that are having these bugs live in my area... Do you think its possible we all got a bad batch of n5s at the rogers store here?
Edit: everyone experiencing these issues has bought their phones from rogers stores here in my city.
OFWGKTADGAF said:
Hmm... So it seems that the only people that are having these bugs live in my area... Do you think its possible we all got a bad batch of n5s at the rogers store here?
Edit: everyone experiencing these issues has bought their phones from rogers stores here in my city.
Click to expand...
Click to collapse
Yeah the devices purchased at the play store seem to be fine now. At first, me personally, I had tons of bugs at release. But those issues have been fixed with updates. Mainly concerning the signal and camera speed.
Thread cleaned.
If you think a report is breaking the rules or shouldn't be there for any other reason please report it and move on, antagonizing them adds nothing to the forum but makes our job harder. Thanks, Tijmen.
No issues here besides the occasional Mobile Radio active wakelock, which I did also see occasionally on KK. I did have some memory leak issues on 5.0.0 but either 5.0.1 fixed it or me removing some 3rd party background services did.
OFWGKTADGAF said:
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Click to expand...
Click to collapse
A reboot a day keeps the android bugs away
kevtrysmoddin said:
A reboot a day keeps the android bugs away
Click to expand...
Click to collapse
Rebooting is normally my go-to solution for problems but it doesn't seem to help these bugs. I installed CM Security and it constantly warns me about my CPU usage/RAM and battery Temperature. The culprit almost always seems to be the Facebook app (sometimes using 250+ mb of RAM just for background services) Could this be a bug with the Facebook app making my phone perform poorly... Does anyone know of any solid alternatives to the official Facebook app?
OFWGKTADGAF said:
Rebooting is normally my go-to solution for problems but it doesn't seem to help these bugs. I installed CM Security and it constantly warns me about my CPU usage/RAM and battery Temperature. The culprit almost always seems to be the Facebook app (sometimes using 250+ mb of RAM just for background services) Could this be a bug with the Facebook app making my phone perform poorly... Does anyone know of any solid alternatives to the official Facebook app?
Click to expand...
Click to collapse
Fast for Facebook I'd a good alternative
I've been without issues since the factory images were first released, running CM12 CAF builds without issues (besides cm12 bugs)
So call me crazy but I deleted the Facebook and Messenger apps about 6 hours ago and have had 0 problems since... I'm using the official Facebook "Lite" apk I found online and while it is very ugly, things are running much smoother, just hoping that maybe this will solve the bugs I've been experiencing and I'll be able to help my friends get there phones back to a usable state.
OFWGKTADGAF said:
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Click to expand...
Click to collapse
I know it's really late in the game now, but have you tried starting in safe mode to see if you have the same issues? It could be an app causing all the grief.

Categories

Resources