khaytsus wrote:Getting really sick of the client crashing at every stop from ads. Really, really sick of it.

Sent dozens of logs both in client and android reports.

You were in debug mode?
If you are, please post the time and date it happend and also time and date when you've send the logs.
Thanks!

perlin wrote:

deeggo wrote:Well, decided to find out myself. Locked myself in at home in all possible directions. Then fired up a second phone which would easily give me routes in all directions, not taking closures into account, no warning or mention of closure whatsoever.
So, big launch and the main new feature is completely dead.

Well duh, of course we won't let just one user to be able to close roads for all others. We've set up a special configuration - a set of rules - that determines how this feature should behave - it evaluates the user's rank, the number of closure alerts that have been reported and it also takes under account the road type (2 users with low rank will be able to close a street but not a freeway (just an example)).

I guess you know deeggo is not a low rank user, but a very high rank user.
Also his house is not on a freeway

No trafficjam visible: Idem: This is not the Distributieweg:

Missing button:

darkneon wrote:I can't find a reply button when i received a message from a Wazer.

Verstuurd van mijn GT-N7000 met Tapatalk

Me too!

No button:

That's the Waze blackhole.
Everything that goes wrong ends up there.

o.oo, o.oo

When adding a stop, the route goes to the stop. Then after that back to the point where I'm now and then continues to the final destination.

I almost never get the fastest route btw, when having a stop.
Also when I'm leaving the freeway an exit too early it (heading for my final destination) it lest me go back to the freeway the leave at the correct exit.
Example:
http://goo.gl/maps/6KyNY
I took the exit right after 'A'.
Then I got that route.

I now quite often have the problem that map tiles are not loading fast enough. This sometimes leaves me with only the purple navigation line on screen which is not very useful.

At the same time it seems that there are now two different versions of map tiles: zoomed in and zoomed out? sometimes one of them is loaded and the other not, which results in the app switching between "no map" and "map" when my Auto-Zoom is changing...

Maybe it would make sense to preload all the maptiles along a route when starting the journey? Or compress the data to make the transfer quicker?

Assuming that map tiles are getting refreshed on a more frequent basis now, they probably need to be downloaded to the phone more frequently as well... So this problem might occur even more in the future...

don-quijote wrote:Hello

Today I report police twice, and both time after I get "you helped" message - map was faded to black, only bottom menu button stays active. All others working but map was black. When i press left menu button - main menu appeared and map became visible.

I am experiencing the same issue. Using Galaxy N7000

everything works just fine as long as you dong press that Report button at the lower right corner, pressing it will show the usual Report Menu but once you go back to the map itself, it will just be BLANK, pressing the menu/report button will let you see the map (dimmed) with the menu on top but will just do the exact same thing when going back to the map. the only solution is to restart the app to see the map again.

http://imageshack.us/a/img18/8123/20130302095858.png
http://imageshack.us/a/img259/5548/20130302095906.png
http://imageshack.us/a/img829/9003/20130302095915.png
http://imageshack.us/a/img62/5766/20130302095923.png
this is frustrating.