GmsCompat as a persistent notification

mythodical

Regarding GmsCompat's Sandboxed Google Play is running persistent notification, are there any functional concerns with blocking or dismissing this notification?

I have seen other posts where users are instructed to block the notification in order to remove it, but it begs the question, why is there a persistent notification?

Is there a risk that the compatibility layer may be closed by power management if not given persistent status?
And if the process is stopped, does Google Play Store/Services simply stop working as well?

Apologies if this has been discussed before.

unwat

mythodical

From the Android website:

Foreground services show a status bar notification, so that users are actively aware that your app is performing a task in the foreground and is consuming system resources.

The notification doesn't keep the app open. The OS forces a persistent notification because the app is always running.

mythodical

unwat Thanks for the link. I wondered because of my previous experience with Huawei's aggressive power management, since they often killed processes if the app didn't use persistent notifications to stay in the foreground.

I did notice that GmsCompat itself is battery-optimised by default, so I suspected it might simply spawn as needed.

I'm new to both GrapheneOS and all things Android above v10, so still learning what the expected state of things are.

strcat

Apps running foreground services must create a persistent notification that's not hidden/collapsed by default. The user can set the notification channel as hidden/collapsed or can disable the channel completely. It will still work fine since it still exists and the user has chosen not to show it.