Android 3.5.3 official feedback thread

[Autourdupc]

Since a fix some 1-2 beta versions ago, when a user/report popup is displayed, it is sufficient to click the map anywhere around it (or at it, except its buttons) and the popup will be closed, not necessary to look for [ X ] or the tiny (x) button anymore.

Unfortunately the same happens when a report dialog is opened (in contrast to a popup window, this is not only some informational area, which can be repeatedly opened again), but well, one can get used to it. But the Radar/Camera report dialog differs from the others - there is a pretty large informational area in the middle of it and inadvertently touching it (while trying to tap on any of surrounding buttons) causes the dialog to disappear - its GPS position is gone. The same is true for all dialogs, when touching their title bar.

The whole area of all report dialogs (except their [ X ] and [ Send ] buttons) should be excluded from closing them.

And [ X ] is too small !
Should have a true button for that !

[foxitrot]

Yesterday I've got a few identical crashes on a gas station. It had the 1st and 4th price defined, the middle two were N/A. While trying to define and report also the missing ones (all at once) and click between the fields, the client always crashed on the last one. Finally I had to define and report all four prices one-by-one.

[foxitrot]

And [ X ] is too small !
Should have a true button for that !

That is another story. On Android, Waze apparently attempts to mimic iOS' buttons on the upper left/right corners of dialog windows. But the attempt is just half-baked usually a button consist of at least some border, which highlights its (clickable) area (rectangular, elliptical, circular, whichever) and some description text inside. iOs' buttons are additionally e.g. gray on a black title bar area. Waze buttons ... can be just guessed one can see only its description text. And if these buttons get also scrolled up above the dialog area

Waze, please, modify these buttons ASAP! It is sometimes really a pain to notice them (especially after reading some texts down to the dialog's bottom, to finally confirm them)!

[Autourdupc]

And [ X ] is too small !
Should have a true button for that !

That is another story. On Android, Waze apparently attempts to mimic iOS' buttons on the upper left/right corners of dialog windows. But the attempt is just half-baked usually a button consist of at least some border, which highlights its (clickable) area (rectangular, elliptical, circular, whichever) and some description text inside. iOs' buttons are additionally e.g. gray on a black title bar area. Waze buttons ... can be just guessed one can see only its description text. And if these buttons get also scrolled up above the dialog area

Waze, please, modify these buttons ASAP! It is sometimes really a pain to notice them (especially after reading some texts down to the dialog's bottom, to finally confirm them)!

Argh ! Android is not IOS... If I wanted an IOS system, i already bought it !
And if I own an Android system, it is because I don't want an IOS !
IOS is opposite to Android. So, Waze, please do a good job on android and what you want on IOS.
Give us good screen interface and not poor pop-up or ballon, on which we need to have a little finger, a good eyesight and a big brain storm to understand how it works !

Don't forget that we use Waze while we are driving in our vehicule... Informations should be simple to read, understand and use !

[perlin]

Yesterday I've got a few identical crashes on a gas station. It had the 1st and 4th price defined, the middle two were N/A. While trying to define and report also the missing ones (all at once) and click between the fields, the client always crashed on the last one. Finally I had to define and report all four prices one-by-one.

Please send permalink of the station. Maybe it's related to its location.

[foxitrot]

Yesterday I've got a few identical crashes on a gas station. It had the 1st and 4th price defined, the middle two were N/A. While trying to define and report also the missing ones (all at once) and click between the fields, the client always crashed on the last one. Finally I had to define and report all four prices one-by-one.

Please send permalink of the station. Maybe it's related to its location.

Here it is: https://world.waze.com/editor/?lon=17.1 ... rks=250060 Would be interesting.

[perlin]

Map chat do not stay on screen when not sent.
To reproduce :
1) Tap on bottom right button and select Map chat (see arrow 1)
2) Let the countdown reach 0. The unset map chat comes to map screen (see arrow 2)
3) Tap again on bottom right button (see arrow 3)
--> Map chat is deleted !

Screenshot_2013-01-27-22-55-45.png

Can't reproduce. Can you try again?

[olestas]

Android 2.3.3. LG P500.
Crashing when searching while route is active.
Crashing just like that.
GPS disappears after second/third launch.
Logs sent (no time).

[perlin]

Yesterday I've got a few identical crashes on a gas station. It had the 1st and 4th price defined, the middle two were N/A. While trying to define and report also the missing ones (all at once) and click between the fields, the client always crashed on the last one. Finally I had to define and report all four prices one-by-one.

Please send permalink of the station. Maybe it's related to its location.

Here it is: https://world.waze.com/editor/?lon=17.1 ... rks=250060 Would be interesting.

Failed to reproduce.

[Autourdupc]

Map chat do not stay on screen when not sent.
To reproduce :
1) Tap on bottom right button and select Map chat (see arrow 1)
2) Let the countdown reach 0. The unset map chat comes to map screen (see arrow 2)
3) Tap again on bottom right button (see arrow 3)
--> Map chat is deleted !

Screenshot_2013-01-27-22-55-45.png

Can't reproduce. Can you try again?

I can reproduce it each time I do it !
Watch the video...
http://www.monvendeur.com/VID_WAZE.mp4 (7 Mo)