Android 3.5.3 official feedback thread

[zCougar]

I'm not sure is it a client or server problem but something is wrong here. This part of freeway is in the city where speed limit is 50km/h. Client reported a traffic jam because speed was "only" 130km/h



Here is the map permalink

[zCougar]

To illustrate how we get penalized for having high resolution large displays I have photographed three of them side by side displaying same menus.

Nice

--
Cougar

[zCougar]

I'm still not happy with tablet UI. A lot of menus and texts are too small to be useful. For instance I almost can't read gas price numbers when my 7" Nexus is sitting on car dashboard.



I resized it specially so that it looks smaller than pixel-by-pixel screenshot. There are a lot of room to use big clear numbers that driver could see without moving all attention to those small numbers.

It can be argued about info popup and menu sizes where some may prefer to see more map and some prefer bigger popup. But in this case there is nothing else on the screen to justify this room saving.

--
Cougar

[zCougar]

Works fine as most of releases.

Tablet UI still needs more work. Menu is small and needs to be scrolled even there are a lot of room. Font size for gas price entry menu is tiny and almost not usable.

The biggest annoyance is that every audio prompt pauses media player. In previous release I lowered prompts volume and heard guidance when playing podcasts but now every beep and word from Waze pauses podcast. It is very annoying. Please restore the previous behavior or add a config option for that under sound settings menu.

--
Cougar

[world_msqy1rgs]

This mornig a freez of the phone while driving to Work. Same spot as 3 times before. This time in debug mode on. So log send ~20min ago
At this spot I also get the candy. not to day. (to less edits)

[Twister-UK]

I noticed that when I "munch" newly created roads, it shows the munching icon but the next day, the same roads are ready to munch again.

Try zooming in on those segments - I've seen what appears to be recently munched roads reappearing as unmunched, but if I zoom in then I get a normal looking segment with what appears to be an unmunched segment rendered underneath it, with just the edges of each dot showing either side of the cleared segment above. Zoom back out and this cleared segment stops being shown again, leaving just the unmunched segment on show.

[Twister-UK]

Feature Request: Better audio quality of the Waze navigation voice.

I did a comparison of Google Maps versus Waze, and Google's navigation lady's voice is much clearer and easier to understand, especially when there's a lot of road noise. The Waze lady's voice has less audio fidelity and sounds digitally compressed.

I had a look at the recordings and the TTS and saw the recordings have 44KHz and 320kbps whilst the TTS is only 8Khz and 32kbps.

That quality level seems like overkill for recorded vocals, especially vocals which are being played back through a phone loudspeaker in a moving vehicle - most of us don't even store our music at such a high bitrate for playback via headphones/decent quality speakers in quiet environments...

[Twister-UK]

In case of network failure while transmitting report, Waze should be able to buffer the report and sent it back again when network is back.
Actually, the report is lost !

Reported several times in forum, questionnaire and even at meetup, that the client has to remember all reports until they are sent successfuly and we mentioned situations where the network is not available on bad signal reception or during phone call when the old GPRS connection type is interrupted. I am pretty sure that the HQ is aware of it and the only information we miss from them now is when it will be implemented.

We are working on that option and will enable it pretty soon.

Whilst there are some other things I'd prefer the client to do differently, this is THE one piece of client behaviour that has really annoyed me since I started using Waze. So this change cannot come too soon, and knowing that it is finally on the way is excellent news.

[Twister-UK]

Found an annoying UI issue today, which possibly explains the ongoing issue I've had with reports seemingly going missing. When the client is displaying a pop-over window above the map, such that parts of the map remain visible around the edges of the pop-over, tapping on any of those pieces of map causes the pop-over to close.

When trying to submit a hazard report or similar, the Send and Later buttons are sufficiently close to the edge of the pop-over that it's easy to accidentally tap on the map rather than the button (especially on phones like the One X which seems to have a particularly sensitive screen), which then silently closes the report pop-over instead of queueing or sending it as expected.

A UI design which requires the user to tap one part of the screen to submit data, whilst tapping the almost-immediately adjacent part of the screen causes immediate and irreversible loss of that data, isn't a good design IMO...

[Twister-UK]

Cosmetic issue with text alignment on the petrol station selection screen...