mm-qcamera-daemon bug - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.

newmanx4 said:
This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.
Click to expand...
Click to collapse
I would suggest checking to make sure you have Smart Stay turned off; it's not a complete solution but it eliminates a way the camera can turn on without you having directly initiated it. Since Smart Stay uses the camera to check if you are still looking at the phone before turning the screen off, it can cause the daemon to start even without a person realizing it leading to the overheating and power drain.

The morning this happened I booted to recovery and wiped the cache partition then left the phone off until it cooled down. I have not had this happen again since.

This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?

newmanx4 said:
This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?
Click to expand...
Click to collapse
It isn't just a lollipop problem. I'm on 4.4.4 NI2 and it happened to me. I deleted apps and still couldn't get it fixed. I had to go back to an earlier backup to get rid of it. Never figured it out.

Strange I never experienced this on KK. A cache wipe always fixes it but it's very annoying.

Probable Solution!
I had same problem on towelrooted 4.4.2 NE9 stock ROM. You can try this. I removed skype, rebooted and re-installed it again. And I never had this battery drain issue because of this again.

Related

[Q] Nexus 7 screen turning itself on?

Hi all,
I'm experiencing an issue on my stock 4.1.1 Nexus 7. The screen seems to be turning itself on randomly. It normally turns off again but may toggle on/off quite a few times. Then it seems to go for a while whitout turning on. Bit odd.
Anyone else experienced this or have any thoughts on a reason for it?
Thanks
Same problem here, except with a Samsung Galaxy Nexus.
I just updated to 4.1.1 today and this is the first time I've seen it happen. Was previously on 4.02 without issues.
I have had the same problem. It seems to happen in the evening and I wondered whether the case was causing it to overheat. Seems to be OK when I take it out of the case. I phoned Google and was told that it hadn't happened before. I will contact them again if it doesn't get any better.
Sorry. Misread the post. Mine goes to sleep, not turns on
Sent from my Nexus 7 using xda app-developers app
gifton1 said:
Hi all,
I'm experiencing an issue on my stock 4.1.1 Nexus 7. The screen seems to be turning itself on randomly. It normally turns off again but may toggle on/off quite a few times. Then it seems to go for a while whitout turning on. Bit odd.
Anyone else experienced this or have any thoughts on a reason for it?
Thanks
Click to expand...
Click to collapse
Same here but mine is not exactly stock.
I have installed Apex Launcher plus numerous apps. I thought maybe it was the launcher doing it. But at this point... I have no idea. Just noticed it tonight coming on and then going off within 1 sec. but its random. it may do it once within an hour, or it may do it up to 5 times within a min... then go several minutes completely black screen. Crazy stuff. I thought maybe it was getting a message at first but then realized I had the WiFi off on my phone so it was dead to any incoming messages/wifi. I am really curious as to what is causing it and will be following this post as well as others quite frequent. Also.... the latest app that I have downloaded was OSMOS HD. it wasn't waking then sleeping before that app... just my 2 cents.
Hi Qbensis,
By stock, I just mean not rooted and not running any custom firmware. I had various apps and the like installed.
I have actually since rooted my N7 and installed a few custom ROMs and since then have not seen the issue at all. If you want to stay stock, I assume the issue will be fixed in the next update
I have seen this a few times. Middle of the night I look over and the screen is on then off. I check the power usage overnight and I see little blips of screen on when looking at the graph. Not sure whats causing it (I figure a app).
Same Problem over here, any solutions???
I'm on stock 4.1.2 and having the same problem, not rooted. Creeped me out in the middle of the night when it goes on and off.
N7 Random Turn On
Same here on 4.2.1. I carry in front pocket all the time with screen facing leg and feel heat when it happens. Has even done it when in Power Off mode and still does it. I thought that would prevent it for sure. Very irritating and drains battery. We Winter in 55+ community and drive around in golf carts. I am starting to wonder if WiFi spots trigger it. Will continue to track behavior and search other forums. Curious that there have not been any solid suggestions or solutions.
Happens to my rooted but stock 4.2.1. It happens randomly when I recharge using a battery pack (4AA) as opposed to charging using regular AC. It's annoying as heck! I don't know how to get this fixed!
I've been getting this on both SmoothROM and raspbeanjelly, and it's very irritating.
It has to be an app that is causing this. I initially thought perhaps it was GPS Status, because I caught it in the notification bar a few times when the screen turned on.
My device definitely isn't hot when it happens.
I'm suspecting the Email app, Maps, or Facebook.
EDIT - not any of them either. I'll test Beautiful Widgets next.
Okay guys, try this.
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
I'd been suffering from this for weeks, factory reset, reinstalled and changed out ROMs, installed apps one by one over the course of several days to keep an eye on what might be triggering it etc. Nothing worked for more than 2-3 days at most, and the issue always came back in one way or another.
It was causing me to have to turn the Nexus off when not in use because it would be draining battery (15-20% overnight compared to 2-3% when the issue wasn't present).
Then I stumbled upon that guide and using Gemini I disabled Maps from auto-running, turned off Latitude, and so far so good.
If it works for you too, be sure to hit thanks on Karpfenhai's post!
I was having this same problem on my Nexus 7 running stock 4.2.2 rooted with SuperSU. Finally tracked it down to having installed BetterBatteryStats and for some reason, I had not granted it perpetual root. It was causing the device to wake and turn the display on for random times (up to 13 hours, which killed the battery), not always showing the SU request dialogue. I granted perpetual SU privilege to BetterBatteryStats and problem went away.
Try taking out the battery and clean out the USB port with a toothpick. This worked for me. All the dust that accumulates in the post can cause the phone to think it's charging.

[Q] GCM_LIB Partial wakelocks

Just flashed the new MG1 on my SGH-I337M. I am noticing a consistent high partial wakelocks with GCM_LIB. Almost completely stops deep sleep. I just removed each of my google accounts and readded to see if that fixes the problem.
Anyone else experiencing this anomaly?
Cheers
R0N1N said:
Just flashed the new MG1 on my SGH-I337M. I am noticing a consistent high partial wakelocks with GCM_LIB. Almost completely stops deep sleep. I just removed each of my google accounts and readded to see if that fixes the problem.
Anyone else experiencing this anomaly?
Cheers
Click to expand...
Click to collapse
+1
Carried by a Raven
mrnovanova said:
+1
Carried by a Raven
Click to expand...
Click to collapse
+1! Something I did/installed/modified in the last week since I got the phone made the battery life plummet. Thought it was the "listen for wake-up command" part of S Voice... better, but nope. GCM_LIB had it awake 7 1/2 hours out of 8 I slept last night. This morning removed Samsung acct to see how that goes. Next the google acct...
I have the exact same problem as the OP, same phone/model too. Any clue what this "GCM_Lib (Android System)" under BetterBatteryStats is? It is preventing the phone from going into Deep Sleep. I notice this GCM_Lib is only active when there is an active connection (either WiFi or Mobile Data) turned on. With Flight Mode, there is no excessive battery drain. I am losing 15% battery over night (6-8 hours sleep). With Flight mode, I am only losing 1%.
I have removed all accounts off my device, and GCM_Lib is still wrecking my battery usage. Phone is unrooted. Any ideas?
I had the same problem on my SGH-M919V, upgrading firmware from MDJ to MG1. Same symptoms about suddenly poor battery life during sleep, and constant GCM_LIB wake locks. In the end, I never did figure out what was causing it, or a good way of fixing it, however I did end up solving the problem indirectly.
I flashed my phone back to the old MDJ firmware (NO data wipe, just firmware only), to check if I was getting the same problem previously, without knowing it. Sure enough, the problem went away, and didn't happen on the old MDJ firmware. So next, I re-applied the new MG1 firmware (again, NO data wipe, just firmware only), figuring that I would systematically disable/uninstall everything, one thing at a time, to try and figure out what app, account or setting was causing this. However, as soon as I re-flashed the new MDJ firmware, the GCM_LIB wake lock problem never re-appeared afterwards.
I don't know if this was something uniquely corrupt or misconfigured with my accounts or phone settings, or something unique to the SGH-M919V phone or firmware, but oddly enough, the firmware rollback & upgrade process described above did somehow fix the problem for me. I'm not sure if this process of firmware rollback without data wipe is supported or recommended without causing other issues along the way. I haven't other any other issues as a result of doing this. But still, make sure to have a full backup of your phone before you start, just in case something goes wrong during the process or some time afterwards.
Having the same issue here, don't know what causes it and how to fix it. I tried killing all the process with the System Panel app, it fixes the wakelock for a moment then it starts again

[Q] Random shut downs and battery drops. Battery problem?

I've been facing these problems for over a week now and it's extremely frustrating. I get these random shutdowns when I'm just opening an app or using my phone longer than a certain amount of time. The phone will have 100% charge in the morning then shuts down and if I try restarting the Google splash screen shows up and shuts down again. Then the battery level will be at 70% and the whole thing happens again till I have no charge.
So when 4.4 came out I thought I'd update and these problems will go away and they didn't. Now the same thing happens I've done a data wipe/factory reset, cleared cache but still nothing. I thought some apps were causing problems so I uninstalled everything but still no use. I'm currently on stock 4.4 using the stock kernel. I was also on stock 4.2.1 when these problems started. Does anyone have any idea what the problem could be?
Thanks.
Do you also have a bad network connection/sim locks? Then you should read this topic. It could be a faulty battery.
Faeshaas said:
Do you also have a bad network connection/sim locks? Then you should read this topic. It could be a faulty battery.
Click to expand...
Click to collapse
Yeah my sim is deactivated but I think that's a sim problem. I spoke to my network provider to reactivate it tomorrow. Thanks for that thread I must've missed it somehow. Hopefully its just a battery problem so I can just get a replacement.

Note 4 freezes while charging after lollipop

I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
ks-man said:
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
Click to expand...
Click to collapse
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
jbkmin said:
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
Click to expand...
Click to collapse
Did your issues first start after you upgraded to lollipop?
ks-man said:
Did your issues first start after you upgraded to lollipop?
Click to expand...
Click to collapse
Definitely after the upgrade.
While on KitKat, it never happened (1 month ownership). But after upgrading to lollipop, it has happened 4 times (6 nights since lollipop).
Have you figured anything out with your situation? Woke up this morning to my backup alarm and the Yellow Sprint screen on my phone.
I guess I'll have to try another factory reset and if it still happens try and get a replacement. It just doesn't seem widespread enough of an issue to be a software bug with 5.0.1.
Very frustrated. I did another factory reset but the issue still plagues my device. It still only occurs once or twice a week but when I hear my old clock radio alarm in the morning I know when I look over I'll see the yellow frozen Sprint Spark screen. I am completely out of ideas and guess I will need to have it replaced under warranty. I'm hoping Sprint won't give me a hard time as this will be very hard to demonstrate.
It definitely appears to be a software issue as it never happened before I upgraded to Lollipop but there must be more to it or others would be complaining.
If anybody has ideas please let me know. Thanks.
Response to Note 4 Freeezing while charging
I have found that after turning the quick charge feature off the problem is not happening. Hopefully this is fixed in 5.1
I'm having the same issue even after turning quick charge off..def a lollipop bug, never experienced this on kk.
I know its not the BEST option, but after taking the update to lollipop, sometimes left over kitkat files can make the system poop out. Sometimes a factory reset will take care of the leftovers. But of course, then you have to set your phone up again
If you've tried this or plan to to, let us know the results.
(When i first took the update, my heartrate monitor sensor was always on, so i did a factory reset and it fixed my problem).
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
same problem here
Ive tried turning off fast charging option on the powersaving mode
And also tried the option on developer mode, the "keep device awake while charging"
And even flashing dofferent firmwares from sammobile through ODIN and installed custom roms. These options doesnt resolve the issues on freezing while charging..
I think turnong off your device while charging is the only option..
Im using note4 N910C..
Clasimodo said:
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
Click to expand...
Click to collapse
Thanks a lot, Mate. I'm trying your workaround now. Will report later if it works on my phone. BTW, so, are you sure it is a just a system issue? Definitely, isn't a hardware problem? Did you fix it, after your post -a month ago-, installing, for example, lollipop 5.1.1 or Cyanogenmod 12.1? I'm on 5.0.1, SimpleRom V4. Of course, mi device, N910C, is rooted.
Thanks again.
With lollipop 5.1.1 the problem is solved for me, even without this workaround.
Sent from my SM-N910F using XDA Forums PRO
I'm having similar issues as you guys. I found out that my phone will only perform normally when I charge it with my laptop USB port which I think is around 0.5amps. Anything above that, even a 1amp charger would cause the phone to freeze, reboot and turn off and not turn back on. The phone has been in repair 4 times and the problem is still there. Now every night I'm forced to charge my phone with my laptop which takes an age instead of the fast charger that came out of the box.
Currently my phone is still freezing and rebooting when I'm out and about and the only way I can get it to perform normally is when I plug it into my laptop. This normal functioning would only last whilst the phone is plugged in.

T-mobile S7Edge stock, after Sept. 1st Security patch update, battery drain

I do not know whether it is coincidence, but I updated couple of days ago and all of sudden, starting this morning, the Android system is draining battery at alarming rate. It does appear that this happens only when I am on cellular network and not on wifi.
I have been off the charger about 2 hours and my battery is down to about 50% already.
The phone is running very hot. (I took it out of the case) It does not appear that turning off cellular data affects this at all.
Rebooted the phone couple of times to no avail, at this point, I am considering factory reset of the phone, but would like to get some opinions on what may be the cause.
I saw the thread on the "android system battery drain", but this does not appear to be related to what majority of people are reporting as this slows down the phone significantly enough that the phone is almost unusable at this point.
Cleared cache but don't think is helping. That said, when I was trying to get to the recovery, the system said "Installing update" and then "No command", before getting me to the cache, I am wondering whether the "update" did not clean up itself...
Thanks.
EDIT: Looks like the system cache clearing did help after all.... System appear to be working normally now. Will have to see..
Ok, well, back to the drawing board. The phone behaved ok all day long. Came home, I did 2 things, turn on wifi, and then turned on bluetooth to test out a headphone and then shut off the bluetooth. High battery drain again. Phone got hot and everything is VERY sluggish.
Shut down, cleared the cache again. Will see what happened.
Is there a way to go BACK to previous stock ROM WITHOUT factory reset?
Found out the issue, it was Oculus update which caused the issue. Looks like the bug caused the "Oculus Room" to install it self over and over again. I manually ran the Oculus home app, and it prompted me to update, which I did and it appear to have fixed the issue.
Flash your decice with version from sammobile.com
I have this exact same problem, posted about it yesterday but had no help.
I don't have Oculus on my phone though. But phone behaves for a most of the day, then does as the OP describes, still cant see why, but its only since the update.
Steve

Categories

Resources