crazycaveman wrote:I noticed that the voice commands (ASR) doesn't prompt for confirmation before submitting a report, which does occur on Android. Is this the way it is supposed to work, or should it confirm before sending the report? I was using an original iPad on iOS 5.1.1.

It depends on the speech recognition engine's reliability factor. If it feels the voice pattern it recognizes matches the patterns it looks for within a certain accuracy level, there will be no confirmation. It has been this way for quite some time.

crazycaveman wrote:I was not aware of this. I always get asked to confirm on Android (and never had a misheard command), but on my iPad, I asked it to shutdown and instead it thought I reported police. That's why I figured I'd ask...

Interesting that the versions behave differently. I thought the same software was being used in both... Sometimes I'd rather the iOS one did ask for verification more often as it has posted something completely not what I intended too. It's good you brought this up as perhaps there is a settings difference coded in the two OS versions? Perlin?

Bug: When a route is resumed after exiting Waze, upon arriving at the destination, Waze does not announce the POI or favorite name as it normally does for an uninterrupted route.


--
If it looks strange, or I used bad grammar or misspelled anything, it's my phone's fault.

Bug: (As the passenger). Requires that you have not previously received the "Passenger, Ok" warning dialog about typing while driving.

At a stop, report gas prices. Select a station. Tap No. Car starts moving. Try to enter a price and the following will pop up: It is impossible to enter gas prices because the "Passenger, Ok" dialog defaults and times out on Ok. The only way to get out of this is to hit back and re-select the station again. However, you could already be too far away from the station and the price update is lost.

Recommended fix: the "Passenger, Ok" dialog should first dismiss the keyboard if it is on-screen.

In general, requesting alternate routes is buggy and does not work reliably when you have a Stop Point in place. Most often, after an alternate route is selected, the pink line disappears even though the stop point still appears to be active. However, bringing up the route info shows the default "1min .1mi" display which never changes, and Waze is actually, at this time, routing to your final destination and not the stop point. The only way around this is to cancel the stop point, do your alternate route selection again, then add the stop point again. Very inefficient.

It is still unclear, when you do an alternate routes request when a stop point is active, which portion of the route is supposed to be affected: from start to stop point, or stop point to destination?

invented wrote:I'm finding that when I'm driving along my route, there will be random gaps missing in the route. When I approach a gap, it goes to recalculate.

Unclear if this is a client issue. I posted this to the NA map tiles thread in the Map forum as I think it's a map thing not an app thing?


--
If it looks strange, or I used bad grammar or misspelled anything, it's my phone's fault.

Waze categorically does not fully cache route tiles when on wifi. I've experienced this many times and captured more info about it today.


--
If it looks strange, or I used bad grammar or misspelled anything, it's my phone's fault.

But there are other bugs which crop up with autozoom off like if you aren't moving and bring up alt routes, go back without selecting a route. Waze transports you to coordinates 0,0 until you move again. I think that bug still exists...


--
If it looks strange, or I used bad grammar or misspelled anything, it's my phone's fault.

jasonh300 wrote:

AlanOfTheBerg wrote:But there are other bugs which crop up with autozoom off like if you aren't moving and bring up alt routes, go back without selecting a route. Waze transports you to coordinates 0,0 until you move again. I think that bug still exists...

Does this only happen in 3D mode? I've never gotten this to happen, but I keep mine in 2D mode.

This bug looks to be fixed.