You will only see the Anti-memory thrashing option on Android 6.0 or earlier since Android 7.0+ already implements these changes.
Any app may declare the following event receivers in its manifest:
- Connectivity change events, which are triggered whenever your network connectivity changes, e.g. when you switch from mobile data to Wi-Fi and vice versa or you toggle your Wi-Fi or mobile data connection.
- New picture / video events, which are triggered whenever you take a new picture using your camera app or record a video.
Whenever these two events are triggered, Android will start the app in the background in order to execute the code to handle these events. This requires the entire app to be loaded into the phone’s memory even though the app is never displayed. If the app is large this may cause other recently used apps to be unloaded from memory, which negatively affects multi-tasking. It may also make your phone feel sluggish because when an app’s process is loaded into memory it usually executes a number of initialization functions.
It’s also a privacy concern. Why should an app’s background task be started whenever you take a picture? Why does the app need to know you just shot a photo?
The Anti-memory thrashing option allows you to disable these events for the cloned app.