I’ll explain again. Unless I’m playing something on my phone, through my car’s bluetooth, I hear no notifications. I’ve run Waze on my phone in another vehicle, I do not hear any notifications. Now, in addition to that, I would like to have the option to vote down an alert on the other side of the road if it doesn’t exist anymore.
There’s two things then: 1) you haven’t got the settings correct to play audio either to the phone speaker/headset or via bluetooth. Those are found in the Sound settings. 2) it is possible Waze may change to allow “clearing” of a police or other kinds of alerts on a road when you’re traveling the other direction. I bet there’s a vote on the client uservoice for that already.
Related: there is definitely a uservoice vote already going for alerts which apply to both driving directions at the same time such as police or accident which blocks/affects both directions of travel.
Today you cannot do this, but the desire is out there to be able to do what you’re looking for. If/when Waze decides they are inclined and have development time available, it will happen.
I agree - 1500 ft is the absolute minimum for the police alert.
I can also say that I’ve had intermittent problems with actually hearing the AUDIO for “police ahead” even when the police are ahead on my side of the road. This happens on my iPhone 4 whether playing through the phones speaker or bluetooth thru my vehicles speakers.
yep that’s true, just yesterday there were some police officers with a speed radar and i saw them about 2 hundred meters before and did not have the alarm but long after i saw them, had they targeted the radar to me i would probably had gotten a speed ticket, not for much but less money in my pocket plus the hasle. is it posible this can be improved? or should we alert way before being in front of them?
on ROTW a policetrap is reported at a distance around 500m. So that’s more than 1600 feet…
On faster roads this is ok, but on normal street, especially in the city, this is much to far…Reports are working with driving directons. Of you approuch the report from less then 500m, you only see the icon on the map. The popup and voice won’t appear…
It seems like this was universally changed to 2000ft in a recent update; this is no good. If I’m in traffic and I get notified of a road hazard 2000ft ahead it’s still going to be a minute or so until I get there…by which time the notification has often dismissed itself so I can’t even give thanks or hit “not there”.
I get that for some driving situations 2000ft makes a lot more sense than 500ft, but for mine this has become quite annoying. This really needs to be a configurable option. If it already is, please let me know where I can find it!
And it would be very usefull, is the icon is change, to something more noticeable, something like a big red “P”. Many time, while driving at higher speed, and the device is at a little distance from the eyes (best allocation posible in the car dashboard), it´s not clear which icon you are looking at, and as stated above, only at 500ft that audio warning is trigger, so, if in a long straight, police radar will caught you well before the 500ft mark.
I cannot stand the longer distances for alerts. 1,800 ft (500 m) is way too long for the congested roads within Northern New Jersey. We often have multiple and different hazards on the roads within the new 1,800 feet distance and before we can confirm or “Not there” the hazard, a new hazard pops up and takes precedent even though the first hazard is closer. This is not good.
Furthermore, 1,800 feet for a “hazard” is simply too long of a warning even at 65 MPH (IMHO). I just don’t need that much time to adjust my driving accordingly. And by the time the hazard has appeared, I’ve spent too much time looking at the feet count down to where the hazard may be. This is distracting (potentially dangerous) for drivers to pay attention so long during the count down on multiple lane highways. I have found that many times I end up not paying attention to it by the time I approach where it was reported because too much time has elapsed and I need to pay attention to driving.
I don’t necessarily have a problem with a “police” alert being further than 500 feet but realistically don’t need it more than 1,200 feet or about a quarter mile.
>> Long story short, I suppose we should have user selectable alert distances. <<
*However,the new/current hazard alerts at 1,800 feet SUCKS! Please revert the hazard alerts back to 500 feet in the interim!
But let’s be honest most drivers using Waze during their daily commute will not be the lone car on a long straight-away. It’s going to be in traffic, and 500 ft may be on the short side, and the officer is going to be targeting vehicles 200-300 feet out to ensure he knows exactly which one pinged with the highest speed. 500 is too short, but 1800? You’ve slowed down, been distracted and sped back up by the time you cover that distance.
You guys are smoking something if you think 1800 ft is too long. Some LIDAR guns can get you at that distance. It takes a little more than 15 secs to travel 1800 ft at 80 mph, 20 secs at 60 mph. There’s an easy fix, let us set the distance for each alert type. I’ll set mine at 2,000 ft and others can use 500 ft. That way the police have a customer when I pass.