-
Notifications
You must be signed in to change notification settings - Fork 741
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
Notifications in F-Droid version doesn't work #2669
Comments
@kszzsk That's a dead link. :( |
@sydbarrett74 corrected |
Is the play store version different to the droid version on this matter? I have had the same trouble... |
#2143 |
Grouping into #4298 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Element is getting killed by Android system while being in the background. This completely disables notifications until next manual start. This happens on every Android device I've tested (Android 8.0 - Android 10).
Disabling every Android setting for lower power usage doesn't help.
The reason for that - Element doesn't display permanent notification.
I believe even Android dev manuals explicitly state that every permanent background app should have permanent notification now.
RiotX worked perfectly fine while having this permanent notification.
I have no Idea why this regression took place while transitioning from RiotX codebase to Element, but I guess this should be fix ASAP, because as far as I understand (correct me if I'm wrong), this is quite a simple thing to fix and right now it makes F-Droid version of Element pretty much unusable.
The text was updated successfully, but these errors were encountered: