Good morning.
Is anyone else getting this message when they attempt a routing event? So far, I’ve tried from KY to OH and vise versa… I have reset the phone a few times. Same behavior on wifi as 3G. I also tried out in the open air.
Thanks for the help! Waze is awesome and the only reason I asked Santa for a car mount 
Welcome to the forum – glad to hear that you’re enjoying Waze!
For me, I find that the “failure to communicate” 
error happens most when I have WiFi enabled but am not connected to a WiFi network; since I’m not normally connected to WiFi when driving ;), I just disable it before starting Waze. The only other times that I’ve seen that error (without having WiFi enabled) was during times of temporary server outage.
Thanks for the tip! After work today, I will turn off the wifi and see if that helps.
I have WiFi and cellular data enabled on my iPhone and don’t have this issue. In addition, in the latest release version of Waze 3.x, they have improved how Waze works when moving on/off of WiFi when Waze is running.
Must be nice to be able to use an up-to-date version – maybe if they ever finally roll out Waze 3 for Android, I’ll be able to try that also.
Strangely enough, I still cannot get it to work.
iPhone 4, no jailbreak, deleted/re installed the app, wifi on, wifi off, 3G on, 3G off (while on wifi)… my next step is to completely wipe the phone and only install waze. It probably sounds crazy, but I sold my TomTom and bought the entire car kit around waze and the iPhone 4… so I would like it to work 
Have you tried with a shorter, local route vs trying to route a longer distance between states? Try routing to your local 7-11 or Dunkin Donuts
Here is an interesting tidbit that might help pinpoint the exact issue…
I am in my driveway (3G connection only) in KY. I put in a OH address… “Uh oh, can’t find server”
I am in OH, put in my home address… “Uh oh, can’t find server”
I am back in my driveway and put in another known address, in KY, and it picks right up and says “LET’S GO!”
So then, I try that same known address in KY, from OH, and I get “LET’S GO!”
Honestly, it might be something incorrect about my home address…? When I get out of work today, I’ll try our next door neighbor’s house and see if it works…
I’ve been noticing a few instances lately where I’ll leave from the house with a location and it finds a route immediately. While on route, I deviate from the path calculated by Waze because there is a better way. When it tries to recalculate, I get the “failed to communicate” error and it takes me out of navigation mode. If I go back to the menu and pick my location again, it picks up the new route immediately.
No issues when starting a route from either end, just a lot of lag (and some errors) when recalculating in the middle.
Hi. I’m in Toronto, Ontario. I’m currently using Waze v3.0.0.0 for Android on Samsung Galaxy S2 on 4G network (Bell Mobility) and I get this error pretty much every single time which makes the app useless. I don’t remember having this problem with version 2. Any help will be appreciated. Thanks.
I’m in Sydney, Australia, and I also get this error practically every time I go to navigate. I also had this in the beta versions, and had to go back to 2.x. Interestingly, Waze can still download traffic info from the routing server. But I can’t get routing info and I can’t post traffic reports, do goodie munching, etc. As elishnevsky notes, this makes the app basically useless.
Could this be related? It is completely city specific, all other addresses are working.
Having the same problem - posted here: http://world.waze.com/forum/viewtopic.php?f=6&t=14867&p=139182#p139182 before I saw this thread though… :oops:
Same here! Toronto, Waze v3, Dell Streak with custom 2.3.3.
Navigation was flawless on v2. Switching to v3, I found that THE VERY FIRST TIME after (re)installation I’m getting the route, then nothing in 100% of tries.
Uninstall, clean Waze folder on SD card, install again. One successful route, then nothing.
I am having the exact same issue. On an SGS2 in Toronto on Rogers. Using Android 3.0, navigation never works. Anyone have the definitive explanation/solution? Is it a bug? The server?
Sent from my SAMSUNG-SGH-I727 using Tapatalk
The official Waze staff is a very small team. So even though the forum is great place to compare notes, and possibly get issues solved by other waze users, they cannot respond to every thread here. I would suggest everyone submit logs (menu->settings->help->send logs) and submit issue reports via the nanorep on the support webpage.
If you type 2##2 into the address search bar and then hit search it will put the app into debug mode allowing more detailed information to be included in the log files. The more log files that get sent to the team the quicker they are able to determine areas that need work. I normally send in the files at the end of my driving for the day but it won’t matter when they get the info. It will all help in the end.
Also, ensure that you fill in this form so that Waze is aware of the Routing Timeoutes.
https://docs.google.com/spreadsheet/viewform?formkey=dFVfOHI4aU9nNC1jcXI2MnE3bDUyX2c6MQ
im in toronto. It seems like it’s not even letting us route online live.
here is a video of me trying to get from toronto to burlington, toronto to ottawa and even toronto to a local mall “square one”.
NOTHING WORKS>…
How about an update?
Sent from my SAMSUNG-SGH-I727 using Tapatalk