This happens to me virtually every time I run google translate or try to perform a google search from the home screen (using the dedicated search button, of course). I've even tried other tts. systems and it keeps happening. Is there a reason for this? Perhaps a related function that could cause this?
Related
When trying to use google maps & the built in turn by turn navigation it will load up then just say searching for gps & it never locks on & doesn't give me the voice guided turn by turn anymore. Google maps is up to date, gps is on & showing in the status bar, & I have tried in numerous locations with the same result. Am I alone on this one?
This has happened to me a few times with diff ROMs even. GPS test app shows that there are sufficient sats in view but the system never locks in. Next day it works fine.
Could be radio or kernal related. Try clearing data and cache. Probly wont help but can't hurt.
Do you open maps first then navigation? For some reason, when I open just navigation, it will do what you say and never lock on. Get to navigation by typing the address in to maps and then hitting driving navigation.
does the same in mine no matter what... i dunno what to do. running incredibly re engineered rom (newest one)
Driving around while trying to get a lock can cause it to take a little longer... Cloudy skies can do this also. Being inside a building can also interfere.
If you just have standalone GPS turned on, well that's your problem right there. The other two assist in getting a GPS lock alot quicker. The other two that I'm talking about is Google's and VZW's Location Services. Those two will also help get a better and more precise position aswell.
NOTE: Navigation. If this was a fresh/wipe install or you get stuck at "Checking Navigation Availability" do the following:
1) Turn on GPS
2) Start Maps
3) When prompted turn on WiFi (do not need to connect to any)
4) Map should then show approximate location
5) Get out of maps
6) Reboot
6) Start Navigation
I think this stuff is all on the right track. Here's my method (I get the same thing on a de-sensed stock rom):
I think Google Maps has the ability (not so great) to 'block' itself via using huge amounts of resources whereas the GPS doesn't use much resource and needs a helper app to get itself oriented the first time. Once oriented it is fine.
The one I use is a free market tool called "GPS Status" by EclipSim. It takes ~3 seconds to get a fix. So you start GPS (via power widget settings, whatever) and start GPS Status, wait a little while and you can see it locking onto satellites, and when it says first fix = ~3 seconds or ~30 seconds, (it depends on some unknown conditions), then close it and you can use navigation because it knows where it is.
Worth a shot. I've been doing that since the 'dawn of droids'.
I completely unrooted my phone and no matter what I do it will not get a GPS lock. I deleted Google maps and redownloaded it, uninstalled updates, tried every combination of settings in location, etc. and nothing.
I tried on my wife's stock incredible also and it immediately locks on to her location and starts the turn by turn navigation without any issues.
I think there was something wrong with the internal GPS chip/locator in the phone itself. I contacted Verizon and they are sending me out another replacement. Hopefully this one works properly.
Thanks for all the replies guy's but it looks like the phone is just defective.
read on another thread to wipe dalvik cache. So I tried it and it works. After initial wipe, GPS quickly acquired satellites and locked on.
Anyone knows what causes this. Try to use Google voice search a lot but it instantly goes to retry over and over almost all the time. I thought was maybe skyvi doing..but it works just fine with it before. I have to either restart phone or run task killer.. even if nothing is running
I'm having a devil of a time trying to switch my default navigation app to Waze. I'm bone stock, non-rooted. Tried clearing the defaults for Maps, Google Search and Waze, but no luck. Did a lot of Googling, but nothing seems to work. I want to be able to say "OK Google, navigate to xxxx" and have it go right to Waze. Each time I try it, it goes into navigation mode on Google Maps. If it makes any difference, I'm running Nova Launcher. When in my car dock, I run Car Dashdroid.
I think the ok Google feature is limited to Google apps. So it will always default to maps. It doesn't seem to have a default setting.
On my N910V running VRU2CPF3 CM13.0-20160724, I have noticed a very strange behavior with the Google Now app (recently re-branded as simply, the "Google" app). Immediately after a phone call (and during other circumstances I haven't identified precisely yet), the Google app will lost the ability to "hear" me, even if I press the microphone button and start talking. The "ok Google" function doesn't work during the issue either, nor can I retrain the ok google voice model because it plain doesn't register any mic input. I can make calls and people hear me fine, and I can record audio on my camera, so my microphone is working.
The issue always goes away if I reboot, but eventually comes back, even if I haven't made any calls. On one occasion, I got the mic function for the Google App back after opening my phone app, then lost it after closing my phone app. On another occasion, I got the mic function back for the Google app after uninstalling Google Chrome and Chrome Beta (per this post). I was also able to get functionality back once by plugging in an external headset and then unplugging it, and another time by force killing all open apps. All of these "fixes" failed to fix the issue this time around - strange, right? Again, reboot always gives a temporary fix, and a phone call usually (not always) causes the issue to occur. I have found at least one individual with the same issue (khalil) here
I have tried a fresh install of the system, and the issue seems to go away for hours or even days at a time, but always comes back. I froze every user installed app on my phone using Titanium backup to see if an app was the issue, but the issue persisted. However, the issue does not seem to occur when booted into safe mode (which screams of software problem). I am currently in the process of reflashing a blank system to see if the issue persists without any user apps.
This behavior is not specific to this operating system; I had a similar issue when I was on stock unrooted 5.1.1. I did not notice the issue on Jasmine rom running 6.0.1, but I also didn't run it for very long. I seem to recall having a similar issue with my Galaxy S3 on CM11 (though it was a while ago so I can't confirm the truth of this!), so I suspect that something about my setup is to blame, rather than the hardware.
One more juicy tidbit: force uninstalling the google app fixed the issue for a day, then the app started force closing on launch, and no amount of finagling would stop the force closing. For the record, I've flashed google apps mini from opengapps.
I don't know what tools to use for proper logging of hardware - ie, when an application has control of the mic or not. I suspect that the issue is coming from improper ending of microphone use state in a certain program.
I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.
This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.