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

no notification #8323

Open
B3MH opened this issue Apr 11, 2023 · 3 comments
Open

no notification #8323

B3MH opened this issue Apr 11, 2023 · 3 comments
Labels
A-Notifications O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@B3MH
Copy link

B3MH commented Apr 11, 2023

Steps to reproduce

When the phone screen is turned off, notifications are not shown (No sound and No Vibration) and there are no announcements.

Outcome

What did you expect?

I expect notifications like software similar to WhatsApp and Telegram to be announced

What happened instead?

Do not make a loud sound

Your phone model

Samsung A51

Operating system version

Android 13

Application version and app store

Element v 1.5.30 Google Play store [4.1.53.2] (G0b09a51b)

Homeserver

matrix 1.5.30 (0b09a51)

Will you send logs?

Yes

Are you willing to provide a PR?

Yes

@B3MH B3MH added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Apr 11, 2023
@TLATER
Copy link

TLATER commented Apr 11, 2023

Possibly the same as #3996 ?

@kittykat kittykat added A-Notifications S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience labels Apr 17, 2023
@z411
Copy link

z411 commented Jun 9, 2023

Same issue on 1.5.23 Xiaomi with MIUI 13. Very critical as there was an emergency and I couldn't respond in time. The chats aren't marked as read so I don't think it's the same issue.

It just feels like nothing is triggering a sync when the message arrives. I have to open the app so it syncs. Same thing with calls as well. Push troubleshooting gives no errors.

@z411
Copy link

z411 commented Jun 9, 2023

I rectify. Using 1.6.2 the notification indeed appears but then disappears after half a second. After opening the all the unread number is correct, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

4 participants