You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 7, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 7, 2026. It is now read-only.
Still trying to get some form of incoming call working on Android
Currently using latest addition loopSound to get a ringtone to play on incoming call, works fine, except the notification dismisses itself in 3-4 secs
Could we also get FLAG_ONGOING_EVENT for AndroidFlags such that the notification remains heads-up until interacted with?
1- ongoing: true doesn't do anything (reproduced in stock rn app, similar issue here #450),
2- foregroundService doesn't work either. I read that it now takes 10 seconds to show, but even after 10 seconds, doesn't show. Android docs mention an exception for foregroundServiceType=phoneCall: https://developer.android.com/guide/components/foreground-services , but that doesn't work either
3- Fullscreen notifications have issues I mentioned earlier #501
I tried adding the constant value 2 for FLAG_ONGOING_EVENT in notification flags but it throws an error
what error? Just curious - as with the other issues, more than happy to accept any PR that seems reasonable. It's not a use case I personally need (so I'm not motivated to personally author it, being honest) but it is one I would like to support (so I am motivated to collaborate in any way possible...)
TBF this is a use case that is supposedly already addressed in the lib with the ongoing attribute, so this could be a bug rather than a feature request
EDIT: Looks like I misunderstood ongoing, which means "ongoing in the notification panel" rather than "persists as heads-up".
So my bad, no, not a bug, and seems FLAG_ONGOING_EVENT has the same behavior, which does not solve the persistent notification use case
Sorry for the confusion, closing this while looking for other options
TBF this is a use case that is supposedly already addressed in the lib with the ongoing attribute, so this could be a bug rather than a feature request
EDIT: Looks like I misunderstood ongoing, which means "ongoing in the notification panel" rather than "persists as heads-up". So my bad, no, not a bug, and seems FLAG_ONGOING_EVENT has the same behavior, which does not solve the persistent notification use case
Sorry for the confusion, closing this while looking for other options
Hi @frozencap,
Did you manage to have an persistent incoming call notification working ?
Cause I'm having a similar issue:
my notification is being moved to the "notifications shade" instead of staying on the foreground and visible, despite being associated with a foreground service, and being setup as ongoing.
Activity
mikehardy commentedon Sep 8, 2022
what error? Just curious - as with the other issues, more than happy to accept any PR that seems reasonable. It's not a use case I personally need (so I'm not motivated to personally author it, being honest) but it is one I would like to support (so I am motivated to collaborate in any way possible...)
ice-cap0 commentedon Sep 8, 2022
adding this to
androidobject ofdisplayNotificationgetting
ref: https://developer.android.com/reference/android/app/Notification#FLAG_ONGOING_EVENT
ice-cap0 commentedon Sep 8, 2022
TBF this is a use case that is supposedly already addressed in the lib with the
ongoingattribute, so this could be a bug rather than a feature requestEDIT: Looks like I misunderstood
ongoing, which means "ongoing in the notification panel" rather than "persists as heads-up".So my bad, no, not a bug, and seems
FLAG_ONGOING_EVENThas the same behavior, which does not solve the persistent notification use caseSorry for the confusion, closing this while looking for other options
hadri3n commentedon Nov 1, 2024
Did you manage to have an persistent incoming call notification working ?
Cause I'm having a similar issue:
my notification is being moved to the "notifications shade" instead of staying on the foreground and visible, despite being associated with a foreground service, and being setup as ongoing.
mikehardy commentedon Nov 1, 2024
@hadri3n you might like the work that happened this week --> #1134
hadri3n commentedon Nov 1, 2024
I may actually love it ! Thanks for pointing it out ! 🙏