I'm having issues with Google Navigation and I'm wondering if someone can help.
Let's get this out of the way first. I'm running the CM7 Nightlies, but this isn't a GPS issue. I've done the GPS fix. GPS is working fine. I can see myself in Maps to a 20m accuracy even when I'm in my concrete bunker of an office building. Google Maps sees me just fine.
I can scan around in Maps and I'm getting the satellite layer updates. I know where I am and I can see where I'd like to go. I can click on the location and the Places update comes up. I can surf around in there, read reviews and do all that that app offers. So far, so good.
If I click on the Get Directions it will provide me with a list of directions. Awesome. I know where I am, I know where I'd like to be and now I know how to get there. Great!
If I click on the Navigation button Google Navigation comes up. It goes to "Getting Directions" and will just sit there... forever...
I've cleared the app data. I've even reinstalled Maps. It still will not work. Is anyone else having this issue?
Just another piece of information, if I install Waze and all of this works fine. I can even see other Waze users driving around town live. It's not a GPS tracking issue then either. Should I just switch to Waze?
Wow... I can't believe nobody else has this issue. Has anyone else tried this?
Because I really hate it when someone has an issue, fixes it themselves and never lets anyone know how, I bumped this thread to post what the problem was and how I fixed it. That way, if anyone does a search for this problem, they have both a reference and a resolution.
I believe the problem was my overzealousness in deleting apps that I didn't use or didn't believe I used. When flashing a new ROM, the first thing I always do is go through the /system/app folder and delete the crap I didn't want on my phone. One of the things I always deleted was the GoogleQuickSearchBox.apk. I never use the quick search widget because I always pull up the browser for Google searches.
I updated to CM7 Nightly Build 39 yesterday and, instead of pulling that APK I decided to test the GPS, Maps, Places and Navigation interaction. I was able to get an almost instant GPS lock. I could scan around Maps and get the layer updates. I could find the places I wanted in Places. Then, for the real test, I attempted to get driving directions to a local restaurant. It came up in a couple seconds.
So, the morals of the story are to not delete things when you aren't completely sure of everything they are tied to and don't give up solving problems on your own when nobody else is able to help you. I hope this helps someone.
no problems here. i think u deleted something.
Related
I clean installed (RAR file) the Blazn build w/ sound a couple of days ago. Now I having a lot more stability issues and Navigation freezes up every time I open it. I have searched through google and on here, and I see people with the same problems with the new build but no solutions or acknowledgement that multiple users are having issues like this. Here is what I did.
I go into google maps to insure I have a GPS fix. It finds me within 2 meters or so. I then go into navigation. It doesn't give me the location error because I have a GPS lock. I then type in the address I want to go to. I have the bar at the bottoms saying "Getting GPS" or something like that. In the middle of the screen it has the "getting directions" or whatever it says, but the little spinning circle animation freezes up. If I click to try to get to the menu. Android tells me it is not responding and I can Force Close or Wait. I force close. Of course Android opens it back up. I then hear the first voice prompt of where to go on my directions. When I click on Navigation to get back into it. It shows me the next turn, but freezes up again. This will go on forever until I force maps and navigation to close manually for good by going into settings and force stopping the processes.
I thought maybe it was the Blazn build, so I renamed the boot directory to something else and clean installed (using the RAR file) the stock build. While it is more stable and I don't get as many random crashes of apps and processes, I still get the same problem with Navigation.
I also have tried to format and attempted to clean install both builds and still have the same problem.
Is there any Sprint customer able to get navigation to work and not crash? I am thinking this is a CDMA/Sprint problem only, and it has something to do with the app accessing the sound, or at least that is my hypothesis, because it was working in all prior builds up to this one.
Any suggestions or thoughts?
slickdaddy96 said:
I clean installed (RAR file) the Blazn build w/ sound a couple of days ago. Now I having a lot more stability issues and Navigation freezes up every time I open it. I have searched through google and on here, and I see people with the same problems with the new build but now solutions or acknowledgement that multiple users are having issues like this. Here is what I do.
I go into google maps to insure I have a GPS fix. It finds me within 2 meters or so. I then go into navigation. It doesn't give me the location error because I have a GPS lock. I then type in the address I want to go to. I have the bar at the bottoms saying "Getting GPS" or something like that. In the middle of the screen it has the "getting directions" or whatever it says, but the little spinning circle animation freezes up. If I click to try to get to the menu. Android tells me it is not responding and I can Force Close or Wait. I force close. Of course Android opens it back up. I then here the first voice prompt of where to go on my directions. When I click on Navigation to get back into it. It shows me the next turn, but freezes up again. This will go on forever until I force maps and navigation to close manually for good by going into settings and force stopping the processes.
I thought maybe it was the Blazn build, so I renamed the boot directory to something else and clean installed (using the RAR file) the stock build. While it is more stable and I don't get as many random crashes of apps and processes, I still get the same problem with Navigation.
I also have tried to format and attempted to clean install both builds and still have the same problem.
Is there any Sprint customer able to get navigation to work and not crash? I am thinking this is a CDMA/Sprint problem only, and it has something to do with the app accessing the sound, or at least that is my hypothesis, because it was working in all prior builds up to this one.
Any suggestions or thoughts?
Click to expand...
Click to collapse
remember this is a work in progress still. No need to freak out.
[ACL] said:
remember this is a work in progress still. No need to freak out.
Click to expand...
Click to collapse
I love you guys... I have lurked here for months and xda-developers for years. I love how you post toward people that don't post all the time. You treat them like idiots, crazy people or whiners.
I am not freaking out. I am not a newb. Is this not the place to post problems with the xandroid project? I am posting a problem that I have not seen posted on here before. I am not complaining about the usual stuff that still isn't working. I understand it is a work in progress. I was just posting a new problem that has come up since the sound started working. I did this so that potential programmers will see it, and to also see and get feedback on whether other Sprint users or other carrier's users are having the same problem, or if theirs is working fine.
slickdaddy96 said:
I love you guys... I have lurked here for months and xda-developers for years. I love how you post toward people that don't post all the time. You treat them like idiots are crazy people.
I am not freaking out. I am not a newb. Is this not the place to post problems with the xandroid project? I am posting a problem that I have not seen posted on here before. I am not complaining about the usual stuff that still isn't working. I understand it is a work in progress. I was just posting a new problem that has come up since the sound started working. I did this so that potential programmers will see it, and to also see and get feedback on whether other Sprint users or other carrier's users are having the same problem, or if theirs is working fine.
Click to expand...
Click to collapse
Thats what we are known for .. but think about this.. where would the dev process be without us ? lol ..So sorry for treating you like one of the crazies ..
My advice is to hit up PPC geeks since most of the cdma community is there. Fyi, im not involved with xdandroid. Just with the kernel development and Those have really nothing to do with one another. However we do cross paths from time to time. Also dont be afraid to joint the irc chat for xdandroid. People there will be able to give you a better idea of whats up.
sounds ridiculous but i just updated my focus to mango on monday. for the longest time my home pc would not update it, kept giving different error codes each time. i had to replace my original phone with an ATT refurbished one and so i just assumed in the refurbishing process this "new" phone was FUBAR with updates. anyway someone recommended trying another PC, so i used my netbook to no avail and then my work laptop with great success. mango is awesome!
anyway, i love how bing maps will read directions through bluetooth in my car, but i am a little irritated that it won't continue to read the directions until i get to my destination? it will just read the direction i click on and the one after it, but then say "thank you, goodbye" and will stop giving directions. i have to manually go into bing maps again and click on the direction i want to be read to me. just curious if anyone has gotten it to read all the directions until you get to the new location without touching your phone? i notice you can go through a text message conversation without touching your phone via bluetooth, so it would be nice if you could do that with maps also.
Nope, that is the way it was designed to "work" (despite it being an illegal activity in many areas). There is nothing you can do about it, short of buying a real GPS nav system from the marketplace.
Question, Why wasn't this an issue with WM? As crapy as WM was the Maps app worked flawlessly and makes this new one look like crap. Just trying to understand I guess at to why it wasn't an issue before but it is now. It is kind of dangerous to have to tap and look at the screen to see where your going.
Hi,
Recently my Lumia 900 is not finding it's location when I use apps like Bing Search or Yelp. When using the built in Bing search it finds my search request but when I click on the directions icon it is unable to find my location and gives me a No Location Information error.
The only app that consistently gets my location is Nokia Drive. I'm getting frustrated that many of the apps that use location are not working. I've enabled location sharing for the phone and all the apps to no avail.
Anyone else seeing this? Any suggestions?
TIA!
ganks said:
Hi,
Recently my Lumia 900 is not finding it's location when I use apps like Bing Search or Yelp. When using the built in Bing search it finds my search request but when I click on the directions icon it is unable to find my location and gives me a No Location Information error.
The only app that consistently gets my location is Nokia Drive. I'm getting frustrated that many of the apps that use location are not working. I've enabled location sharing for the phone and all the apps to no avail.
Anyone else seeing this? Any suggestions?
TIA!
Click to expand...
Click to collapse
Mine is doing the same thing. It used to work fine. Over the last several weeks it has been getting worse. I've uninstalled most of the apps that have access to location to see if they were causing some interference with something but nothing is working. Local Scout fails to load anything half the time now, too. Nothing has changed with my phone. Never dropped, never abused, and used to work like a charm.
awesomeindeed said:
Mine is doing the same thing. It used to work fine. Over the last several weeks it has been getting worse. I've uninstalled most of the apps that have access to location to see if they were causing some interference with something but nothing is working. Local Scout fails to load anything half the time now, too. Nothing has changed with my phone. Never dropped, never abused, and used to work like a charm.
Click to expand...
Click to collapse
To be honest I can't tell if Local Scout works well or not. It never has what I want (like an option to search) so I just use better apps like Yapf or Yelp. I do know that it took a while for my location to be correctly determined when I was in NYC this past weekend. Today on a drive from southern Vermont to northern New Hampshire, my Nokia Drive lost GPS a few times. It took 5 or so minutes before it was back on track.
Do you guys also have issues with losing/having an incorrect GPS location while using Maps or Nokia Drive?
Hey Guys,
I've searched and searched and searched (albeit I admit I suck at searching), and cannot find anyone talking about this. Thus here I am. Even the Google Product forms seem to have zero answers for me (and no one answering me there), and thus why I'm here. I also don't know if this is the right place to ask, but here goes anyway:
The new (pretty) Google Maps/Nav works on my S3 on Cyanogen mod: as in, I can search the map, use it and start using navigation ... BUT, if I switch to a different app (desktop screen, check sms, mail, settings, anything that isn't the navigation app) while live navigation is running, it'll reset back to the nav search screen BUT live navigation will keep running in the background (voice + GPS still running) and the map will NOT show any navigation.
To recreate for me the steps are:
1) Load up navigation and navigate somewhere, anywhere.
2) Switch to a different app.
3) Go back into navigation. Instead of being presented with the route (live nagivation) I'm presented with the nav search screen.
If I click the 'back' button, I get a regular ol' map. Searching for any route while the old nav is running will cause the Maps app to crash. The only error message I get if I get it to crash is: "Google Maps has unexpectedly closed."
I have tried re-installing the new Google Maps. I have even tried doing a complete phone wipe, also didn't help.
The only thing that sort of seems to do 'something', is if I clear the Google Maps/Navigation cache, force stop it, and then start again. Then I'll be able to use the quick app switch (pressing home button for a few seconds) to switch in and out, but that's about it .. and that only works for one nav route. After that first one if I try again it'll start crashing again.
Has anyone ever experienced anything like this? Or point me in the right direction?
Thanks!
p.s. I did post in the google product support form, no responses there yet
piotrkrzyzek said:
Hey Guys,
I've searched and searched and searched (albeit I admit I suck at searching), and cannot find anyone talking about this. Thus here I am. Even the Google Product forms seem to have zero answers for me (and no one answering me there), and thus why I'm here. I also don't know if this is the right place to ask, but here goes anyway:
The new (pretty) Google Maps/Nav works on my S3 on Cyanogen mod: as in, I can search the map, use it and start using navigation ... BUT, if I switch to a different app (desktop screen, check sms, mail, settings, anything that isn't the navigation app) while live navigation is running, it'll reset back to the nav search screen BUT live navigation will keep running in the background (voice + GPS still running) and the map will NOT show any navigation.
To recreate for me the steps are:
1) Load up navigation and navigate somewhere, anywhere.
2) Switch to a different app.
3) Go back into navigation. Instead of being presented with the route (live nagivation) I'm presented with the nav search screen.
If I click the 'back' button, I get a regular ol' map. Searching for any route while the old nav is running will cause the Maps app to crash. The only error message I get if I get it to crash is: "Google Maps has unexpectedly closed."
I have tried re-installing the new Google Maps. I have even tried doing a complete phone wipe, also didn't help.
The only thing that sort of seems to do 'something', is if I clear the Google Maps/Navigation cache, force stop it, and then start again. Then I'll be able to use the quick app switch (pressing home button for a few seconds) to switch in and out, but that's about it .. and that only works for one nav route. After that first one if I try again it'll start crashing again.
Has anyone ever experienced anything like this? Or point me in the right direction?
Thanks!
p.s. I did post in the google product support form, no responses there yet
Click to expand...
Click to collapse
I can't reproduce the issue you are having (I'm on TW 4.1.2, though), but I have had my own set of issues with it. If you disable wifi and network location (to keep the Nlp wakelocks under control), sometimes when the GPS locks it still shows and old location. Only way to fix is to wipe data.
Since the fix is the same, I'm going with bug in the app. Old version was better in pretty much every way.
Don't forget that recently google made a lot of changes to maps. I'd imagine they know about a lot of the bugs people are having and will probably fix in the near future.
When you try to go back to navigation, do you select it from the notification area?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Don't forget that recently google made a lot of changes to maps. I'd imagine they know about a lot of the bugs people are having and will probably fix in the near future.
When you try to go back to navigation, do you select it from the notification area?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah, I selected it from the notification area.
IF, and ONLY IF, I clear the Google maps area will navigation still work if I reselect it from the notification area and/or the quick switch thingy. But that niceness only lasts for one route :-/ After that, it's back to always search menu for me.
It all really sucks because for work I do get a lot of texts or calls, which means if I'm using navigation ... yeah ... I basically have to reset navigation every single bloody time I get a notification :-/
I've never used it, but what about Samsung Drive Link? Isn't that supposed to provide an interface for when you're driving? Maybe using it will allow you to switch normally. Thats just a complete guess, like I said, I've never used it.
Only other option, and probably the best one, is to use an older version of maps. I posted one in a similar thread to this in the Themes section.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
I've never used it, but what about Samsung Drive Link? Isn't that supposed to provide an interface for when you're driving? Maybe using it will allow you to switch normally. Thats just a complete guess, like I said, I've never used it.
Only other option, and probably the best one, is to use an older version of maps. I posted one in a similar thread to this in the Themes section.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I took your advice and found the old google map APK. <sigh> I already miss the integration and style of the new one, but heck you are so right: the old one works perfectly! Keeping that.
Thanks for the idea!
Now if we could only get Google to fix the new maps app bugs.
I'm under the impression they are working on it.
Sent from my SGH-T999 using xda premium
I have been having the exact same issue ever since the big Google Maps interface update.
I have a Samsung Galaxy S3, stock.
My Pixel XL GPS doesn't report accurate location during navigation and it causes the navigation app to always show my car a few feet off the road and keep recalculating the route. It is more severe in Waze but it is noticeable in Google Map too. Someone created a video of the issue: See this videohttps://youtu.be/LyOZW3BSQcY
Talked to Google support per usual they say go to Safe mode or reset the device but it didn't help. Anybody else observed this issue? It is common enough that Sprint created a document on how to address it but it doesn't help. People have reported it on Reddit and Verizon forums too but wanted to see what has been the experience here.
no video link. Regardless I have only encountered what you describe once when there was a split in the highway for an exit. After I started pointing a different direction it snapped back into place. Outside of that my GPS has been great. I am on Verizon if that matters.
mehdi_s82 said:
My Pixel XL GPS doesn't report accurate location during navigation and it causes the navigation app to always show my car a few feet off the road and keep recalculating the route. It is more severe in Waze but it is noticeable in Google Map too. Someone created a video of the issue: See this video
Talked to Google support per usual they say go to Safe mode or reset the device but it didn't help. Anybody else observed this issue? It is common enough that Sprint created a document on how to address it but it doesn't help. People have reported it on Reddit and Verizon forums too but wanted to see what has been the experience here.
Click to expand...
Click to collapse
I had an incident yesterday where I was continuing on a freeway at 70 MPH,. But Google Maps thought I had veered from its directions by exiting on a low speed very curvy road, so regenerated directions for that. This never happened wth any of my Nexus devices.
Im having this issue as well. Google Maps seems fine, but Waze seems a lot more jumpy and recalculates my route every few seconds. Pretty annoying.
NWTSCL said:
I had an incident yesterday where I was continuing on a freeway at 70 MPH,. But Google Maps thought I had veered from its directions by exiting on a low speed very curvy road, so regenerated directions for that. This never happened wth any of my Nexus devices.
Click to expand...
Click to collapse
Yea I never seen this issue on any Nexus. Since it seem to be common,not sure if a replacement would solve it. Posted it on Google product forum too to raise it to Google:
https://productforums.google.com/forum/m/#!category-topic/phone-by-google/y6G3etvT3U0
Sent from my Pixel XL using Tapatalk
Me Too...
So are you guys still having problems with this?
It's gotten to the point where I don't want to use Waze anymore - and I LOVE Waze. It seems like it should just be some sort of software tweak to fix this problem...
I hope it at least gets fixed before Waze comes to Android Auto.
Lame was hoping this got better and was looking forward to a working gps on Pixel.
Ive had this issue eventually pop up on every device. Currently on LG v10.. Upsetting :/
clockcycle said:
Lame was hoping this got better and was looking forward to a working gps on Pixel.
Ive had this issue eventually pop up on every device. Currently on LG v10.. Upsetting :/
Click to expand...
Click to collapse
Try deleting the app data and cache. Then uninstall and reinstall the app. So far its worked for me. Need to test it a few more days before I can confirm its a permanent fix.
I saw this post so I turned on Google Maps & used it to navigate home from work, about 15 miles. Not a big test, but it worked fine, followed be closely, always had me exactly where I was on the road down to the lane I was in.
I have had zero issues with Maps. I do not use Waze. (on ATT)
I have had the GPS issue first on the Pixel (was not following my location accurately and would not give me turn by turn directions) spoke with Google support, all their solutions failed including the factory reset so returned the Pixel and upgrades to the XL model have had it for 3 days and started having same issue again today!!! This issue is on maps and I have only downloaded normal certified apps I was very excited about the 1st Google phone as I love their products but this is very discouraging as the exact same problem has now happened with BOTH phone models. I have Verizon service but based on all of these comments am starting to believe it is a hardware issue and not the service provider. Hoping they can get this bug fixed and quickly otherwise I will be returning for a different device.
My Pixel XL was fine for the first few days. Then I put it in a case and rooted it, and ever since then the GPS is acting wonky in Waze, losing its fix, not getting satellites, acting nuts.
Trying to determine the issue...
I find it awful on maps!! I've had it showing me going backwards and the rotation is off!
Tried with waze and it was OK though so I've no idea
Sent from my Pixel XL using Tapatalk
Waze and Google Maps both keep losing GPS signal.
Waze starts to go absolutely haywire.
Google Maps just says "seeking GPS signal" every 30 seconds
Ive done a full factory reset and it's still happening.
Maybe something wrong with the GPS chip, or on the underlying OS??
Just spent 2 hours troubleshooting with a Google tech. They will be calling me back son (they just told me to test it after a full factory reset). No luck!
I'm also having this issue with the pixel xl. Seems much worse in Waze but happens in Google maps a little as well.
Well my GPS died some time this weekend. I was loosing GPS lock on google maps. GPS test is no longer shows it lock onto any satellites when my nexus 6 sees 7-9. Replacement is on the way. I would recommend anyone having this problem check with a gps test/info app and make sure the hardware is working correctly.
I replicated the problem on NDE63V, the OS the device shipped on and was working on before, along with NMF26O and NMF26Q.
Waze is unusable now. I am seeing the same behavior. Google Maps is ok, but waze jumps all over the place.
It is pure speculation, but I wonder if it is tied to how the OS is using the accelerometers. I think google Maps uses both the GPS position and accelerometers.
-J
1/2/2017 - Google Confirming Software Issue with GPS
I'm having the same problem.
Last week my GPS on my Google Pixel stopped working. When I open google maps, it shows the blue dot correctly with the compass working properly. However, when I start navigation or driving mode, it does not work. I also tried Waze and that also does not work - just holds on Searching for GPS. I also tried the app 'GPS Test' and it shows 'No Fix' on the GPS Status.
I contacted google pixel support this morning and they confirmed Google is aware of the problem and have identified it as a software issue.
nixforme12 said:
I'm having the same problem.
Last week my GPS on my Google Pixel stopped working. When I open google maps, it shows the blue dot correctly with the compass working properly. However, when I start navigation or driving mode, it does not work. I also tried Waze and that also does not work - just holds on Searching for GPS. I also tried the app 'GPS Test' and it shows 'No Fix' on the GPS Status.
I contacted google pixel support this morning and they confirmed Google is aware of the problem and have identified it as a software issue.
Click to expand...
Click to collapse
That's wonderful! Did they give you any information on how you others can refer to the issue, such as a bug number or anything?
I'm also having the same issue with my Pixel when using Waze, and since stopped using it, due to it being redirected consistently. Switching to Maps Navigation the issue doesn't seem to exists, however, if I just use Maps, I can see that the compass is not oriented in the correct direction, and have to do the figure 8 calibration consistently so that it can be oriented correctly. The blue indicator dot is also not correctly located on the map, and can be off by many feet/meter. This is the only way I have been able recreate the issue I'm seeing with Waze but on Maps this time, it seems that Maps Navigation is more forgiving on the GPS irregularities than Waze, which is why Maps Navigation is a much better experience than Waze on the Pixel or Pixel XL.
Haven't experienced anything drastic with the gps lock, but I do notice that the direction of where i'm facing is constantly off. Tried calibrating the compass to no avail. The direction feature would also throw off driving directions as it doesn't know which way you are headed when stopped.