I'm having a strange occurrence. When I am running Google maps and press the multi function (Voice input) button on my Bluetooth earpiece, Google maps goes into a minimized smaller box.
I am using a US T-Mobile Galaxy S9 plus.
Can anyone please suggest whether there is a setting to stop that from happening or possibly confirm the issue.
It's not an issue. Google maps has Picture in Picture support on Android 8.0+
craya said:
It's not an issue. Google maps has Picture in Picture support on Android 8.0+
Click to expand...
Click to collapse
That took care of it thank you very much
craya said:
It's not an issue. Google maps has Picture in Picture support on Android 8.0+
Click to expand...
Click to collapse
If it is intentional then ok, but I (and not only me, because I can see many issues like this throughout the internet, platform agnostic) face a google maps navigation minimizing randomly and in my opinion it seems like a bug. I assume it has to more with google OS/apps than producer. Phone is Samsung Note 8 but I saw reports like this also e.g. for One+.
Anyone figured how to turn it off? Google maps goes into picture-in-picture every time a notification comes in. Very irritating.
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.
I see many users suggesting to whitelist Google Search if you want "OK Google" always on. However I've never noticed the need to do this. I do occasionally notice OK Google not working, but it continues to fail even when I turn my screen on. David Ruddock is noticing it in his Pixel review as well.
I see many users suggesting to whitelist Google Search for Battery Optimization/Doze, but I always wonder if this is Snake Oil. Why?
1. Because first off hotword detection is a hardware solution using a dedicated audio processing core to then wake up the system to turn on the mic.
2. Also, if we need to whitelist the app, don't you think Google would tell us this? They do it for Android Wear after all and the app prompts you to whitelist it in Doze/Battery Optimization.
3. Has anyone actually tested if Doze is the culprit? Doze doesn't take long (like an hour to kick in right?). If OK Google actually works while your phone is dozing, then it's pretty easy to show that whitelisting the app is not the real solution. Another way is to just basically force your phone to Doze, and if OK Google responds, then this theory is already disproven.
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.
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?
I have a problem with my Google Assistant on my Malaysian Set GT 2 Pro (Global Rom i suppose). Where if i call out 'Hey Google', Assistant will respond, even when the screen is off.. The assistant overlay appears, and mic is turned on ready for whatever I'm about to say next, but when i start speaking, it doesn't listen to me and no dictation of what i speak appears on the assistant as if i have not said a word. This only happen everytime after calling out the assistant with 'Hey Google'. If i start the assistant by long pressing home button, the assistant hears me and start dictating what i say and works normally.
I am not sure if this is mic problem or the google/assistant app's problem. For mic, i have given all required mic permission to the Google app.
I have a video of this, please have a look in the attachment and help me out. Thanks
same problem, mines was converted from chinese Rom to global from.
I have the same issue and its driving me crazy
Are you using Bitwarden?
https://forum.xda-developers.com/t/ok-google-not-working-correctly.4434669/
Quake94 said:
Are you using Bitwarden?
https://forum.xda-developers.com/t/ok-google-not-working-correctly.4434669/
Click to expand...
Click to collapse
Thank you that helped me resolve the issue.
Same issue on global European rom. I was crazy with this bug. Thank you so much for the solution. I disable accessibility services for "tasker" app and it work.
Another one who had the same issue. Thanks for the fix! For me was CCleaner!
Hi, I'm using BitWarden and I would like to keep accessibility enabled (it's very useful). Have you found a workaround to this problem?