Luckily LineageOS and GrapheneOS have a lockdown mode (Graphene also supports disabling fingerprint for screen unlock), though rebooting your phone usually doesn’t cause you to lose any work since everything autosaves as phones kill background apps to save battery and memory. Separate user profiles for situations like protests or certain contexts (preferably with some dummy data to make it not look to sus) are also useful.
It’s very unlikely the OS actually kills apps in the background as that would legitimately break many apps and is a source of frustration from other OEMs.
There’s a difference between killing an app and putting it into a less active state.
When you swipe an app away from your recent lists, it’s not actually killing it, its just putting it in a different state.
When your force stop an app from its info under settings, you’re actually killing it. Nothing about it is alive.
When you actually kill an app, things like alarms stop functioning. The app needs to be alive for the alarm to function. Even so much that when you set an alarm on your phone, you need to set the alarm again after rebooting as they arent permanently stored and if the phone is rebooted the app needs to be woken up and the alarms re set. There’s a whole development workflow to do that.
There was a brief period many years ago when an OEM actually force killed an app when swiped away from recents without fully understanding the implications and they later reverted the change.
Push notifications of any type would also completely cease functioning.
Luckily LineageOS and GrapheneOS have a lockdown mode (Graphene also supports disabling fingerprint for screen unlock), though rebooting your phone usually doesn’t cause you to lose any work since everything autosaves as phones kill background apps to save battery and memory. Separate user profiles for situations like protests or certain contexts (preferably with some dummy data to make it not look to sus) are also useful.
It’s very unlikely the OS actually kills apps in the background as that would legitimately break many apps and is a source of frustration from other OEMs.
There’s a difference between killing an app and putting it into a less active state.
When you swipe an app away from your recent lists, it’s not actually killing it, its just putting it in a different state.
When your force stop an app from its info under settings, you’re actually killing it. Nothing about it is alive.
When you actually kill an app, things like alarms stop functioning. The app needs to be alive for the alarm to function. Even so much that when you set an alarm on your phone, you need to set the alarm again after rebooting as they arent permanently stored and if the phone is rebooted the app needs to be woken up and the alarms re set. There’s a whole development workflow to do that.
There was a brief period many years ago when an OEM actually force killed an app when swiped away from recents without fully understanding the implications and they later reverted the change.
Push notifications of any type would also completely cease functioning.
I always hated how android phones seem to have everything running. This certainly explains why there is no proper task manager in them.