Confirm that we have the same parameters as other clients use

[gnunicorn]

like Element-X or Fluffy Chat have to ensure we don't miss any important parameters in the way to ensure notifications are visible.

Is there anything in the options or flags they use compared to what we have that could explain why our notifications sometimes go missing?

[gnunicorn]

Fluffychat - for iOS just uses defaults and for linux has its own way of doing things, but on Android I've found a few things that indeed are different:

They are using the AndroidNotificationCategory.message on it:

https://github.com/krille-chan/fluffychat/blob/583bf5f2da7a492e121330c1151b510d8050561e/lib/utils/push_helper.dart#L251C15-L251C42

And mark them as highly important:

https://github.com/krille-chan/fluffychat/blob/583bf5f2da7a492e121330c1151b510d8050561e/lib/utils/push_helper.dart#L275-L276

[gnunicorn]

Further Reading about Android Notifications from the Element-X team . Not all applies for us (we don't have a dedicated f-droid version without FCM support yet), but it shows the problems space and gives a good intro...

[gnunicorn]

Element-X Android also sets the category to Message:

https://github.com/element-hq/element-x-android/blob/a69b04e3a7d7ab047703f06d2efa1d1d0c9c39d4/libraries/push/impl/src/main/kotlin/io/element/android/libraries/push/impl/notifications/factories/NotificationCreator.kt#L137

So does Element-X iOS (though it seems to be a string only)
https://github.com/element-hq/element-x-ios/blob/21a15936a9943abbad0493f3c5e48685a961b0e3/NSE/Sources/NotificationContentBuilder.swift#L73

Android Element-X has a bit more of a sophisticated approach to setting the priority for backwards compatibility:
https://github.com/element-hq/element-x-android/blob/a69b04e3a7d7ab047703f06d2efa1d1d0c9c39d4/libraries/push/impl/src/main/kotlin/io/element/android/libraries/push/impl/notifications/factories/NotificationCreator.kt#L177-L192