CUPERTINO — The window between a phone leaving your hand and a thief gaining unrestricted access to its contents is measured in seconds. An unlocked iPhone grabbed mid-use is a phone with banking apps open, messages readable, and the authentication layer bypassed before the victim has registered what happened. Apple has been working on closing that window. Code references in iOS 27.2 beta 2, released Monday, show how.
The feature, called AutoLock internally, would automatically lock an iOS 26-era iPhone when the system determines the device has been taken from its owner. Apple has not announced it. It is not enabled for users in the current beta. The code now reveals the mechanism in unusually specific detail. The element that matters most is not the detection logic. It is the safeguards against getting the detection wrong.
AutoLock runs on a voting system across three signals. The first is acceleration: a sharp, sudden movement consistent with the phone being grabbed rather than set down or pocketed. The second is the status of a paired Apple Watch: if the watch becomes unreachable in the seconds following that acceleration, the system treats that as corroborating evidence that the owner and the device have separated. The third is time: if the device remains unlocked beyond a threshold interval with no user interaction after the acceleration event, that, too, counts in the vote. No single signal is treated as sufficient on its own. The system requires convergence.
Apple’s proposed anti-theft system treats convergence—multiple signals pointing to a genuine phone snatch—as essential. Phones undergo frequent acceleration events from being dropped, set down forcefully, or tossed into a bag, so triggering a lock on motion alone would create false positives and potentially lock owners out of their devices.
Suppression layers
The beta code reportedly points to several safeguards:
- A successful Face ID unlock after the acceleration event indicates that the owner is still holding or controlling the phone, suppressing the automatic lock.
- Active use of a foreground app that registered the jolt can likewise suggest that the device has not been stolen.
- A backoff mechanism temporarily suppresses additional automatic locks after a false trigger has been resolved.
Together, these measures reflect the central design challenge: a theft detector must be sensitive to abrupt grabs without mistaking ordinary handling for theft. Otherwise, a security feature becomes a recurring source of disruption.
What Apple has deployed so far is deliberately staged. As detailed in Apple’s iOS 27.2 beta 2 release notes, the underlying AutoLock service is running, collecting signals, evaluating votes, exercising the suppression logic, but the component that would actually execute the screen lock is disabled. Apple is testing whether the sensor inputs behave as expected before switching on the consequence of getting them wrong. The practical translation: AutoLock is watching, but not yet acting.
The problem it is designed to address is measurable. Samsung addressed the same threat vector differently in One UI 9, hardening the power-button behavior to prevent a thief from forcing a screen-off during a grab. Both approaches are responses to the same documented pattern of theft.
Research by the House of Commons Library documented 71,391 phones stolen in London in 2025, with snatch-and-grab incidents accounting for a disproportionate share. Metropolitan Police investigators dismantled a network in October 2025 found to have shipped nearly 40,000 stolen devices to buyers in China over twelve months.
Apple Watch integration is central to how AutoLock works, which is both a technical strength and a practical limitation. Owners without a paired watch, a significant share of iPhone users, would have that signal absent from the voting equation, leaving the system to rely on acceleration and the unlock timer alone. Apple has not described how the feature behaves in that configuration, and the beta code does not make it explicit.
Apple’s iPhone Ultra and iPhone 18 Pro, announced at the Surprise and Shine event on September 9, shipped with the current stable release. AutoLock code appearing in iOS 27.2 beta 2 places the feature on the development track for the next update cycle. Whether Apple announces it formally, ships it quietly, or defers it to a later release is not indicated anywhere in the code. The company has not responded to requests for comment.
The detail that lingers from the beta code is not the three-signal voting system. It is the number of ways Apple has built in to prevent that system from firing.
