sigma2017
commented
1 year ago Hello again, After I completely cleaned and uninstalled of current installed app from all phones, I reinstalled FCM again directly from google play instead of using apk downloaded from here and looks like the notifications now work, not all the time but most of the time so seems like i was partially wrong with what I believed in the first place. Unfortunately, can not rely on the notifications, like I said in previous post...... The biggest issue here which is still present is the answer dialog, sometimes it appears on the locked phone, sometimes you need to manually open the application in order to answer (green button). So the issue is very real and should be fixed. Ans yes, I will say again, I can rely on schildi because when call or being called, all the time I have an usable ESTABLISED call in contrary with former element android app which in many cases do not establish the call and remains in "connecting" and "calling" status after the call was answered. Thank you.
github-actions[bot]
Describe the bug SchildiChat is loosing connectivity to the synapse server once the phone screen is off for about 10-20 mins or even earlier sometimes.
To Reproduce It is happening almost all the time with all android phones I am using.
Expected behavior Expected behavior is to receive notifications and to be able to answer a call when somebody calls me. Nothing happens. Phone is not ringing, no button available to answer.
Smartphone (please complete the following information):
Additional context
Upstream relevance
Both Element or SchildiChat are loosing connectivity to synapse server, that's why almost all the time I am not able to see notifications doesn't matter the settings related to battery optimization and so on.. Most of the times I have to manually open the application in order to see the received messages. Same applies with the calls, you can NOT rely on it. You have to use another messenger to announce your friend that you gonna chat or call him on SchildiChat. Once the application is open and somehow the connectivity with the server is automatically re-established in about few seconds, you can call and the call is working. This is not happening with element android, in most of the tries, the caller remain in "calling" and the other phone remain in "connecting" after he answered to the call. That's why I am using SchildiChat because at least I can trust that I will be able to have an audio or video call with a friend. Is clear that this is a big step ahead for SchildiChat when compared with the former element-android app. I am using one synapse server deployed on a vps with coturn integrated. Is not a server issue when it comes to notification because for example FluffyChat never miss a notification because somehow it never loose the server connectivity. How it does? I really don't know. Unfortunately fluffychat has some other bugs... Also web element works perfect in all the situations, all the calls are established and share screen works as expected. So, there is NO issue related to the server side.
I hope you got my point here, I can not rely on SchildiChat because almost all the time I miss either messages or calls. This is he biggest issue SchildiChat (and Element) have. One more thing: Troubleshoot Notification checks all the checks all the time because once the server connectivity is re-established it is working as expected. The issue here is actually server connectivity not the notifications. Thank you.