Database Info

[Q] restarting happening with high CPU usage on ICS stock

I am on stock rooted ICS, and nearly every time I update apps, if more than one is updating, then it will restart itself. I'm not sure if Lookout antivirus could be causing this with scanning after every install, but I wanted to check.
Also, I want to know about any possible answers as to updating when it stops about halfway on updates, and it waits a while to continue the download?

toastthemost said:
I am on stock rooted ICS, and nearly every time I update apps, if more than one is updating, then it will restart itself. I'm not sure if Lookout antivirus could be causing this with scanning after every install, but I wanted to check.
Also, I want to know about any possible answers as to updating when it stops about halfway on updates, and it waits a while to continue the download?
Click to expand...
Click to collapse
Lookout doesn't get along with ICS. It used to cause freezing every time it scanned an app. Its really only useful if you are downloading apps not from the play store.
And updates shouldn't go to 100% it only downloads the specific pieces needed to update.
Sent from my MB865 using xda premium

I can say this, the play store apps update has definitely got some issue post ICS OTA i.e if the screen times out the app update hangs midway, etc etc. only resolution is wait up keeping the screen active until all apps have updated fully. I am using Avast while on GB and even now as well as Apps2SD (SamLu). This is surely a bug.

RAD7 said:
I can say this, the play store apps update has definitely got some issue post ICS OTA i.e if the screen times out the app update hangs midway, etc etc. only resolution is wait up keeping the screen active until all apps have updated fully. I am using Avast while on GB and even now as well as Apps2SD (SamLu). This is surely a bug.
Click to expand...
Click to collapse
I haven't heard of anybody having this problem. I know for a fact mine updates with the screen locked because I set everything to update automatically and I always wake up to at least one notification that something updated successfully.
Sent from my MB865 using xda premium

Scottyfer said:
I haven't heard of anybody having this problem. I know for a fact mine updates with the screen locked because I set everything to update automatically and I always wake up to at least one notification that something updated successfully.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
See this http://forum.xda-developers.com/showthread.php?p=32568467#poststop
& as I quoted there I will try and see what occurs if I set apps to auto update. Will not be a permanent thing though cause I don't want update wakelocks sucking the battery & it'll just be to figure out if it'd help.
---------- Post added at 12:28 AM ---------- Previous post was at 12:24 AM ----------
OP - Your subject "high CPU usage" does not chime with your actual question about updates of apps. & as I mentioned there is already a thread which I posted in here on the same. FYI

RAD7 said:
See this http://forum.xda-developers.com/showthread.php?p=32568467#poststop
& as I quoted there I will try and see what occurs if I set apps to auto update. Will not be a permanent thing though cause I don't want update wakelocks sucking the battery & it'll just be to figure out if it'd help.
---------- Post added at 12:28 AM ---------- Previous post was at 12:24 AM ----------
OP - Your subject "high CPU usage" does not chime with your actual question about updates of apps. & as I mentioned there is already a thread which I posted in here on the same. FYI
Click to expand...
Click to collapse
I hadn't seen that thread, I'm sorry. You could try disabling auto screen off and see if that changes anything. I've got my battery tweaked out so the wakelocks don't really affect me as much as they should.
My only other suggestion would be to clear play store data and uninstall the updates for it. I generally do that to force it to update, and it may just be an outdated version causing issues. Current version is 3.9.16
Sent from my MB865 using xda premium

Okay, so I am definitely thinking that the restarting is due to high CPU usage. It happened after I uninstalled Lookout and installed Avast which also scanned after each install. Now, I tried running a few other processes after I disabled Avast's scan after every install. I can produce the same result: a reboot because of what I suspect to be high CPU usage. It did not do this before the OTA update, so I think it might be somewhat due to the OTA overclocking to 1200Mhz. I might try to underclock it to see if that helps.
I will try messing with the deep sleep stuff too, but it even happens when the screen stays on, so I am not sure if this is the cause.

Scottyfer said:
I hadn't seen that thread, I'm sorry. You could try disabling auto screen off and see if that changes anything. I've got my battery tweaked out so the wakelocks don't really affect me as much as they should.
My only other suggestion would be to clear play store data and uninstall the updates for it. I generally do that to force it to update, and it may just be an outdated version causing issues. Current version is 3.9.16
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
No issues and thanks for your helpful inputs, how do I go about clearing the play store data? All I see is "clear search history". The Play store ver what I have is 3.9.16. There are also two settings which are greyed out i.e "Unlock settings" & "use pin for purchases". Don't know if other users have this same as me?

RAD7 said:
No issues and thanks for your helpful inputs, how do I go about clearing the play store data? All I see is "clear search history". The Play store ver what I have is 3.9.16. There are also two settings which are greyed out i.e "Unlock settings" & "use pin for purchases". Don't know if other users have this same as me?
Click to expand...
Click to collapse
For clearing Play Store data (or any other application data for that matter) just go to System Settings>manage applications>find Google Play Store>select "clear data option"...

Google Maps

