iOS beta 3.5.99.2 feedback thread

[perlin]

I am sure you are aware of this, as you responded to a previous post similarly, but the inbox functionality on iOS is totally broken.

I'm not sure what you mean by "totally broken", but we're working on some fixes regarding it.

[AlanOfTheBerg]

I am sure you are aware of this, as you responded to a previous post similarly, but the inbox functionality on iOS is totally broken.

I'm not sure what you mean by "totally broken", but we're working on some fixes regarding it.

What I mean is no private messages ever appear in it with this beta. I had a multiple message conversation ( pm not map chat) yesterday and no messages from the other wazer appeared my inbox. I was hoping to test the ability to reply from there.

[AlanOfTheBerg]

I am confused on the ASR activation method. I've done a "single wave" and it seems to work. I'm unsure what a "double wave" looks like. The menu item in the Settings still says "Hover" so that should be changed to whatever the action actually is.

If it works after a single wave- it's a bug. It should work after hovering the hand above the screen once and then backwards (left and right). We will rephrase the setting so it'd be clear enough.
Also on that topic- what do you think about this activation method? Convenient? Not convenient?

I find it less convenient, but I also had no issues with the previous method. Some people did. I have learned to work with it now.

[AlanOfTheBerg]

Are you guys planning to have mute mode configurable?

For sure we appreciate that now we can mute our device completely but if one may be allowed to hear only traffic alerts, that would be nice too. I mean, if it's not planned yet as a future feature.

We decided to revert the feature to what was before (mute button will mute only prompts and not alerts).

I really do feel it would be best to have two mute modes: Mute All and Mute Nav.

[AlanOfTheBerg]

We've set up a new zero-speed popups mechanism, that displays up to 4 alert popups at stand-still, in relation to your location near events. If you select to see events on your route only, the popups will be displayed up to 100 km on your route. If you select otherwise (and it doesn't matter which radius you'll choose), they will be displayed up to 5 or 10 km. If you're not near any event, nothing will be displayed when standing still. (you're now probably asking "then why do you still have the old radius selecting if you ignore it". The answer is- we'll change that).

So, it may be the "5 or 10km" part of your post that is filtering. I will need to test more closely. But why did you write "5 or 10"? Which is it? Or does it select 5 or 10 depending on situation?

I have received friends online and ad popups when stopped at an intersection, but I have not received any traffic/alert/hazards popup when stopped for over a month now, since before this beta. I do still get hazard alert and group alert popups while driving, as expected.

So, you are saying that the "Event Radius" selection purposely has no effect any longer? I think that would be important to mention in beta testing release notes.

[sketch]

Bug: the "Wazers nearby" popup found itself in the wrong place the other day.



I don't know why it was here, but it persisted for the entire drive. Tapping on it did nothing.

I am sending logs now. This occurred on Feb 4 around 14:33.

-----

Request: the next turn should be given priority on the nav line.



In this example in particular, the Wazer would benefit more from the nav line if it pointed out the small U turn segment. This instance illustrates the need for this prioritization a little more strongly, I think.

-----

Request: the nav line should show ramps.



(In this image, the "ramp" name is shown, because the "ramp" is set to Freeway type for navigation and display purposes.)

Even if the client didn't parse out the exit number, instead simply displaying the exit text, I think it's better this way.

[jasonh300]

In sketch's example above, the "610" is an interstate. Is that the former shield functionality causing that? On interstates where the shields are broken (ours work), would it show "610" or "I-610"?

How about making that "610" into an interstate shield?

[milkyway35]

When select dog or cat mood, icone in menu do not match the "My Waze" button

[AlanOfTheBerg]

In sketch's example above, the "610" is an interstate. Is that the former shield functionality causing that? On interstates where the shields are broken (ours work), would it show "610" or "I-610"?

How about making that "610" into an interstate shield?

I posted something similar related to the state shield, where waze shows "219" in purple and the state shield. I don't like the "219" in the state shield. As also noted above, some places show "I-##" in the purple and some show just the route #. It's a mish-mash and no one has told us how the value in purple is arrived at.

[CBenson]

Request: the nav line should show ramps.

I would vote against this.