iPhone 3.5.3 official feedback thread

These forums are specific to the Waze mobile app. Post here if you experienced a problem while using the app, have a question about the app functionality or a feature such as navigation or search.

Moderators: Unholy, bextein

Re: iPhone 3.5.3 official feedback thread

Postby lakeyboy » Wed Feb 06, 2013 2:25 am

perlin wrote:
lakeyboy wrote:I noticed this error today. Traffic alerts generated by Waze (and not reported by the user) seem to be grabbing the wrong road name when Waze automatically reports.

Can you find another examples?

Was able to find another 2 examples of this behaviour:

[ img ]
Says "Catherine Av" when it should say "Stephensons Rd"

[ img ]
"Says "Elstone Ct" when it should say "Keilor Rd"

Looks to me like Waze gets the name from the intersecting side street of where the traffic jam begins instead of the road actually being travelled on.
lakeyboy
Australia Waze Champs
Australia Waze Champs
 
Posts: 543
Joined: Thu Jan 26, 2012 5:19 am
Location: Melbourne, Australia
Has thanked: 155 times
Been thanked: 256 times

Re: iPhone 3.5.3 official feedback thread

Postby n_street » Wed Feb 06, 2013 12:14 am

I have to agree with wlau. I like most of the recent enhancements except for the change with "Favorites" and "History". The "Favorites" are one click deeper, which doesn't sound like much, but general UI design tries to reduce the number of clicks to get to commonly used features. My "Favorites" by definition are commonly used.

Does WAZE research actually show that people pick addresses from history more often than they do from favorites?

With regards to "History", could there be a way to purge all history instead of having to go through them one by one?

Thanks!
n_street
 
Posts: 1
Joined: Sat Apr 09, 2011 8:21 pm
Has thanked: 0 time
Been thanked: 0 time

Re: iPhone 3.5.3 official feedback thread

Postby perlin » Tue Feb 05, 2013 2:20 pm

lakeyboy wrote:I noticed this error today. Traffic alerts generated by Waze (and not reported by the user) seem to be grabbing the wrong road name when Waze automatically reports.

Can you find another examples?
perlin
 
Posts: 1312
Joined: Thu Sep 16, 2010 8:42 am
Has thanked: 4 times
Been thanked: 74 times

Re: iPhone 3.5.3 official feedback thread

Postby lakeyboy » Mon Feb 04, 2013 8:07 am

I noticed this error today. Traffic alerts generated by Waze (and not reported by the user) seem to be grabbing the wrong road name when Waze automatically reports. The first screen capture shows the traffic jam on Highbury Road, however it is reported as Cumming Street, which is a side street off Highbury Road. The second screen capture shows where Cumming Street is in relation to Highbury Road.

[ img ]
[ img ]
lakeyboy
Australia Waze Champs
Australia Waze Champs
 
Posts: 543
Joined: Thu Jan 26, 2012 5:19 am
Location: Melbourne, Australia
Has thanked: 155 times
Been thanked: 256 times

Re: iPhone 3.5.3 official feedback thread

Postby AlanOfTheBerg » Tue Jan 29, 2013 4:39 pm

This morning I was on my way to work, following one of the normal routes. When stopped at a stop light, I received an "Oh, snap!" message without any interaction with the phone.

ohsnap_why.jpg
(53.32 KiB) Downloaded 1594 times


Problems here:
1. This is a very large popup
2. Despite being an oversized popup and on an iPhone 5, the text still doesn't fit on the screen due to overuse of whitespace and graphics and buttons too large. (How many years do we need to keep harping on about poor use of screen space?)
3. I don't understand "Info" and "Go there" because there's no indication what this popup is about. Why would I "Go there"?

This looks to be from a popup advertisement which failed to get information. As we've mentioned dozens of times before, Waze needs significantly better error handling and needs to stop assuming that nothing will ever go wrong with other parts of the system. This is an example of a popup which should never have come up on the screen in the first place.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23613
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4791 times

Re: iPhone 3.5.3 official feedback thread

Postby AlanOfTheBerg » Tue Jan 29, 2013 4:33 pm

perlin wrote:
AlanOfTheBerg wrote:BUG: 500ft turn notification happens at 1000ft (reported multiple times in beta testing)

Please send me (debug) logs that contains an example.

Not sure why logs are required. This is reproducable 100% of the time and I explained in detail already that Waze gives the "500ft" notification as soon as the distance to the turn goes from .2 to .1 miles. The problem is not enough significant digits or rounding, because the announcement is made at .19 miles, which is 1000ft feet, not 500ft.

In any case logs uploaded at 4:30PM GMT on 2013-01-29. I noted it specifically at (local times) on 2013-01-28 at 5:59PM, 6:05PM, 6:30PM, 6:31PM. However, as noted, it happens without fail, every single time a .1 miles notification comes up at the .19 mile mark.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23613
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4791 times

Re: iPhone 3.5.3 official feedback thread

Postby AlanOfTheBerg » Thu Jan 24, 2013 6:17 pm

OldGnome wrote:I can confirm that on an iPhone 4S running iOS 6.0.1, I get some returns on some searches.

I can get some results on 6.0.1, but sometimes, those search results have no match to the name being searched for.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23613
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4791 times

Re: iPhone 3.5.3 official feedback thread

Postby OldGnome » Thu Jan 24, 2013 4:34 pm

perlin wrote:We are aware of the problems with contact searching and working on fixing them. So far we've detected that waze doesn't return contact results on iOS that's lower than 6 and returns results partially on iOS 6.0.1 and up. If you have information that confirms or contradicts this, please share.

I can confirm that on an iPhone 4S running iOS 6.0.1, I get some returns on some searches.
OldGnome
 
Posts: 184
Joined: Sun Sep 23, 2012 7:14 pm
Location: Riverview, FL USA
Has thanked: 0 time
Been thanked: 28 times

Re: iPhone 3.5.3 official feedback thread

Postby perlin » Thu Jan 24, 2013 2:10 pm

AlanOfTheBerg wrote:I tested an concur that there is a significant issue with contact searching in 3.5.3

We are aware of the problems with contact searching and working on fixing them. So far we've detected that waze doesn't return contact results on iOS that's lower than 6 and returns results partially on iOS 6.0.1 and up. If you have information that confirms or contradicts this, please share.
perlin
 
Posts: 1312
Joined: Thu Sep 16, 2010 8:42 am
Has thanked: 4 times
Been thanked: 74 times

Re: iPhone 3.5.3 official feedback thread

Postby perlin » Thu Jan 24, 2013 12:02 pm

seriousarsonist wrote:So... Major issues today, first off, about 1ish (GMT) waze couldn't get a network, everything else was fine including twitter and iMessage.

Next up, about 20.45 (GMT) navigating home I was nearly home and waze asked if I was going home 3 times. Not sure what gives there. [ img ]

Also got told I couldn't do petrol prices as I am a baby, don't think so...
[ img ][ img ]

Thanks for reporting, we're checking your logs.
perlin
 
Posts: 1312
Joined: Thu Sep 16, 2010 8:42 am
Has thanked: 4 times
Been thanked: 74 times

PreviousNext

Return to Waze App

Who is online

Users browsing this forum: Bing [Bot]