iOS 3.8.0 Feedback Thread

[bz2012]

words from 'support'
I was discussing a problem with support and said:

Currently much more concerned with the MAJOR problems with the new IOS release.
....
See the ongoing discussion:
https://www.waze.com/forum/viewtopic.php?f=3&t=96661
....
I hope SOMEONE at headquarters is reading the thread!!!!

SUPPORT REPLIED:

We are reading all the feedbacks and also managed to reproduce most of them (like direction heard too early or late - after the turn), missing some alerts (meters alerts), missing some street names alerts etc.. we're working to fix all these bugs and will release them in the new fixed version (3.8.1).
About the BT sound, we'll try to reproduce it.
If you have more feedback about the TTS (other than what I mentioned: missing meters alerts, Last minute turn alert / heard the alert after the turn, missing some street names, Double roundabouts causing some TTS issues) please let me know.

I told support that it would be reassuring if someone 'official' would post such information here.
Support said they couldn't do that but they gave me permission to post a quote.

It IS good to know that they ARE reading this, isn't it????

[bz2012]

Just allowing voice commands isn't enough. I allowed them in the previous version.
Perhaps disable and re-enable might work, or switching to another app that uses the speaker and switching back, but we should NOT need to know magic words and arcane gestures to make features like these work.

'Switching to voice memo and adjusting the volume' will do it.
Tried it on the way to work this morning and it worked!!!!

[bz2012]

After applying this latest update from app store to iphone 4S, volume is too low to be helpful while driving. Using the volume button only brings up the ringer volume not the app volume.

It's been like this for years. Literally. You need to change the volume when a sound is playing or when voice command is activated. The hardware buttons only act on the currently open audio channel. Waze doesn't constantly keep the audio channel open, so when it's not playing a sound, iOS defaults the buttons back to ringer.

Never noticed that problem with the previous version. I DID need to turn the volume up the first time I used WAZE during a day, but it remembered the rest of the day.
Now, I can not get WAZE to put any sound out of the speaker at all.
It DOES use the bluetooth, when I have the bluetooth device turned on but even if I turn OFF 'prefer bluetooth' and turn on 'use speaker' it does NOT use the speaker (or the volume is zero and it doesn't let me turn it up).

The voice cues have gotten better now that the street name server seems to be working.

[bz2012]

checked this morning on the way to work.

Could NOT get the speaker audio to work period for WAZE while navigating.

Could get the bluetooth to work.

[bz2012]

The morning, no voice navigation audible.
I didn't have my bluetooth with me.

I DO have the option 'prefer bluetooth' but that SHOULD use the speaker if no bluetooth.

Either that or they should make the two choice:
use speaker AND prefer blue tooth so that they can BOTH be turned on at the same time.
(that would be the logical way to configure things)
1) both off, no sound
2) speaker only on, use only speaker
3) prefer blue tooth only on, use only blue tooth
4) both on, use speaker unless blue tooth connected, then use blue tooth.
The way it has been working, is that turning on 'prefer blue tooth' turns OFF the speaker button but if the blue tooth is not linked, the speaker is used, like option 4 above.
But it didn't seem to be working that way this morning.

[bz2012]

The new version still has a problem that I have reported many times:
The 'speaker volume' gets reset to zero over night.

I have 'prefer bluetooth' checked.

When I start in the morning without my bluetooth turned on, I hear NOTHING from the speaker until I turn up the volume.
When I head home at lunch time, WAZE remembers the volume from earlier and I don't need to turn it back up.

Sometimes, if I activate my bluetooth, the volume is the volume I have 'set' within WAZE.

I am not sure this problem is still here:
On bluetooth, when the volume was zero, if I used the volume control ON the blue tooth, it would use that volume for the current voice prompt and reset to zero for the next prompt.

[bz2012]

I DON'T find the 'and then' useful when there are several possible turning places in between the point where the 'and then' was issued and the actual correct place to turn.

I find it WRONG and DANGEROUS in those cases.

I agree that it IS useful in some cases, but previously I received correct instructions in such a case on my route home where I needed to make a left turn and then immediately turn right, the directions were correct.

Last night, along a different route to my house, WAZE told me to turn left (correct) and then turn right (incorrect because there were THREE wrong 'right turns' before the correct right turn.

For someone unfamiliar with the area, they would have gotten lost.
For someone in traffic, on an expressway, they could have had an accident.

If it had said ...and then turn right after 500 feet onto ... THEN it would be much better.

Sometimes, on the way to work, today, it did well by saying 'and then turn ... on ....'
However at one point, on the expressway, it gave too short notice at a point of decision. It needs to take driver reaction time delay and travel speed into account when it says 'keep left' at the start of an exit ramp.

[bz2012]

After the latest upgrade the verbal directions are terrible!
Often the verbal cue is too early.
It says things like
"turn right then turn left".
The only problem is that the left is 3 blocks away but it sounds like the left is immediately after the right.

Then sometimes the cue is late like a 'keep left' on the expressway, only given AT the point where you must keep left. No verbal cue before and nothing from the sign.

Another a cue too early and too cryptic to be useful.
Three blocks before a right turn onto an entrance ramp to the expressway:
"Exit"
No clue as to when or where or why.
At the ramp it said "Exit right".
Again no clue as to where or why.

These verbal cues are dangerous and misleading!

[buttercup19]

Just allowing voice commands isn't enough. I allowed them in the previous version.
Perhaps disable and re-enable might work, or switching to another app that uses the speaker and switching back, but we should NOT need to know magic words and arcane gestures to make features like these work.

'Switching to voice memo and adjusting the volume' will do it.
Tried it on the way to work this morning and it worked!!!!

Thanks for posting this workaround! It worked for me, too. I'm so grateful as I was about to go back to Google Maps navi.
To the Support team that reads these posts: the low sound is definitely an issue. Never had an issue until recently. App isn't usable without hearing the navi audio directions. Can't be looking at the map while driving a car. I'd bump the bug up to "fix soon" status if I were you. Thanks.

[brewbyte]

You only get the "Hold up" screen if you've already disallowed waze access to your contacts, or you perhaps have a Settings > General > Restrictions > Privacy in place to disallow changes to your contact sharing.

That was it, thanks!