Molly UP and eOS

This is to follow up on this thread which was automatically closed a while ago:

Since a few days I experience a rather well performing Molly-UP-config on my device (3.7-a16-20260410606674-community-sunfish) which I tried because my previous setup seemed to drain my battery more than I liked:

I changed from:
extra install of ntfy io.heckel.ntfy with push server https://ntfy.yourdevice.ch and Mollysocket via https://mollysocket.yourdevice.ch
to:
eOS integrated ntfy foundation.e.ntfy + https://mollysocket.yourdevice.ch
Result:
I receive all test notifications in due time (Molly internal and UP-Example) and (most important for me) I even get call rings whilst device is asleep.

1 Like

That’s exactly what I have for about two weeks now.

Some days ago my device still got quiet. But it has not been this problem, it was another /e/ related issue I described long time ago here. I’m rather sure this happens also with my brand new 3.7-t.

1 Like

This is also my current setup, with push.murena.com as push server.
I have additionally set the foundation.e.ntfy options to WebSocket (as mentioned in the forum, there is not an foundation.e.ntfy app icon, so you need an additional app that can launch activities to access the settings).

There is also the MollySocket server molly.adminforge.de, but the admins are currently figuring out why a considerable message delay (or even message loss) occurs after a while; see MollySocket: Verzögerte Zustellung beobachtet - adminForge Services - adminForge Community (in German)

1 Like