Practical guide
How to diagnose Kodi playback problems on NVIDIA Shield
Check the connections, active profile and error timestamp before changing a player or reinstalling an add-on. nvidia-MCP can collect that evidence for a compatible local assistant.
A playback failure can come from the device, Kodi, an add-on, an account, routing or the media source. A successful connection does not prove the stream works, and a redacted URL cannot identify an individual failed stream.
1. Keep the first pass read-only
After setting up nvidia-MCP, ask the assistant to read nvidia://playbook and inspect the configured device. Leave writes and provider browsing off. Do not stop a film just to collect diagnostics.
Diagnose the last Kodi playback failure read-only. Check the configured
TV's connection readiness and Kodi's version, profile and playback state.
Read only a bounded, redacted log excerpt around the failure time.
Separate observed errors from hypotheses. Do not restart, stop playback,
change settings or browse provider folders.2. Separate connection failures
| Observation | What to check next |
|---|---|
| ADB unauthorized | The configured TV's approval prompt and device state. An earlier “connected” message alone does not establish authorization. |
| ADB works, Kodi HTTP fails | Kodi is running, HTTP control is enabled, and the configured port, credentials, LAN permissions and route are correct. |
| Kodi works, Manager fails | The optional service is installed and active, LAN access is enabled and the token matches the active Kodi profile. |
| All connections work | Continue to the playback error and routing evidence; connectivity alone does not diagnose the failure. |
3. Record the failure context
Keep the approximate timestamp, Kodi and add-on versions, active profile, what action failed and the relevant error category. Use kodi_get_status, shield_get_status, kodi_list_addons and bounded current/previous kodi_read_logs. For a native crash, add a short shield_read_logs tail.
Do not upload raw logs, backups or settings files. Redaction reduces common secret exposure but does not make every diagnostic result safe to publish. Review any snippet before opening an issue.
4. Inspect routing, when the companion is available
Kodi Manager can show the path from the skin through a metadata helper to the selected player. Compare the configured player and observed evidence. A detected relationship between add-ons is different from a verified signed-in account or a working media source.
If only one profile fails, inspect that profile's settings rather than copying another profile's credentials or configuration. A profile switch can also change the Manager token, so recheck authentication before treating it as a service failure.
5. Propose one repair with a way back
Ask the assistant to explain the evidence, uncertainty and the smallest supported change. Preview it, keep the backup and verify the specific result afterward. File repairs have their own checksum and stopped-Kodi requirements. Add-on settings and APK upgrades use different recovery paths.
Disruptive tools check both playback and foreground state; paused media or unknown focus can block them. Finish viewing before approved navigation or repair. Never reinstall or downgrade Kodi merely to test a theory: app data and recovery limits matter.
nvidia-MCP is prerelease software with live evidence from one customized Shield. This workflow helps gather evidence; it does not guarantee a fix for every add-on, account, network or media source.