iOS Version 3.1 Feedback Thread

[perlin]

Essential for accurate voice recognition: ability to give commands over a bluetooth headset.

There is an option to give voice commands over a bluetooth headset. If it doesn't work, there is a toggle to prefer BT under sound settings.

Bug: Even with voice commands turned OFF, the proximity sensor is still active and blanks the screen when your hand gets close.

Can't reproduce. Does it happen to you every time? Can you give a specific scenario?

[perlin]

When the voice control function will be available for other countries?

We're still not sure about that, but we appreciate your patience.

[perlin]

I believe this doesn't happen now. Perhaps it just didn't turn off right away, but I will double-check.

I had the same issue when I did a fresh install of Waze 3.1. Even though Voice command was disabled by default it seems that it was still partially active. The screen will dim when waving your hand in from of the iPhone. I reconfigured the Voice command options in settings and it no longer does this. I do have Voice command enabled with the 3-touch option only.

Likely in order to reproduce the Waze application will need to be removed and freshly installed. I restarted my iPhone after removing and prior to reinstalling Waze 3.1.

I was able to reproduce. Apparently this is happening only when first running waze. You will see that if you close and re-open, it won't happen (the screen won't dim).
The proximity sensor is active in initial start in order to allow the ASR message pop (which allows you to choose between Enable/Later). The bug is that the sensor won't turn off when you tap "Later".

Thanks for letting us know.

[perlin]

I'm chiming in to report the same issues being mentioned elsewhere: Waze is no longer audible, no sound is coming through the phone or bluetooth, and music playback stops when I launch it, which was not the case beforehand.

I'm having similar problems. Since the 3.1 update, I get almost no sound. (I think it's there, but very faint.) I've tried changing my main volume, changing my ringer volume, turning bluetooth on or off, toggling the sound through the speaker, toggling the "Prefer Bluetooth" option, and none of it helps. I do use the phone connected to the Sync system in my car (which has its own problems), but 3.0.1 had no such issues. I love that I can set a volume for the app itself now, but only if it actually worked.

iPhone 4S, 5.0.1 (AT&T)

Mark-

I was having the same issue and it was driving me crazy... But then I figured it out. There is a separate OS related volume, that I can't seem to access anywhere, except when noise is being played. Try this... Click "Navigate" then choose a location (home, work, etc) then when the route summary appears click "Go", then immediately, click the "up volume" on the side of the iPhone and you will see that the "OS related volume" was low... (or at least it was on mine).

(The point of this method is to force waze to play audio "Let's go" and then tell the iPhone that you want the volume to be higher on that audio)

thenbagis, you are correct.
The audio problems will be fixed for next version.

[perlin]

thenbagis, you are correct.
The audio problems will be fixed for next version.

Awesome! Any time table for the update? (i.e. will it be a maintenance/bug fix release... maybe 3.1.1. or will it be more of a feature update 3.2)

It will be fixed for the next beta version, but don't have estimated time.. sorry.

[perlin]

When using the Sound, Navigation Guidance set to "Include street names" , the pronunciation of "Glisan" is said with a hard "I" sound (i.e. Gl-eye-son) instead of the hard "E" sound (i.e. Gl-ee-san).

Is there a way to use the map editor and the Alternate Street Name to correct pronunciation issues?

We're working on it. It will be possible in the future.

[perlin]

I keep my Waze, navigation guidance set to None. I cannot find a setting to mute the audio of "reports" such as "Hazards, accidents or police."

At the moment there isn't any option to mute the audio for reports pop-ups, only for navigation guidance.

[perlin]

At night, the screen dims, but also dims every other application.... Is that by design?

That's the iOS brightness setting you have selected.

Interesting.

Why does only Waze activate this dim?

I will experiment tonight. I have turned the brightness to max and turned off auto-dim.

Currently it's by design (since 3.1.1) and it's according to Apple's guidelines. But we're working on improving it, so it will only affect our app. There is an auto-brightness option in the settings, however I'm not sure it's related.

[perlin]

I'm noticing with my iPad (Retina) while navigating in Waze that some popup notifications are showing up partially offscreen. They usually seem to overlap the bottom of the screen (making the close button impossible to see/tap). I usually use the iPad in landscape mode, so I'm not sure whether it happens in portrait mode or not.

We fixed it for the upcoming version.

[perlin]

Where to post or correct a translation bug in the iPhone client ?

You can post it here or send it to beta@waze.com

Thanks.