Understand where middleware sits
The device, portal software and streaming-service account are different layers. Infomir’s MAG documentation describes pre-integrated Ministra support and operator customisation. The operator can determine which portal functions and settings are exposed.
A consumer should therefore identify the portal address, supported device and account method supplied for their actual service. Downloading a similarly named application is not a substitute for an operator account or a compatible portal version.
Use the device’s supported connection route
A Linux MAG box and an Android/Google TV device do not automatically use the same application package or configuration menu. Follow the device and middleware documentation that matches the operator’s supported setup.
If a portal displays an older-version compatibility message, record its exact wording and the device firmware. Infomir documents some model-specific compatibility options, while also identifying outdated operator portals as a separate issue.
Separate interface visibility from service facts
Seeing a live-TV menu, EPG tab or recordings area tells you about a software interface. It does not prove that every feature is enabled for the account, that content is included, or that the operator has rights for a particular territory.
Test the authorised task that matters: portal loading, account recognition, guide data and actual playback. Keep those results separate instead of calling a successful login a complete service test.
A concise operator enquiry
Provide the device model, firmware, portal software context and the stage of failure. Keep MAC identifiers, credentials and private portal access details out of public images. An operator can then address provisioning or portal compatibility without guessing which software layer the household is using.