Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
That's great news. I hate undismissable notifications and I always thought they were an awkward workaround for apps that needed to stay in the background and not be terminated or put to sleep by battery saving features
And as long as things keep working, I think dropping this feature is a great idea.
That's not so great because now you don't know when an app is running in the background.
It also makes it harder for notifications you actually do want to persist like OPs - I use AccuBatterry and don't want to be able to dismiss by accident.
now you don’t know when an app is running in the background.
we've always had plenty of apps running in the background that don't use notifications
notifications you actually do want to persist
I think notifications should never persist. There should be an entirely different UI concept for apps that need to have information displayed at all times - like a widgets drawer or shade. Having a notification displayed at all times defeat the purpose of a notification, which should be an ephemeral / momentary display of information, usually time-sensitive.
That's not so great because now you don't know when an app is running in the background.
Not true. This shows at the bottom of the notification shade, tells you how long the app has been running a service and lets you stop it.
Oohh thanks! TIL. Now I wonder if I need Samsung Health to be always on, to be honest...
Fair enough, I just wish it was a long tap or something instead of a swipe (or having long tap be an option that you could enable)
I like being able to dismiss some, like my voicemail or background apps
It sounds like what would really be helpful is a way to "pin" or "lock" notifications so they can't be dismissed easily. This could be a setting for all notifications from certain apps. That way apps can't abuse it, and users can set it up how they like.
Edit: It could be an app permission as well.
This would be perfect too
Long press to pin
Oh that is nice. Finally! Bye bye undismissable notifications!
On the flip side of you i hate un dismissable notifications. And i especially hate a crowded notification area. So your use case would drive me insane. Sorry its borked your usage but for me being able to dismiss everything is great
Its pretty much clear for me, I periodically go through and deal with each one (respond to each message, read each alert).
When I need a persistent one, it's usually something like "grab X from office before leaving work". In order to dismiss those, I'd have to tap it and check off the task and it disappeared.
I'd love to get that option back, but ah well I guess
This is why we can't have nice things
To each his own, but your use case seems like the worst way to accomplish what you need. There are so, so many apps that will allow you to pin a widget to one of your homescreens with a to-do; why on earth would you want to have that living in your notification shade? I have a Keep to-do widget and the Android battery widget on a second homescreen to the right of the main. Exactly as much work as pulling down the shade, except I swipe left instead of down, and no chance of accidentally clearing the persistent notification.
I have a calendar widget that I use, but this was more for the very important "leave a sticky on the doorknob" type tasks.
I tried a widget for a while, but I found that I either didn't swipe to that page or I didn't like having that space blocked off by an empty widget for the periods of time when I didn't have a task.
It worked for what I needed, but I guess I'll explore options again
The problem is you are trying to use a system for something it was never intended for. Persistent notifications were only ever intended for long running background services.
Even for those though it's broken now. For example, I use fkm as an indicator that my phone is dozing/charging correctly and rotation control to force apps into the orientation I want them. Both effectively require persistent notifications to work as intended.
This behavior decision by Google is a straight downgrade. It needed to be at worst togglable by the user.