1: I don’t know if im doing it wrong but my points do get added up properly(if at all? i think) i’ve logged out and back in a few times to see if that would fix it but i still only seem to get about 100 points a day and that isn’t reflected in the scoreboard.
2: Randoml with out even touching my phone(i.e it’s sitting on my seat i’ll notice that i some how did a traffic update while sitting at a light or in a drivethru. is there something that is like a confirm update dialog in waze?
3: when i do find something wrong and go to report it, the program doesn’t seem to let me just select which street i want to report, it only wants me to report the actual street im on… which if the street im trying to report happens to be a private street and cant access it that i dont see how that is any good.
4: i’ve read a few posts on here but i can’t seem to have my cookies saved on the wazesite/forums.
Overall i love the program and i love that it gives me an actual excuse to just drive around aimlessly in my city. i hope these are just common problems with easy fixes, i searched for the answers but the forums search doesnt seem to ever give me actual results i was hoping for.
Points in the ticker are approximate. Once a day the client asks the server what your real point value is, then it gives you points that day based on what the client thinks you will earn.
The points are really calculated on the server though. So it is possible to “loose” points, because the client gave you points that the server says you didn’t (gps track was off. munching points you have already earned on the server side, etc.)
And finally, the points on the server are calculated when your driving routes are analyzed. This is designed to be once a day, but if there are high loads on the server or a mass update of the maps going on, this can be delayed. So people experience some points drifting. I presume that any delays in the processing will then also effect the scoreboard display.
The server tries to analyze Wazer’s movement in real time and based on the average speed for a segment detect when traffic/congestion is more than normal. The servers try to ignore small sections of slowness, but there are times when “false alerts” do happen. The development team is continually tweaking this, and the common response to these reports, is that if another waze user travels the same section, the report will get removed (faster than the timeout).
There have been discussions about different ways to report from the client, but currently it marks the position at where you press the report button. Being an area manager myself, I request that if you can, please provide details in the text box. If you can’t enter text right away, it will put the report in the side of the client, but I believe you can only have one pending, so it’s best to enter details as soon as you can.
The road munching dots can reappear if an map edit causes the server to want to re-validate the road, or if the analysis of your driving route on the server did not match up well enough to give you the “real” credit. The client shows you what it thinks you are getting points wise, and road munching, but the server has the final say, as it does a more in depth analysis.