How to fix Telegram notifications not working on Android and iOS?

When someone searches for Telegram notifications not working on Android and iOS, they usually arrive at the problem after a reinstall, a factory reset, or an operating-system upgrade. The symptom is identical in every case — messages arrive in the chat list, but the phone stays silent — yet the cause is almost never the same switch twice. Notification delivery is decided by four independent layers: the operating-system permission gate, the Android notification-channel policy (or the iOS alert style), the power and focus rules that defer or drop background wake-ups, and Telegram's own global and per-chat rules. Break any one of them and the result looks identical: silence. That flattening of four distinct faults into one symptom is precisely what makes the problem so slippery to diagnose.

This guide is organised the way the problem actually evolved. We start with how the control surface changed across recent OS and app generations, then walk through the migration steps that rebuild a working configuration on a new device or a new OS version, then lay out a compatibility table, and finally cover the risk controls — what you give up when you make notifications reliable, and when it is better to leave them quiet.

Why the Problem Changed: A Short Version Evolution of Notification Control

For a long time, "notifications are broken" meant one of two things: the app had been denied permission, or the chat had been muted. That model survived until mobile operating systems started inserting policy layers between an app's intent to notify and the user's screen. On Android, the shift happened in two stages. Notification channels arrived with Android 8, which handed importance, sound, and vibration control to the system settings rather than the app. Runtime notification permission arrived with Android 13, which turned notifications into something an app must ask for at first launch and can lose again if the user never opens it. Together, those two changes mean a Telegram install can be perfectly healthy inside the app and still produce nothing, because the decision now lives outside it.

iOS took a different route to the same destination. There were never per-category notification channels, so importance stayed app-wide. Instead, iOS 15 introduced Focus modes and Scheduled Summary, both of which sit between the app and the lock screen and can hold or redirect a notification without the app knowing anything went wrong. Later iOS releases kept refining that layer rather than replacing it. The practical result is that an iPhone user with an unchanged Telegram configuration can lose notifications simply by adding Telegram to a Focus filter or a summary schedule months earlier and forgetting about it. In both ecosystems, the trend points the same way: control migrates outward, away from the app and toward the system.

Telegram's own settings surface evolved in parallel, though more conservatively. Empirical observation across recent major versions suggests the structure has been stable for some time: a global hub under Settings → Notifications and Sounds, and per-chat control reachable from the chat's own profile screen. What varies between platforms and builds is the labelling and the grouping — Android exposes category-level entries that iOS simply does not have, because those categories map to system channels on one platform and to nothing on the other. Treat any description of the settings tree, including the one in this article, as a map rather than a screenshot.

The Four-Layer Model: Where Delivery Actually Breaks

The reason notification troubleshooting so often ends in guesswork is that people repair the layer they can see. Consider a concrete scenario: a work group of roughly 200 members, with a steady trickle of messages through the day, and one participant who receives nothing on an Android phone while every other member receives everything. Reinstalling Telegram changes nothing. Muting is not the issue — the chat shows no muted icon. What is actually happening is that the Android 13 permission was granted months ago, then silently revoked by the system's automatic permission reset for apps the user rarely opens, and the user never re-opened Telegram from the launcher in a way that triggered a re-prompt.

That scenario only makes sense once you separate the layers. Layer one is the permission gate: can this app post notifications at all? Layer two is policy on content and intensity: even if it can post, at what importance, with what sound, and in what visual form? Layer three is scheduling and power: will the operating system actually wake the app and draw the notification now, or later, or never? Layer four is Telegram's own rules: does this particular message even qualify for a notification from Telegram's point of view?

• Layer 1 — Permission: Android 13+ runtime permission, iOS authorization, or the master toggle in system settings.
• Layer 2 — Form: Android notification channels and their importance levels; iOS alert style, sounds, badges, and previews.
• Layer 3 — Timing: battery optimisation, Doze, vendor background managers, iOS Focus, Scheduled Summary, Low Power Mode.
• Layer 4 — Eligibility: per-chat mutes, archived chats, in-app notification toggles, category-level switches inside Telegram.

The order matters more than the list. Fixing layer four while layer one is broken produces a device that behaves exactly as before, which is why so many people conclude that Telegram is at fault. The correct diagnostic order runs from the outside in: permission, then form, then timing, then eligibility. Each layer has a cheap verification, described in the sections that follow, and each one can be checked in under a minute once you know what you are looking for.

Layer 1 in Practice: Permission on Android 13+ and iOS

