A runtime permission is an Android authorization that an application requests while running before it accesses a protected capability or category of device data. Examples can include camera, microphone or certain media access, depending on the platform and feature. A meaningful request should connect to an action the user chose, such as scanning a setup code. The prompt does not prove that every requested capability is necessary for basic viewing. Permissions govern local device access, while the streaming service separately decides whether an account may retrieve media. The available choices and settings vary across Android versions and devices.
Runtime permission and Subscription entitlement
Device permissions control local capabilities; they do not activate a streaming plan.
Connect the request with the chosen feature
A camera request can make sense when a supported setup feature scans a QR code. It needs a different explanation if it appears while merely opening a channel list. Review the app's stated purpose for the access and choose the narrowest suitable option the platform offers. Declining a permission can disable the associated feature without necessarily disabling the entire application.
A denied capability has a specific effect
If local file import fails after media access was denied, that permission state is useful evidence. A rejected server login, however, usually needs investigation of credentials, server address or account authorization. Granting more device permissions does not renew a plan or correct an unsupported stream. Keep those layers distinct so that troubleshooting does not become a sequence of unnecessary access grants.
Review the current permission state
Device application settings usually show permissions already allowed or denied, though menu names differ. Record the exact failed action, app version, Android version and permission wording before changing anything. Some platforms can revoke unused permissions or offer temporary grants, so a feature that worked previously may need a fresh request. Use the publisher's documented flow rather than assuming every permission must remain enabled permanently.
An illustrative example
A player can stream channels but cannot import a local playlist after the user denies the access requested for that import. The symptom fits the selected local feature. It does not show that camera, contacts or microphone access are required for streaming, and it does not establish a problem with the service account.
Practical actions
- Match each permission request to the feature you deliberately selected.
- Check the app permission state when that specific capability fails.
- Record the permission wording and platform version before asking the publisher for help.