Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 1.6.24 - Some rooms / conversations switched to "Silent Notifications". #8963

Open
ToddCrimson opened this issue Dec 19, 2024 · 1 comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@ToddCrimson
Copy link

Steps to reproduce

  1. In a room or private direct conversation
  2. Send a message
  3. When recipient responds, it is "silent" (used to be Noisy)

PS: This was not happening in 1.6.18 (as we didn't upgrade to 1.6.20, due to microphone bug)

We tried to see everywhere if we can switch a room from "silent notification" to "noisy notification", but there is absolutely no toggle anywhere. In the app, if we go notifications, everything is correct. And if we go into Android notification settings, we can see that some of the "rooms" and "conversation" are randomly marked "Silent notifications". If we click them, and change silent on top to default, it doesn't change it to Noisy Notification. Also, if we do "default", in sound, it makes us choose a bell for ringing VS a notifications sound.

Please look into this bug, as we will have to once again downgrade back to ver 1.6.18.

Outcome

What did you expect?

I expected my phone to create the default sound

What happened instead?

No sound at all :(

Your phone model

Pixel 8 Pro, Pixel 7 A, Pixel 9

Operating system version

Android 14 and 15

Application version and app store

Element version 1.6.24 from F-Droid

Homeserver

Synapse private server

Will you send logs?

Yes

Are you willing to provide a PR?

Yes

@ToddCrimson ToddCrimson added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Dec 19, 2024
@ToddCrimson
Copy link
Author

Update: We switched back to version 1.6.18 the above problem went away.
Out of curiosity, we updated again, the problem came back.
So we are now running 1.6.18, confirming that 1.6.24 while fixed the microphone issue, has introduced other regression.

Caveat: Ver 1.6.18 doesn't do well when on Synapse Matrix server you have media requiring authentication. So we had to turn it off in vars.yml using matrix_synapse_enable_authenticated_media: false. We will wait until bug fixes come for the latest version.

Please let me know if we can help any way to support fixing of this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

1 participant