A feature that drops and returns on a phone or tablet is usually a background battery-optimization or connection-management setting killing it, not failing hardware. For iPhone Face ID, first clean the sensor area, remove obstruction and test unlock plus one supported app.
What this covers
- iPhone Face ID with this exact failure state
- Diagnosis across attention/appearance and screen protector versus camera obstruction and hardware
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleNote how long the device was idle or locked before the drop, and whether it correlates with low signal or a Wi-Fi handoff. Expected behavior: recognize the enrolled face through an unobstructed TrueDepth system under supported conditions.
Isolate the component boundary
ReversibleClean the sensor area, remove obstruction and test unlock plus one supported app. Disable battery optimization for the one app and test with the device kept awake on a single network. Boundary to separate: attention/appearance and screen protector versus camera obstruction and hardware.
Correct only the proven cause
ReversibleUpdate, reset and re-enroll Face ID only after passcode and app credentials are available. Exempt the app from aggressive battery management, or turn off adaptive Wi-Fi/cellular switching for the test.
Verify and stop safely
ReversibleRun the same use pattern that triggered the drop for at least 30 minutes without it recurring. Service after impact, liquid or a TrueDepth unavailable message that persists.
Evidence ledger
Sources behind this answer
Exact questions