iOS Version 3.1 Feedback Thread

[AlanOfTheBerg]

I agree that they need to add more touch buttons for weather. Ice is the most-often requested one.

[dlangille]

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.

Confirmed. Thank you.

[markwu]

I had high hopes when the release notes for 3.1.1 said that it fixed audio output issues, but I was disappointed. The issue I reported earlier for version 3.1 still has not been resolved (see earlier posts in this thread). I have Waze set to play output through the speaker, and regardless of the volume settings in the application, it still uses the volume set by the last app that played sound. And I can't increase the volume unless Waze plays a sound, because it always shows up at full volume (even though it doesn't play that way). So I spend the first few turns of my drive fumbling with my phone to try to raise the volume when the app is trying to tell me directions. This is much more dangerous and distracting than version 3.0, before the sound volume setting was introduced, and all I had to do was raise/lower the volume at any time (the system volume) before I started moving.

I don't know if it's a Waze problem or an iOS problem, but hopefully they'll find this problem and fix it soon!

[jasonh300]

I noticed this weekend that when I have Waze running for a long time (hours), the volume gets lower and lower.

I discovered that if I put the phone to "sleep", the volume becomes so loud there's some distortion. If I wake it back up, the volume drops again.

Also, I had the little "battery at 20%" popup come up the other day, and before I could kill the battery message, Waze gave a turn instruction at a very high volume.

These were all the Waze TTS, not the iOS TTS voice.

[AlanOfTheBerg]

I noticed this weekend that when I have Waze running for a long time (hours), the volume gets lower and lower.

Did you go into the Sound settings and watch what the device volume changes to when Waze makes a sound?

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

[invented]

Audio output is still wonky. I use Sound Check, not sure if that matters. When in my car, I use my iPod control-enabled deck, and sounds go through that. The caveat being that you're only going to hear waze instructions when the deck is on the iPod dock connector input. Also, the volume keeps getting lower and lower with music when waze is active. Just today, waze faded out the music entirely, issued a command, then didn't even raise the volume back up, leaving complete silence. I had to replug the dock connector to force a re-sync with the deck. Another weird problem is having a song playing, going forward then backward, and now the song is quieter.

[dlangille]

Invented: Many times I've seen Waze mute my music. The solution: restart waze. :/

[AlanOfTheBerg]

Based on audio interactions of apps in general, I am fairly certain that some of the errors we have with audio are due to iOS. It handles the audio output, so when one app wants to use the speaker instead of bluetooth or dock connector, it is iOS which does all the fade/pause work. iOS allows only one audio output at a time. It can be multiple apps outputting simultaneously, but all to the same output. If an app doesn't specify the output method, it is automatically routed to the currently in use output.

[tasmaine]

I have to say I hate this version - it simply does not work. This week I drove both 150 miles south of Portland, ME (i.e. south of Boston), and 150 miles north (north of Bangor). In neither case was I able to connect to a signal, even though I have no problem connecting in Portland. It was kind of weird driving on the Interstate and the app not even recognizing that I was on a road.

So, not only is it a bummer that I didn't get 1000 points for driving 500 miles in one week, but I've rapidly concluded that I cannot rely on Waze. I guess it's time to get a real GPS, if I want something I can rely on.