element-hq / element-hq/element-android
Ongoing call produces notifications within Element
- Dominant language
- Kotlin
- Stars
- 3.7k
- Forks
- 917
- Avg merge
- 8d 20h
- Merged PRs (30d)
- 1
Description
### Steps to reproduce
1. get called (various scenarios: Element is closed or open or you are even in the corresponding chat)
2. accept the call
3. leave the chat/call window (don't exit the actual call)
4. view the list of chats which contains the chat where that call was placed
5. see (multiple) notifications despite no new messages (but probably call events in the background - nothing the user wouldn't be already aware of);

### Outcome
#### What did you expect?
- no new notifications
- no highlighting
In other words: the entry in the room list should look like any other room entry pointing to a room in which nothing new has happened (aside perhaps an indicator that the ongoing call is in the specific room)
#### What happened instead?
Indication of 5 new ~~messages~~ events which I already know of and won't find when I open the chat, because there are no new real messages.
### Your phone model
Fairphone 3+
### Operating system version
Android 10
### Application version and app store
Element version 1.3.8 [40103082] (G-b4480)
### Homeserver
matrix.org
### Will you send logs?
No
Contributor guide
Research direction
Start by reproducing the call flow on Android 10 with Element 1.3.8, including leaving the room while remaining in the call, and trace the room-list notification behavior. Done means an ongoing call does not create new-message notifications or highlight the room, while any ongoing-call indicator may remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100