I noticed this very weird behavior before. when im done using maps and turns off location setting the maps continues to use gps. Even when it's off. These caused big drain from maps. I'll post successive screenshots of the battery info. I also post pic showing location is off. Anyone experiencing this and found any solution?
Sent from my D6633 using XDA Free mobile app
Info
infinitylook said:
I noticed this very weird behavior before. when im done using maps and turns off location setting the maps continues to use gps. Even when it's off. These caused big drain from maps. I'll post successive screenshots of the battery info. I also post pic showing location is off. Anyone experiencing this and found any solution?
Sent from my D6633 using XDA Free mobile app
Click to expand...
Click to collapse
If you didn't any install any 3rd party app that control GPS so force stop map and reboot
and check battery usage after few hours if problem remains try to repair firmware by PC companion
:good:
Yeah i did force stop but didn't reboot though. Do you think this has to do with the Google maps itself? I hope there's some nice alternative to this app
Sent from my D6633 using XDA Free mobile app
Related
My google maps keeps saying checking navigation availability. Anyone know how to fix it.
Sent from my SAMSUNG-SGH-I897 using XDA App
+1 same issue
anyone? ................
my google maps works, this only happens on my google navigation GPS thing
did you clear app data>uninstall>reinstall?
i dont care for google nav any way, it seem problematic on the captivate. a few times it worked perfectly and other times it causes the gps to crash on some roms. on others the positioning becomes eratic one trip not the next. the most stable my gps has been on a nav program is with navdroyd.
I was noticing the same problem when Google maps did a recent update. Try going into the market place and uninstall the update. If that doesn't work try upgrading to a 2.2.1 rom like Preception or Darky's. When I went from a 2.2 to a 2.2.1 it seemed to fix the problem.
I was having this problem with navigation. It stopped after I went into places and did a navigate from there. After that I could go into navigation without the issue.
psloan said:
I was having this problem with navigation. It stopped after I went into places and did a navigate from there. After that I could go into navigation without the issue.
Click to expand...
Click to collapse
I also did something similar to this. Instead of Places, i picked a random location from within Google Maps (long press) and then chose to navigate to it. Worked fine after that.
Sent from my SAMSUNG-SGH-I897 using XDA App
I just did a full wipe and flashed CleanRom 2.1, and since then I've been having partial wakelock problems.
I keep getting LocationManagerService partial wakelocks that stay there forever (>95% of the time). The phone never goes into "deep sleep." I can't figure out which app is calling the service, and it comes up under "Android System" in BetterBatteryStats.
In the Alarms tab on BBS, com.google.andoird.apps.maps has 95 wakeups in an hour, almost all of them ALARM_WAKEUP_SENSOR_COLLECTION_POLICY. I haven't used Maps for anything.
I can make this go away if I disable "Google Location Services" and reboot, but that seems to increase how long it takes to get a location lock (I'm always on Wi-Fi).
Anyone have any ideas / experience with something like this?
scorchedsky said:
I just did a full wipe and flashed CleanRom 2.1, and since then I've been having partial wakelock problems.
I keep getting LocationManagerService partial wakelocks that stay there forever (>95% of the time). The phone never goes into "deep sleep." I can't figure out which app is calling the service, and it comes up under "Android System" in BetterBatteryStats.
In the Alarms tab on BBS, com.google.andoird.apps.maps has 95 wakeups in an hour, almost all of them ALARM_WAKEUP_SENSOR_COLLECTION_POLICY. I haven't used Maps for anything.
I can make this go away if I disable "Google Location Services" and reboot, but that seems to increase how long it takes to get a location lock (I'm always on Wi-Fi).
Anyone have any ideas / experience with something like this?
Click to expand...
Click to collapse
I've had similar problems in the past and Latitude was the culprit. I also had LocationManagerService wakelock problems from the last update for 1Weather after they upgraded their radar map to GoogleMaps.
Try going into maps--settings--location settings--and uncheck the report from this device option
Sent from my SCH-I535 using xda app-developers app
I just updated 1Weather and noticed the new radar...uninstalled and I haven't seen the wakelock since rebooting. All boxes are ticked in location services. I don't have a report from this device option - only VZW, GPS, and Google.
Sent from my SCH-I535 using xda app-developers app
The report from this device option is in the settings for Google maps
Sent from my SCH-I535 using xda app-developers app
scorchedsky said:
I just updated 1Weather and noticed the new radar...uninstalled and I haven't seen the wakelock since rebooting. All boxes are ticked in location services. I don't have a report from this device option - only VZW, GPS, and Google.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
If you updated 1Weather then that was likely the issue. Same thing happened when I updated. I spoke with their support department last week and ended up sending them a few logcats. They sent me several updated apks and after a few tries they were able to stop the wakelock. I believe they are supposed to be updating the app sometime this week with the fix.
Try a different kernel too... I know one other person besides myself had wakelock problems with the kernel that comes with CM10 Official. I put lean kernel v0.9 on my phone and now my phone is sleeping like a baby when I'm not actively using it.
failsaf3 said:
If you updated 1Weather then that was likely the issue. Same thing happened when I updated. I spoke with their support department last week and ended up sending them a few logcats. They sent me several updated apks and after a few tries they were able to stop the wakelock. I believe they are supposed to be updating the app sometime this week with the fix.
Click to expand...
Click to collapse
Yep, after a factory reset and no reinstalling 1Weather I can confirm that was the issue. Glad they got it fixed, the app is great otherwise
Sent from my SCH-I535 using xda app-developers app
I use Google Navigation on a daily basis and have found a bug while using CM and PACman ROMs. If I am in the middle of a navigation route and the screen is turned off, when the screen comes back on the navigation continues to appear in the notification bar, but I cannot return to the visual turn by turn directions. It always takes me back to the Navigation landing page of choosing your destination again. Any help?
Hmm.. I don't have this problem. Have you tried clearing data for Maps?
Also, is this the latest version with live traffic rerouting?
Sent from my HTC One S using Tapatalk 4
usaff22 said:
Hmm.. I don't have this problem. Have you tried clearing data for Maps?
Also, is this the latest version with live traffic rerouting?
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
I cleared data and it seems like that might have fixed it.. I'll keep you posted. In the meantime, thanks!
Unfortunately, the problem is persisting.. now even getting FCs and freezes. This is the only buggy app
usaff22 said:
Hmm.. I don't have this problem. Have you tried clearing data for Maps?
Also, is this the latest version with live traffic rerouting?
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Any other ideas for why this might be happening? And why clearing data from time to time sort of helps?
skaters05 said:
Unfortunately, the problem is persisting.. now even getting FCs and freezes. This is the only buggy app
Click to expand...
Click to collapse
Does the problem exist on a stock ROM? Maybe the problem is a setting on your Google account that syncs with the Maps app and causes it to crash.. Don't know what could be causing it really
Sent from my HTC One S using Tapatalk 4
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 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.