This "feature" has to be given a kill switch ASAP. On the way home tonight I got caught up in traffic that wasn't yet shown on the map, and so whilst at a standstill I thought I'd manually check for an alternate route, knowing that Waze itself wouldn't give me one until it became aware of the traffic ahead of me. I started to pan around the map, but within seconds it relocated itself to show me the position of a traffic report several miles away. I hit the crosshairs and started panning again, only to be yanked away by another report Waze thought I'd be more interested in knowing about. This continued for about 30 seconds before I got utterly fed up with this damn stupid behaviour and just resigned myself to sitting through the jam. If the user has manually repositioned the map, the client should NOT be overriding the position until the user has tapped the crosshairs to restore the default position again.
Between this badly thought-out feature, and the cutesy UI tweaks which might look so cool when demoing Waze to your friends whilst sat at your desk/around the coffee table/anywhere other than behind the wheel, but which make the client just that tiny bit slower and more difficult to use than before whilst driving, not to mention the collection of annoyances from previous versions no-one at Waze seems to have any interest in fixing, i'm beginning to wonder just how much time any of the developers spend using the client in real world situations. Because whilst previous versions were at least useable most of the time, 3.5 manages to be an exercise in frustration with pretty much every single drive.
L4 AM for NW London and Shetland Islands - HTC One M8/Android 5.0.1Waze App 188.8.131.52, not about to switch to 4.x any time soon...WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store