iOS beta 3.5.1.993 feedback thread

by **AlanOfTheBerg** » Sun Dec 30, 2012 2:52 am

Alert popup overlayed the next turn. Quite annoying. This happens when an alert pops up when Waze is recalculating the route. When this happens, the alert should automatically get pushed down.

: ImageUploadedByTapatalk1356835962.289669.jpg (24.7 KiB) Viewed 486 times

Logs uploaded at 6:58PM GMT.

by **AlanOfTheBerg** » Sun Dec 30, 2012 2:55 am

This type of alert should never ever pop up. There is simply no purpose to this. Either the app or the server should just delete it. An alert which only says the name of the city is just useless.

: ImageUploadedByTapatalk1356836108.789147.jpg (41.19 KiB) Viewed 485 times

by **AlanOfTheBerg** » Sun Dec 30, 2012 2:58 am

I am quite happy with the adjustments to the red light camera alerts. However, as mentioned before, in an urban setting, this alert may be on the screen for 3 minutes until the light is passed. This alert needs to be able to dynamically adjust based on ETA to the camera, IMO.

http://www.waze.com/user_blog/?p=48 · by **Shorty-CM** » Sun Dec 30, 2012 2:59 am

And muted when sound is muted. Why does the app *still* make any noise at all if it is muted?

AlanOfTheBerg wrote:I am quite happy with the adjustments to the red light camera alerts. However, as mentioned before, in an urban setting, this alert may be on the screen for 3 minutes until the light is passed. This alert needs to be able to dynamically adjust based on ETA to the camera, IMO.

by **AlanOfTheBerg** » Sun Dec 30, 2012 3:02 am

I have noted several times recently, getting N/A in my routes selections. What's up with this?

: ImageUploadedByTapatalk1356836550.956057.jpg (68.34 KiB) Viewed 479 times

iOS and Tapatalk have conspired to screw up this post.

by **AlanOfTheBerg** » Sun Dec 30, 2012 3:07 am

This is likely a routing server issue, but I've noted recently that when I select an alternate route when starting for work, if I make a turn not on the route as I leave my neighborhood, Waze recalculated back to the original route it wanted me to take, not the alternate route I prefer and previously selected.

iOS and Tapatalk have conspired to screw up this post.

by **Dave2084** » Sun Dec 30, 2012 10:17 am

[Long Post Warning]

First time out on the road with the beta yesterday as I've not been driving anywhere since it has been released. So here goes:

1. Performance issues. This is the least stable Waze beta I have ever tested, bordering on unusable for me. At random intervals the app would lock up for a period of time from a few seconds to a minute or so and be totally non responsive to any input and the screen would not update so I missed a few turns (luckily I knew where I was going). If you waited patiently it would always come back only to lock up again a few minutes later. If the app was minimised while locked up and then opened again you'd bee greeted by a 30 second splash screen then it would crash. This happened constantly on my 45 minute/30 mile trip. At no time did the app offer me the opportunity to upload logs. This was done manually a few minutes ago at 9.53am UK time, and yes I was in debug mode).

2. Speed Camera Visual Alerts. Same old story ... these pop up and as I'm a landscape user I CANNOT SEE THE MAP. However now the warnings seem to come up much earlier (measured in miles rather than feet) so I get to see even less of the map! How about I extend one of the Waze Dev's an invite to drive around Nottingham and see if they get lost as you rarely get to see the map there for all the Speed Cameras!

: IMG_2051.PNG (87.01 KiB) Viewed 437 times

3. Unable to find routing server when looking for alternate routes. When this happens not only do you not get an alternate route, but it dumps your existing route so you have nothing. If alternate routes fail it should retain the existing route.

4. Report menu with no Network Connection. If you open the report menu when you have no network connection you get a warning box, the ETA/Distance box also shows "Location and Time Saved". What for ... are we supposed to be able to carry on with our report later, if so it does not work.

: IMG_2053.PNG (79.88 KiB) Viewed 437 times

5. Foursquare Check In. From the approaching destination bar the text has been changed and you now "post" to Foursquare. This is incorrect it should read "Check In" as it does in the report Menu. Also why are the Facebook and Foursquare logo's not in full colour? It doesn't make then recognisable.

: IMG_2055.PNG (44.02 KiB) Viewed 437 times

6. Has the behaviour for the Approaching Destination Bar been changed? It seems to come up much closer to the destination now which is most welcome as I get to see more of the map in the final turns for my Journey

by **npv1459** » Sun Dec 30, 2012 11:36 am

Dave2084 wrote:[Long Post Warning]

1. Performance issues. This is the least stable Waze beta I have ever tested, bordering on unusable for me. At random intervals the app would lock up for a period of time from a few seconds to a minute or so and be totally non responsive to any input and the screen would not update so I missed a few turns (luckily I knew where I was going). [CUT]

Same issue yesterday during a trip only in gps mode and not in navigation(no destination set)
(I knew also where I was going

)
App locked-up for a couple of minute and no response to any imput.
Need logs or not??
Bye

by **meow01** » Sun Dec 30, 2012 5:05 pm

Dave2084 wrote:[Long Post Warning]

At random intervals the app would lock up for a period of time from a few seconds to a minute or so and be totally non responsive to any input and the screen would not update

I drove over 400 miles and I encountered the same issues without understanding what might trigger them.

Frequencies of occurence seem random.

by **Dave2084** » Sun Dec 30, 2012 5:59 pm

AlanOfTheBerg wrote:I am quite happy with the adjustments to the red light camera alerts. However, as mentioned before, in an urban setting, this alert may be on the screen for 3 minutes until the light is passed. This alert needs to be able to dynamically adjust based on ETA to the camera, IMO.

I'm very unhappy. They stay on the screen blocking the map for just too long.

Waze please make them smaller or give me a way to turn these off leaving just the audible alert and the cams on the map (with attention getting radiating circles).

In their current form my preference would be to NEVER see them