For a couple weeks now after I navigate to somewhere and then end navigation, the application opens again randomly and tries to resume navigation. I have tried to clear it out of the recent apps list as well as force closing the app. After a force it will not reopen until I start the maps application again. Once the maps app is opened it will resume randomly opening.
I am on the Nexus 6p, running 7.1.1 with the January patches. This problem also happened with the December patches.
Maps Version 9.44.3
It just started happening to me this morning. I'm on the 5X and the latest patch. Damn this is really annoying. Any ideas?
hideous said:
For a couple weeks now after I navigate to somewhere and then end navigation, the application opens again randomly and tries to resume navigation. I have tried to clear it out of the recent apps list as well as force closing the app. After a force it will not reopen until I start the maps application again. Once the maps app is opened it will resume randomly opening.
I am on the Nexus 6p, running 7.1.1 with the January patches. This problem also happened with the December patches.
Maps Version 9.44.3
Click to expand...
Click to collapse
Install task killer app from play store
In app, go to settings>ignored apps
Add all apps to ignore list except google maps
Now again go to settings>auto kill
And set it to 15 sec
Done
Also push the thanks button if I helped
Regards milkyway3
Same thing here on a 6p but marshmallow. Driving me a little nuts
Been noticing the same thing for the last few days or so.
*me too*
On Nexus 5 marshmallow. Noticed it for the past 2-3 days or so.
same problem on Nexus 6p
same here on nexus 6p. It is starting to get unusable as it starts shouting directions from my pocket randomnly or it boots me from whatever app I am using on the phone.
Same issue here on a Nexus 5 with 6.0.1. I think it started when I used Google Now to start navigating.
Moto X (2013)
I'm having the same problem on my Moto X (2013) Developer Edition (and rooted) with the Resurrection Remix ROM. It's been happening for about a week now. It seems to be completely random as to when it starts up.
-Troy
Yeah this happens for me too, on Nexus 6P on 7.1.1.
I'm wondering if it's really a Google Now issue though as I use voice actions to start navigation a lot, and the random navigations all seem to repeat the last voice navigation. Maybe Google Now sends the previous navigation intent to Google Maps.
I'm using beta version of the Google app.
Do other people here use Google Now to start navigation?
Same issue for a few weeks here on my Galaxy S7. I reboot and it goes away for a few days, but keeps coming back.
I agree that it seems to be voice search. I'm not 100%, but I've had a suspicion.
Also using Google Now Launcher.
jameschao said:
Yeah this happens for me too, on Nexus 6P on 7.1.1.
I'm wondering if it's really a Google Now issue though as I use voice actions to start navigation a lot, and the random navigations all seem to repeat the last voice navigation. Maybe Google Now sends the previous navigation intent to Google Maps.
I'm using beta version of the Google app.
Do other people here use Google Now to start navigation?
Click to expand...
Click to collapse
Good call, this makes sense. I use Google Now Launcher as well.
TaoTeShaun said:
Same issue for a few weeks here on my Galaxy S7. I reboot and it goes away for a few days, but keeps coming back.
I agree that it seems to be voice search. I'm not 100%, but I've had a suspicion.
Also using Google Now Launcher.
Click to expand...
Click to collapse
Ermagherd this is SO annoying. I also use voice navigation a lot. OnePlus 3 here .
Me too, Moto X, been doing it a couple of weeks. My phone will be sitting on the desk next to me with its screen off and suddenly it's trying to tell me how to get to the last page I navigated to.. often wherever I already am.. I use Google now all the time, will keep an eye on if that makes a difference..
It might well be the Google now launcher thing.
I had it launch on its own again after ending a navigation that I had started with 'ok Google'.
It launched itself again.
Then I stopped the navigation, and did the task switcher thing and swiped to close the Google now window as well. After that it didn't launch again.
That was just one try. So no real confirmation. But maybe this can be a workaround until this is fixed.
Moto-Z Play
Same thing (maps entering navigation mode at random times) has recently started happening to me. Really frustrating.
Like suggested by JamesChao, I always start navigating using voice.
It's definitely an issue with Google Now voice search. Rather than killing a process, you can temporarily resolve this issue by either performing another voice search, or clicking the Google Now search bar on your homescreen and performing any other search. Obviously the issue will return next time you do another "Navigate" voice command.
Moto X 2015 latest updates checking in, same issue, i concur that its a Google Now issue.
Same - LG G4 Android 6.0
I have the same issue and have for about the last month.
Metamyr said:
Rather than killing a process, you can temporarily resolve this issue by either performing another voice search, or clicking the Google Now search bar on your homescreen and performing any other search.
Click to expand...
Click to collapse
Same problem here, nexus 5x. See that there's a software update, hopefully this'll fix te problem. Solution mentioned above seems to be working for now, but still annoying.
Related
As soon as I've started Google Maps once it keeps running even after I close Google Maps. As a result the LocationManagerService is often chewing up my battery in the background. Only solution is to reboot the phone or force quit with Titanium Backup. Has anyone experienced a similar issue?
I'm running:
Google Maps 6.0.1
Phenomenal 1.1 kernel
UltraToxic 8.0.1 Rom
I noticed the same after using Navigation soon after updating to KK5. Freezing the NetworkLocation apk (com.google.android.location) resolved it for me, while leaving GPS working correctly.
Xspringe said:
As soon as I've started Google Maps once it keeps running even after I close Google Maps. As a result the LocationManagerService is often chewing up my battery in the background. Only solution is to reboot the phone or force quit with Titanium Backup. Has anyone experienced a similar issue?
I'm running:
Google Maps 6.0.1
Phenomenal 1.1 kernel
UltraToxic 8.0.1 Rom
Click to expand...
Click to collapse
Freeze it with Titanium,while your at it freeze all Samsung bloatware and no more excessive batter drainage.
oinkylicious said:
I noticed the same after using Navigation soon after updating to KK5. Freezing the NetworkLocation apk (com.google.android.location) resolved it for me, while leaving GPS working correctly.
Click to expand...
Click to collapse
Thanks for your reply!
I froze Network Location 1.1.08 with Titanium Backup Pro. However Google Maps still keeps running in the background after closing it. Did I freeze it incorrectly?
Xspringe said:
Thanks for your reply!
I froze Network Location 1.1.08 with Titanium Backup Pro. However Google Maps still keeps running in the background after closing it. Did I freeze it incorrectly?
Click to expand...
Click to collapse
Are you logged into Latitude? That manifests itself as Google Maps activity and is a real battery killer.
Might be worth checking - log out and stay out if it is active.
Gustopher said:
Are you logged into Latitude? That manifests itself as Google Maps activity and is a real battery killer.
Might be worth checking - log out and stay out if it is active.
Click to expand...
Click to collapse
I wish that was it! I've never used Latitude though.
Xspringe said:
I wish that was it! I've never used Latitude though.
Click to expand...
Click to collapse
I assume you probably have checked, but if not, just double check that you definitely aren't logged in. Can't remember now the sequence of events, but in answering a relatively innocent question shortly after getting the phone I inadvertently found myself to be a Latitude user! I had never knowingly opened it or logged in.
Soon as I killed it my battery life improved immeasurably.
downgrade to 5.x solved the problem
Sent from my GT-I9100 using xda premium
ghmail2 said:
downgrade to 5.x solved the problem
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for the tip! I downgraded to 5.8 but it's still not fixed.
OK, if it isn't Latitude, the next most likely culprit would be an app or a widget that is somehow using mapping. A weather widget? Shopping? Anything else that thinks it needs to know where you are right now?
If you have the stomach for it, I have read various threads that talk about removing one widget at a time (and then one app at a time) until the culprit is identified.
Equally you could install a clean ROM and then start installing apps and widgets until you get the issue back.
No precise science, just lots of trial and error...
Clear cache from maps.
Gustopher said:
OK, if it isn't Latitude, the next most likely culprit would be an app or a widget that is somehow using mapping. A weather widget? Shopping? Anything else that thinks it needs to know where you are right now?
If you have the stomach for it, I have read various threads that talk about removing one widget at a time (and then one app at a time) until the culprit is identified.
Equally you could install a clean ROM and then start installing apps and widgets until you get the issue back.
No precise science, just lots of trial and error...
Click to expand...
Click to collapse
Thanks! I don't have any widgets running. I've also tried the Simple & Clean v2.4.3 ROM (and various kernels) and it produced the same result. It's just that as soon as I start anything related to google maps it will just keep google maps running until I kill it or reboot.
I wonder if it is a common bug and only few people notice it or if it's a rare bug. Sure eats up that battery though!
I read they'll be releasing ICS beta next week so I'm going to hope that fixes this issue.
So can you boot the clean ROM, start Google Maps and Google Maps alone, close it down and have it close cleanly? That is to say, no battery drain?
I must admit I fight a little shy of Maps since my Latitude experience but I have used it and I'm not aware of the behaviour you are seeing.
If you run the clean ROM for a while without anything else running I assume all is well?
Gustopher said:
So can you boot the clean ROM, start Google Maps and Google Maps alone, close it down and have it close cleanly? That is to say, no battery drain?
I must admit I fight a little shy of Maps since my Latitude experience but I have used it and I'm not aware of the behaviour you are seeing.
If you run the clean ROM for a while without anything else running I assume all is well?
Click to expand...
Click to collapse
As soon as I start Google Maps it will run indefinitely in the background. But as long as I don't run anything Google Maps related then there's no problem (it doesn't autostart or anything).
Xspringe said:
As soon as I start Google Maps it will run indefinitely in the background. But as long as I don't run anything Google Maps related then there's no problem (it doesn't autostart or anything).
Click to expand...
Click to collapse
It's the 'Google Maps related' bit that I'm interested in. What are you counting as Google Maps related?
If you only open Google Maps what happens? Same thing?
What (if any) other apps are causing this to happen? Can you list everything that triggers this behaviour.
Gustopher said:
It's the 'Google Maps related' bit that I'm interested in. What are you counting as Google Maps related?
If you only open Google Maps what happens? Same thing?
What (if any) other apps are causing this to happen? Can you list everything that triggers this behaviour.
Click to expand...
Click to collapse
So far I've tested with Google Maps, Latitude and Navigation and they are all affected by the same issue.
Xspringe said:
So far I've tested with Google Maps, Latitude and Navigation and they are all affected by the same issue.
Click to expand...
Click to collapse
...and if you don't start any of these you don't get the issue, correct? Just want to eliminate something else logging you onto Maps as Latitude is prone to do.
Gustopher said:
...and if you don't start any of these you don't get the issue, correct? Just want to eliminate something else logging you onto Maps as Latitude is prone to do.
Click to expand...
Click to collapse
Exactly. If I never start any of these there's zero issues.
Hmmmn, that is odd then.
I'm not aware of issues with Maps but I'll have a play with it on my own phone and see if I can replicate.
I had this on KK5.
On KJ3 and previous ones, there are no problems.
So I was using Navigation to get home (and running Street Bump - http://goo.gl/9922u to log potholes) and while on the highway I had a strange thing happen in Navigation. I took a screenshot of this. Basically it kept tracking me but no longer had my route. I had to close Navigation and set the route again. Anyone ever have this happen?
"Unfortunately, Google Play Services has stopped" - Google has abandoned older phone
So, just Google this error and you will find no shortage of users complaining about this error message.
Heck check out the latest reviews on the Play Store: play.google.com/store/apps/details?id=com.google.android.gms&hl=en_GB
For some it's a couple times a day, for others a few times a hour, for others (like me) it's 4-6 times per minute. Rendering the phone completely unusable because the message locks up the UI. It happens right after a clean reboot, and happens regardless of force stopping/disabling the service! Clearing the data and cache makes no difference for me and the vast majority of users experiencing the problem. Removing all Google accounts and re-synching makes no difference. Downgrading and upgrading the services makes no difference. The only thing that cures it is to completely uninstall all updates to the service and let it ***** about being old, but then every other Google app complains it cannot run because Play Services needs updating. What happened to ethical and modular development standards Google???
I have a Samsung S3 (GT-I9300) running Android 4.3. Kernel 3.0.31-2735602. Build number JSS15J.I9300XXUGNH4. I had this issue on an older ROM and also on a custom ROM I installed in the distant past. The only way I was able to fix the problem was by performing a clean wipe. I am NOT prepared to do that for the 3rd time this year. The phone is perfect for my needs but rendered completely unusable by this devil service called Google Play Services. This service and the way it runs, updates and crashes displays no sense and logic.
Anyone have a de-facto solution for curing this?
I've gone to apkmirror and brought all versions of Google Play, Play Services and Google Apps to the versions they were From Feb 2015 and played with every combination. It makes no difference.
NJ247 said:
So, just Google this error and you will find no shortage of users complaining about this error message.
Heck check out the latest reviews on the Play Store: play.google.com/store/apps/details?id=com.google.android.gms&hl=en_GB
For some it's a couple times a day, for others a few times a hour, for others (like me) it's 4-6 times per minute. Rendering the phone completely unusable because the message locks up the UI. It happens right after a clean reboot, and happens regardless of force stopping/disabling the service! Clearing the data and cache makes no difference for me and the vast majority of users experiencing the problem. Removing all Google accounts and re-synching makes no difference. Downgrading and upgrading the services makes no difference. The only thing that cures it is to completely uninstall all updates to the service and let it ***** about being old, but then every other Google app complains it cannot run because Play Services needs updating. What happened to ethical and modular development standards Google???
I have a Samsung S3 (GT-I9300) running Android 4.3. Kernel 3.0.31-2735602. Build number JSS15J.I9300XXUGNH4. I had this issue on an older ROM and also on a custom ROM I installed in the distant past. The only way I was able to fix the problem was by performing a clean wipe. I am NOT prepared to do that for the 3rd time this year. The phone is perfect for my needs but rendered completely unusable by this devil service called Google Play Services. This service and the way it runs, updates and crashes displays no sense and logic.
Anyone have a de-facto solution for curing this?
Click to expand...
Click to collapse
Just set the location to "Device only" instead of "High accuracy", this stops the error completely until google fixes the issue...
EDIT: BTW, this has nothing to do with older phones, this happens on my Nexus 6...
luizffgarcia said:
Just set the location to "Device only" instead of "High accuracy", this stops the error completely until google fixes the issue...
EDIT: BTW, this has nothing to do with older phones, this happens on my Nexus 6...
Click to expand...
Click to collapse
Thanks but the setting you describe is not present on Android 4.3.
luizffgarcia said:
Just set the location to "Device only" instead of "High accuracy", this stops the error completely until google fixes the issue...
EDIT: BTW, this has nothing to do with older phones, this happens on my Nexus 6...
Click to expand...
Click to collapse
Source?
markus4000 said:
Source?
Click to expand...
Click to collapse
I am using this solution in my Nexus 6 right now... And really, its all over xda... Dont have a specific link right now.
luixffgarcia is right. I have looked everywhere and this was the only thing that solved that problem. Oddly enough, I got a message from Sprint earlier this week saying that if I didn't upgrade to lollipop they would disconnect my service.
Yes guys, there are solutions that work for some people but it's totally dependent on the version of Android. Generally, the older the version of Android (in my case 4.3 running on a Galaxy S3), the less likely any of these fixes are going to work. I do not even have the option that is mentioned above.
In the last few days I've seen the number of 1 star votes for Google Play Services jump drastically.
Well just FYI
I use XPosed on my LG G2 Android 5.0.1 and the module Amplify caused the issues for me. It's not the entire module but some wakelock that I had blocking enabled. This worked previously so it seems like they updated something in their library that would cause it to crash if the wakelock is blocked. For now I just reset Amplify to default settings and I dont have any issues anymore.
Hope this helps.
I have a Samsung Galaxy Tablet S2 running Android 6.0. Recently I noticed that whenever I come out of the lock screen, after the device has been left alone for a few minutes, that google maps has launched. I am not sure how to figure out what other app might be calling maps, as I doubt if it is launching itself. Is there a way of determining what app is calling maps, or if it is in fact launching itself. I don't remember making any changes to the system settings or downloading anything that would call the app. This is very annoying having to close out of maps each time I come out of the lock screen.
Same thing happening on my Note 3. Perhaps a bug in the latest update?
It's been like 5 days since I was able to say ok Google with screen off, call ( name here) and the phone would unlock and dial the number, regardless if it was a contact or not.
Now I say ok Google call ( name here) and either the assistant will not respond after opening to make the call, or it goes open and it shows example,
Call circles pizzeria
But it never makes the call.
Now if I using my fingerprint to unlock the device, say ok Google call circles pizzeria, it will make the call.
Want to note, this is not a contact. Also don't matter if it's a contact or not. I've showed 2 examples of ok Google getting "stuck" on the commands.
I've factory reset the device. I'm thinking this has to be on Google's end. Just want to know if anyone else is affected.
So 19 views, and no one quick tested their own device? Gee thanks....
Sent from my LG-H932 using XDA Labs
I don't use Assistant at all (in fact I struggle to keep it disabled on my phone, and Google tries to enable it all the time). So I am one those views, but unfortunately have no experience.
Which OS version are you on? That might affect the results of others who try it.
Does it matter if you're in a Smart Lock situation (Trusted location, Trusted BT device etc)?
Just tested mine. My Google Home took the initiative of making the call, and gave me some tips on my first call that way. This was while my phone was in my hand, too, so I'm not sure why the GH took over, but whatever. In the end, it did dial out... or try to, before I told it to hang up.
Not exactly your situation, so I didn't respond. Mine has nothing to do with unlocking the screen, as I keep my screen unlocked and on Navigation app while driving.
But here's my story...
_________
A few months ago, new Google app update stopped Google Assistant from making the daily phone calls to my wife when I'm coming home from work. (I never know what time I can leave.)
"OK, Google, call (my wife's name)"
Normally automatically dials via Bluetooth through Google Voice.
This time nada, repeatedly -- from trying to show me search results, to not responding at all.
Even tried "OK, Google, call my wife" (instead of her name). Google Assistant: "Who is your wife?" (She's listed in Contacts as my wife, besides her full name.)
Suddenly Google Assistant wasn't performing as previously and also had amnesia.
This happened two days in a row. I had to manually hit a pinned dialer screen shortcut to call my wife while driving home. (Which is technically against the law now in Georgia, touching your phone while driving.)
So, I reverted back to the previous Google app version (downloaded through APK Mirror) -- which does exactly what I need -- and refuse to let it auto update in Google Play Store. I also have Titanium Backup of that specific version on hold, in case Google accidentally updates somehow.
I know I'm now a few months behind in app versions, but I don't have time to mess with trouble shooting. If the version I have works, I'm keeping it.
_______
I have half a dozen apps I also keep from auto updating for similar reasons.
For instance, because of newly imposed Google rules about a year ago, an long time app called My Data Manager has to put an icon on the left side status bar to show it's technically running in the background. On previous versions you could disable that stupid icon or "badge" in the app settings. It's a neat app, because I can merely swipe down and at the bottom of my notifications, there's a pinned box that shows my current data usage. And it's quite accurate. Every time I compare it to my carrier's report of my data usage it's within a few MB.
But I do NOT want to see a CONSTANT icon on my left side status bar for that app. So, I reverted to older version before the Google rules change and it works EXACTLY the way I wish. I unticked "auto update". I've done that for my phone, my wife's and my mom's.
________
I just finished working one month straight, with no days off. Feb 15 - March 13, often 12-14 hour days. In one two week stretch, I worked over 160 hours (4 weeks of work, crammed into 2 weeks.)
So, I'm not putting up with any crap from my phone.
If new app version breaks something, I'm reverting to previous app version and preventing it from updating. At some unknown point in time, if I want to test they've finally fixed what they broke, I will do that when I have free time. Other than that, I need my daily phone to work, period.
ChazzMatt said:
snip.
Click to expand...
Click to collapse
What version of the G app are you on?
Also on EdXposed, or regular Xposed grab sudohide.
You can hide any app from play store.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
What version of the G app are you on?
Click to expand...
Click to collapse
See screenshot.