On Android, the shortest reachable path is Settings → Apps → Telegram → Notifications, where the first switch is the app-wide permission. On Android 13 and later this maps to the runtime notification permission the app must request; if it was denied at first launch and never re-requested, this switch is the only place to restore it. On some devices the same screen is reached through Settings → Notifications → App notifications → Telegram, and manufacturer skins sometimes label the top-level entry differently while keeping the same nested structure. If the app-wide switch is off, everything below it is irrelevant.

iOS keeps the equivalent control in Settings → Notifications → Telegram. Two things deserve attention there. First, the Allow Notifications master switch, which is the obvious one. Second, the alert-style options beneath it — depending on your iOS version you will see checkboxes or a style picker controlling whether alerts appear on the lock screen, in the notification centre, and as banners. It is possible, and surprisingly common, to have notifications allowed while all three display surfaces are unchecked, producing a phone that receives nothing visible but still shows the badge. Sounds and Badges are separate toggles further down the same screen.

A second Android-specific hazard belongs to this layer even though it is configured elsewhere: recent Android versions can automatically remove permissions from apps that go unused for an extended period, and "pause app activity if unused" behaves similarly. From the user's perspective the app was never touched, so nothing should have changed — but the system quietly withdrew the permission it had granted. If notification loss correlates with a period of low activity rather than with an update, this is the first hypothesis to test.

Layer 2 in Practice: Android Channels, iOS Alert Style

This is the layer that most changed the troubleshooting workflow, and the one most people never open. On Android 8 and later, an app does not post notifications into a single stream; it posts them into named channels, and the user — not the app — owns each channel's importance, sound, vibration, and whether it shows on the lock screen. Telegram creates a set of channels corresponding to its notification categories, which in recent builds typically cover private chats, groups, channels, and an "other"-style bucket for service messages. The exact names come from the app, but everything about how loud they are comes from the system.

The consequence is a specific failure mode: a user turns down the importance of one channel — say, channels, because a busy news feed was annoying — forgets about it, and months later concludes that a particular group is broken. Inside Telegram the chat looks normal, the mute icon is absent, and the global setting is on. The only place the truth is visible is Settings → Apps → Telegram → Notifications, where each channel is listed with its current importance. If any relevant channel reads as low importance or silent, Telegram's in-app sound choice cannot override it; the platform wins.

iOS has no equivalent ladder. Notification intensity is app-wide, controlled by the alert-style, sound, and badge toggles described above. That asymmetry explains a common migration complaint: a user who carefully tuned per-category sounds on Android finds that the same tuning does not exist after switching to iPhone. What does exist on iOS is Show Previews, which governs whether the message text appears in the notification or is replaced by a generic placeholder — useful when a shared device or a lock-screen-visible phone makes full previews a privacy problem.

Layer 3 in Practice: Battery, Focus, and Background Policy

Even with permission granted and importance set to high, the operating system still decides when the app is allowed to wake up. On Android, battery optimisation and Doze are the standard mechanisms, and they are designed to defer background work when the device is idle. Most manufacturers add their own layer on top — an aggressive background manager that may terminate or freeze apps that are not on an allowlist. The settings screens differ, but the shape of the fix is consistent: find Telegram in the battery or app-management section and make sure it is not restricted. On Android 11 and later the relevant control is often labelled as a battery mode — restricted, optimised, or unrestricted — on the app's own info screen.

On iOS, the equivalent layer is composed of separate features rather than one battery screen. Focus modes can silence an app entirely, or allow it through, depending on how the filter is configured; a Focus filter that excluded Telegram during work hours and was never removed is a plausible explanation for notifications that stop at predictable times. Scheduled Summary can batch notifications into delivery windows, so a message that arrives at an unscheduled hour stays invisible until the window opens. Low Power Mode reduces background activity and may delay delivery; empirical observation suggests it mainly affects timing rather than dropping messages outright, but the effect is device- and condition-dependent, so verify rather than assume.

The trade-off at this layer is the most honest one in the whole article. Making Telegram unrestricted on Android measurably increases background wake-ups, and on a phone with a small battery that is a real cost paid for real reliability. The decision rule is straightforward: if immediate delivery matters for work, unrestrict it and accept the battery cost; if it does not, leave the optimisation in place and stop treating delayed delivery as a bug. Both choices are defensible, but only one of them can be true at a time.

Layer 4 in Practice: Mutes, Archive, and Telegram's Own Settings

