Android beta 3.5.3.906 feedback thread

[Suik]

After a clean install I received twice the message that the application waze stopped working and actually started at third attempt.

[Wajo357]

I tried testing the road closure feature at work and I assume it isn't working because I don't have a GPS lock. You may want to let the user know this to be a bit more user friendly.

Also, since you have now implemented this feature, do you have plans for the user to be able to avoid parts of the route when looking at the turn-by-turn directions? I liked (back in my TomTom days) the ability to select step 7 of my route and avoid it, knowing I just don't want to go down there. I assume these 2 features go hand in hand - both avoid parts of the route based on user input.

[davipt]

Also, question for the devs, how does the 'Duration' part work? Is there a timer on the closure, a comment on it...? - in other words, what ultimately clears the event? (As with the above, depending how implemented, this may be a first step toward 'Time based road closures and turn restrictions' with start times/recurrences in the future.

Or better question, how does one remove a closure done by mistake^wfor testing? 8|

[xteejx]

Yeah I've done that just now. Drive through it? Umm...help?
Road closure is nice but I guess until things are done on the backend it's just an "avoid this road". But surely that can be done at a junction by driving another way?
I know it's in beta and I'm not trying to knock it at all, just saying. It's the start of something very promising indeed.
If for now it will only be device dependant, we need to select roads further away.
Also, it needs big enough buttons to press while driving. Currently it's too small and finicky.
Addresses in recent destinations cannot be seen, they're shifted too far down. Same in last beta.
Whatever happened to the voice recording for reports?

Other than that, amazing work as always. Looking forward to seeing what results from this road closure we've been waiting for. NOW Waze is becoming a serious threat as a general consumer GPS app

Sent from my GT-I9100 using Tapatalk 2

[fotrik]

The road closure report works great with one problem found. No matter if Hazard, Construction or Event reported, all three types are then shown as Construction in the report list.

[Suik]

The road closure report works great with one problem found. No matter if Hazard, Construction or Event reported, all three types are then shown as Construction in the report list.

same here

[Suik]

When I tried to update the prices on GS via the automated popup (see here), I got a screen with just N/A's instead of last prices for that gas station. When I checked the same GS via Navigation -> Categories, the prices were displayed as usual. Sending logs (8pcs) now.

"-1 wazer" still present also...

[Nacron]

Haven't tried the closed road feature but it's nice to have. On my Tom Tom there was an avoid area feature and it would reroute you around it.

Is Foursquare integration removed in this build? I can't find it

Sent from my SPH-L710 using Tapatalk 2

[waasup42]

Installed after work and briefly tested on the drive home. No functional problems found. Help - > About incorrectly shows version as 3.5.99.905

Sent from my Nexus 7 using Tapatalk HD

[foxitrot]

After setting closures and disallowing all directions with green arrows through a junction, Waze still chooses a route either through red arrows, or through the disallowed directions, or makes even a Uturn through a red arrow AND a short segment.

Ouch these penalties

[edit] On other place, also on a split minor's one way segment, I was directed to turn left to a street already behind me.

I admit these are tricky situations, I'm also not sure, whether I'd prefer "Uh-oh could not find a route" over a broken rule.