voytech wrote:The iPhone client no longer alerts of police and other road hazards when the spoken guidance is muted. This was very helpful when going to work where I know the route but I still want to be alerted of police.

As noted in this thread and elsewhere, mute now mutes all.


Tapatalk made me do it.

PhantomSoul wrote:Anyone else seeing a notification badge on the Waze icon on your iPhone's home screen with no apparent messages in Waze or ways to dismiss that notification badge?

Yes. There appears to be (another) disconnect between the badge count and inbox count.

zexpe wrote:iPhone -> Settings -> Notifications -> Waze -> Badge App Icon -> Off

Smartass.

perlin wrote:This example specifically is not valid, since we disabled light an moderate traffics from the zero-speed popups (I did not know that before.. sorry ).

Okay, I can understand that, but what about the other part of the problem which is that the slowdown is reported on a side street and not the actual street? The "Spaniel Ct" in the reports is not where the slowdown was. This has been reported by others more than once recently.

orbitc wrote:I'm part of it. Recently switch my phone and re-submitted my info. The only email I found is for previous beta.

And you are still out of luck. They can only add/update device information once per year. Next update is, I believe, around September.

invented wrote:When I use Add a Stop, the routing goes completely to shit. Now it has me going as far out of the way as possible to get to my stop point, alternatively it has me going quite far out of the way to get to my end point.

If it's not doing that, it's telling me to drive in circles...

The routing server seems to be strongly preferring to get us very close to our final destination, then routing to the stop point, then back to the final destination again. They need to work on this.

kentsmith9 wrote:

AlanOfTheBerg wrote:

invented wrote:When I use Add a Stop, the routing goes completely to shit. Now it has me going as far out of the way as possible to get to my stop point, alternatively it has me going quite far out of the way to get to my end point.

If it's not doing that, it's telling me to drive in circles...

The routing server seems to be strongly preferring to get us very close to our final destination, then routing to the stop point, then back to the final destination again. They need to work on this.

Alan, do you know if this was added to the list of open items? (Don't currently have access.) I see this a lot and I can add some examples if we need more.

I believe so.

EDIT: Yes, line 169.

Tapatalk made me do it.

Here are more examples of jams being reported on streets connected to the jammed street. These were not on my route, but I was able to easily find these by going to the Traffic Reports.

Cirrus Dr continues to the left and connects to Hall Blvd which is where the jam is showing as starting.
http://imageshack.us/a/img853/6364/img0949f.png

Jam reported on 152nd, but really is on Farmington Rd.
http://imageshack.us/a/img812/7307/img0950.png

Jam reported on 121st, but really is on Walker Rd.
http://imageshack.us/a/img21/5840/img0951.png

EDIT: logs uploaded after these screenshots were taken at 1:27 GMT 2013-03-14

davipt wrote:Here is a screenshot of a road label on the wrong segment (the jam is correct)

I don't think the label is actually on the other street, but is "floating" in the wrong spot. I've seen this happen once and have a screenshot as well, but wanted to see it happen again, which it hasn't for me. I'll attach it now.

http://img.tapatalk.com/d/13/03/15/vuhanyzy.jpg



Tapatalk made me do it.

Here's an example of a jumbled screen. Too many objects in a small space. We need some more design thought put into how to decided not to show some elements/objects so things are easier to see.

There's wazers, red light cams, two ads and street labels trying to use the same space.

http://img.tapatalk.com/d/13/03/15/y9ydepam.jpg


Tapatalk made me do it.