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.
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.
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?
New versions of Maps and Google Now might break navigation initiation. I had to revert to version 9.2.0 for Maps and 4.1.29.1706998 for the Google app before navigation could be initiated by the watch again. If I started navigation on the phone first it worked fine on the watch. Anybody else have this issue?
Yes, apparently. If I try to start navigation on the watch, it says "Calculating route..." and then "Check on phone", but never actually starts navigating.
Me too.
Anyone have android auto working with a head unit?
Yes. It was working fine, then Waze started presenting a screen with only the buttons in the bottom row. After trying a variety of things, like uninstalling Waze, and Android Auto, it has eventually settled down again and I haven't had problems for the last several days. This was on a Pioneer AVH-4200NEX headunit.
...and this morning the problem with Waze returned. But the fix is simple, just go into Settings, Apps, find Android Auto, Force Quit it, and go to the Storage settings for the app and do a Clear Data (which also clears cache I think). Then launch Android Auto, answer the prompts to give it access to contacts/location/etc, plug it in and you should be back in operation.
n9yty said:
...and this morning the problem with Waze returned. But the fix is simple, just go into Settings, Apps, find Android Auto, Force Quit it, and go to the Storage settings for the app and do a Clear Data (which also clears cache I think). Then launch Android Auto, answer the prompts to give it access to contacts/location/etc, plug it in and you should be back in operation.
Click to expand...
Click to collapse
Thanks, I had an issue with it not working. It took clearing Google Play Services cache to get it to connect.
I put my phone in my dash mount this morning and say, "Hey google, play some music". Assistant pops up and tells me I have to set up voice actions. Which I've set up well in the past. Then when I got to work, I also find that the stock launcher is overriding Nova again and I can't get Nova to stick. I'm assuming some updates borked my settings. Just wondering if this happened to anyone else.
Edit - After multiple restarts I was finally able to turn on voice match and get Nova to stick. Don't know what it was, but it finally worked itself out.