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 Android default-app routing, first clear the current default for one action and choose the intended app once.
What this covers
- Android default-app routing with this exact failure state
- Diagnosis across system default versus in-app browser and domain-specific verified links
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: open links, calls, messages and files in the intended eligible app.
Isolate the component boundary
ReversibleClear the current default for one action and choose the intended app once. Test with the new accessory removed, or check the update's known-issues note for the exact symptom. Boundary to separate: system default versus in-app browser and domain-specific verified links.
Correct only the proven cause
ReversibleSet the supported default category and adjust verified-link handling. 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 clear app data when changing a default is sufficient.
Evidence ledger
Sources behind this answer
Exact questions