Android 13 or later notification behaviour · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Read the permission’s actual scope
Android’s developer documentation describes the notification permission introduced for Android 13 and later. It also documents exemptions and a distinction between foreground-service notices in Task Manager and the notification drawer when permission is denied. The permission’s visible result should not be promoted into a complete audit of every running app activity.
Consider an apparently quiet app
A viewer may deny ordinary notifications and then assume the app cannot have any active service. That conclusion goes beyond the notification setting. Check the actual system and app state using the device’s supported controls instead of inferring process or network behaviour from the absence of a banner.
Keep media exceptions qualified
The official notification documentation identifies media-session notifications as exempt from the particular permission change. This does not remove other app-lifecycle requirements, including later Android version rules for background audio. A notification exception and permission to continue every background task are different matters that should not be combined into a universal playback guarantee.
Report a precise observation
Name the device and Android version, whether the ordinary notification was absent and what the system showed for the active task. Do not claim that the app collected no data or stopped every service merely because no notification appeared. If the task is ending playback, use its documented control and inspect the actual result.
Questions, answered
Does no banner prove an app has no active task?
No. The documented notification rules have a narrower scope.
Are media sessions mentioned as exempt from the permission change?
Yes. Keep that exemption separate from other lifecycle rules.