I wish modern Android didn't force you to fill your notifications with clutter in order to allow apps to run in the background

maybe it doesn't. I'm realizing I just assumed you need to set the notifications to Minimize rather than disabling them

so now I'm seeing if everything still works with them outright off

after reading the docs some, it appears the point of the notification is to allow a service to run as a "foreground" service rather than "background"

so I suspect this is related to aggressive OEM service killing and may not be necessary on AOSP? background services are only supposed to be killed when the system is low on resources, and, importantly, auto-restarted once the condition is over

it's however unclear if the user disabling your notification causes you to lose foreground status

Follow

@unascribed I'm pretty sure it doesn't, I had the persistent notification for the Pebble app off the entire time

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!