How to fix Telegram push notifications not working on Android?

Telegram Push Notifications Not Working on Android: What You Are Actually Debugging

When Telegram push notifications stop working on Android, most people go looking for a single broken switch. In reality you are troubleshooting a chain of six independent systems — Telegram's own in-app settings, Android's notification channels, the operating system's background execution policy, the OEM's autostart manager, the network path, and finally Google's push infrastructure. A notification only reaches your lock screen when every link in that chain is intact, which is why a fix that works on a Pixel can do nothing on a Xiaomi, and why a fix that worked two Android releases ago may now be irrelevant.

This article is organized the way an engineer would actually work: first understand what the layers are, then follow a decision tree, then apply the platform-specific steps, and only then reach for the exotic explanations. Along the way you will find explicit boundaries — the situations where a setting is genuinely the cause, and the situations where it is a coincidence that people keep repeating because it once worked for someone. Keeping those two apart is the difference between a fix that lasts and an afternoon of random toggling.

Six Symptom Families, Six Different Root Causes

Before touching any setting, classify what you are seeing. "Telegram notifications are broken" covers at least six distinct behaviors, and they do not share a root cause. Each one narrows the suspect list before you have changed anything at all.

• Nothing at all, ever — no sound, no banner, no badge, but messages appear instantly when you open the app. This is almost always a channel-level or permission-level block.
• Delayed by minutes to hours — messages arrive, but late, often in a burst. This points at background execution restrictions or Doze.
• Works on Wi-Fi, fails on mobile data — background data restrictions, data saver, or a carrier-level issue.
• Group and channel notifications work, private chats do not (or the reverse) — category-level settings inside Telegram or inside Android's channel list.
• One specific chat is silent — per-chat mute or a per-chat custom notification rule.
• Phone silent while desktop or tablet buzzes — this is often correct behavior, not a bug, and we will explain why later.

Writing down which of these six you have will cut the remaining work roughly in half. The reason is structural: the first family is a presentation problem, the second is an execution problem, and the third is a network problem — three different subsystems that barely overlap. If your answer is "it works fine when the app is open," you can skip every section about permissions and channels and go straight to battery optimization.

How Telegram Delivery Differs From an Ordinary Android App

