1 Platform troubleshooting 

 Audio troubleshooting

3 Effective Tactics

  •  Isolate the Problem

Before writing a bug report, it is advisable to try and find the source of the bug. There are two good ways to do this:

  1. Temporarily remove user data
  2. Temporarily uninstall an add-on

If, for example, you remove an add-on and the bug still occurs, then that add-on is not the source of the bug. If there is no problem after temporarily removing the component in question, then you have narrowed down the source of the bug. Doing this will help the developers find and fix the bug faster.

  • Update and Upgrade

Before writing a bug report, make sure that the add-on you are using, or the Kodi itself, is fully updated to the newest version. It is entirely possible that the problem is fixed in the most recent versions of the add-on and/or the Kodi. The add-on support section of the forum contains information and help with the Kodi add-ons. There may be versions of add-ons that are not officially added to the repository that fix the problem.

  •  Test on Multiple Devices

Reproducing the bug on multiple devices will determine whether or not the source of the bug is the user’s hardware or the Kodi itself. Testing the bug on multiple devices before submitting the bug report can isolate the source of the problem and help determine whether or not the developers can fix it. This tactic also greatly reduces the confusion that can occur when others try to reproduce the bug. Depending on the hardware involved with the bug, the user should reproduce the bug on second devices including, but not limited to:

  • Computers
  • Televisions
  • TV remotes
  • Blu-Ray or DVD players
  • Xbox 360 controllers

If the bug is successfully reproduced on at least two devices, then it is more likely that there is a problem with the Kodi.

4 Reporting bugs/errors

HOW-TO:Submit a proper bug report

5 Getting more help

  •  How do I ask a question in a smart way?

How to ask questions in a smart way?:

  • When you ask:
    • Use meaningful, specific subject headers on posts.
    • Be explicit about your question.
    • Be precise and informative about your problem.
    • Include screenshots to aid in problem description.
    • Describe the problem’s symptoms, not your guesses.
    • Describe your problem’s symptoms in chronological order
    • Describe the goal, not the step.
    • Don’t ask people to reply by private e-mail or private message.
    • Courtesy never hurts, and sometimes helps.
    • Follow up with a brief note on the solution if you find one

6 Test files and samples

See: Samples


7 See also