signalapp / signalapp/Signal-Android
Notification count in Notification tray and notification sound is wrong
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.4k
- Forks
- 6.9k
- PR merge metrics
- No merged PRs in 30d
Description
Guidelines
- I have searched searched open and closed issues for duplicates
- I am submitting a bug report for existing functionality that does not work as intended
- This isn't a feature request or a discussion topic
Bug description
In the notification tray the count of signal message is always +1 because it is including "signal is unlocked".
This is also causing problem with notification sound in following scenario:
- Unlock Signal and send message to someone.
- Come out of signal and wait for someone to respond within the period when Signal is still unlocked.
- When they respond 2 sounds are triggered within 1 second even though they sent 1 message.
This is observed after I upgraded to OneUI8
Screenshots
Even the notification sound that we get when we receive message is one or two more when we receive message when the phone is locked and sometime within few seconds if unlocked then I can hear one more sound.
Following image is "Sound History" from an app called "nice catch" under "Good Lock" by Samsung.
Device
Samsung S24 Plus
Android version
16
Signal version
7.62.0
Link to debug log
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked debug log and reproducing the notification tray and sound behavior using the listed steps on a Samsung S24 Plus with Android 16. Done means a received message contributes one notification count and triggers one sound, without counting the “signal is unlocked” notification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100