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

Smartphone theft‑detection features that lock a device when sudden movement is detected are generating both praise and frustration. Users from high‑theft cities describe rampant phone snatching and welcome any automatic lock that protects banking and identity apps, while others report frequent false alarms during runs, hikes, or public transit rides and complain about opaque or hard‑to‑tune settings. The exchange broadens into concerns about over‑engineered “smart” behaviors in phones, watches, and mapping apps, and how poorly calibrated assumptions about real‑world use can turn safety and convenience features into everyday annoyances.

Prevalence of Phone Snatching

  • Several regions report phone snatch‑and‑run as routine, not rare:
    • London (UK) is cited with tens of thousands of phone thefts per year; multiple commenters know several victims personally and describe it as “very common.”
    • Brazil and Mexico are mentioned as hotspots; Brazil has a national “stolen phone” app, and Mexico has common scooter/motorbike grab thefts.
  • Others note very low robbery/theft rates in cities like Tokyo, Seoul, Singapore, Taipei, Ottawa, Sydney, Dubai, and some argue London’s numbers are unacceptably high rather than “normal for big cities.”
  • Some stress under‑reporting is likely, making official figures a lower bound.

What Stolen Phones Are Used For

  • Thieves try to:
    • Quickly drain bank/crypto apps before the phone locks.
    • Resell devices or strip them for parts, sometimes using sophisticated chip‑swaps and exploits to bypass Apple/IMEI locks.
    • Run social‑engineering scams to coerce the owner into unlocking or removing “Find My” / activation locks.

Security Features and Countermeasures

  • Google’s theft‑detection lock and similar features are seen as valuable in high‑theft environments; some prefer false positives over leaving accounts exposed.
  • Reported mitigations:
    • Requiring biometric re‑auth for banking, email, and sensitive apps.
    • Using eSIM so thieves can’t easily eject SIMs.
    • Turning off or avoiding auto‑theft features due to fear of lockouts from sensor misclassification.
  • iOS/Android lock mechanisms (activation lock, parts pairing, “partner finance lock”) are discussed as raising the bar for resale.

False Positives and UX Frustrations

  • Users report theft detection or activity detection misfiring:
    • Running with a phone, boarding trains/metros, subway acceleration, and even turbulence on flights can trigger “theft” or “workout” prompts.
    • Apple Watch and other wearables often misclassify normal walks or slow steep hikes as “workouts ended” or “auto pause,” annoying active users.
  • Some want more configurability: per‑app exceptions, better use of heart rate, Bluetooth context, or the ability to disable auto‑logic per activity.

Crime, Harm, and Proportionality

  • Heated debate over whether severe or even lethal responses to theft are ever justified:
    • Some, citing traumatic muggings, express strong emotional desire for harsh retaliation.
    • Others argue that killing over property is disproportionate and itself traumatizing, and that “fear of crime” is often amplified beyond actual risk.

Broader Concerns: Overfitted and “Smart” Systems

  • Many see these features as overfitted to tech‑worker lifestyles and fear‑driven design:
    • Devices increasingly try to infer intent (running vs theft, walking vs workout, “suspicious” movement) from sensors and often get it wrong.
    • Commenters worry about a drift toward pre‑crime style monitoring and always‑on behavioral classification.