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

Allow all noisy notifications for direct messages - not just upon first received (google play) #5095

Closed
binarydad opened this issue Jan 28, 2022 · 7 comments
Labels
A-Notifications T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements X-Needs-Product Issue needs input from Product team

Comments

@binarydad
Copy link

binarydad commented Jan 28, 2022

Your use case

What would you like to do?

I see I'm receiving notifications just fine, and none are missing. The issue is, upon receiving my first message, I would get a "noisy" notification. However, if another message comes in, I don't get a noisy notification. I do see that they are being added to the notifications when swiped down, but they are silent. My of my chats are direct 1-on-1.

Why would you like to do it?

If I happen to miss that first notification (phone is in pocket, etc), I'm never aware of additional (possibly urgent) messages received. Element for desktop creates a noisy notification for every message, as does FluffyChat. I wish Element Android behaved the same way.

How would you like to achieve it?

Allow an option for "noisy notifications for every direct message received".

Have you considered any alternatives?

Yes, FluffyChat works as I would like, but I do not care for other aspects of the app.

I do not believe this relates to this issue: #5038

@binarydad binarydad added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Jan 28, 2022
@marcusaram
Copy link

I think it is related to that issue, because it was working that way. Now it doesn't behave anymore like that.

@binarydad
Copy link
Author

binarydad commented Jan 28, 2022

I think it is related to that issue, because it was working that way. Now it doesn't behave anymore like that.

Ok, thanks. I wasn't sure because I do in fact see notifications coming in, they're just not NOISY, and there seems to be NO inconsistency in the behavior.

@ouchadam
Copy link
Contributor

ouchadam commented Jan 28, 2022

@marcusaram there might be some confusion~ #5038 is about notifications not showing up at all whereas this issue is for allowing notifications from direct messages to notify (make a sound/vibrate) for each new message

the change to only notify (make a sound/vibrate) for the first unread message in a room was introduced in 1.3.4

for reference #4632 #4398

@binarydad
Copy link
Author

I understand. I can see how that can be really annoying for rooms, etc, but direct messages are a different beast. What I'm not understanding is there are settings for notifying in group chats only for "Mentions & Keywords", so this should've resolved the noisy-ness in either regard.

This should be an option to toggle. Element is the only messaging app I have/use that only notifies upon the first message received.

@marcusaram
Copy link

@ouchadam Oh ok, then I first ran into that issue and after playing with settings. (enabling and disabling push, debugging etc) I had this behavior. Sorry for the noise 😅.

@ouchadam
Copy link
Contributor

I understand. I can see how that can be really annoying for rooms, etc, but direct messages are a different beast. What I'm not understanding is there are settings for notifying in group chats only for "Mentions & Keywords", so this should've resolved the noisy-ness in either regard.

This should be an option to toggle. Element is the only messaging app I have/use that only notifies upon the first message received.

totally agree, part of the original problem stems from the default rules for rooms being to notify for every message and android lacking the ability to enable notifications for mentions (rooms currently have all or nothing)

@ouchadam Oh ok, then I first ran into that issue and after playing with settings. (enabling and disabling push, debugging etc) I had this behavior. Sorry for the noise sweat_smile.

no worries! that information is helpful but for the other ticket 😄 the missing notification issue is quite troublesome to reproduce...

@ouchadam ouchadam added Z-WTF WTF moment: High Impact, Low Effort X-Needs-Product Issue needs input from Product team and removed Z-WTF WTF moment: High Impact, Low Effort labels Feb 17, 2022
@ouchadam
Copy link
Contributor

ouchadam commented Feb 17, 2022

I'm going to close this issue and centralise the topic to #4632 (whilst upgrading the original priority to a z-wtf)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements X-Needs-Product Issue needs input from Product team
Projects
None yet
Development

No branches or pull requests

3 participants