Only after the three system layers are eliminated does it make sense to inspect Telegram itself. The fastest check is visual: open the chat list and look for the muted-speaker icon next to the chat in question. If it is there, the chat is muted, and no amount of system configuration will produce a sound. The shortest path to change it on both mobile platforms is to open the chat, tap its header to reach the profile screen, and use the notification control there — on Android you may find it as a bell icon near the top of the profile, on iOS as a Notifications row. Exact placement shifts between builds, so the reliable instruction is "open the chat profile and look for the notification or mute control".

Mute durations are chosen from a set of presets offered by the client, ranging from short intervals to an indefinite option, and the specific presets differ between versions — check what your build offers rather than assuming. Two properties of mute state matter for migration planning. First, it is tied to the account rather than the device, so un-muting on your phone also un-mutes the same chat on your tablet and desktop. Second, archive behaviour interacts with it: archived chats are commonly muted by default when you archive them, and clients typically ask for confirmation before doing so. A chat that was archived during a busy week and never revisited can therefore stay silent indefinitely while looking perfectly ordinary in search results.

Above the per-chat level sits Telegram's global notification hub. In recent builds it exposes separate switches for message categories, an in-app notification toggle that controls whether banners appear while the app is in the foreground, sound and vibration choices, and badge-counter behaviour that determines whether the number on the home-screen icon counts unread messages, unread chats, or includes muted chats. If your badge shows a number while the sound is missing, the problem is not eligibility — it is form or permission, and you should return to layers one and two.

Migration Steps: Rebuilding the Setup After an Upgrade, Reinstall, or Device Switch

The four-layer model is diagnostic, but most people encounter it as a migration problem. Something changed — an OS upgrade, a reinstall, a new phone — and the previous configuration no longer holds. Treating that as a migration rather than a repair makes the work finite and repeatable.

After an Android Major-Version Upgrade

1. Confirm the app-wide notification permission survived: Settings → Apps → Telegram → Notifications.
2. Open the channel list on the same screen and check that no relevant channel was reset to a low importance or silent state. New channels created by an app update commonly start at the app's default, which may be lower than what you had chosen for an older channel.
3. Re-check battery mode for the app, since upgrades sometimes re-apply optimisation defaults.
4. Re-check automatic permission removal settings if your device exposes them, and consider excluding Telegram from unused-app cleanup.
5. Finally, verify per-chat mute state on the two or three chats where delivery actually matters.

The sequence is deliberately ordered from the widest layer to the narrowest, so that a failure at any step is caught before you spend time on the ones beneath it. In practice most upgrades break one or two of these, not all five, and the list is short enough to walk through in a few minutes.

After Reinstalling Telegram or Restoring a Backup

A reinstall is the cleanest migration because it resets layer two automatically: channel settings are removed with the app, so the fresh install starts from app defaults. What it does not reset is everything stored in your account. Mute states, archive placement, and chat organisation return as soon as you sign in, because they live server-side. The practical consequence is that a reinstall fixes channel-level problems and cannot fix mute-level problems — which is precisely why "I reinstalled and it is still broken" and "I reinstalled and it works now" are both true statements about the same app.

Switching Between iOS and Android

Cross-platform migration transfers the account-level state and loses the device-level state. Mutes follow you; Focus modes, notification channels, battery allowlists, and alert styles do not. Two asymmetries deserve planning for. First, if you relied on per-category sounds on Android, you will not find an equivalent on iOS and should decide on a single sound instead. Second, if you relied on iOS Focus to keep Telegram quiet during meetings, you need an Android equivalent — typically Do Not Disturb plus, if you want the per-chat behaviour Focus filters provide, a mute applied to the chats that were previously filtered. Setting that up in advance avoids a week of notification noise in both directions.

Compatibility Table: What Exists on Each Platform

The table below summarises where each control lives and what breaks most often. It describes the platform models as they stand in the OS versions current at the time of writing; individual builds may place entries differently, so use the verification step in each row rather than memorising the path.

Two entries deserve emphasis. Telegram Web depends on browser permission, and a browser that blocked notifications for the site will produce silence even while the web client shows unread counters climbing. Telegram Desktop, by contrast, has a genuine in-app master toggle, so a desktop that stops notifying may simply have that toggle off — the fastest check is the desktop settings panel, not the operating system.

Troubleshooting Matrix: Symptom to Fix

Symptoms are more useful than causes when you are standing in front of a phone. The matrix below maps observable behaviour to the layer that most plausibly explains it, along with a verification step you can run immediately and the corresponding fix.

One row in that table is worth expanding, because it is the most frequently misread. A working badge with no visible notification is not a delivery failure — the message reached the device and the app told the system about it. What failed is presentation. Working on delivery when the real problem is presentation wastes time, and it is the single most common reason a troubleshooting session ends without a fix.

Verification and Observation Methods You Can Reproduce

Every claim in this article can be tested on your own device in a few minutes. The tests below are ordered from least invasive to most, and each one isolates a specific layer rather than testing everything at once.

Start with a controlled delivery test. Ask someone to send you a direct message from a second account, preferably while your phone is locked and idle, then note three things independently: whether a notification appears, whether it makes a sound, and whether the badge changes. Those three observations already separate delivery from presentation from counting, and they tell you which layer to inspect next. Repeating the test with a group chat and a channel narrows the scope further, because those categories may map to different channels on Android.

For a more technical check on Android, the platform's notification dump lists notifications the system is currently tracking. With a USB-connected device and debugging enabled, the following command filters for the app name; the exact output format varies by Android version, so read it as evidence of presence rather than as a fixed schema:

If entries appear while your phone is idle and locked, delivery works and the fault is in presentation or timing. If nothing appears, work backwards: permission, then channel importance, then battery policy. On iOS the equivalent check is behavioural rather than textual: lock the phone, send a message, and watch whether the notification arrives within seconds, after a delay, or bundled with others. Bundling points to Scheduled Summary; immediate arrival with no sound points to the sound toggle; no arrival at all while other apps notify normally points to the Telegram-level toggles.

Exceptions, Trade-offs, and When Not to Chase Notifications

Reliable notifications are not free, and the costs are worth naming before you start flipping switches. Making an app unrestricted on Android increases background activity, which on a small battery is noticeable by the end of a long day. Full message previews on the lock screen put conversation content in front of anyone who glances at the phone. Adding Telegram to the allowed list in a Focus mode means meetings are no longer protected from it. None of these are reasons to avoid the fix — they are reasons to decide deliberately which of them you actually want.

There are also situations where chasing notifications is the wrong answer. If the device is shared, keeping previews off and accepting that notifications are less informative is the better trade. If the account is used mostly for reading rather than replying, leaving battery optimisation in place and accepting delayed delivery costs nothing real. And if the phone belongs to an organisation that manages it, per-device workarounds may conflict with policy; the durable fix is a policy change, not a settings change.

A final boundary concerns the difference between a quiet device and a broken one. Users who want fewer interruptions sometimes keep adjusting settings until notifications are genuinely broken, then report a bug. The cleaner approach is to keep the pipeline healthy and control noise at the eligibility layer instead — mute specific chats, use the system's own quiet hours, and leave the permission and channel structure intact so that when something does matter, it gets through.

Bots and Third-Party Integrations: Least Privilege

Notification problems attract a particular kind of bad advice: adding a bot or a third-party relay to "fix" delivery. It is worth being explicit that a bot cannot repair a local permission, channel, or battery problem. A bot sends a message into your account; whether that message produces a visible alert is decided entirely by the four layers described above. If anything, adding a bot makes diagnosis harder, because it introduces a second source of messages that behaves identically to the first.

There is one legitimate use. If you control a bot that can message you on demand, sending yourself a test message through it is a clean way to verify the pipeline without involving another person. That is a diagnostic convenience, not a fix. The least-privilege rule applies as usual: a bot needs only the ability to send you messages, and there is no notification scenario that requires granting administrative rights in a group or access to conversations it does not participate in. If a third-party tool asks for broad access in exchange for "better notifications", the correct response is to decline and return to the system settings.

Applicable and Non-Applicable Scenarios

The layered approach pays off best under specific conditions, and it is worth recognising when a simpler answer is appropriate.

• Worth doing in full: a phone used for time-sensitive coordination, where a missed message has consequences — small teams, on-call arrangements, family logistics. Here the battery cost of unrestricted background activity is easily justified.
• Worth doing partially: a personal device with a mix of chatty groups and a few important contacts. Fix permission and channels once, then control noise with per-chat mutes instead of touching the pipeline again.
• Probably not worth it: a secondary device used mainly for reading, where delayed delivery is acceptable. Leave battery optimisation alone and stop treating latency as a fault.
• Out of scope: managed corporate devices, where notification policy is set centrally. Local workarounds may be reverted by policy refresh and can create confusion for whoever supports the device.

A simple admission test works well here: if you cannot describe a specific message that you needed within seconds and did not get, you probably do not need the unrestricted configuration. If you can, you already know which chats and which channels matter, and the work becomes targeted rather than global.

