Notification Channels: The Setting That Decides How Loud an App Is

Two messages arrive from the same messaging app within a minute of each other. One buzzes, lights the screen, and drops a banner across whatever you were doing. The other just appears in the shade, silent, easy to miss until you happen to pull it down. Same app, same icon, wildly different behaviour, and nothing in the app's own settings screen seems to explain why. The answer is not the app. It is the notification channel that message was posted to, and notification channels android has used since Android 8 are the actual setting deciding how loud, how visible, and how interruptive any given alert gets to be.

Most people never open a channel list on purpose. They just live with the result: one type of message from an app that always breaks through, and another that quietly does not.

One app, many channels

Before Android 8, a notification belonged to an app, full stop. One switch, on or off, covered everything that app ever sent. Android 8 replaced that with channels: named categories that an app defines up front, each one covering a specific kind of notification it might post. A messaging app typically ships with separate channels for direct messages, group chats, and account or security alerts. A delivery app might split tracking updates from delivery-day alerts. The app decides how it wants to slice its own notifications, and every notification it posts has to declare which channel it belongs to.

This is also why the settings screen for one app can look more complicated than you expect. Open Settings, Apps, the app, Notifications and you are not looking at a single toggle anymore. You are looking at a list, sometimes a long one, and every entry on it can be muted, demoted, or tuned on its own, completely independent of the others.

Importance is the whole game

Every channel carries an importance level, and that single property is what actually decides the behaviour you notice. Urgent and high importance channels can show a banner over other apps, make a sound, and vibrate. Default importance shows a banner without necessarily interrupting whatever is on screen. Low importance delivers the notification into the shade with no sound and no banner. Minimum importance goes a step further, keeping the notification out of the shade's top section entirely unless you scroll for it. Nothing about the app changed between those levels. Notification importance android assigns per channel is the entire difference between a message you notice immediately and one you find twenty minutes later by accident.

The app sets an initial importance when it first creates a channel, usually a sensible guess based on what that channel is for. Account alerts get a lower default than direct messages, for instance. But that initial guess is only a starting point, and it is yours to override the moment it stops matching how you actually use the app.

Why a channel cannot be changed after it is created

Here is the part that trips people up, including some developers: once a channel exists on your phone with a given importance, the app that created it cannot quietly change that importance later. Android locks a channel's settings to whatever you, the user, have set them to, specifically so that an app cannot creep its own notifications back up to full volume after you demoted them. If a developer wants different default behaviour going forward, the only route is creating a brand new channel with a new internal ID, which then shows up in your list as a second entry, sometimes confusingly named, sitting next to the old one it was meant to replace.

This is also the mechanism behind change notification sound per app requests that never seem to stick. If you set a custom sound or vibration pattern on a channel, that choice is yours until you change it again. An app update cannot silently reset it. What can happen is the app introducing a new channel for a new feature, which arrives with its own default sound because it is a channel you have never touched, not because your old preference failed to save.

Silencing one channel instead of a whole app

Once you know channels exist, the fix for an app that sends too much noise stops being an all-or-nothing decision. Open the app's notification settings, look at the channel list, and demote the one channel actually responsible for the noise rather than muting the app entirely. A shopping app's order updates can stay loud while its daily promotion channel gets set to low or off. A social app's direct messages can stay loud while its "someone liked your post" channel disappears from view. The record still exists either way. A low or minimum importance channel still delivers into the shade and into Android's built in notification history if you have it turned on, it just does so without interrupting you.

This is also the setting worth checking first whenever a notification seems to be missing entirely rather than just quiet. A channel set to blocked delivers nothing at all, which looks identical to an app that has gone silent for some other reason until you find the channel list and see it sitting there switched off.

What this means for apps that resend notifications

Channels matter for a notification history app too, because a resent notification has to be posted through a channel like anything else, and it inherits whatever importance you set on that channel. This is one reason ReNotify keeps its own channels separate from the apps whose notifications it stores: resending should not depend on guessing which of an app's five channels a given message originally belonged to.

One limit is worth repeating here because channels do not change it. Resending a notification restores its original tap target, the thing that actually opens when you tap it, for roughly six hours and only until the phone reboots, since that is how long Android keeps the underlying PendingIntent alive. No channel setting extends that window. Past it, resending still brings back the full text, just without the link behind it. And whatever you decide about channel importance or filtering, calls, alarms, navigation prompts, media players, and other foreground services are never hidden by rules or a status bar filter, on any channel, because those categories sit outside what filtering is allowed to touch.

The practical version of all this is short. When one type of message from an app is too loud or too quiet, do not reach for the master toggle. Open that app's notification settings, find the channel actually responsible, and change importance, sound, or vibration on that one entry. Leave the channels that already work for you alone. It takes longer to find the first time than flipping one switch, but it is the only way to get one kind of message from an app to behave differently from another, because that is exactly the problem channels were built to solve.