A Kodi error message tells you that something failed; a useful debug log helps identify what happened immediately beforehand. Capture one reproducible failure, record the time and protect private information before sharing the result.
This workflow assumes you can open Kodi’s settings. It does not diagnose every warning in a log or claim that a particular device has been tested.
Describe the failure first
Write one sentence that another person could repeat: “Opening this local video produces an error after five seconds” is more useful than “Kodi is broken.” Include the device, operating system, Kodi version and relevant add-on version.
Also note whether the same problem happens with another file or source. That comparison gives the log a context and helps avoid blaming an add-on for a storage or network failure.
Capture a focused debug session
- Prepare the test. Choose one action that reliably produces the issue. Avoid installing several unrelated tools while investigating.
- Enable debug logging. Kodi documents this under Settings → System → Logging; wording can vary with the interface.
- Restart normally. Use Kodi’s power menu rather than disconnecting electricity.
- Reproduce the problem once. Record the approximate time and the exact message shown.
- Retrieve the log for your platform. Follow the official instructions rather than assuming every Android device exposes the same folder.
- Turn debug logging off afterward. Keep the captured file for the investigation, not an endless sequence of unrelated sessions.
These capture steps follow the official easy logging method. If you cannot access Kodi’s menus, use its linked advanced method instead of improvising settings changes.
Read the sequence, not just the word “error”
Start near the recorded failure time. Look for the resource or component involved and what changed immediately before the failure. A warning elsewhere in the session may be unrelated.
For example, a failure involving a remote file deserves a storage-access check before a full reinstall. If playback works from a local copy, you now have a narrower question to investigate. This is a diagnostic comparison, not proof of a specific root cause.
Share safely and make the report actionable
Logs may reveal usernames, folder paths, server addresses or private media URLs. Review them before uploading. Never publish passwords, access tokens or subscription links. If you redact information, explain what was removed so the remaining evidence is understandable.
A good report includes reproduction steps, versions, failure time, comparison results and a reviewed log. Follow the maintainer’s reporting instructions; do not send account credentials to strangers offering a quick fix.
Frequently asked questions
Should I reinstall Kodi before collecting a log?
Usually, collect evidence first. Reinstalling may change the conditions you were trying to understand. Preserve a checked backup before considering major changes.
Will a debug log fix the problem?
No. It is evidence for troubleshooting. Use it with a specific test and the add-on troubleshooting checklist.