A phone or tablet feature that has completely stopped should be checked for a disabled permission or setting before assuming hardware failure. 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
ReversibleCheck whether the feature is grayed out, missing from settings entirely, or present but unresponsive when used. 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 the same feature in a different app that uses it, and with recently installed apps disabled or in Safe Mode. 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. Re-enable the permission or setting, or update/reinstall the one app where it fails.
Verify and stop safely
ReversibleConfirm the feature works from a cold restart in at least two different apps. Do not clear app data when changing a default is sufficient.
Evidence ledger
Sources behind this answer
Exact questions