Repository navigation
Support notifications for f-droid version #257
Description
In #58 it was asked to release an version to F-droid , thanks that this happend.
Also there were a huge discussion related to #75, why not to use gcm/fcm.
To summarize, there are users which have concerns to use Google- infrastructer in anyway.
#75 was closed because of the relation to #58.
But now we do have a gcm/fcm free version of talk so I would like to ask to support notifications in this version.
My proposal would be to handle it like every other open source messenger like telegram, signal or riot by keeping it in foreground through a notification.
Thanks in advance! And please keep up the great work.
Activity
gradinaruvasile commentedon Jul 25, 2018
mario commentedon Jul 25, 2018
You do understand this will kill through battery and still be super NOT reliable?
gradinaruvasile commentedon Jul 25, 2018
Well it is still worlds better than NO notifications.
Riot (F-Droid version) for example works quite well even with 20 sec checks. The app places a notification icon and it worked for me on Android 6 and 8.1. It was reliable. Now i'm not arguing in some setups this could create issues, but you could take a look how Riot works, it seems quite all right.
gradinaruvasile commentedon Jul 25, 2018
@nr458h I used the fdroid Riot for a half a year or so and it was very stable. I used even a faster, 20 sec refresh time. The overall battery time improved only marginally after i installed the google play version.
mario commentedon Jul 25, 2018
Not metadata-free, just that it's all on your server. Push is the only way to wake up a device. All content in a push message is encrypted with YOUR OWN DEVICE-SPECIFIC KEY which can be verified.
Gaeldrin commentedon Jul 30, 2018
+1, @DudleyDursley summarized it perfectly.
A little repetition for newcomers (original link): the only thing I wish I knew is how WhatsApp does it as it works perfectly and shows no "permanent notification" at all (maybe a hidden notification? I know the icon can be hidden but whole notification?) without any noticeable battery drain. Facebook Messenger works the same at least for calls (I receive calls immediately, messages often slip by without notification..).
I am running LineageOS 14.1 (Android 7.1.2) without any Google licensed apps.
Edit: added original link and also a correction: today even the Messenger works great for message notifications
mikelupe commentedon Aug 3, 2018
+1, @DudleyDursley summarized it perfectly.
testbird commentedon Aug 3, 2018
Only workaround with f-droid I know is using something like the https://delta.chat Email-Messenger, to ask each other to call back.
The situation could be improved of course:
And there are at least two ways to solve the push issue properly:
testbird commentedon Aug 3, 2018
In case you haven't seen it: Battery consumption in deltachat is down to 1% (seems less than what gcm would use if it were installed) and reliability is good since v0.18.2
bam80 commentedon Aug 3, 2018
@testbird, it's fine!
Is there any overhead of IMAP-push notifications compared to GCM?
testbird commentedon Aug 3, 2018
Don't have any comparison, but the Email-chat spec that deltachat uses sure leaves room for some Email-notify spec that could minimize the overhead.
200 remaining items
ASerbinski commentedon Sep 15, 2025
"Nextcloud services" is a poor solution, it polls the server, which means delayed notifications and increased power consumption.
Use this; https://gitlab.com/Nextcloud-Push
0x47 commentedon Sep 15, 2025
While that might be so, the repository/app you linked (and, presumably, of which you are the owner) seems outdated and unmaintained. The latest supported version is Nextcould 23, while I am running Nextcloud 31.
ASerbinski commentedon Sep 15, 2025
It is maintained
p1gp1g commentedon Sep 16, 2025
I'm working on it very soon :)
TheDarkula commentedon Oct 8, 2025
@p1gp1g That is excellent!
Is there an open issue/pull request for this?
darioandreella commentedon Oct 14, 2025
Thanks @mahibi I even tried to look around before opening that #5457 but - as in forums or other platforms - you relay on searching or reading it all... not a guarantee of success, but a time consuming operation for sure.
I have been daily-driving Android without Google for 9 years now, and would appreciate a solution using NextPush to start using Talk as a communication platform (I use Element X that relays on that, and works fine). I don't think that pulling notifications from the server would be that great (not on smartphones at least, it may be fne on desktops).
With the upcoming move by Google to force any devs to give away their id, restricting side-loading etc, there will be even more need for alternatives, at least until we don't get a decently working Linux tablet or phone, or an alternative to Google Android, that even in its AOSP declination still has several blobs of locked stuff (software and hardware).
Cheers!
Nextcloud 32
Talk for Android 22.0.2 (2025-10-06-15.21.56 via Obtanium)
LineageOS 23 (Android 16)
Nextcloud Hub 25 Autumn (32.0.0 as Docker, not the AIO)
CodeByMrFinchum commentedon Nov 6, 2025
I hope the nextcloud team reconsiders other notifications options, such like UnifiedPush (NextPush), they don't have to create something completely new but integrate something that is already existing, it would ofcorse still be work.
I think @darioandreella has some good points, Google is shutting down android and many people dislike this which will fuel the need for degoogled solutions.
I use NextCloud talk daily on the phone, I'm about to switch to a degoogled phone, and having no notifications for NextCloud talk seems very annoying.
Fuseteam commentedon Nov 7, 2025
@CodeByMrFinchum it isn't just on Nextcloud to implement it, it is all open source so anyone can work on it and contribute it
As mentioned here:
there are people look into it, the best we can do to support that is react and/or subscribe to the issue to follow progress (being subscribed here for that progress, i'm slightly annoyed by these "+1" replies, but that's a separate topic)
CodeByMrFinchum commentedon Nov 7, 2025
Thats exactly why I commented (and reacted) :)
Trying to show that there are more people out there having an interest in this topic but lagging the knowledge to help by submitting code.
Fuseteam commentedon Nov 7, 2025
to do that simply react on the initial post or the post where it was declared that they were looking into it, nagging only disrupts and doesn't help— it also buries post with important information such as
among many others hidden in "xx remaining items"
The more "+1" posts we post, the more information gets hidden this way, the more annoying it is to developers who might want to reference that information
Just subscribe, react, sit back and relax. When someone posts an update, you'll get a notification: hopefully next time it will be about progress on the implementation
CodeByMrFinchum commentedon Nov 7, 2025
Hi @Fuseteam,
thanks for explaining how this works.
So it seems that showing my interest and support in a comment to an issue from 2018 (which looks a bit out of date now in 2025, as now people mention new concrete implementations) is not really okay, because it makes unnecessary comments, hides the real conversation, and notifies everyone.
Also showing support for people and their suggestions is seen the same as posting "+1".
Good to know for next time, I do not interact often on github. I was honestly a bit unsure about posting at all, but thought that supporting a comment that had a specific suggestions that I find good in a niche topic would be good (more concrete comments show greater interest), but thank you for being so kind and showing me how I should do it better: I should not interact (with a comment).
p1gp1g commentedon Dec 4, 2025
For your information:
* there is also a PR to get web push on the web front end
mahibi commentedon Apr 30, 2026
Thank you @p1gp1g 🙏 💯
UnifiedPush will be officially available with Nextcloud 34 on 2026-06-09