Not receiving new message notification

[UntypedLetter]

Describe the bug
When I send a message from Windows to Android, it does not display any notification on Android. Only when Schildi is opened, then it shows the green circle with 1 inside. Battery is set to unrestricted. Even while Schildi is open, new messages do not produce a banner notification, rather just a badge / green circle. A week or two ago, it was working perfectly, but then something happened. I have already run the notification troubleshooter and tests came correct. The notable thing is that the troubleshooter was able to produce a banner notification, yet newer messages were unable to produce it.

To Reproduce
Steps to reproduce the behavior:

1. Send a message from Windows Element.
2. No banner notification is received on Schildi. But when you open Schildi, a green badge will be displayed.

Expected behavior
A banner notification should be triggered for every new message.

Smartphone (please complete the following information):

• Device: Samsung Galaxy A03
• OS: Android 13

Additional context

• App version: 0.11.4(12100)
• Store: Google Play
• Homeserver: matrix.org
• Related experimental/labs settings: No
• Logs have been submitted using the app's built-in bug report (/"rageshake") mechanism: No

Upstream relevance

• Does this issue exist in Element X Android?
  I don't know since I am not using Element X.

[kitters-kat]

I also have this issue on 0.11.5 from SpiritCroc's F-Droid repo using unified push. Might be upstream: element-hq/element-x-android#7160

[woiwoiwoiwoi]

I also think it's upstream I had the same problems using Element X. Downgrading solved them.

[woiwoiwoiwoi]

Noticed I forgot to mention the upstream issues here and the hopeful fix here.

[bestskillzzz]

Noticed I forgot to mention the upstream issues here and the hopeful fix here.

For me it only shows you have blank new messages and what is way to fix I tried using PR linked artifact to issue that you linked but it didn't work for notifications? Also schildichat doesn't have actions and debug build?

[woiwoiwoiwoi]

So the upstream fix has made both Element X and SchildiChat Next functional again for me. That's the good news. However, I now noticed that I am also not receiving any notifications. I had not noticed before, since I had turned off notifications on purpose. But now I turned them on and they don't work. However, they don't work with Element X either. So I would still guess the issue is upstream - the first above-mentioned issue might be the right one after all.

This is with a selfhosted Matrix Tuwunel server and selfhosted ntfy instance.

[asimons04]

Dumb question: Does Schildichat-Next require the use of some kind of push/notification server to receive message notifications?

Can't it just run in the background and get notifications directly from the home server?

• I run my own Matrix homeserver
• My devices are all de-googled, so no FCM.
• I don't want to setup and run a Nfty or other push notification service
• I've used Schildichat (Legacy) for years and background sync has worked perfectly. The battery drain from keeping it running in the background has never been an issue.

I don't even see the option in -Next for "background synchronization" like was is available in Legacy.

Is this planned for -Next?

[SpiritCroc]

Dumb question: Does Schildichat-Next require the use of some kind of push/notification server to receive message notifications?

Right now, yes.

Can't it just run in the background and get notifications directly from the home server?

* I run my own Matrix homeserver

* My devices are all de-googled

* I don't want to setup and run a Nfty or other push notification service

* I've used Schildichat (Legacy) for years and the battery drain from keeping it running in the background has never been an issue.

Newer Android versions are getting stricter and stricter with that, so even if battery drain is managable, reliability is also a concern.

I don't even see the option in -Next for "background synchronization" like was is available in Legacy.

Is this planned for -Next?

No, not worth the effort from my end. If it gets implemented for Element X, sure, we'll not remove it if it's already there. But nothing I want to spend time on implementing or maintaining currently.

[asimons04]

No, not worth the effort from my end. If it gets implemented for Element X, sure, we'll not remove it if it's already there. But nothing I want to spend time on implementing or maintaining currently.

Disappointing, but fair if it's something that would require major effort. Guess I'll stick with Legacy until I just can't anymore.

Newer Android versions are getting stricter and stricter with that, so even if battery drain is managable, reliability is also a concern.

UP requires Ntfy which requires running it in the background and exempting it from battery optimizations. So it just seems like that is kicking the can to another app. Like I said, I'll just stick with Legacy as long as I can, or maybe I'll bug the ElementX project to re-add background polling.