A phone or tablet problem starting right after an OS update, a new case/accessory or a restored backup should be checked against that change first. 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 the exact update version, accessory or backup date, and confirm the feature worked immediately before it. 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. Test with the new accessory removed, or check the update's known-issues note for the exact symptom. 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. Reset the one setting the update changed, or replace the incompatible accessory.
Verify and stop safely
ReversibleConfirm normal operation with the change present for one full day of typical use. Do not treat automated screening as an emergency-call or spam guarantee.
Evidence ledger
Sources behind this answer
Exact questions