Android 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.

Moderator: Unholy

Re: Android 3.5.3 official feedback thread

Postby foxitrot » Tue Jan 29, 2013 2:42 pm

Maybe a small unobtrusive pin (like these which pop up during a category search) popping up when approaching any GS vicinity would be sufficient. With "vicinity" I mean the same distance, which is necessary to update gas prices. Upon a click (tap), open the GS properties dialog, even on the Info tab...
...with the good old crashing :roll: Symbian 2.1.99.114 (N-E52), while
trying to get used to the good new social Android 4.0.xx.yyy (OP-X LOL-a-popp).
foxitrot
Waze Global Champs
Waze Global Champs
 
Posts: 6625
Joined: Thu Jul 14, 2011 10:22 pm
Location: Slovakia
Has thanked: 1915 times
Been thanked: 872 times

Re: Android 3.5.3 official feedback thread

Postby fotrik » Tue Jan 29, 2013 2:44 pm

Yes, could be sufficient too.
ImageImage
fotrik
Localizers
Localizers
 
Posts: 1755
Joined: Tue Oct 12, 2010 1:08 am
Location: CZ
Has thanked: 111 times
Been thanked: 118 times

Re: Android 3.5.3 official feedback thread

Postby perlin » Tue Jan 29, 2013 3:06 pm

fotrik wrote:
Autourdupc wrote: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.
Image
Join Waze. We have cookies..
perlin
Waze Team
Waze Team
 
Posts: 1312
Joined: Thu Sep 16, 2010 8:42 am
Has thanked: 4 times
Been thanked: 74 times

Re: Android 3.5.3 official feedback thread

Postby perlin » Tue Jan 29, 2013 3:11 pm

fotrik wrote:It's a month ago when the gas prices were launched in our country and most of the users which do not visit forums still don't know it. And if they know, they don't know that they can update them.

Could be nice to have an optional small popup window when comming near a gas station (like a speed camera or other warnings) where the reported prices will be shown with buttons "Confirm" and "Update" the prices. Of course this window should have also the 10 seconds auto-close. This would make it easier also for user who already report the prices.

That's a great idea and actually we've already created that option. It will enter one of the upcoming versions ;)
Image
Join Waze. We have cookies..
perlin
Waze Team
Waze Team
 
Posts: 1312
Joined: Thu Sep 16, 2010 8:42 am
Has thanked: 4 times
Been thanked: 74 times

Re: Android 3.5.3 official feedback thread

Postby perlin » Tue Jan 29, 2013 3:18 pm

jdeyoung wrote:I appreciate that there are lots more android devices than iOS, but it seems like the most recent version has quite a number of pure stability problems where the app crashes. That is not helpful when we try to rely on this for commute. I shouldn't have to worry whether whether waze has stopped or not. I have tried sending reports nearly every time waze crashes - and since it seems to happen nearly every time I stop moving, this results in 4 or 5 reports during my commute. Do we have any idea when we might see a beta for an incremental release on android?

You are absolutely right and we are aware of the crashes (that seem to have increased in this version).
Stability is always our top priority to handle and fix and we're about to release a much more stable version, in which we fixed most of the crashes that were reported.
Image
Join Waze. We have cookies..
perlin
Waze Team
Waze Team
 
Posts: 1312
Joined: Thu Sep 16, 2010 8:42 am
Has thanked: 4 times
Been thanked: 74 times

Re: Android 3.5.3 official feedback thread

Postby Twister-UK » Tue Jan 29, 2013 4:26 pm

perlin wrote:
fotrik wrote:
Autourdupc wrote: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.
L4 AM for NW London and Shetland Islands - HTC One M8/Android 5.0.1
Waze App 3.9.9.0, not about to switch to 4.x any time soon...
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Image
Twister-UK
Area Manager
Area Manager
 
Posts: 1932
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 256 times
Been thanked: 1512 times

Re: Android 3.5.3 official feedback thread

Postby Bikr » Tue Jan 29, 2013 4:28 pm

Feature Request: Tapping the "Thanks" button should close the report window.

If I'm tapping the "Thanks" button, it means I read the report. Why would I still want to see it? If I don't want to thank, that's when I'd actually tap the close ("X") button in the upper right corner.
Bikr
 
Posts: 5
Joined: Sat Oct 20, 2012 8:04 pm
Has thanked: 4 times
Been thanked: 0 time

Re: Android 3.5.3 official feedback thread

Postby Bikr » Tue Jan 29, 2013 4:32 pm

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.
Bikr
 
Posts: 5
Joined: Sat Oct 20, 2012 8:04 pm
Has thanked: 4 times
Been thanked: 0 time

Re: Android 3.5.3 official feedback thread

Postby davipt » Tue Jan 29, 2013 4:41 pm

bikr wrote: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.
ImageBruno D. Rodrigues | Global Champ
Coordinator for Portugal | Expert iPhone and others
Forum PT | Wiki PT | Facebook PT | Twitter PT
davipt
Waze Global Champs
Waze Global Champs
 
Posts: 2734
Joined: Tue Nov 02, 2010 8:51 am
Location: Oeiras, Portugal
Has thanked: 271 times
Been thanked: 556 times

Re: Android 3.5.3 official feedback thread

Postby fotrik » Tue Jan 29, 2013 4:56 pm

bikr wrote: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.

Please specify the language first and then if you have problem with the standard recorded prompts or text-to-speech functionality.
ImageImage
fotrik
Localizers
Localizers
 
Posts: 1755
Joined: Tue Oct 12, 2010 1:08 am
Location: CZ
Has thanked: 111 times
Been thanked: 118 times

PreviousNext

Return to Waze App

Who is online

Users browsing this forum: Bing [Bot], Erguitar, Google [Bot], MissPriss76, narendrn, onivaldom