Define the question before opening an overlay
Kodi exposes several information overlays, each serving a different purpose. Decide whether you need the source properties, the active decoder, the output mode or a changing playback symptom. A screenshot filled with numbers is less useful when the report never states which behavior is wrong.
Choose one known local sample and a repeatable passage. Keep the same tracks and display route throughout. If the issue occurs only after seeking or switching a track, write that sequence down before opening extra diagnostics. The reproduction and the displayed values should refer to the same event.
Open the relevant documented information view
Kodi documents o for Player Process Info and Control, Shift and o for Player Debug Info on a keyboard. A remote may need a mapping. Use the actual binding available on the installation rather than assuming every television remote has a dedicated information button.
Read source resolution and frame rate separately from screen resolution and refresh rate. The developer’s page distinguishes those fields. For an original example, an older programme can be displayed on a higher-resolution desktop; the output number does not turn its source into newly captured high-resolution video.
Keep counter changes tied to the observed event
If you are examining dropped or skipped frames, note the values before the action and after the same short passage. A cumulative total without a starting observation cannot show how many changes occurred during the moment you are describing. Preserve whether the visible symptom and counter movement coincide.
Keep system-wide resource readings in context as well. The Kodi information guide describes system CPU and memory values as covering all processes. A high number is not automatically a measurement of Kodi alone. Avoid closing unrelated applications and changing player settings together without recording which change affected the result.
Report only what the evidence establishes
Retain the Kodi version, sample type, decoder indication, source/output pair and short reproduction. Review screenshots for private filenames or paths before sharing. Turn off the overlay after the comparison so it does not obscure ordinary viewing.
The expected outcome is a precise record of the active playback route. It does not replace a full log when support needs one, measure every network bottleneck or prove that a single dropped-frame count identifies a defective device. Use the observations to select the next narrow test rather than attaching a broad verdict to one overlay.
Questions answered
Does the screen-resolution field prove the video source has that detail?
No. Record source properties and output properties separately.
Can I attribute the system CPU reading entirely to Kodi?
Kodi’s guide describes that reading as system-wide. Keep other running processes in mind and use a controlled comparison.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.