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 Pixel Call Screen, first confirm Pixel Phone is default and test with a normal unknown caller outside Focus.
What this covers
- Pixel Call Screen with this exact failure state
- Diagnosis across feature eligibility versus Phone app version, default-dialer and network
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: answer eligible calls through the supported Phone app, language, region and account.
Isolate the component boundary
ReversibleConfirm Pixel Phone is default and test with a normal unknown caller outside Focus. Disable battery optimization for the one app and test with the device kept awake on a single network. Boundary to separate: feature eligibility versus Phone app version, default-dialer and network.
Correct only the proven cause
ReversibleUpdate the Phone app and enable only supported Call Screen options. 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. Do not treat automated screening as an emergency-call or spam guarantee.
Evidence ledger
Sources behind this answer
Exact questions