Device Drop Detection

New in SA6 **SA6 version introduced**

Purpose

Detects when a device is physically dropped (free-fall followed by an impact) using the accelerometer, and reports it as a devicedrop event, giving fleet operators visibility into physical device damage risk/history without relying on self-reporting.

Location

utils/DropDetector.kt, reporter/DropEventReporter.kt.

**Screenshots <will provide screenshots for this>

Responsibilities

• Monitor accelerometer data for a free-fall signature (near-zero acceleration) followed by a high-magnitude impact spike, within configurable thresholds.

• Apply a cooldown period after a detected drop to avoid duplicate reports from a single event (e.g. a bounce).

• Report the devicedrop event via DropEventReporter → SupportAppRepository.

Configuration

Drop-detection sensitivity is configurable directly on SupportAgentConfig (not a nested object):

Configuration	Type	Default	Description
dropFreeFallThresholdMs2	Float	2.0	Acceleration below this value is treated as free-fall
dropImpactThresholdMs2	Float	25.0	Acceleration spike above this value, following a qualifying free-fall, is treated as an impact
dropMinFreeFallDurationMs	Integer	80	Minimum free-fall duration before an impact counts as a drop (filters out brief sensor noise)
dropCooldownMs	Integer	5000	Minimum time between two reported drop events

An internal, non-configurable impact-watch window (2000 ms) bounds how long after a qualifying free-fall an impact spike is still attributed to that fall.

Events

• devicedrop — see Event Catalog <link this to event catalog>