Database Info

Google Search keeping phone awake?

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.

Play Services - Always Awake, Fixed?

I had this problem, but have been reflashing my device in attempt to see if other ROMs have the same issues that I have been having in CM11S.
Yesterday, I went back to CM11S and have noticed that my device no longer stays awake constantly, and I don't seen to have any system apps draining large amounts of battery!
Did they fix this issue? Why would it just fix itself, I haven't changed anything in Privacy Guard or done anything to prevent it!?
My phone has been turned on for an hour, with 15 minutes screen on time, and it's still on 100% this is amazing!

It could be possible that Google fixed things on their end server side or that it was just a coincidence. I read about your post on Reddit too

zephiK said:
It could be possible that Google fixed things on their end server side or that it was just a coincidence. I read about your post on Reddit too
Click to expand...
Click to collapse
Haha, hey! Just downloaded the latest OTA, hoping that has some more bug fixes too!

mm-qcamera-daemon on 4.4.4

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 .

S7 black screen problem

Hi,
I just got this s7 for 3 days and i have this problem where the screen wont turn on but the phone still is active.
A hard boot will fix it but its only a temp fix because i had this problem 4 times now in 3 days.
I didn't root it nor did i install any weird apps outside the google play store, i disabled a couple of bloat ware apps like all microsoft apps and a few google apps like hangouts and gmail.
I did some research and found out that more people have this problem but all the fixes they got it to wipe the cache but the phone still has the problem after that so i would like to know if more people on xda have this problem and i would like to know what they did to their phone so i can see if we have anything in common to pin point the problem.

See if the setting for preventing the phone to turn on in your pocket is enabled. If so, try disabling it and see if that works. It may be a problem with the proximity sensor if it's a hardware issue.

Thanks for the reply and i have that setting indeed turned on! So ill switch if off right now and lets hope this will fix it!

Seems like turning off that feature didn't work

If you have an SD remove it or format it. I had this on kitkat because of too many files in internal memory

Think i found the problem because i think its fixed. While restoring my old settings like wifi etc from my ggole account caused this problem and now that i skipped this part in the setup the phone seems to be working now for 2 days perfectly but thanks for the reply and help.

Woot, I have fixed the problem!!!!! Its the App Power Saving Feature that causes this!!! I had some app set to "always" and when i used any of these app and then put the phone in standby then it would lock up every now and then. Now that i have turned off this setting the phone runs steady for a week!

RiTCHiE007 said:
Woot, I have fixed the problem!!!!! Its the App Power Saving Feature that causes this!!! I had some app set to "always" and when i used any of these app and then put the phone in standby then it would lock up every now and then. Now that i have turned off this setting the phone runs steady for a week!
Click to expand...
Click to collapse
Is your phone still working fine without blackscreens?
I've got the same issue (sometimes 4 times in an hour, sometimes it doesn't happen for 2 days..!!).
I've tried fixing by doing a factory reset and turning app power saving mode off.
Unfortunately this did not fix the problem. Yesterday I got an unresponsive blackscreen again :crying:
Any ideas what could fix the problem?
(Ignore my signature, I'm writing about the S7, not the S6)

TomTomGo! said:
Is your phone still working fine without blackscreens?
I've got the same issue (sometimes 4 times in an hour, sometimes it doesn't happen for 2 days..!!).
I've tried fixing by doing a factory reset and turning app power saving mode off.
Unfortunately this did not fix the problem. Yesterday I got an unresponsive blackscreen again :crying:
Any ideas what could fix the problem?
(Ignore my signature, I'm writing about the S7, not the S6)
Click to expand...
Click to collapse
Yea, mine is working like it should now for 3 weeks.

Nouget BETA users...list your issues here

I seen threads about thoughts of the update but I figured this thread to be more specific on the issues your experience on nought beta: bugs, freezes, force closes, lag, etc.

Posting issues or suggestions here will be useless to the Samsung team. To give feedback on the beta, just open the "Samsung Members" app and provide your feedback there. This way the team can actually address it.

Aside from standby battery drain, it's been pretty smooth.
Oh, the keypad sometimes can't keep up with my typing lol. That's about it.
Sent from my SM-G935T using Tapatalk

I am still getting the sound cutting out bug that was seen in Marshmallow.... ie; sound on YouTube videos, etc will play for a few seconds and then cut out to silence. Have tried all the "solutions" offered but it still happens.
*Very frustrating.

I have the battery drain problem too.
Sent from my SM-G935T using Tapatalk

I've reported this to Samsung member but in camera when you look at the last pic you took it shows last image of what you downloaded or received also. If you downloaded something after to took your last picture that is. Only pictures taken with the camera should be in here. Note 7 had this same issue.
Sent from my SM-N9200 using Tapatalk

That is strange. Battery life on mine has been the best i have ever gotten with this phone.

Probably poor battery other than that running great

M9x3mos said:
That is strange. Battery life on mine has been the best i have ever gotten with this phone.
Click to expand...
Click to collapse
Did you factory reset after the install?

Encrypted SD keeps popping up.
The "Clear All" button in recents is in a bad location (top right, better at bottom right)
Noticed that double tap AOD screen can wake the screen but only if you Dtap the notification or music playing. Suggested that we get full double tap anywhere to wake option.
Default e-mail does not have marked as read or delete options in notification bar.
Battery drain faster.
It may just be me but My Knox seems broken. I changed password and everything but on last attempt before lockdown but does not work.
All reported to Sammy except my Knox which may be a user error

I've had GREAT battery life, no drain.
Only issue is when I download an APK through Chrome and tap the notification to install then Package Disabler crashes. If I install it with Root Explorer it installs fine.

Android System battery hogging. Whopping 40%!

I average 8% an hour and have an average 5hr screen on time per charge cycle I think a lot of people some have some rogue apps

Battery life is much better! The main issue I'm having is no sound or vibration notification when I get a text. Sometimes I loose my data connection.

Looks like google voice doesn't work with the update. How do I report this ? I can't get any outgoing call to work through google voice
Sent from my SM-G935T using Tapatalk

Network mode 3g only.....
Then it should be 3g....
But it is connecting as 4g.....

I'm now getting a Wi-Fi connection problem. Just disconnects and reconnects. Kind of annoying
Sent from my SM-G935T using Tapatalk

Z51 said:
I'm now getting a Wi-Fi connection problem. Just disconnects and reconnects. Kind of annoying
Click to expand...
Click to collapse
Go into the settings with for it to turn off, then manually turn it on. Also I recommend leaving it on as well as Bluetooth. There is a known bug with both of those and leaving them both on fixes the battery drain issue you will have if you try to turn them off and they keep automatically turning on/off on their own.

ShrekOpher said:
Go into the settings with for it to turn off, then manually turn it on. Also I recommend leaving it on as well as Bluetooth. There is a known bug with both of those and leaving them both on fixes the battery drain issue you will have if you try to turn them off and they keep automatically turning on/off on their own.
Click to expand...
Click to collapse
my battery drain issue seems to be gone.
I will however turn on the bluetooth to see if it helps/.

Haven't seen this posted, hopefully i didn't miss the post though.
When playing a game using the "Game Launcher", I always played with "No Alerts during Game" selected. But since I upgraded to the Nougat Beta, Facebook Messenger somehow still sends me messages even though it should be blocked.
Anyone else with this issue?