Use the supported-device list
At this check, OSMC’s supported-device page explicitly excludes Raspberry Pi 5 while describing its supported Pi and Vero options. Follow that specific statement rather than extending an older phrase such as all Raspberry Pis beyond its exception. Recheck the current list before obtaining installation media.
Record the exact board or Vero model and the proposed OSMC release. If you already have a working system on a storage card, back it up before repurposing that card. An installer’s hardware selection is a compatibility decision, not merely a preference for a different home-screen appearance.
Establish a simple media baseline
After installation on supported hardware, confirm navigation, display and a permitted local sample before adding a complex library. Keep the original connection path in a note. A television connected through a receiver can present different output capabilities from a direct connection.
Use one known file or authorised source for the first comparison. If it plays while another item fails, preserve the source-specific result. Do not conclude that every OSMC-supported device has identical decoding or output capabilities; the Vero specifications and board-specific limitations still matter.
Keep system and service responsibilities distinct
OSMC supplies the media-centre environment. A source account, add-on, tuner or personal library supplies the actual media through its own supported route. Installing OSMC does not create a subscription or establish that an unrelated provider will support the setup.
When seeking help, identify the hardware, software release, add-on or source and exact symptom. A failed installation, a missing source and a specific playback error need different evidence. Retain a recovery plan and private configuration backup so a major upgrade does not erase the only record of an authorised working setup.