Related
I've never had Facebook eat this much of my battery before, but whenever its background services (MediaUpload service I think is the name), my battery drains at least 1% per minute.
I've tried force closing every time I quit the app, I've tried getting rid of its background data completely. I've tried disabling notifications. I don't sync at all. But the damn app still pops up every now and then and eats my battery while it does NOTHING.
This is an issue that I've found on the Nexus S. I've had a Galaxy S and Optimus One before and I've never encountered such an issue. I'm on Air Kernel 4.2 and AOKP milestone 5, but this problem also occurred on other ROMs and kernels.
Does anyone else have a similar issue and is there a way to fix it (outside of deleting Facebook or freezing it)?
chw2006 said:
I've never had Facebook eat this much of my battery before, but whenever its background services (MediaUpload service I think is the name), my battery drains at least 1% per minute.
I've tried force closing every time I quit the app, I've tried getting rid of its background data completely. I've tried disabling notifications. I don't sync at all. But the damn app still pops up every now and then and eats my battery while it does NOTHING.
This is an issue that I've found on the Nexus S. I've had a Galaxy S and Optimus One before and I've never encountered such an issue. I'm on Air Kernel 4.2 and AOKP milestone 5, but this problem also occurred on other ROMs and kernels.
Does anyone else have a similar issue and is there a way to fix it (outside of deleting Facebook or freezing it)?
Click to expand...
Click to collapse
yea, it started after a recent update. i had to uninstall it from my nexus s and galaxy nexus because it was annoying the heck out of me. i wasnt using it but it was still eating 8-12% of my battery.
Uninstall it and wait for the next update maybe then it doesnt use so much battery anymore.
You might want to try Friend caster or Fast for Facebook
Sent from my HTC PH39100 using XDA
The Facebook app for android is worthless. Much better to just use the browser instead.
I wonder why they still haven't managed to create a decent app.
I have seen this reported often recently and not sure of the cause. My battery life has not been effected at all by the newer versions.
Maybe its something to do with roms that include the hack to sync fb. The new apps changed something related to that.
This usage is from today. Was outside with screen on full brightness ( extremely sunny and crisp today in NY) and used GPS with fb. When I dont use the app doesnt use any battery. No waking the device etc aokp m5 with trinity
My n5 seems to have the GoogleSearch keep awake for 20hours+. is it normal? being in EST, I was not using device for atleast 10 hours from 10pm yesterday until now.
Attached screenshot. Any one else facing same issue?
real painful bug. I've gotten it once on my n5, twice on my n7 v2, once on my n7 v1 and twice on my n4. ONly my n5 and n7 v2 are on kit kat. the other 2 are on 4.3. Just no rhyme or reason thus far as to why it happens but BBS says it's cacheupdate service or entries refresh wake lock. Only thing to stop it is to restart the device. At first i thought it was a kitkat thing but it's rearing it's ugly head on my n4 and n7 v1.
ive been having the same issue. a temporary fix on my n5 was to force stop google search, but it would inevitably return 3-4 hours later. putting it in airplane mode solved the issue...but obviously i couldn't always keep my n5 in airplane mode.
i literally just reset my phone to see if that helps solve the wake issue with google search. i even tried contacting google nexus support, but they haven't been much help at this time. ill let you know if factory resetting my device has helped at all
So, I am not alone with this problem. Its occurred a couple of days ago, went away, and came back.
monilchheda said:
So, I am not alone with this problem. Its occurred a couple of days ago, went away, and came back.
Click to expand...
Click to collapse
No u r not alone. I have it every now and then. I installed Cpu spy so I can see if my phone is sleeping or not. If I have the wake lock it stays on 300mhz when screen is off when it should be sleeping.
Sent from my SPH-L900 using xda premium
Stock krt16s on nexus 4. The problem started with the official factory image (didn't had it with slimkat) and since my device never slept again.... Heeelp
Envoyé de mon Nexus 4 en utilisant Tapatalk
The only consistent way i've seen to clear the entries refresh wakelock is to uninstall the updates from within the Google Search App.
This completely clears the issue rather than a restart which works temporarily so Google has messed up with the last Google Search update (the one that brings extra funcionality to Google Now.
I had the same problem, turned off location reporting in Google Settings and it's gone..
V.Dragos said:
I had the same problem, turned off location reporting in Google Settings and it's gone..
Click to expand...
Click to collapse
Turning off location reporting never cleared it for me i still needed to uninstall the latest search update.
I had the same issue, so disabling Google now (opening Google now, settings, toggle it off) has stopped this wakelock for me!
Sucks a bit to turn it off, but I'd rather not have the wakelock than have good now info, I'll just wait for an update/fix.
YoHoJo said:
I had the same issue, so disabling Google now (opening Google now, settings, toggle it off) has stopped this wakelock for me!
Sucks a bit to turn it off, but I'd rather not have the wakelock than have good now info, I'll just wait for an update/fix.
Click to expand...
Click to collapse
this just happened to me, out of no where. kept my device awake the whole time i was in the shower. i will be testing by disabling google now. i agree, it just isn't worth it to deal with these bugs, i can get weather notifications elsewhere
Just got my N5 yesterday and this is going on, Google search using 45% of my battery by the end of the day. Will try turning it off :-/
Sent from my Nexus 5 using Tapatalk
same here
I too have the same problem and only restarting the phone fixes it and it just happened to me again an hour back.
I have noticed that sometimes when I remove the charger from the socket after the full charge, the problem comes only after that time....so after charging the phone almost every time I check my battery stats for few seconds and if it persist then I restart the phone and yea it get solved but a temporary solution and its really annoying .......hope google fixes it soon
http://forum.xda-developers.com/showthread.php?p=49389752#post49389752
Google search seems to be keeping my phone awake and destroying my battery.
Using the GEL, my phone was awake any time my launcher was active. Switching to Nova, it seems this issue is mitigated, however if I ever go to use the search app (or Now), it initiates the battery rape-fest.
Just wondering if anyone else has had this issue. I know lots of people here have their data and/or wifi enabled/connected 24/7, so it may not effect them.
I'm linking photos stored in my DB account showing some of these battery drains.
https://www.dropbox.com/s/jhw1f4prbneyg45/2013-12-26 06.19.30.png
https://www.dropbox.com/s/gfhr2vf1z5kf4tw/2013-12-26 06.19.24.png
https://www.dropbox.com/s/0f506skwf26q3se/2013-11-27 01.43.17.png
https://www.dropbox.com/s/ky7yjo2628p1ngl/2013-11-27 01.43.22.png
https://www.dropbox.com/s/dr0e2jjswt52mce/2013-11-27 01.43.26.png
The periods of no signal is when I'm at work - there's no service out here so I might as well have it on airplane mode.
Unfortunately, I really like the GEL, and was hoping that there'd be an easy fix to this. Switching run times doesn't help. I'm currently on ART.
Any advice is helpful.
Do you have hot word detection on? If so then it off that could be triggering it it solved the issue I had with it
Sent from my Nexus 5 using Tapatalk
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
bblzd said:
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
Click to expand...
Click to collapse
Hmm I also had this problem and also was tinkering with location settings the other night... interesting. If it starts acting up I'll force stop it.
I wanted to disable or uninstall Google Now and Google search and it wiped my homescreen
kevtrysmoddin said:
Do you have hot word detection on? If so then it off that could be triggering it it solved the issue I had with it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This was the first thing i thought of. I turned it off, no change.
bblzd said:
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
Click to expand...
Click to collapse
My issue is that I shouldn't have to force stop it. Why is it running wild? This is a Google application, shouldn't this be near flawless?
Sent from my Nexus 5 using XDA Premium 4 mobile app
new ion? said:
This was the first thing i thought of. I turned it off, no change.
My issue is that I shouldn't have to force stop it. Why is it running wild? This is a Google application, shouldn't this be near flawless?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just know it's a pretty easy fix (force stop or reboot) so not a huge deal IMO.
If I had to guess Search is trying to look up some location information which it can't currently access. Instead of stopping it just keeps trying forever. I've yet to see the issue since disabling Locations completely and experienced the issue only with partial location services enabled.
My advice would be to leave Location services completely on or completely off. It may effect those with locations on, but either reporting or history (or both) off.
Sent from my Nexus 5 using Tapatalk
Oooo, apparently I had history on and reporting off. I'll try turning both off and letting search run for a bit tomorrow, I'll see what happens. If it comes down to it, I'll submit a bug report.
Sent from my Nexus 5 using Tapatalk
shouldn't be an issue
I have been having the same identical issue as you guys. I have found shockingly little in my searches, which I've been doing periodically for the last few months, really, since I've had the phone(12/5/13).
Now for the particulars :
I have a nexus 5. I'm running the stock ROM and kernel via OTA (4.4.2).
I am rooted (via wugfresh's toolkit) and I have the xposed framework installed along with only a couple of modules, (gravitybox, bootmanager).
Now all this means I am essentially bone stock which means since its a nexus 5 I have the GEL launcher by default and I love it and the setup in general, (my favorite setup so far of all my phones, nexi and other).
Now I've been fortunate and have never really needed to track down and eliminate software causing battery decimating "wakelocks" on any of my devices. And apparently the newer versions of KitKat make finding and solving wake lock issues difficult using apps developed for the purpose.
If I were to upload screenshots of my battery screen when the issue is presenting itself, Google search is up in the top five at least. And when I click it for details it shows similar readouts to what's been posted by OP in his screenshots.
I can't be the only one having serious issues with wakelocks cause by Google search on their nexus 5 and I'm baffled by the lack of discussion I've been able to find regarding this issue, (my google-fu is in my opinion at least up to par)
Whenever I notice my battery draining faster than normal without fail I go into my battery settings and discover that my phone is awake constantly regardless of screen-on time and the culprit is always exclusively Google search. Now its far from difficult to force stop the app and go about my business. And it usually doesn't cause me any issues for a time once that's been done. However, the unpredictability of the Google search app causing a crippling wake lock is for me the main issue as it means I cannot leave my phone unattended for more than a few hours without the possibility of coming back to my phone with my battery that's been molested. The battery in my opinion is more than acceptable and I quite like it. However the uncertainty is horrible.
I've read through the posts In this thread (regrettably few) and I have not been able to make a correlation between location services being on in any of the three modes and Google search wakelocking my ****. Also, I use Google Now all the time every day, and hotword detection is always on to call it up from the home screen by voice which i use even more so. So in my opinion while it is possible I'm sure that somewhere in all that there is a trigger for the issue, it is by no means predictable and in my experience never reproducible.
Now, for the "Google Search" app to cause a wake lock that will persist until the apps been manually force stopped, completely unpredictably represents a HUGE BUG that un-does all of the amazing work with our chipset and kernel and os that gives us such great battery life without having to sacrifice clock speed via custom min/max settings or governor controls.
I just don't get it. This is the first time I've ever encountered such a glaring problem/bug with so little complaint or even discussion.
I think we all should submit official bug- reports to Google about this issue and start being vocal in all of the android communities. I very very rarely comment or post as I am always able to make do by searching and reading diligently. But this blows my mind, the lack of posts and discussion would normally suggest this is a very limited problem affecting a very small minority. But I don't buy that. My set up is too stock, too close to the largest percentage of nexus 5 users to be so. Maybe people are just force stopping the app and forgetting about it, chalking it up to something they've personally done to their phone because "how could Google search be doing this to everyone else". I don't know. But this has to be more widespread of an issue than search results are indicating.
In summation: what OP said lol. But I don't think it has anything to do with what's been suggested by other posters on this thread. Their suggestions may work, and they may mitigate the issue. But if that is the case. Than this a very huge bug that threatens to undo all of the amazing work that's been done with aosp regarding battery efficiency and optimization.
- FerrousState
PS. Let's get some real discussion going in this community and all the others. Smarter people than us should be working on this - Top men guys, TOP MEN!
Hey guys I have this problem as well. I can't view the pics in OP but Google search is running at about 14%
Sent from my Nexus 5 using xda app-developers app
Brockg said:
Hey guys I have this problem as well. I can't view the pics in OP but Google search is running at about 14%
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Tap Google search in your battery and check how long it's kept your phone awake. Then back, and check again. If the seconds just got higher it's currently eating your battery and needs to be force stopped.
Any suggestions are just to mitigate the problem for now of course. Hopefully it's being worked on.
I've yet to see the issue again but I have Locations and Hot Word off, Google Now on. I strongly believe using either "device only" or turning off the 2 settings within Locations can act as a temporary fix however.
Hello everybody,
I have this problem that's more than annoying and that I really couldn't find a solution to. I've tried finding someone with the same issues but couldn't. The problem is, when someone is calling me, my phone rings, but the screen doesn't turn on, only the capacitive buttons do. I didn't have this problem before, but after installing some stuff it appeared. I don't really know what caused it and how to fix it. I have XPERIA Z FIRE SERIES 5 rom for Tipo, Nova launcher and running Crystal 2 theme. Could any of those possibly cause the problem? I can't see the number thats calling me and it's hard to answer the call since I can't see the buttons either. Aside of that, I have one other problem. My phone ram is allways on ~400 without any app turned on. I have a few apps for apps killing and clearing ram and I do that often but still it doesn't help since after cleaning it's back to like 95% in a matter of an hour. And even when I kill all the active processes and apps, my ram is still on like 65% usage. I don't know whats using it up, I can't run anything on the phone, I've deleted all the games since they lagged like hell, even the most simple ones that should run smoothly. Hell it laggs even when I have to unlock it, enter menu, call someone, do anything...
Well, thanks in advance for any advice that you have to offer.
shonemoc said:
Hello everybody,
I have this problem that's more than annoying and that I really couldn't find a solution to. I've tried finding someone with the same issues but couldn't. The problem is, when someone is calling me, my phone rings, but the screen doesn't turn on, only the capacitive buttons do. I didn't have this problem before, but after installing some stuff it appeared. I don't really know what caused it and how to fix it. I have XPERIA Z FIRE SERIES 5 rom for Tipo, Nova launcher and running Crystal 2 theme. Could any of those possibly cause the problem? I can't see the number thats calling me and it's hard to answer the call since I can't see the buttons either. Aside of that, I have one other problem. My phone ram is allways on ~400 without any app turned on. I have a few apps for apps killing and clearing ram and I do that often but still it doesn't help since after cleaning it's back to like 95% in a matter of an hour. And even when I kill all the active processes and apps, my ram is still on like 65% usage. I don't know whats using it up, I can't run anything on the phone, I've deleted all the games since they lagged like hell, even the most simple ones that should run smoothly. Hell it laggs even when I have to unlock it, enter menu, call someone, do anything...
Well, thanks in advance for any advice that you have to offer.
Click to expand...
Click to collapse
It seems to me that your rom isn't bugfree... Flash a stock fimrware, and everythig should be pico bello . The RAM usage is strange, but the call issue isn't very rare, many people report this. Flashing a stock firmware will most likely fix this!
Have a nice day!
I had this on 4.4.2 but 4.4.3 fixed it. I'm on 4.4.4 now and have been since it came out, but all of a sudden last week, mm-qcamera-daemon came back and I'm not alone.
With L just around the corner, I doubt there will be any fix for this from Google, so what's the best way of finding out which app is keeping this service alive?
P.S. I have neither Skype, Instagram, nor Snapchat installed - and never have done - so it's not them.
Did you have a camera app running in the background? ie. minimized it without swiping it away.
Nah, nothing like that. I'll even get it when I boot my phone, open no apps at all, and charge to 100% before unplugging from the charger - this action seems to be the cause of the daemon, like some of the other users on that issue report are saying. Never mind, I guess I'll just wait it out until L.
I have never had this problem on my nexus 5 until today (I bought the Nexus 5 on day one)!
This process is draining all my battery!!
The only app I installed in the past week is "Google Opinion Rewards" which was installed 6 hours ago.
Please help if you find a solution
UPDATE 1: I just noticed, via CPU-Z, that all 4 cores are continuously active at high frequency and the phone is overheating
UPDATE 2: Problem is still there even after removing "Google Opinion Rewards"
Just reflash the stock firmware and see if it continues.
Best thing to do with any issue that a solution can't be found for easily. ?
skttrbrain said:
Nah, nothing like that. I'll even get it when I boot my phone, open no apps at all, and charge to 100% before unplugging from the charger - this action seems to be the cause of the daemon, like some of the other users on that issue report are saying. Never mind, I guess I'll just wait it out until L.
Click to expand...
Click to collapse
the camera daemon is supposed to appear. its not supposed to stay around, draining battery. especially at 100%, you will see it, as the phone uses it a little bit, and you havent used the phone at all. it will show up. the question is, if you dont use the camera at all, and it appears in your battery stats, after a full cycle of use, how much battery does it take? chances are that by the end of your battery cycle, it wont even be in your battery stats.
simms22 said:
the camera daemon is supposed to appear. its not supposed to stay around, draining battery. especially at 100%, you will see it, as the phone uses it a little bit, and you havent used the phone at all. it will show up. the question is, if you dont use the camera at all, and it appears in your battery stats, after a full cycle of use, how much battery does it take? chances are that by the end of your battery cycle, it wont even be in your battery stats.
Click to expand...
Click to collapse
I actually fixed it now by flashing the system image and restoring all my apps via Titanium Backup, but I swear I'd never even open Camera for it to occur, and I don't have any third party camera apps. It would constantly be active without opening any camera apps at all.
edit- also Google have restated that they're looking into this bug and have marked it urgent, so anyone else getting it - don't panic too much, it's most likely not a problem you've caused.
I suspect the Hangouts/Hangouts dialer. I updated the app few days ago (no other installs), today was the first time that I got this issue (got my Nexus in February). Also first time since updating I used the camera, followed by battery drain/ daemon/ "failed to connect camera" etc.
I think its because of android wear
With android wear u can access the camera, hence u will be seeing the camera drain for sure. i unpaired my watch for few days and i didnt have this problem till now
I had this problema today morning, my android version is 4.4.4, In my case I used yesterday the camera to attach a photo inside the facebook messenger, maybe this buggy app make this mess in my case.
I reboot and waiting for the results
Same here
Everything was ok from 4.4.2 till 4.4.4. But suddenly week ago discovered mm-qcamera-daemon issue, tried many things without success. I am using phone in safe mode (facepalm).
Waiting official Android L or fix from google.
I got the same issue now!
Started today, what the hell?
Some apps will keep the camera wakelocks going. Freeze anything that can possibly use the camera and see what happens.
Or just clean flash stock, and see if its OK. If so... Install a handful of apps per day.... Then if it goes nuts you know it's an app you've just installed.
https://code.google.com/p/android/issues/detail?id=70755#c171
I think i had this fixed. Ihave a rooted nexus 5 stock rom. Installed greenify, pirchased the donate version and had the camera app greenified. No more mm-qcamera-daemon showing up on my battery stats. No more "cannot connect to camera" issues. (So far it's been 2days without it.
camera block app
i see this issue occurs when i use skype or any camera related app in my grand 2 4.4.2 / only way i keep the issue at bay is use camera block app.. which i keep it turned on when i am not really using the camera.
this seem to keep this daemon under control and not drain my battery .