I can slide away permament notifications, and I'm not supposed to

topologic_hydra

I have a lot of app that have permanent notifications, both that run constantly (kde connect, nebulo, etc) and some that give out permanent notification at a given time (rxdroid, which is the one why I am whining so much about this problem). I can just slide away those notifcations, as if they weren't sticky. is this a known bug? I tried to shout in the void (ask in the telegram group that I think is bridged to discord matrix and irc), but no one answered, so I'm asking here. is it a known bug? is the problem between chair and the phone? am I doing something wrong? am I going crazy? before android 14 i did not have this problem, I've noticed this thing started around after updating to Android 14.
are you experiencing the same problems? what is wrong my permanent notifications?
forgot to mention: if i press clear all notifications, the permanent one remain, but I can manually slide them away, which is no bueno.
sorry if this post came up as angry/arrogant, it was not my intention, it's just that i'm a bit frustrated about this whole ordeal. I switched to the beta channel for updates, might switch to alpha too if needed.
anyway thank you for coming to my ted talk

Dumdum

topologic_hydra I tried to shout in the void (ask in the telegram group that I think is bridged to discord matrix and irc), but no one answered,

I think you quite literally shouted into the void... at least going based off of the official contact methods, there doesn't seem to be any kind of telegram group. I could be mistaken.

But for the record, its also something I'm experiencing too (Mullvad VPN and KDE Connect). Personally I'm not fussed about it, as I can just get the notifications back by opening their apps. Certainly curious why these notifications aren't so permanent any more though.

akc3n

Dumdum they've been "bumping" that question daily for almost a week. I don't really know what they are talking about so I never replied to them in our chat community. It would be safe to assume that no one else did either, otherwise they would have gotten a reply.

I am going to share there post here internally and see if we can get it addressed and help topologic_hydra

matchboxbananasynergy

topologic_hydra Which GrapheneOS release are you currently using? You can check by going to Settings > About phone > Build number - please provide that full build number.

This was briefly an issue due to a change made in Android 14 but has been fixed already, several releases ago - the fact that you're experiencing this makes me think you might be on an old release and might need to update.

The reason why you might not have updated is because the updater might've downloaded the new update and then gave you the notification to reboot, but because it could be swiped away, you might've not seen it and therefore not updated.

I think if you simply update to the latest stable release, you should be golden.

You can see when this was fixed, on this release:

https://grapheneos.org/releases#2023102300

allow system apps to make sticky notifications again (important for System Updater to avoid users missing the notice to reboot after update installation)

matchboxbananasynergy

matchboxbananasynergy Actually - backtracking to correct myself on this. The fix was for system apps specifically, not user-installed apps.

My guess is that Android 14 changed how these notifications work in general, and the apps in question still haven't adapted to the new way of doing things.

topologic_hydra

matchboxbananasynergy my build number is UP1A.231105.003.2023111500; I am on stable channel; I switched to beta as a last hope.
[deleted] I don't get it, android 14 removed sticky notifications and now I have to manually tell each app what sitcky/permanent notification I want?

[deleted]

Changes to how users experience non-dismissible notifications

If your app shows non-dismissable foreground notifications to users, Android 14 has changed the behavior to allow users to dismiss such notifications.

This change applies to apps that prevent users from dismissing foreground notifications by setting Notification.FLAG_ONGOING_EVENT through Notification.Builder#setOngoing(true) or NotificationCompat.Builder#setOngoing(true). The behavior of FLAG_ONGOING_EVENT has changed to make such notifications actually dismissable by the user.

These kinds of notifications are still non-dismissable in the following conditions:

When the phone is locked

If the user selects a Clear all notification action (which helps with accidental dismissals)

Also, this new behavior doesn't apply to notifications in the following use cases:

CallStyle notifications

Device policy controller (DPC) and supporting packages for enterprise

https://developer.android.com/about/versions/14/behavior-changes-all#non-dismissable-notifications

Portions of this page are reproduced from work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.

[deleted]

topologic_hydra Dismissible notifications have become dismissible for apps that deliver it via an foreground service, subject to certain conditions as described by the quoted content. Apps that deliver notifications while in background (like Google Play services) might still be able to deliver undismissable notifications.

GrapheneOS

Current Android doesn't work the same way as before. Foreground service notifications can be dismissed. Only specific system apps can use sticky notifications. GrapheneOS expanded this to allow all system apps to use sticky notifications since some of them are important such as the OS update reboot notification, post-update app compilation restart notification and some of the standard ones they didn't exclude from sticky being ignored.

bookreader

Definitely a really horrible change, but as noted, its upstream. They shouldn't have made that change without making a way to avoid accidental dismissal.