[Abishek_Muthian]

Although iOS background killing is obscure, it's well known that background service would definitely get killed(at max ~3 mins?), the behaviour is same across all devices and different OS iterations.

But in Android, apart from default doze, battery optimisation feature, each manufacturer implement their own aggressive app killing services and so managing background tasks becomes very hard. At least in recent versions of Android, app developer can navigate the user to disable battery optimisation for their app if needed, which would affect default system behaviour but out of luck if the manufacturer implements their own app killer.

Unfortunately, I didn't see any of the contact tracing apps of several countries explicitly asking users to disable battery optimisation/app killers or whitelist bg task permission for their apps and I think that's one of the main reasons for the supposed failure of contact tracing apps.

[bluerobotcat]

The app doesn't get killed that quickly because it has location services on in the background. It's the same reason that Google Maps doesn't get killed in the background when it's giving you directions. iOS prompts for permission, but the authorities gave us instructions to grant such permissions.

That being said, it is thee case that if you open sufficient apps (especially memory hungry ones) the app will be killed regardless.

I've resigned to manually bringing the app to the foreground every now and then in an attempt to reduce the number of phone calls I get from the government to a minimum (currently 1-2 per day).