[GH-ISSUE #702] Using ntfy.sh, messages take hours to arrive (Android) #514

Closed
opened 2026-05-07 00:24:59 +02:00 by BreizhHardware · 3 comments

Originally created by @go-vegan on GitHub (Apr 15, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/702

I was under the impression that the public ntfy.sh server uses FCM and does not require using the instant delivery method.
Was I wrong?

Originally created by @go-vegan on GitHub (Apr 15, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/702 I was under the impression that the public ntfy.sh server uses FCM and does not require using the instant delivery method. Was I wrong?
BreizhHardware 2026-05-07 00:24:59 +02:00
Author
Owner

@binwiederhier commented on GitHub (Apr 18, 2023):

I assume this is on Android?

I think if this was a widespread problem, we'd see more complains. It definitely doesn't take hours or even minutes for messages to be delivered. Usually just a second. If the phone is in deep sleep, it may take a minute or two, sometimes longer. But rarely.

It does depend heavily on your phone, and whether or not you have disabled battery optimizations. Also check out https://dontkillmyapp.com/ for phone-specific optimizations.

<!-- gh-comment-id:1513314356 --> @binwiederhier commented on GitHub (Apr 18, 2023): I assume this is on Android? I think if this was a widespread problem, we'd see more complains. It definitely doesn't take hours or even minutes for messages to be delivered. Usually just a second. If the phone is in deep sleep, it may take a minute or two, sometimes longer. But rarely. It does depend heavily on your phone, and whether or not you have disabled battery optimizations. Also check out https://dontkillmyapp.com/ for phone-specific optimizations.
Author
Owner

@binwiederhier commented on GitHub (Apr 22, 2023):

Closing this for now. Let me know if you still have issues. Happy to re-open

<!-- gh-comment-id:1518448456 --> @binwiederhier commented on GitHub (Apr 22, 2023): Closing this for now. Let me know if you still have issues. Happy to re-open
Author
Owner

@go-vegan commented on GitHub (Apr 22, 2023):

I'm using LineageOS 18.1 and have excluded the app from the battery optimization.
Also tried clearing the app's data and reinstalling several times.

If I remember correctly, it started after restoring the app using Titanium Backup, but now whatever I do I can't seem to fix it :(

<!-- gh-comment-id:1518604651 --> @go-vegan commented on GitHub (Apr 22, 2023): I'm using LineageOS 18.1 and have excluded the app from the battery optimization. Also tried clearing the app's data and reinstalling several times. If I remember correctly, it started after restoring the app using Titanium Backup, but now whatever I do I can't seem to fix it :(
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#514
No description provided.