Recalculating Route Ruins Waze

My biggest problem with Waze is that when I’m trying to navigate somewhere that I am constantly getting Recalculating Route every 30 sec to a minute. Is it really necessary to notify me of this? Can’t the system just do it silently. This though is just an annoyance. What makes Waze unusable is that 50 to 90% of the time it comes back with that Routing Server has Timed Out and the route that it was displaying disappears till maybe the next time it recalculates the route (presuming it succeeds and of course only lasts till the next time the routing server times out).

This makes Waze completely unusable except for mapping and reporting traffic. I’d like to set my wife up with Waze but I know she wouldn’t use it because of this.

I get that Waze is constantly being updated and in theory that your route may be adjusted due to updated traffic but if the server times out leave the existing route displayed, I’d rather have that than no route at all. Maybe change the route’s color so we know that it isn’t up to date with latest traffic information but always display the route.

If it’s possible to selectively make one sound not affect the music volume, I’d like that for the Recalculating sound. It’s very nice to have for turn indications but not terribly important for recalculation.

What area are you in? It shouldn’t recalculate unless you leave the route it set. Is this happening? If the maps in your area are very inconsistent, then that will cause it to re-calc a lot.

There does seem to be a bug in the re-calc, as you mention. I see it happen also. I’m not sure if it fails to re-calc the route, and then stops displaying routing, or if the server connection fails and it stops displaying the routing, but it does sometimes seem to just go away without any notification in this case.

Just want to add that recalculating puts a big fat black sign above the map that it recalculates… (at least on Android) Great feature to block my view to the map when I actually need to find my direction manually… :smiley:

I’m in the Jacksonville/Northeast FL area. For me it is constantly recalculating the routes every few hundred yards or so. Even when there isn’t a turn to be made. Heck I’ve started a route at stop light, drive straight and within 50’ it will recalc. I don’t how well the roads are actually mapped out around here but for most roads I travel there are no opportunities for dot munching.

Again for it isn’t so much that it is recalculating than it is that the route disappears if the server times out.

I love the concept behind Waze but if I want to get anywhere I have to use something else.

Oh yeah for what it is worth I’m using a Touch Pro with a WinMo 6.5.5 ROM on MetroPCS. I am using the latest beta of Waze.

I’ve been having those same recalculating problems for months. I have an htc touch pro on uscc, running windows mobile, and none of my other GPS programs (Bing, Google Maps) have this problem. I’ve tried to reinstall the stock rom and that didn’t fix anything.

I only saw that recalculating like crazy only once, on a one-way-road, fixed, that was pointing in the opposite direction. Are you very very sure that the road this happens on is defined completely right?

My only issue is that the recalculating action causes the app to miss cupcakes and / or road munching when I run on the iPhone.

The road may not appear munched, but the actual points from doing so are done when the server analyzes your route in post processing. If the GPS is not so far off, that post processing can’t figure out what road you were on, you got the points.

The cupcakes issue, maybe so, but it has also been found that gps inaccuracy can cause missing cupcakes, even when the snap to function of the phone put’s you over one.

Damn, opened a topic on this yesterday! People need to use search more!

I also opened a request on user voice so vote on it if you agree!

Note that the built in search on the forum is useless. The common word filter is on, and it’s basically removed all the words anyone would search on. So unless people use the google search workaround
http://www.waze.com/wiki/index.php/Search_forum_for_common_words they will have a hard time finding previous conversations.

True! Searched on a username in combination with ‘login’ ‘button’ and those where too common. :roll:

My experience so far has been every time I turn to get a cupcake (or pumpkin/ghost) that’s a block or two over from my current route, the recalc causes me to miss the goodie, 100% of the time. If I turn of the routing and go around the block again, I get the credit for the goodie.

Note this is taking place in rural areas, where the nearest road running parallel is a good 2 kilometers away.

My interim solution has been simply to not use Waze for automatic routing.
GPS is normally quite reliable for me ( within 5-10 metres) when geocaching - and I dashboard mount it so I’m quite certain it’s not an accuracy issue. iPhone 4.

im agree hehe :lol: and also how can i do to really “cancel” the navigation, when im using the navigation feature and if try to “stop it” I cant it just kepp telling me where to go! Hehe

BTW will be nice to just select a place on the map (touching the screen on my moto-droid) and say: take me here. Cuse right now if you don’t find the place your going on “address” or if you don’t have it on “favorites” you cant use the navigate to take you there even if you know the place of it on the map

Press the yellow/green bar at the very bottom of the screen while navigating. Then select “stop navigation”. Voila… stopped.

Yes, you can. This is already a feature. Long press ON the street (it’s very sensitive… you have to press ON the street exactly) that you want to navigate to, and then click “set as destination”.

thx bro! ill try both cuse im pretty sure that i tried to stop the navigation like u said, but then my cel ran out of signal and when i got it again it starts the navigation by itself again =P

and for the navigation destination, i will have tu zoom +10x in first to see if it works :wink:

So, I started using Waze again the past couple of days and I see my problem still hasn’t been addressed. I have though open a report on UserVoice here: http://waze.uservoice.com/forums/59223-client-how-can-we-improve-waze-on-your-phone-/suggestions/1343005-system-constantly-reroutes-then-the-server-times-o.

I really want to use Waze on a regular basis, I want to be able to recommend Waze but I can’t if the route disappears. By the way I’m not talking about being somehow covered, or somehow not getting points…I mean the line and all UI telling and showing me where to go disappears. It is as if I hadn’t set a route. This makes it unusable.

What I have seen many times is that until it is able to actually figure out a route based on my location, or it is able to contact the server to compute the route, it cannot show anything. Waze is an online nav system. it doesn’t keep the a full world or US map saved to do local route calculations. It requires the server.

If there is a problem with intersections and roads in your area, then just driving with Waze running will auto adjust road location, direction and intersection turns allowed. When you notice problems, please open a map problem request and an Area Manager can address it. When I started with Waze, I got crazy and odd routes. After driving with it running for 2-3 weeks, it had updated the roadways and began to give good results.

I get that it needs to be able to connect online in order to calculate a route. My problem is it has calculated and displayed a route (with maps and everything, heck it often displays the map without network connectivity). Then for whatever reason the system decides it needs to recalculate the route, for whatever reason that this point the server times out. That is when the route disappears at least till it recalculates again.

What Waze should do is once the Waze client receives a route it should be cache. That way when it recalculates if it is unable to receive a new route it can continue to display and work off the cache route.

I have seen this happen several times, too. Now I understand more of what you mean. I haven’t been able to determine why it does this, but it could be poor GPS reception or a poor GPS device and Waze thinks I’m now on a different road close by, so it thinks it needs to recalc. That’s a valid reason to recalc.

Now, how Waze handles the recalc is another good topic. It can’t recalc just a middle portion of the route, which is frustrating, and once it decides it should recalc, the old route is wiped and you’re screwed. You area correct about this and it would be nice to see this changed.

You should put up a uservoice suggestion to get some votes and get it in front of the developers.