Element can receive messages normally while it is open yet fail to alert you after the screen is locked. On an Android phone without Google Play Services, that usually points to the delivery path rather than the Matrix account itself. The goal of this guide is not merely to make one test notification appear. A good result is repeatable: messages arrive while Element is in the background, after the phone has been idle, and without needing to reopen the app.
This guide focuses on current Element X for Android, which Element recommends for new users. As of October 6, 2026, the latest public GitHub release is Element X Android 26.09.4, and recent releases include active UnifiedPush components. UnifiedPush is an open protocol that lets an Android app receive push messages through a distributor other than Google's Firebase Cloud Messaging (FCM). Element's own project guidance states that installing a UnifiedPush distributor allows Element X to detect it and offer it as a push provider. See the Element X Android repository, Element X Android releases, and the Element team discussion on notifications without Google Play Services.
Before changing settings, define the result you are trying to achieve. A notification setup is healthy when all of the following are true:
If messages appear only after opening Element, you have synchronization but not reliable background delivery. If they appear immediately while the app is open but are delayed when it is closed, focus on the push distributor and Android background restrictions rather than room notification rules.
Most mainstream Android applications use FCM, Google's push service, to wake the app when new data is available. Element's notification documentation explains that FCM requires Google Play Services. On a de-Googled phone, an FCM-only configuration cannot provide the normal wake-up path. Android also limits what ordinary applications can do in the background, especially when a device enters idle states.
UnifiedPush replaces that dependency with a distributor. A distributor is the Android app that maintains the push connection and passes incoming notifications to applications that registered with it. The UnifiedPush project lists ntfy, Sunup, NextPush, gCompat-UP, and other options. See the official UnifiedPush distributor list.
Start with the simplest failure point. On Android 13 and later, applications need the POST_NOTIFICATIONS runtime permission before normal notifications can appear. Open Android Settings, find Element X under Apps, and verify that notifications are allowed. Also review individual notification categories if your Android version or manufacturer exposes them.
Android's official documentation confirms that newly installed apps on Android 13 or later cannot send ordinary notifications until the user grants permission. See the Android notification permission documentation.
Quality check: if Android shows notifications disabled, fix that first and retest. If notifications are already allowed but nothing arrives while Element is backgrounded, continue to the push provider.
Install a UnifiedPush distributor from a source appropriate for your device. ntfy is a common choice because it can use its public server or a self-hosted server. The UnifiedPush quickstart for ntfy instructs users to install ntfy, grant the required notification and battery permissions, then select ntfy as the distributor inside compatible applications. See the official ntfy UnifiedPush quickstart.
Open ntfy and make sure UnifiedPush support is enabled. If you use a self-hosted ntfy server, verify that the Android app is connected to that server and that the server is reachable over HTTPS from the phone's current network.
Quality check: simply having ntfy installed is not enough. The distributor should be enabled and reachable. If Element cannot see the distributor after installation, fully close and reopen Element X, then check for app updates before changing server-side Matrix settings.
Open Element X settings and go to the notification area. When a compatible distributor is detected, Element X can expose a push-provider choice. Select the installed UnifiedPush distributor rather than Firebase/FCM. Element's project maintainers explicitly described this flow for devices without Google services, and current source includes a UnifiedPush push-provider module.
If your build does not show a provider selector even after a distributor is installed, do not assume the homeserver is broken. First update Element X to a current supported build and restart both Element X and the distributor. UI labels have changed across Element X releases, so the exact menu name may differ.
Quality check: the useful sign is not just that the provider name appears. Send a real message from another Matrix account while Element is backgrounded. A working provider should cause the device to wake Element and display the message notification without opening the app manually.
UnifiedPush depends on the distributor staying reachable. If Android places ntfy or another distributor in a Restricted battery state, the push connection can be suspended. Android documents three broad background battery modes on many devices: Unrestricted, Optimized, and Restricted. Restricted can prevent jobs, alarms, and foreground-service behavior that apps rely on.
Open Android Settings for the distributor and change battery usage from Restricted to Unrestricted if notifications are delayed or disappear during idle periods. You can also inspect Element X itself and make sure it is not explicitly restricted. Manufacturer-specific Android builds may add separate controls for auto-start, background data, or app sleeping.
Google's Android documentation notes that a user-selected Restricted state can fully prevent an app from running in the background on some devices. See Android background optimization guidance.
Quality check: lock the phone and leave it idle for 10 to 20 minutes, then send several messages from another account. If alerts arrive promptly and consistently, the background path is healthier than a test performed immediately after opening the app.
| Observed result | Most likely area | Next action |
|---|---|---|
| No notification even while Element is open | Room rules, account notification settings, or Android notification permission | Check Element's room/account notification settings and Android permission first. |
| Notifications appear only when Element is opened | Push provider or distributor background connection | Confirm Element is using UnifiedPush and remove battery restrictions from the distributor. |
| Works for a few minutes, then stops after idle | Doze, OEM battery controls, sleeping-app policies | Set the distributor to Unrestricted and inspect manufacturer-specific background controls. |
| Element shows a distributor, but no real messages arrive | Distributor server, Matrix push gateway, or endpoint rate limiting | Test a different distributor/server before reinstalling Element. |
| Only one room is silent | Room-specific notification rule | Check that room's notification level instead of changing global push settings. |
A configuration can be technically correct and still be a poor fit. Element's tracker documents cases where some UnifiedPush endpoints, including public ntfy infrastructure in certain Matrix scenarios, can be rate-limited, which means registration may look correct while notifications still fail to arrive. See Element's issue on UnifiedPush endpoint rate limiting.
If permission, provider selection, and battery settings are all correct but delivery remains inconsistent, try a different UnifiedPush distributor or a self-hosted push server. UnifiedPush documents both hosted and self-hosted choices. This is often a better diagnostic step than repeatedly clearing Element data, because it changes the part of the delivery chain most likely to be failing.
Self-hosting can provide more control, but it adds operational responsibility. For ntfy, the Matrix gateway must be configured correctly for a self-hosted deployment. The official UnifiedPush ntfy guide notes this requirement. Do not move to self-hosting solely because one test notification was delayed; switch when failures are repeatable and you have already ruled out Android restrictions.
The previous-generation Element Android application also implemented non-FCM operation and UnifiedPush. Its official documentation describes both F-Droid background polling and UnifiedPush support. However, Element now recommends Element X for new users, so the current Element X path is the better starting point unless you have a specific compatibility requirement. The legacy implementation details remain useful for understanding why polling alone is less reliable under Android idle modes. See the archived/current project documentation for UnifiedPush in Element Android.
There is no universal setting that guarantees instant delivery on every Android build. Device vendors can impose additional background restrictions, networks can interfere with persistent connections, and a push endpoint can be temporarily unavailable or rate-limited. The strongest result is therefore repeatable behavior across several background and idle tests, not a single successful notification.
Compare seven tools that support or complement WSUS, from Microsoft’s native console and diagnostics to third-party patch publishing and remote deployment.
Compare six Windows system monitoring tools for server health, application visibility, and alerting, with current notes on deployment and licensing.
Compare seven Wake-on-LAN tools by features and availability, including free utilities, network-admin suites, and 2021 picks that have since been retired.
Compare nine ping tools for quick reachability checks, subnet discovery, TCP tests, and latency monitoring, with guidance on which one fits your network task.
Compare the best TFTP servers for Windows, Linux, and macOS, including SolarWinds, Tftpd64, tftpd-hpa, atftpd, haneWIN, and dnsmasq.
Compare five Microsoft Access alternatives for desktop, SQLite, no-code, and browser-based database work, with strengths, limits, and best-fit use cases.
Compare open-source and closed-source monitoring tools by cost, support, customization, security, and current options including Zabbix, Nagios, PRTG, and more.
Understand how ingress and egress describe incoming and outgoing traffic, why direction depends on the network boundary, and how to monitor bandwidth and spot risky data transfers.
Compare six free syslog servers and collectors for Windows and Linux, including GUI tools, open-source options, search, alerting, and secure transport.
See what Microsoft IIS does, how its request pipeline and application pools work, and when Apache, NGINX, or Caddy may fit your web server needs better.