Most Android apps receive notifications through a single path: Google Play Services maintains the connection to Firebase Cloud Messaging (FCM, Google's push transport), the app is woken by the incoming push, and the operating system draws the notification. Telegram is a hybrid. It maintains its own long-lived connection to Telegram's servers while it is running or recently running, and it also registers with FCM so that notifications can still be delivered when the app has been fully killed by the system.

That dual design explains a lot of confusing behavior. If Telegram's own socket is alive, the update can arrive through it; if the process has been frozen or evicted, only the FCM path remains. Both paths ultimately have to hand the message to Android's notification system, which since Android 8.0 (Oreo) means they have to hand it to a notification channel (a named bucket that controls importance, sound, vibration, and whether the notification can be shown at all). A channel set to "Silent" or blocked will swallow the notification even when everything upstream is perfectly healthy.

The practical consequence is that two users can describe the identical symptom while sitting on opposite ends of the pipeline. One has an app that receives everything and displays nothing; the other has an app that displays everything and receives nothing. Distinguishing those two cases is the first genuinely useful thing you can do.

Tip: Keep the distinction in mind throughout: permission is about whether Telegram is allowed to notify you; the channel is about how it notifies you; battery policy is about whether the app is running to receive anything in the first place. Fixing one does not fix the others.

Version Evolution: Why Advice From Two Years Ago No Longer Applies

Notification troubleshooting is unusually vulnerable to stale advice, because the rules changed at the platform level three separate times. If you are following a forum post from the Android 7 era, you are probably looking for a menu that no longer exists — or toggling something that has been superseded. The section below is not history for its own sake; it tells you which instructions to discard so you do not spend time on them.

Era 1: The Single-Switch Model (pre-Oreo)

Before Android 8.0, an app had essentially one notification switch at the system level. Telegram exposed granular controls inside its own settings — separate sound, vibrate, LED, and priority per chat category — and the operating system simply accepted them. The classic fix in this era was "go into Telegram's own notification settings and turn Private Chats and Groups off and back on." That advice still circulates today, but its effect is now indirect at best, because in the channel era the app cannot freely override system-level importance.

Era 2: Notification Channels (Android 8.0 and Later)

Oreo introduced notification channels, and with them a shift in who controls what. Telegram, like every other well-behaved app, now creates channels, and the system owns their importance, sound, and vibration. Inside Telegram you may still see controls such as Priority, Sound, Vibrate, and LED, but on modern builds these often act as defaults that the channel overrides or that are shown read-only. Empirical observation: on many current builds, changing Telegram's in-app "Priority" for a category does not change the banner behavior, because the corresponding Android channel is already set to a fixed importance. To actually change behavior you must edit the channel in Android's own app-notification screen.

The mental model worth keeping is a division of labor: Telegram decides whether an event deserves a notification, and Android decides how that notification presents itself. When the two disagree, Android wins.

Era 3: Background Restrictions (Android 12 Through the Current Release)

The most recent shift is about execution, not presentation. Recent Android versions tighten what a backgrounded app may do, and many manufacturers add their own layer on top — aggressive app freezing, autostart managers, and "sleeping app" lists. On these builds the notification is not blocked; the process that would receive it is simply not allowed to run. This is where most unresolved 2026-era complaints actually live, and it explains the distinctive symptom of delayed rather than absent notifications. A delayed notification is, in effect, a message waiting for permission to be delivered.

Migration Advice: What to Stop Doing

If you are migrating from an older phone or restoring a backup, do not expect the old notification setup to come with you. Notification channels are recreated fresh on a new install, and per-chat settings restored from a backup may not re-register with the system. After moving devices, re-check three things: the app-level permission, the channel list for Telegram, and the battery classification of the app. Everything else can be diagnosed from there.

A 60-Second Decision Tree Before You Change Anything

Work top to bottom and stop at the first check that fails. This ordering matters: it removes the most common causes first and avoids the classic mistake of disabling battery optimization for an app whose notifications were simply muted. Each step is cheaper than the next, so you spend the least effort to eliminate the largest number of possibilities.

1. Is there a notification anywhere? Pull down the shade while the phone is unlocked and have someone send a test message. If a notification appears but silently, jump to the channel section.
2. Is Telegram muted as a whole? Open Telegram, check the chat list for a mute icon next to the header or account name.
3. Is the specific chat muted? Open the chat and check the bell icon or the chat's own notification settings.
4. Are Android-level channels enabled? Android Settings → Apps → Telegram → Notifications.
5. Is background execution allowed? Android Settings → Apps → Telegram → Battery (the label varies) → set to unrestricted where that option exists.
6. Is background data allowed? Android Settings → Apps → Telegram → Mobile data / Data usage → background data enabled.
7. Does the OEM have an autostart manager? Only relevant if steps 1–6 all passed. See the manufacturer table below.
8. Does the device have Google Play Services? If not, push delivery in the killed state is genuinely not available and you are relying on the app staying alive.

Steps 1 through 4 take under a minute and resolve the majority of cases. Steps 5 and 6 explain most of what remains. Only a minority of genuinely persistent problems require step 7 or 8 — and if you reach that point, you already know something unusual is going on, which is itself useful information.

Step 1 — Confirm the Message Is Actually Being Pushed

The most expensive diagnostic error is assuming the problem is on the phone when the message never left Telegram's servers in the intended way. Run a clean test before changing any setting, because once you start toggling options you lose your baseline.

A reproducible test: use two accounts, or ask a contact to send a plain text message to a private chat. Close Telegram completely — swipe it out of the recent-apps list — then lock the screen. Have the message sent. Note three things: how long until anything appears, whether the notification is visible on the lock screen, and whether sound or vibration accompanies it. Repeat the same test with a group and with a channel you follow. If private chats behave differently from groups, the cause is almost certainly a category setting rather than a device-wide restriction, and you can skip most of the battery material below.

Also worth confirming: a chat you have muted on one device is muted at the account level, not the device level. If someone in your household muted a chat from your desktop client last month, your phone will stay silent too, and no amount of Android settings work will change that. Checking the mute state in the chat list costs five seconds and eliminates this entire class of false alarm.

Step 2 — Android App-Level Permission and Notification Channels

This is the layer that silently blocks more notifications than any other, largely because people do not know it exists. Android gives you a per-app notification screen, and inside it a list of channels that Telegram has registered — one for private chats, one for groups, one for channels, and typically several others for service-like messages.

Shortest path (stock Android and most AOSP-derived skins): Android Settings → Apps → Telegram → Notifications. Toggle "All notifications" on, then open the channel list and check each entry. A channel showing as Silent, or with its own toggle off, will suppress that category regardless of what Telegram itself thinks.

Alternative entry points: long-press a Telegram notification directly on the shade and tap the settings gear — Android takes you straight to that specific channel. This is the fastest route when you can produce a notification at all, and it lets you adjust the exact channel rather than guessing which one governs the chat you care about. On some skins, Android Settings → Notifications → Recently sent also lists channels and gives a shortcut to their settings.

When you open a channel, the important controls are the toggle at the top, the importance level (which determines whether you get a banner, a sound, or nothing), and the sound and vibration selectors. Setting importance to a level that suppresses sound but keeps the notification visible is a common accidental configuration — often the result of a user silencing one noisy group and not realizing the change applies to the whole channel.

Step 3 — Telegram's Own Notification Settings and Per-Chat Rules

Telegram's in-app settings are the most misunderstood layer, because they overlap with Android's. The practical rule of thumb on modern Android: use Telegram's settings to decide whether a category notifies you at all, and use Android's channel screen to decide how it looks and sounds.

Shortest path: Telegram → Settings → Notifications and Sounds. The top of that screen lists your accounts and their chat categories — typically Private Chats, Groups, and Channels. Opening one of those categories exposes per-category controls such as a notifications toggle, sound, vibration, and priority. Below the categories you will usually find global options like message preview, in-app notifications, and a list of notification exceptions.

Per-chat path: open the chat, tap the chat title at the top to open the profile, then find Notifications. Depending on your build this appears as a bell icon, a labeled row, or an item inside the chat's overflow menu. From there you can mute the chat, or enable custom settings that override the defaults for that conversation only. The longest-press alternative: long-press the chat in the chat list and choose the mute or notification option directly.

A Small Scenario: One Noisy Channel, One Silent Group

Suppose you follow a busy announcements channel and you also participate in a work group. You mute the channel from your phone so it stops buzzing — and a week later you notice the work group is now silent too, even though you never touched it. What happened, in the overwhelming majority of cases, is that both conversations map to the same Android notification channel and the mute was applied through a channel-level action rather than a per-chat one. The fix is to open the offending chat, apply a per-chat mute there, and then restore the channel to its normal importance. Doing it in the other order — fixing the channel first, then the chat — often leaves you with the original problem reappearing.

This is also the reason to prefer per-chat mutes over category-level ones. A per-chat mute is scoped precisely, survives future category changes, and does not accidentally reclassify how the other chats in that category behave. When a category-level change is necessary — for example, to silence all channels you follow — apply it in Telegram, then immediately verify that private chats still notify you.

Step 4 — Battery Optimization, Doze, and Sleeping Apps

If notifications arrive late rather than never, this is almost certainly your problem. Android's Doze mode and App Standby features suspend background network and CPU activity for apps the system considers idle, and aggressive OEM implementations push this much further. When Telegram is frozen, the update still arrives at Google's servers, but the phone cannot hand it to an app that is not allowed to run — so it waits, and you get a burst of notifications the next time the screen turns on.

Shortest path on Android 13 and later: Android Settings → Apps → Telegram → Battery → choose the option that keeps the app unrestricted or "allow background activity." On earlier releases the equivalent lives under Android Settings → Apps → Telegram → Battery → Battery optimization → All apps → Telegram → Don't optimize.

Additional system-wide controls to check: on devices with Adaptive Battery, look for battery settings that adapt to usage patterns and consider excluding Telegram from that optimization. On Samsung devices, check Settings → Battery and device care → Battery → Background usage limits and confirm Telegram is not in the sleeping or deep-sleeping app lists; if it is, add it to the exclusion list. On Xiaomi, Huawei, Oppo, Vivo, Realme, and similar devices, the relevant control is usually a per-app autostart or background-run permission. The manufacturer table in the next section maps those out.

When Not to Disable Battery Optimization

Setting Telegram to unrestricted has a real cost: the app may be kept alive longer, hold its network connection open, and consume more battery. On a modern phone with a large battery the difference is usually modest, but on an older or low-end device it is measurable. If you receive a handful of messages a day and can tolerate a delay of a few minutes, leaving the default optimization in place is a legitimate choice — you are trading latency for battery life, deliberately.

The middle ground, available on many builds, is to exempt Telegram from optimization but leave it out of any "always running" list, and to check afterward whether your standby battery drain changed noticeably. Verification method: compare the phone's battery-usage screen over a couple of days before and after the change, looking at Telegram's share of background usage. If the change is large and unacceptable, revert and instead rely on the fact that FCM-delivered notifications still usually arrive within a few minutes even when the app is optimized.

Step 5 — Background Data, Data Saver, privacy tools, and Private DNS

A surprisingly common cause is that the app is simply not allowed to use the network in the background. If notifications work while you are on Wi-Fi and fail on mobile data — or the reverse — this is the first place to look. The asymmetry itself is the clue: a device-wide block would fail on both networks, so a network-specific failure points at a per-network or per-tool restriction.

Shortest path: Android Settings → Apps → Telegram → Mobile data (or Data usage) → enable background data and, where the option exists, allow unrestricted data usage. Then check Android Settings → Network and internet → Data Saver and confirm Telegram is either exempted or that Data Saver is off.

Two related factors are worth ruling out because they produce confusing symptoms. First, privacy tools and always-on privacy tool configurations can interfere with a long-lived connection — empirical observation suggests some tunnels drop idle connections more aggressively than a direct mobile connection, which delays delivery rather than blocking it. Second, a private DNS or ad-blocking DNS resolver that filters Telegram's domains will produce the specific symptom of the app working on one network and failing on another. The reproducible test is simple: switch the private DNS setting to automatic, or disconnect the privacy tool, and repeat the locked-screen test. If notifications return, you have found it.

Also check that you have not enabled any per-app network restriction through a third-party firewall or "network blocker" tool, and that no battery-saver mode is active that disables background data globally. These are easy to forget because they were installed months ago and are not visible in the Telegram or Android settings screens. If you keep a mental list of everything you installed that touches networking, this category of problem becomes much faster to close out.

Step 6 — OEM Autostart and Background Policies, Mapped by Manufacturer

Several manufacturers add an autostart manager on top of Android's own restrictions. The mechanism differs by vendor — some block the app from starting after a reboot until it is launched manually, others kill background processes more aggressively than stock Android, and some do both. If every step above passed and you still miss notifications on a killed app, this is the remaining suspect.

The paths below reflect the typical location at the time of writing. Menu names are localized and differ across skin versions, so use them as a search target rather than an exact route.

Two boundary conditions are worth stating plainly. First, on some vendor skins the autostart manager is a hard gate: if auto-start is off, Telegram may not receive anything until you open it manually, and no notification setting will change that. Second, disabling every power-saving feature system-wide is a poor trade — the correct move is to exempt Telegram specifically and leave the rest of the device's battery management intact.

Example: on a Xiaomi device where Autostart is disabled, a message sent while the phone sits idle may produce no alert at all; enabling Autostart only for Telegram typically restores delivery without touching any global power setting. Note that vendor menus are reorganized between skin versions, so the row that matters may sit under a differently named parent category than the one listed above.

Step 7 — Google Play Services, FCM, and De-Googled Devices

Here is the boundary that many troubleshooting guides omit: on Android, reliable delivery of notifications to a killed app depends on Google Play Services being present, updated, and allowed to run. Telegram's own messaging service does not require Google — you can use Telegram on a device without Play Services — but push delivery to a suspended app does rely on the system's push transport.

If you are on a device where Play Services was removed, disabled, or replaced by a compatibility layer, the expected behavior is that notifications arrive only while the app is running or recently active. This is not a bug you can configure away; it is the designed consequence of removing the push transport. Symptom pattern that confirms it: messages arrive promptly whenever Telegram is open or in the recent-apps list, and stop entirely once the app has been force-stopped or the device has been rebooted and left idle.

Verification steps you can repeat: check Android Settings → Apps for the presence and enabled state of Google Play Services, confirm it is not battery-restricted, and confirm it is not force-stopped. Then repeat the locked-screen test. If notifications return as soon as Play Services is available again, you have confirmed the dependency. Attempting to work around it with a Play-Services-compatible replacement layer is possible in principle but outside the scope of a device-level troubleshooting article — results vary widely by device and ROM, and it is not something to attempt casually on a primary phone.

Step 8 — Persistent Notifications and Other Placebo Fixes

The internet is full of advice that amounts to keeping Telegram permanently alive — pinning a persistent notification, disabling "force stop" behavior, or hunting for a background-connection toggle. Older builds of Telegram on Android did expose connection-related switches in the data and storage settings, and third-party clients have offered similar options. Whether your current build exposes anything comparable is something you should verify rather than assume; on many current builds there is no such switch, because the behavior is managed internally.

Persistent notifications do have a legitimate use: a foreground service keeps the process alive and makes delivery reliable. The cost is a permanent notification you cannot dismiss, plus battery impact. Whether that is worth it depends entirely on how much you value instant delivery — for someone who uses Telegram for work escalation, the answer is often yes; for a general user, fighting the battery system is usually the wrong trade when the underlying issue is a muted chat or a disabled channel.

Why Your Phone Stays Silent While Your Desktop Buzzes

This is the single most common false alarm. Telegram is a multi-device product: your account can be active on several sessions simultaneously, and the servers know which of them are currently connected. When you are actively using Telegram on your desktop, the phone may deliberately not notify you, because the message has already been delivered to a device you are looking at. This is intended suppression, not a broken notification pipeline.

You can confirm this in a repeatable way. Put your desktop client to sleep or quit it entirely, then send yourself a message from another account and watch the phone. If the phone notifies you only when no other session is active, the behavior is by design. The implication for troubleshooting is significant: always test with all other Telegram sessions closed, and never judge a fix by a test you ran while your laptop was open.

There is a related effect worth knowing about. When you read a message on one device, other devices typically clear the corresponding notification. So a notification that appears and then vanishes may be the correct behavior of a synchronized account rather than a bug — particularly if you have a tablet, a desktop, or a browser session signed in. If the disappearance is genuinely unwanted, the lever is the session list in Telegram's settings, not the notification settings on the phone.

Verification and Observation Methods You Can Repeat

Every claim in this article should be testable on your own device. Here is a compact test protocol that keeps variables under control and produces evidence rather than impressions.

1. Quit Telegram on all other devices, or sign those sessions out temporarily. Multi-device suppression will otherwise contaminate every result.
2. Force-stop Telegram from Android Settings → Apps → Telegram, or swipe it out of the recent list. Note which method you used, because the two have different effects on the process state.
3. Lock the phone and leave it untouched for at least ten minutes. This is long enough for Doze to engage on most devices.
4. Send a plain text message from a second account to a private chat.
5. Record the delay until the notification appears, whether it is visible on the lock screen, and whether sound or vibration occurred.
6. Repeat the identical test after each change — one change at a time. Changing two settings at once invalidates the result.

Qualitative trends are what you are looking for: does delivery go from "several minutes late" to "immediate", or from "nothing at all" to "banner appears"? Do not expect deterministic timing. In testing, delivery time varies by device, network, and how recently the app was used, and any specific number you read elsewhere should be treated with suspicion.

Keeping a short written log — change made, observed result, timestamp — turns a frustrating guessing game into a small experiment. Two or three recorded iterations are usually enough to separate a real cause from a coincidence, especially when the fix you tried looked convincing at the time.

Applicable and Non-Applicable Scenarios

Not every notification complaint is worth this much effort, and not every device profile supports the same outcome. The following checklist is meant to help you decide how far to go.

Worth the full procedure: you rely on Telegram for time-sensitive messages, you are on a stock-Android device or a mainstream OEM phone with the autostart manager available, and you can accept a modest battery cost in exchange for reliability. In this profile, working through steps 1 through 6 usually produces a durable fix.

Marginal returns: you receive few messages and the delay is measured in minutes. Exempting the app from battery optimization may not be worth the standby drain, and accepting occasional latency is a rational choice.

Expected limits: devices without Google Play Services, heavily modified ROMs with unpredictable process management, and environments with restrictive network policy. On these, reliable delivery to a killed app is not something the user can configure. The realistic mitigation is to keep the app running and accept that a cold start means a cold start.

Best Practices Checklist and Decision Rules

Once the immediate problem is solved, a few habits prevent recurrence. These are decision rules rather than steps — read them as "if this, then that."

• Prefer per-chat mutes over category mutes. Per-chat changes are scoped, reversible, and do not ripple into unrelated conversations.
• Edit channels in Android, not in Telegram. On modern Android, importance, sound, and vibration are channel properties. Editing them in the system screen is authoritative.
• Make one change at a time and re-test with the app force-stopped. Testing with the app open proves nothing about push delivery.
• Close other sessions before declaring a fix. Multi-device suppression will make a working setup look broken.
• Exempt only Telegram from battery optimization. Wholesale disabling of power management trades a small problem for a large one.
• Re-verify after a major Android upgrade or an OEM skin update. Both can reset or reclassify app battery status.
• After switching phones, re-check permission, channels, and battery status. Notification configuration does not migrate cleanly.

The through-line is that you should be able to name the layer you changed and predict its effect before you change it. If a fix cannot be described that way, it was probably a coincidence, and the problem will return.

Frequently Asked Questions

Summary and Next Steps

Telegram push notifications failing on Android is rarely one problem. It is a permission problem, a channel problem, a background-execution problem, a network problem, or a multi-device suppression that only looks like one of the others. The efficient path is always the same: classify the symptom, work the decision tree top to bottom, change one thing at a time, and re-test with the app force-stopped and other sessions closed.

If you want a concrete plan for the next ten minutes: open Android Settings → Apps → Telegram → Notifications and confirm every channel is enabled with an importance that produces sound. Then set the app's battery category to unrestricted. Then quit your desktop session and run one locked-screen test. Those three actions resolve the large majority of real cases, and if they do not, you now know exactly which layer to investigate next — and, just as importantly, which layers you can stop worrying about.

Future Trends and Version Expectations

Two directions are worth watching as Android and Telegram continue to evolve. The first is that background execution policy keeps tightening, so the balance between notification reliability and battery life is likely to remain a moving target rather than settling into a fixed set of settings. The second is that notification configuration increasingly lives in the system layer rather than inside individual apps, which means the skills in this article — reading channel importance, checking battery classification, testing with a force-stopped app — are likely to stay useful even as individual menu labels change.

The practical takeaway is to re-verify rather than to memorize. After a major Android upgrade or an OEM skin refresh, run the locked-screen test once and confirm the three core layers are still as you left them. That habit costs a minute and prevents the most common recurrence, where a configuration that worked perfectly last month quietly resets after an update.