iOS Version 3.1 Feedback Thread

by **FrisbeeDog** » Sat Mar 17, 2012 8:39 pm

scottfrey wrote:
jamgramet wrote:With the previous version, I would listen to a podcast on my car radio while using Waze. With this new release, the sound is turned off once I start up Waze. I'm using an iPod supported connector in my car - not the simple headphone jack.

I tried turning off the Waze audio input.

This problem means Waze is unusable for me now.

Same problem here, Using Downcast to listen to podcasts

This release is worse than the last beta with these issues. I was hoping they would keep releasing betas until they fixed it as every beta had "audio fixes" in the release notes.

I too have big problems with TTS and Waze connected via dock connector.

by **invented** » Mon Mar 19, 2012 7:43 am

AlanOfTheBerg wrote:
invented wrote:Is there a way to turn off the proximity sensor in Waze? Highly annoying.

In the Settings.

I do not see any setting for proximity sensor.

by **jasonh300** » Mon Mar 19, 2012 9:31 am

What are you referring to as a "proximity sensor"?

I'm not drunk...I'm using Tapatalk.

by **AlanOfTheBerg** » Mon Mar 19, 2012 3:40 pm

invented wrote:I do not see any setting for proximity sensor.

It is for voice commands, so look under voice commands activation method.

by **TheBuca** » Tue Mar 20, 2012 12:14 am

Had a new bug today. iOS 5.1 using v3.1.1.

The highway is about 200' from my office building. The GPS had me in the correct place on the road infront of my building, the routing had me correctly being routed about a mile and a half of road in order to get on that highway, but there was a hazard reported close to my building. I was physically located 500' from the hazard so I had a warning saying it was in 450', but in reality it was probably 2+ miles of road.

Seems like it threw up the hazard warning based on my proximity to it rather than the road miles to it.

Unfortunately I couldn't grab a screen shot. Maybe someone can reproduce it and provide more info.

Sent from my iPad using Tapatalk HD

by **AlanOfTheBerg** » Tue Mar 20, 2012 3:31 am

TheBuca wrote:Had a new bug today. iOS 5.1 using v3.1.1.

This is a known bug, probably not on the list of known issues, that alerts like accidents, red light cams, etc, will pop up if you're within a certain radius of that item.

by **foxitrot** » Tue Mar 20, 2012 4:57 pm

AlanOfTheBerg wrote:
TheBuca wrote:Had a new bug today. iOS 5.1 using v3.1.1.

This is a known bug, probably not on the list of known issues, that alerts like accidents, red light cams, etc, will pop up if you're within a certain radius of that item.

True, happens even on my old Symbian. The problem is that the distance to the alerts/etc. is not measured along the route. I hope this will be ever implemented.

by **zpb52** » Thu Mar 22, 2012 3:26 pm

Yeah, ever since the last update, I have also been having trouble with the proximity sensor. I have all voice commands turned off, and it's still a problem. As I'm driving, sometimes the proximity sensor will pick up some movement and the screen will go off. I, then, have to put my finger back on top of the proximity sensor for it to come back on. Sometimes, I have to do this 3-4 times in succession before it finally stays on for a little while. Highly annoying.

by **MaliciousWolf** » Sat Mar 24, 2012 6:05 pm

zpb52 wrote:Yeah, ever since the last update, I have also been having trouble with the proximity sensor. I have all voice commands turned off, and it's still a problem. As I'm driving, sometimes the proximity sensor will pick up some movement and the screen will go off. I, then, have to put my finger back on top of the proximity sensor for it to come back on. Sometimes, I have to do this 3-4 times in succession before it finally stays on for a little while. Highly annoying.

Lol, so it isn't only me? I have an entire thread dedicated to this issue here: viewtopic.php?f=3&t=17540&start=10

I've logged the bug and submitted it to waze and opened a support ticket on it as well. Should be fixed in next update hopefully. For now, a temp fix is to turn voice command off, and also change it from "Hover & 3 finger" to "3 finger tap only" in the voice command settings.

by **invented** » Sun Mar 25, 2012 1:18 am

jasonh300 wrote:What are you referring to as a "proximity sensor"?

I'm not drunk...I'm using Tapatalk.

The proximity sensor on the iPhone. It should have no bearing on how I use Waze, and yet, Waze is responding to its input.