Best Practices Checklist: Decision Rules for Quick Implementation

The following rules are written as decisions rather than steps, so they can be applied in any order and re-applied after an upgrade without re-reading the whole article.

1. Always start at the outside layer. Confirm the app-wide permission before touching anything inside Telegram.
2. After any OS upgrade, re-check channel importance even if permission survived — new channels may start below your previous preference.
3. Treat a working badge with no visible alert as a presentation problem, never as a delivery problem.
4. Change battery settings only for accounts where latency has a known cost, and note that you changed them so you can revert later.
5. Prefer muting individual chats over reducing global notification strength; the first is reversible per conversation, the second affects everything.
6. Before reinstalling, decide whether the suspected fault is channel-level (reinstall helps) or mute-level (it does not, because mute state is account-level).
7. Record your configuration — channel importance, battery mode, Focus membership — somewhere you can find it, because migrations are when this knowledge is lost.
8. Keep previews off on shared or frequently unlocked devices; convenience is not worth exposing conversation text.

Read together, these rules describe a posture rather than a one-time repair: keep the plumbing open, and manage interruption at the conversation level instead of strangling the pipeline itself.

Frequently Asked Questions

Why do notifications work for direct messages but not for group chats?

Groups and private chats can be governed by different rules. On Android this usually means the group-related notification channel has a lower importance than the private-chat channel, and Telegram cannot override a system-level reduction. On iOS, where there are no channels, the more likely cause is eligibility: the group is muted, or it was archived, which commonly mutes a chat by default. Check the chat list for a muted icon first, then check channel importance if you are on Android.

I see a badge count but no notification banner. What does that mean?

It means delivery succeeded and presentation failed. The message reached the device and the app informed the system, but the alert was suppressed somewhere in the display layer — an unchecked alert style on iOS, a lowered channel importance on Android, or enabled quiet delivery. Work on the form layer rather than the permission layer, because reinstalling or re-granting permission will not change anything.

Does reinstalling Telegram fix missing notifications?

Sometimes. A reinstall typically clears Android notification-channel settings, restoring app defaults, so it can repair a channel-level problem. It cannot repair mute state or archived placement, because those are stored with the account and return as soon as you sign in. If the reinstall does not help, the cause is almost certainly outside the layer it resets.

Notifications stop at the same time every day. Why?

A recurring schedule points to a timing rule rather than a permissions problem. On iOS, review Focus modes and Scheduled Summary windows and check whether Telegram is included in either. On Android, check the device Do Not Disturb schedule and any manufacturer quiet-hours feature. Time-bounded failures are rarely caused by permission or channel settings, which do not change on a schedule.

Will making Telegram unrestricted drain my battery noticeably?

It increases background activity, and the size of the effect depends on how much messaging traffic the account sees and on the device itself. Empirical observation suggests the cost is modest for low-volume accounts and more visible for heavily active ones. If you are unsure, apply the change for a few days, note the battery screen's per-app breakdown, and revert if the trade does not feel justified.

Closing: What to Do in the Next Ten Minutes

The durable lesson from all of this is that Telegram notifications are not governed by a single switch, and the settings surface inside the app is only the innermost of four layers. When something goes quiet, the productive sequence is fixed: confirm the app-wide permission, then the form layer, then the timing layer, and only then the eligibility rules inside Telegram. Working in that order turns an open-ended search into four short checks, each with an observable result.

If you want a concrete starting point, do this now. Open the system notification screen for the app and confirm both the master toggle and the channel or alert-style settings. Then send yourself a controlled test from a second account while the phone is locked and note separately whether you got a banner, a sound, and a badge change. That one test tells you which layer to work on, and it takes less time than reading the rest of this article took.

Future Trends / Version Expectations

Looking forward, the direction of travel is unlikely to reverse. Platform-level control layers have accumulated over successive releases rather than being consolidated, and empirical observation suggests each new generation adds policy between the app and the screen more often than it removes any. For anyone maintaining notifications on a real device, that means treating configuration as something to re-verify after updates, not something to set once and forget — and expecting the checklists above to shift in detail while keeping the same four-layer shape.

Finally, write down what you changed. Notification configuration does not survive an OS upgrade, a reinstall, or a device switch intact — permissions are per-device, channels are per-install, and Focus membership is per-device — while mute state follows the account. Knowing which half of your configuration is portable is the difference between a five-minute migration and another round of blind troubleshooting.