My phone detects going on a run as “someone snatching my phone and running off”

Post by frereubu » Thu, Aug 06, 2026, 11:58 PM UTC

Melatonic wrote: post #110

frereubu wrote: post #45

Earlier quoted context omitted.

You may have tried this, but I run with my phone in an elasticated belt that's just tight enough to keep the phone stable without being uncomfortable. I really don't want to fork out for another device just for running. (I also find a watch on my wrist annoying when I don't wear one normally).

Not the OP but I used to do that - problem is phones are becoming so damn large even the elasticated belt doesnt work that great anymore. Too much bounce. I found a "belt" thats much wider and doesnt have a clip (has to be sized just right) that does work better. But a bit of a pain to wear sometimes. For years I just literally ran with the phone in my hand (got used to switching hands and positions for comfort) so I…

Post by __m » Fri, Aug 07, 2026, 12:02 AM UTC

rsynnott wrote: post #21

Adding “running” to the list of things that Google engineers apparently don’t do. Where it joins “walking”. Google Maps will suggest almost arbitrarily bonkers public transport directions to avoid walking. Personal favourite: the sensible way to get from my house to work, unless the weather is terrible, is six minutes on a train and a 15 min walk. Google Maps would, generally, prefer that I spend 15 mins on the train…

Post by smelendez » Fri, Aug 07, 2026, 12:07 AM UTC

eCa wrote: post #44

rsynnott wrote: post #21

Adding “running” to the list of things that Google engineers apparently don’t do. Where it joins “walking”. Google Maps will suggest almost arbitrarily bonkers public transport directions to avoid walking. Personal favourite: the sensible way to get from my house to work, unless the weather is terrible, is six minutes on a train and a 15 min walk. Google Maps would, generally, prefer that I spend 15 mins on the train…

Speaking of trains, that's another thing they don't do. The auto-snapping of current location consistently snaps to whatever road or goat track it can find nearby, while equally consistently refusing to snap to the railroad they have mapped. Sure, there's not much need for navigation in that situation, but if you're trying to be smart regarding where I am, maybe take into account if I'm travelling at 200 kph before p…

Post by smelendez » Fri, Aug 07, 2026, 12:11 AM UTC

NoDodgeQuestion wrote: post #29

rsynnott wrote: post #21

Adding “running” to the list of things that Google engineers apparently don’t do. Where it joins “walking”. Google Maps will suggest almost arbitrarily bonkers public transport directions to avoid walking. Personal favourite: the sensible way to get from my house to work, unless the weather is terrible, is six minutes on a train and a 15 min walk. Google Maps would, generally, prefer that I spend 15 mins on the train…

At risk of summoning an army of vibe coders, I wish map apps were more configurable and let you set "I'm happy to walk 20 min" or "someone can drive me a few miles and drop me off"

Post by themaninthedark » Fri, Aug 07, 2026, 12:20 AM UTC

dhosek wrote: post #37

Waterluvian wrote: post #2

Is "snatching a phone and running off" a common enough problem in some regions that this is worth having? Or is this a feature chasing after fears of the bogeyman, leading to concrete inconveniences like this?

In Mexico, apparently, the scheme is to grab a phone from an inattentive pedestrian from a motorcycle or scooter.