I recently upgraded my Moto G42 to lineageOS 23.2 after staying on 22 for way too long. Everything is fine but it seems memory management is totally out of control. As soon as I switch to another app, the background process gets killed.
If I would now switch to my browser for 5 seconds to copy some stuff, voyager would have been killed. This is an extremely unpleasant behavior. Does anybody knows a fix for this?
The jump from LOS 22 to 23.2 is significant since Android 14 changed how the kernel handles low-memory killer tuning. Most users expect memory pressure to improve with a newer version, not get worse, which makes the behavior you are describing feel backwards. What does ‘adb shell dumpsys meminfo’ report for your oom_adj scores when the background process gets killed? If the numbers look normal, the culprit is probably a custom kernel governor overriding LOS defaults.
LOS 23.2 is based on A16, and Google really tightened background process rules with that release. The behavior you are describing is the new normal on Android 16 even on stock, not necessarily a LOS bug. Check if the app has the ‘Unrestricted’ battery setting enabled, and also look into disabling the ‘Memory optimization’ feature in Developer Options if it is present. The Moto G42 only has 4GB of RAM, which does not give much headroom once Android 16 itself is using a chunk of it.
LOS 23.2 is based on A16, and Google really tightened background process rules with that release. The behavior you are describing is the new normal on Android 16 even on stock, not necessarily a LOS bug. Check if the app has the ‘Unrestricted’ battery setting enabled, and also look into disabling the ‘Memory optimization’ feature in Developer Options if it is present. The Moto G42 only has 4GB of RAM, which does not give much headroom once Android 16 itself is using a chunk of it.
