You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even with all notifications set to "ON" and the switch "Enable audible notifications for this session" turned off, the ring tone is still very much audible.
Furthermore, while in an ongoing (element 1-1) call, the ring tone noise is often much louder than the other persons voice and causes distress for both parties.
Steps to reproduce
set all notifications to "ON"
turn off switch "Enable audible notifications for this session"
start a 1-1 element call
have another person call you on element
Describe how what happens differs from what you expected.
an ongoing call should never be interrupted by a ring tone, especially not one as persistent and loud
there should not be any audible notification with the settings configured as abovie
Version information
Platform: web (in-browser)
For the web app:
Browser: Chromium 84.0.4147.141
OS: Rasbian
URL: app.element.io
The text was updated successfully, but these errors were encountered:
Could you see if rasbian/raspberry pi os offers a newer version of chromium and try to update it? Since chromium 84 is around 6 months out of date it's possible this issue doesn't exist on newer chromium versions.
As a side note the element team has been recently working on improving 1:1 calls so it's possible this issue is already on their radar.
Even with the latest available chromium - 87.0.4280.141 - the behavior is unchanged.
Especially because the ring tone is so loud, it is very disturbing when in a call.
Description
Even with all notifications set to "ON" and the switch "Enable audible notifications for this session" turned off, the ring tone is still very much audible.
Furthermore, while in an ongoing (element 1-1) call, the ring tone noise is often much louder than the other persons voice and causes distress for both parties.
Steps to reproduce
Describe how what happens differs from what you expected.
Version information
For the web app:
The text was updated successfully, but these errors were encountered: