Applications force-killed by the manufacturer's Android

[unifiedpush]

Applications force-killed by the manufacturer's Android

[christophehenry]

FCM seems to be using a service rather than an empty activity even though they seem to escape battery optimisation for whatever reason.

[p1gp1g]

The BroadcastReceiver starts the application unless the application has been manually force-killed by the user.
This behavior is known and expected (for instance, when testing matrix clients, I force killed all my matrix client except one).

Do you experience non-waking application while you haven't force-killed the application ? If so, we can debug this issue (probably a vendor issue then) and I'll transfer this to android-connector.

[p1gp1g]

If it is the vendor issue, FCM has the same issue: firebase/quickstart-android#378 (comment)

[christophehenry]

I observed, every now and then, some notifications are not distributed to Element or Fedilab when they have been running in the background for some time. I assumed this was because the system reclaimed the ressources for battery optimization and force killing the app did the same (for test purposes). There's no way for me to reliably reproduce this, unfortunatly.

[p1gp1g]

You should check that website : https://dontkillmyapp.com/

Do you see solutions for your device ? Do you see improvement if you do what's recommended ?

[christophehenry]

I run Lineage. There shouldn't be any optimization beyond what's on AOSP. I guess there's not good solution. Maybe future Android API level come with a solution to ensure an app correctly receives notifications.

[p1gp1g]

Lineage uses some vendor blobs, I don't know if some on your device can be related to battery optimization 🤔 .

I wonder if the issue doesn't occur after the message is received by the application: have you disabled battery optimization for element for instance ? If element is in background for a while, the sync with the server can takes time (it will be shorten with matrix sync v3) and the app may be killed during this process.

[christophehenry]

I just disabled battery optimizations. I'll see if it solves the problem. But honestly, I just wished users wouldn't have to do such configurations. Using a phone should be simple…

Sorry for the noise.