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

Feature Request: Only one notification for multiple messages received at once + Timestamps #778

Closed
shaaati opened this issue Feb 26, 2014 · 7 comments
Assignees
Labels

Comments

@shaaati
Copy link

shaaati commented Feb 26, 2014

After being offline (flight mode / no internet connection) my device rings/vibrates multiple times, depending on how many messages have been sent by others in the meantime.
Being in a quite active group my device vibrated for about 30 seconds this morning.

I can see the point of being notified that not only one but multiple messages have been received but this should be reworked to a less annoying way (e.g., ring twice for multiple messages).

Additionally, all messages that get then received are displayed with their receiving time.
I would prefer having them displayed with the sending time, which can also be seen by looking in the message details.
Maybe a menu entry to switch between both options would be a good idea because I can imagine people who like it the way it is handled now.

@moxie0 moxie0 self-assigned this Feb 26, 2014
@generalmanager
Copy link

I personally like the current implementation, because I know exactly how many messages I get, which is often an indication how urgently somebody wants to talk to me. However that would probably change if I had several large groups with a lot of activity.
How about a maximum of 2 notifications per user or group. That should keep the ringing short and it's still distinguishable - for example I get 2 rings in 1 burst, 1 ring, 2 rings in one burst.
This way I know I got multiple messages from 2 people or groups and a single message from somebody else. And if I use the new custom notification feature from #366 I even know who wrote me one or multiple messages.

And because of #366 we also can't limit the total number of rings - only the number of rings per user/group. Otherwise it would be impossible in the above example which ringtones to play if the users/groups have individual ones but we could only play 2 ringtones for all messages.

The second part is a duplicate of #597

@fd0
Copy link

fd0 commented Feb 27, 2014

I second this feature request. At the moment, I seem to always receive messages in bulk batches of 2-6, and having multiple notification sounds at once is very annoying.

@shaaati
Copy link
Author

shaaati commented Mar 7, 2014

I understand @Lindworm's explanation regarding #366 and would in that case like to see his proposal.
One problem left: How should the ringing behave in case people with different notification sounds also message me in group conversations?

@generalmanager
Copy link

@shaaati
In #354 there was also a request for group notifications. So if you didn't set a group notification, it would use the default sound. Otherwise you wouldn't know if the person texted you directly or the group. And you could also not limit it to two rings when more than two people replied to the group.

@jeremymasters
Copy link

I would rather see one ring for a message, two rings for more than one message.

@rhodey rhodey added the feature label Mar 16, 2015
@mawed
Copy link

mawed commented Feb 22, 2016

I just wanted to create a feature request for some similiar situation.
For when in a group some other people are writing really intense, then the amount of vibrations is really disturbing. So a limit of notifications in an amount of time would be nice.

For example, 3 vibrations in 5 minutes.
So if 4+ messages come in in 5 minutes (and I leave my phone wihout reading the signal messages), there should only be 3 vibrations.
After the 5 minutes (or if I read the messages) the counter restarts.

Maybe this is to special, maybe not.

@2-4601
Copy link
Contributor

2-4601 commented Apr 3, 2016

Closing first part in favor of #3165.
Second part duplicate #597.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

8 participants