It does seem to be WiFi related. But if I have to remember to disable the WiFi whenever I want to do some GPS tracking - and if I forget, I basically get random garbage - that pushes it well into "no bloody use" for me.

Surely there is an app for that? Android has plenty of apps that will automatically turn on/off your wifi based on various criteria, such as your location (I always turn it off as soon as I'm 50 yards away from home or from the office).

That's a feature, not a bug ;)

Uh, no, I'm pretty sure that's a bug. Unless you literally want to consider inaccurate tracking a feature.

I would bet it is the cycling of GPS that the app is doing. If GPS is just left on, a battery can get burned through in a couple hours (for one of the newer iPhones, much less an older one). Those wacky readings are some of the initial results after GPS is cycled back on.

One might look for a higher power setting if you are doing an hour / half hour run and not concerned about keeping battery life up.

Moves is on "battery saving" mode (which actually makes little difference - I get bugger all life out of my phone anyway) but that doesn't really explain why it's just around the O2 it has serious issues - that's only about 2-3km out of the whole 30km walk.

Probably put these apps should compensate for the fact that humans can't run that fast nor that they can run over water.