Did try changing to metric on the way into work tonight, but didn't make any difference.

Logs sent today at 16:31 BST

Picture below

http://i160.photobucket.com/albums/t163 ... 57919c.png

Hi Dave.

As requested:

Samsung Galaxy S4, Android Jelly Bean 4.2.2 with Waze 3.7.2.

It was in debug, I had the little red 'debug' next to Menu.

Edit : ...and yes, that's the correct camera.
The screenshot from page 1 of this topic is from the next southbound camera where the exact same happens, though I've since deleted that camera, added it back in (2666471) and approved it. Just waiting for the map tiles to update so I can see if it's any different.

Already tried on way into work last Saturday. No difference.

Dave2084 wrote:One last thing to try ... dump you map cache as although when routing Waze loads the latest maps for your route it DOES NOT update speed cams.

Didn't work, but good that they've accepted it as a bug.

Thanks Dave.

Had audio notifications on for the first time today.

The audio alert prompts at the correct position, i.e. at the actual camera position. Can be a bit worrying when the audio prompts and you then notice the countdown only has 120 feet left. Especially on the motorway.

Dave2084 wrote:What is the current play marketplace version?

3.7.2.0, so it should be fixed in next release version.

Yeah, I've seen this happening from time to time too on my Jelly Bean One X. I thought it was just my GPS being slightly off (I've noticed the client getting my position completely wrong at some points along my daily commute where, up till the last couple of weeks or so, it's always been spot on), but perhaps it's been this early warning problem instead...

I'm also seeing a lot of times where camera and hazard markers aren't showing up at all until immediately after I submit a new camera/hazard report at that location, at which point I then get both my new marker plus the original marker showing up. Which, annoyingly/embarrassingly, makes it look as if I'm submitting duplicate hazard reports just to get the 6 points, rather than (from my point of view at the time) reporting a new hazard that no-one else has reported yet.

Went out earlier for a quick drive, and out of perhaps a dozen cameras passed by, all of which generated the correct "distance to camera" popup, only one was also marked by the throbbing circle highlight.

PhantomFlanFlinger wrote:

Dave2084 wrote: One thing, on Android do you get the circles flowing out of the camera being reported on (or is that just an iOS thing). Don't see in in the screenshot.

It does happen, but not all the time.

Paying closer attention today on a longer drive, and I was getting the circles on perhaps 1 in 10 of the cameras the client was warning me about. Couldn't see any pattern to their appearance - had nothing to do with the type of camera, the speed of approach (one set of circles appeared on a camera the client started warning me about whilst I was stationary at a set of traffic lights...), or whether or not I had a route set.