According to Perplexity.ai
Android’s system media controls are designed to surface active “media sessions” from apps, including browsers, in a swipeable carousel near Quick Settings.
Notifications generally appear only for media longer than a short threshold (for example, around 5 seconds) and when the browser has audio focus.
Background playback and controls can depend on browser policies and site behavior (for example, user-gesture requirements for starting playback and autoplay restrictions).
Common causes when controls don’t show
Browser or OS updates can introduce performance or rendering glitches in Chromium, which may affect video/audio handling, including when media is recognized as “playing” in the background.
Other factors include disabled notifications, “Do Not Disturb”/focus modes, experimental flags (e.g., media or GPU flags), or site-specific behavior that stops playback from being treated as an active media session.
Alter.systems response
When you’re playing media in a browser on Android (audio or video), you should normally get a media notification with playback controls (play/pause, skip, etc.) in the notification shade and lock screen - if the app’s media session is active and Android recognizes it as controllable media.
If this isn’t showing up in Brave or Chrome, the underlying problem usually falls into one of these categories (try):
1. Browser settings blocking the media session
Both Brave and Chrome have toggles that control media session behavior. Check these:
- Go to chrome://flags or brave://flags.
- Search for
Media Session Service and Hardware Media Key Handling.
- Make sure they’re set to Enabled (and not “Disabled” or “Default” if your OEM has tampered with it).
Restart the browser afterward.
Some privacy modes (particularly in Brave) disable media notifications by design to reduce background tracking.
2. Battery optimization / background restrictions
Android often kills background sessions to “save battery.”
If the browser’s background process is killed, the notification disappears. Check this:
- Go to Settings → Apps → Brave/Chrome → Battery → Battery Usage
→ ensure it’s set to Unrestricted or Not optimized.
- Also check Settings → Notifications → App notifications → Brave/Chrome → Media playback is ON.
Certain models (Samsung, OnePlus, Xiaomi) are notorious for killing browser background sessions unless explicitly allowed.
3. Site or media session implementation problem
Some sites don’t expose proper MediaSession API data - so Android doesn’t know it’s a “controllable media source.” You can test this quickly:
- Open sample page for testing (Google’s demo).
- Play audio - if the notification shows up here, then the issue is website-side, not your browser config.
If nothing shows even for that test, it’s a system/browser setting issue.
4. “Do Not Disturb” or Notification Permissions
If Do Not Disturb is active, or notification categories for Media Playback are switched off, Android may silently suppress it. Go to:
- Settings → Notifications → Brave/Chrome
- Enable “Media Playback.”
- Make sure “Allow notifications” is ON globally.
5. Experimental features interference (Brave-specific)
Brave has internal options that can break Android media APIs:
- Background video playback toggle (in Settings → Media)
→ try toggling OFF then ON again.
Block trackers & ads at extreme levels sometimes prevents the MediaSession JS API from working; try whitelisting the site.
6. Corrupted browser state
Occasionally cached site permissions or flags malfunction. Fix:
- Force stop the browser.
- Clear cache (not necessarily data).
- Restart the phone.
If that fails, reinstalling the browser often re-registers the media session service correctly.
In short:
If media plays but no playback controls appear, try this sequence:
-
- Test other sites → isolate whether it’s browser or site issue.
-
- Allow background activity & notifications → in system settings.
-
- Allow hardware media keys & media session at chrome://flags.
-
- Disable aggressive privacy settings in Brave temporarily.
-
- Restart the phone and test again.
Link to a video showing the steps to fix the problem
