Get Element Android Notifications Without Google Services
Set up Element Android with UnifiedPush and ntfy, then check the self-hosted Matrix gateway and Android background settings when alerts fail.
For reliable Element Android alerts without Google services, install the F-Droid build of Element and a UnifiedPush distributor such as ntfy, then select that distributor in Element. On a self-hosted Matrix server, the notification route must also reach a compatible push gateway—ntfy provides a Matrix gateway, either through its public service or a server you host. Without a distributor, the F-Droid build can use background polling, but Android may delay that fallback when the app is idle.
Matrix push is a chain: Synapse sends a notification request to a push gateway; the gateway relays it to a distributor app on the phone; the distributor wakes Element so it can process the event and show an Android notification. A failure at any link can look like “Element notifications are broken.” Installing a new homeserver does not by itself supply a phone-side push distributor.
Element Android’s project documentation distinguishes its app flavors. The Google Play build uses an embedded FCM distributor by default when no other distributor is selected. The F-Droid build excludes that Google-dependent library; if no compatible distributor is installed, it uses polling. Both flavors support an external UnifiedPush distributor when the feature is enabled and the user opts in. For a phone without Google services, F-Droid plus ntfy is the simplest documented route.
ntfy has two roles in this setup: its server is a Matrix-compatible push gateway, and its Android app is the UnifiedPush distributor. These roles are related but distinct. You can use the public ntfy service for a simpler setup, or operate an ntfy server if you want to control the gateway infrastructure. Self-hosting the Matrix homeserver does not require that you also self-host ntfy.
For example, if a Fairphone or a de-Googled Android device receives messages only while Element is open, install the ntfy distributor and select it in Element first. Then test again with Element in the background. If notifications still fail, determine whether ntfy itself receives a test message before changing Synapse settings.
If you run your own ntfy server, it must be reachable over HTTPS from both Synapse and the phones, and its Matrix gateway must be configured. The current Element guide uses the example endpoint https://ntfy.example.com/_matrix/push/v1/notify. Open the corresponding URL for your domain in a browser; a configured ntfy Matrix gateway should return a response indicating {"unifiedpush":{"gateway":"matrix"}}. Confirm DNS, TLS certificate trust, firewall rules, and the ntfy server’s base-url setting if it does not.
Synapse blocks outbound requests to private IP ranges by default. If your ntfy server is reachable only at a private address, the UnifiedPush troubleshooting guidance recommends allowing the push server’s IP as Synapse sees it. Add only the specific address under the top-level ip_range_whitelist setting in homeserver.yaml, for example:
ip_range_whitelist:
- '192.168.1.20'
Use your actual gateway address, not this example. This exception allows Synapse to make outbound requests to that address and should be kept as narrow as your network allows. Restart Synapse after changing the configuration. If you already use an HTTP proxy, note that Synapse documents the IP range setting as ignored when a proxy is in use.
Do not treat polling and push as identical. Polling can be useful as a fallback when no distributor is installed, but it may consume more background activity and can be less timely under Android power management. If immediate alerts matter, test with Element closed and the screen off, then adjust the device’s background settings or the push server path based on the failed check.
Set up Element Android with UnifiedPush and ntfy, then check the self-hosted Matrix gateway and Android background settings when alerts fail.
Restore background photo detection by checking Nextcloud upload settings, iOS permissions, battery mode, and the limits of iPhone background scheduling.
Compare ONLYOFFICE font hinting modes, check zoom and Linux font availability, and verify whether blur is limited to the editor or affects the whole desktop.
Convert a PDF locally in ONLYOFFICE Desktop Editors, then review the DOCX for layout changes, scanned pages, and text that needs correction.
Add your ownCloud account to ONLYOFFICE Desktop Editors, understand what the connection enables, and choose between direct access, sync, and browser editing.
Use the right portal or WebDAV address, test HTTPS reachability from your phone, and distinguish private-network, TLS, and login problems.
Build and test a custom ONLYOFFICE Desktop Editors plugin, install its .plugin archive, and activate developer tools for debugging.
Make a Python function available in Calc, run it against the open spreadsheet, and troubleshoot missing macros or imports without mixing up LibreOffice and system Python.
Lock a specific passage against routine edits while keeping the rest of a Writer document usable, and learn when file encryption is the better choice.
Fix hard-to-see spreadsheet text by checking the theme, cell font color, fills, and conditional formatting in Calc.