Driver monitoring: behavior and checks
Keep driver monitoring enabled by default. For repeated warnings, check the camera, mounting and current mode first.
Current policy
| Item | Behavior |
|---|---|
DriverMonitoringEnabled | On by default; an explicitly chosen value persists across drives/restarts |
DriverMonitoringMode | 0 standard / 1 experimental; default 0 |
| Mode changes | Applied about every 0.5 s; do not clear accumulated warnings or reuse restrictions |
| Camera unavailable | Falls back to interaction-based monitoring when monitoring is enabled |
| File / QR / profile restore | Does not import another device's Enabled choice |
An unavailable camera does not automatically disable all monitoring. Distinguish Driver View face preview from the actual warning policy.
Standard and experimental modes
With a working camera, standard mode monitors face/head position, closed eyes, drowsiness and phone use. Experimental mode changes warning timing and interaction grace periods; do not treat it as the same supervision level. Check detailed timings in the pinned original and distinguish controlled testing from actual use.
Repeated warnings
- Check device and driver-camera operation.
- Park and check mounting and face preview.
- Record monitoring enabled/mode state, branch and commit.
- Record the warning time and exact text.
- For repeated problems, request support with original driving logs.
Limitations
Disabling monitoring removes camera/interaction warnings and the resulting forced deceleration/reuse restrictions. Exceptions for devices without supported cameras do not replace driver supervision. Catalogue search and temporary-disable implementation details are in the pinned source.
Prepare warning-analysis logs.
Source reference
Reference checked 2026-10-30 · carrot-wip · 10bf0a56.
docs/user/ko/driver-monitoring.md · README.md
The development branch continues to change. Check your device’s branch, commit and current settings together.