Is there any way to reduce how much Google maps spends awake in the background? It eats away so much battery... Should I just freeze it with titanium backup?
Sent from my SCH-I535

In the maps settings, uncheck "report from this device" that'll stop it from constantly pinging for a location. Also in Google Now turn off any cards you don't normally use (some of them constantly ping a location as well)

Neverendingxsin said:
In the maps settings, uncheck "report from this device" that'll stop it from constantly pinging for a location. Also in Google Now turn off any cards you don't normally use (some of them constantly ping a location as well)
Click to expand...
Click to collapse
Thanks. It just seemed weird today of all days as I hadn't even opened the app since I last booted which was early this morning.
Sent from my SCH-I535 using Tapatalk 2

You're welcome i never open the maps app unless absolutely necessary, always afraid it'll start to eat away at battery life.

Neverendingxsin said:
You're welcome i never open the maps app unless absolutely necessary, always afraid it'll start to eat away at battery life.
Click to expand...
Click to collapse
You'd think Google would have a fix for that by now so we all aren't scared of something happening when we open the app... Lol
Sent from my Verizon GS3 on Bean's JB ROM

Help me fix my wake locks, Please!

Installed Beans 8 recently and Ive been having my phone be awake at precise intervals overnight. it seems like every 15 minutes. Ive checked my settings and cant find anything that I wouldve done to cause it. Ive neverhad this issue. btw, im running KT747 kernel
aynway, I bought and installed betterbattrystats after searching for help. Im at a loss at the moment. The readings are a little too advanced for me. I dont know the difference between a good wake up and a bad one. Are there common causes for this?
Is there a better way to narrow this down? I deleted the apps I dont use hoping that one was rogue and doing this, but I dont think thats it. The only thing I could think of off the top of my head was that I recently upgraded to nova prime and i am using the unread counter that Nova uses. could that be scanning for notifications constantly?
Any help appreciated. I love this ROM. its by far my favorite taht ive flashed so far, i dont want to flash somethign else. Im sure its something I did.
thanks in advance. If its neccesary ill post up my Betterbatterystats tomorrow after I run through a charge cycle during the day tomorrow.

bumping this up for screen shots. I put this down before i went to bed, and checked when i woke up. I set an alarm before going to sleep, thats all i did. i think my phone being awake has to do with the maps app. how can i control this? ive never had this happen before?
GPS has been off and googles location service is all that I keep on. it looks like its updating at regular intervals. is this google now? Its not a huge drain, but its enough that ive noticed it. any help appreciated.

in the meantime, i cleared data/cache, uninstalled and reinstalled maps.

That looks pretty normal. You may want to post the better battery stats info, it may help. Also for location waking your phone up, open maps, go to settings, location settings and disable report location from this device.
Sent from my VS920 4G using xda app-developers app

I am too lazy to type everything. Download gscript from the play store and create a script that mirrors the picture. Save and run it. Once it completes there will be a txt file on /sdcard so open it up and sift through the entries till you find a line that says Alarm Stats. After that line just see if any entries have a large number beside alarms
Sent from my SCH-I535 using xda app-developers app

Media Server wakelock caused by Snapchat

I've seen some people having trouble with the "Mediaserver" sucking up their battery on the Moto g. I found out what is is, but I don't know how to fix it.
It's caused by a wakelock called "qcamera2factory" and it always starts when I use Snapchat, an app most of you guys should know and probably use. So the "qcamera2factory" starts every time I open Snapchat for the first time after forcing to "kill" Media Server with an app called "Mediaserver killer" and if I don't kill it that way, it just keeps on adding time to the "keep wake" on the battery screen.
It sucks that I can't use Snapchat and I really want a fix for it. Can someone on here help me with this?
Thanks in advance, I would really apreciate it!

fyi: I don't have snapchat but the last 2 days I had the same wakelock from qcamera2factory, solved by clearing data on media storage, force stopping camera and gallery and a reboot, since I don't have root atm.
Sent from my XT1032 using xda app-developers app

miklosbard said:
fyi: I don't have snapchat but the last 2 days I had the same wakelock from qcamera2factory, solved by clearing data on media storage, force stopping camera and gallery and a reboot, since I don't have root atm.
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by clearing data and forece stopping gallery? Thanks for your reply

settings/applications/all, search for the names I mentioned, and click on them and you will see the 'clear data' and 'force close' buttons
Sent from my XT1032 using xda app-developers app

It's not caused by Snapchat, it just appears sometimes when you use the camera. I had this wakelock twice and in both cases I was just making photos, I don't have Snapchat installed.

Happened to me with Focal (beta) camera, and skype. Seems to be something buggy with camera apps

Had this wakelock as well. Turned out to be Skype. Uninstalled and everything Is good.
Who'da thunk a Microsoft app would degrade the performance of an Android phone?

grockstar said:
Had this wakelock as well. Turned out to be Skype. Uninstalled and everything Is good.
Who'da thunk a Microsoft app would degrade the performance of an Android phone?
Click to expand...
Click to collapse
a motorola agent told be that skype is working bad now and causes this bug, but he said that in 4.4 it will be solved

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.