Choose one file with known available tracks
If a subtitle can be selected manually but does not appear automatically, keep that exact file as the example. Record the audio language, subtitle tracks and the intended viewing requirement. A manually selectable track establishes more than a filename that merely mentions a language.
Use a short passage where the intended text is obvious. Keep the file and audio selection unchanged during the first comparison. A different audio language can affect a language-based policy, so changing several choices together makes the result harder to explain.
Inspect the actual automatic-selection policy
Kodi’s Player Language page provides a preferred subtitle language and choices such as forced-only, original language, interface language or none. Inspect the installed version’s actual selection and preserve the starting value. A policy that intentionally selects no ordinary subtitles can explain the observed behavior.
The same page documents a choice not to show subtitles matching the audio language. Review that separately when a same-language caption is the goal. Do not assume a general language preference overrides every suppression or accessibility setting. Keep the desired outcome specific, such as English dialogue with English captions.
Check metadata and accessibility roles
Kodi’s documentation says accessibility preferences rely on correctly tagged tracks. Compare the available track metadata with the intended role. A track labelled for hearing-impaired use may include meaningful sound cues as well as dialogue, while another track in the same language may serve a different purpose.
Manually select the known desired track and confirm its actual content before applying a global preference. If the label is wrong, preserve that as a source-metadata issue rather than declaring the language selector broken. A player cannot infer every intended role accurately from an arbitrary filename alone.
Reopen and verify a second representative file
After one deliberate policy change, reopen the same item and inspect the automatically selected track. Then use a second authorized file if you need to understand the rule across a collection. Keep a note when the requested track does not exist rather than inventing a universal fallback.
The expected outcome is a selection policy with checked examples and understandable limits. It does not generate captions, translate dialogue or certify the content of every track. Preserve a manual selection route for unusual media and keep the final household preference in the device notes.
Questions answered
Why can an available subtitle remain off at startup?
Inspect the automatic-selection policy, including no-subtitle or forced-only choices and same-language suppression. Manual availability and automatic selection are different results.
Can the accessibility preference work with untagged tracks reliably?
Kodi documents a correct-tagging requirement. Check the actual track and its content before expecting an automatic role match.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.