Molly merged it’s Unified Push functionality into the main branch. The until now specialized Molly-Unified Push app informs the user about that and suggests a change to the main branch.
So some days ago I uninstalled my long used Molly-Unified Push app and installed the ordinary Molly-FOSS now, still using Unified Push via ntfy.
I have the impression that the current Molly-FOSS (7.26.1-1-FOSS) does often (but not always) not play the configured notification sound until I manually wake up the screen for any other reason. When I do this it can happen that I suddenly get two or three beeps for received posts which are already older than an hour.
Am I the only one with that phenomenon?
The accu optimization for both Molly and ntfy is of course switched off, so they should both run all the time. What else could it be?
Update: there’s a (new?) option in Settings | System, at the bottom: UnifiedPush, it’s called “Enable the distributor”. That was off in my case. I switched it on now to see if it has any effect.
Sorry, I haven’t noticed that there was already a very interesting thread here about that topic. I learned a lot there.
So when the /e/OS user had a ntfy installation from before and now he activates this new UnifiedPush option he will find indeed two ntfy processes running, with the same name, great.
To get a clear environment I uninstalled my ntfy installed long ago from F-Droind. As expected only one ntfy remains, the one from /e/OS.
Then, when you run a firewall like RethinkDNS and this is configured to disable network access for new processes you will find this new /e/OS ntfy still blocked. You must also enable it in the firewall.
But then it works. I received several messages with an ordinary beep. The question is still open if the coexistence of two ntfy processes was the reason for my delayed notifications.
Molly-UP is a branch of Molly, and this branch has been reintegrated (merged) into the main branch, so the branch is now obsolete and will not be developed further. When you want to use UP functionality in future you should install Molly or Molly-FOSS. This is what the last update of Molly-UP says in a message box when you start it these days.
Molly-UP is still in the Molly-F-Droid-repository, you can scan this QR-code using your F-Droid-client. In the same repo is the new UP-able Molly-FOSS. Uninstall Molly-UP, install Molly-FOSS, both from within your F-Droid-client.
Note: you will still need a proper QR-code for the MollySocket server for UP. This is the only method to specify the server’s address. If you don’t have any better QR-code, take this one.
You can then decide if you use your still installed ntfy or the new /e/OS distributor as I mentioned above.
After more than a day now I would say uninstalling ntfy and using the new OS integrated distributor (“ntfy”) works as expected. I got several messages with ordinary beeps. Nevertheless there’s a gap between the blinking LED (which is always some seconds faster) and the beep but in the last 24h the beep has never been delayed for an hour or more as I had it in the beginning. My conclusion is: my new installed Molly had a problem with the old ntfy and the Molly entry in it’s configuration.
