Page 1 of 19

iPhone 3.6 official feedback thread

Posted: Wed Feb 27, 2013 1:19 pm
by
What's New in this Version

✓ Report road closures in real time. Waze will close off the road and route others around it
✓ Report pins tilted on map to better indicate direction of event
✓ Reduced map clutter by showing only relevant road names
✓ New moods!
✓ New inbox with multiple message selection
✓ Update gas prices popup: When in gas station users prompted to update price (Europe only)
✓ Optimized performance and multiple bug fixes

Re: iPhone 3.6 official feedback thread

Posted: Fri Mar 22, 2013 3:20 pm
by AggieJM
AlanOfTheBerg wrote:I really really dislike the non-switch of day/night mode when Waze has been running for more than 30 minutes before the time to switch. The way this is currently set up makes no sense to me.
Hmmm, is that the behavior? I've noticed an intermittent problem of not switching to night mode, but I hadn't factored in how long Waze was running before the switch. But I knew a restart took care of the problem.

Re: iPhone 3.6 official feedback thread

Posted: Mon Apr 01, 2013 2:17 pm
by AggieJM
I've had some issues with the Add a Stop function lately in 3.6 as well.

I was on a route last night and added a stop in the middle of the route for fuel. The time to the stop was calculated correctly, but it did not display the correct navigation directions to the fuel stop. The navigation directions appeared to continue on the path to my final destination. As I neared a prompted turn, the time to the stop was recalculated and displayed as the arrival time at my destination. I went past this turn and it recalculated to a new path, but this path also went to my destination and ignored the stop point. The ETA and distance were still showing correct to the stop point, but I was not given navigation instructions to that point.

Re: iPhone 3.6 official feedback thread

Posted: Wed May 22, 2013 3:58 pm
by AggieJM
Two issues I'm still seeing:

1) When Waze finds a better route or recalculates an ETA, the "new ETA" and "original ETA" values are reversed. The new ETA shows the original time, the original ETA now shows the new time.

2) When starting on a long route, the application will freeze momentarily on the window with the countdown clock on the 'Go' button. It will usually freeze with '6' showing on the button. If you just let it sit for a while, it will refresh the screen showing your position on route. But the waiting period can sometimes be quite long which makes it appear the application has frozen/crashed.

Re: iPhone 3.6 official feedback thread

Posted: Tue May 28, 2013 3:13 pm
by AggieJM
Another issue I noticed on my drive last night.

When there are multiple reports in the same vicinity along a route, Waze only shows the pop-up for the one farthest from your current location. For example, there was a spot where there were two police report and a car on shoulder report within a mile. When I was a mile from the first report, I received the pop-up notification. As the second report came into range, the pop-up changed to that report (even though I had not passed the first report). So I was unable to mark the first report as "not there" since the hazard had been cleared. I saw this numerous times last night and each time I was only able to update the very last report in the string.

It would seem that the correct behavior should be to keep focus on the closest report and only switch as you pass that location (after a few seconds) so that the report can be cleared or thanked if necessary.

Re: iPhone 3.6 official feedback thread

Posted: Sun Mar 24, 2013 1:24 am
by Ahnominus
I do a lot of driving to phone contacts. This current version has still impeded my ability to do so, where it was not a problem in the past. Overall the searching of points and contacts, and driving to them could be improved.

Further, a big problem is putting in an address manually. If something as small as the street name abbreviation is not to the app's standards, it will take you to a general point on that road generally at a major intersection.

It seems since 3.5.2, this has been the problem. I absolutely love this application, but these flaws REALLY hamper me trusting the application for specific point driving considering I used to be able to.

Re: iPhone 3.6 official feedback thread

Posted: Sat Apr 13, 2013 11:30 am
by aka_serge
enhket wrote:it has been 45 days since the last version was released. is the new beta/version going to be released any soon? :shock:
I think everyone on vacation :cry:

Отправлено с моего HTC One S через Tapatalk

Re: iPhone 3.6 official feedback thread

Posted: Wed Feb 27, 2013 5:16 pm
by AlanOfTheBerg
BUG (likely not app-specific, but a problem in the server queries): I ran into an occurence of Waze showing a traffic slowdown on a street connected to the slowdown. This was brought up previously in another thread.

Here's how the Report list looks for On Route in the menu. The issue is with the Spaniel Ct report:

http://imageshack.us/a/img23/3343/img0800.png

Here is how it looks after I tap on the report from the Reports menu (NOT A POPUP!):

http://imageshack.us/a/img836/9876/img0801y.png

NOTE: THIS IS NOT A POPUP. Despite that these alerts were on the route I am on, and within 5km away or so, I received NO POPUPS. This is clear evidence of the significant and long-term bug with missing popup alerts users have been complaining about since December.

Here is how the view looks at the the location of the street. Note that there is no slowdown on Spaniel Ct, but it is on Murray Blvd, which is connected to Spaniel Ct.:

http://imageshack.us/a/img46/9593/img0799.png

Debug logs were uploaded 2013-02-27 1AM GMT.

Re: iPhone 3.6 official feedback thread

Posted: Wed Feb 27, 2013 5:19 pm
by AlanOfTheBerg
BUG/Continuing issue with non-optimal decisions being made in determining which street names to display. Yesterday, I ran into the following, which, despite driving this road nearly every single day, I have never seen before.

The road highlighted in green is a private drive and is almost never driven on by Wazers. It is into a private area (equestrian center) and so would never be used for routing. This is an example of a poor choice of segment name to display on the app. Not to mention, the name is very long and goes nearly all the way across the (portrait orientation) screen:
IMG_0804.PNG
(72.6 KiB) Downloaded 3317 times
Location: https://www.waze.com/editor/?zoom=5&lat ... s=40464531

Re: iPhone 3.6 official feedback thread

Posted: Wed Feb 27, 2013 5:28 pm
by AlanOfTheBerg
General display bug/issue

I have seen this happen at this location every day for years, but never bothered to report it because it is minor. However, I don't understand how it happens.

The road segment in question is here: https://www.waze.com/editor/?zoom=6&lat ... s=40457442

In the app, when driving along this road, the personal indicator (arrow) has never tracked on the road itself. Never. Ever.

Now, with the new purple route road name indicators, I see that they too are offset from the road location. There is a lack of GPS arrows on that segment despite the fact that I and several other Wazers drive this street every day.

How is this happening?

Re: iPhone 3.6 official feedback thread

Posted: Wed Feb 27, 2013 5:35 pm
by AlanOfTheBerg
fabryx73 wrote:Also with 3.6.0 the non popup issue is present.
Agreed. As noted above in my post in red text, since December, traffic alert popups have not appeared for me at all. Not one except for friends online.