Kill cached processes after screen turns on

[RiKkzu]

Issue type

Other

Device

POCO X3 Pro | vayu

crDroid version

crDroid 12

Exact version / Build date

12.11/2026-07-02

Bug description

Summary

We’ve noticed that cached processes are forcefully killed immediately after the screen is turned on, regardless of how much free RAM is available.
Impact

Browser tabs restart: each browser tab runs as a separate process, so users observe tab reloads.
Performance overhead: other apps that were backgrounded are restarted again, increasing CPU/memory churn.

Suspected component

From the logs, this behavior appears to be caused by the WindowManager process.
Request / Questions

Is it possible to disable (or reduce) the trigger that kills cached processes on screen-on, since it seems unnecessary?
The memory killer (OOM/memory pressure mechanism) should be able to kill cached processes only when memory is actually low—even if the screen isn’t turned off during the whole day.
Evidence

Logs show WindowManager is involved.
Happens after screen-on events.
Occurs even when free RAM is not low.

Steps to reproduce

1. Turn on the device and let it stay idle for a while.

2. Open the browser and create several tabs, then wait until some tabs/app processes become backgrounded/cached.

3. Lock the device or let the screen turn off (the device goes to sleep / screen-off state).

4. Turn the screen back on (wake up).

5. Observe that cached/background processes are forcefully killed immediately after screen-on.

6. Verify the impact:

   browser tabs reload/restart (since each tab runs as a separate process),
   other backgrounded apps may be restarted again.

7. Check system logs to confirm the component triggering the kill (suspected: WindowManager).

Relevant log (logcat/build log)

sudo logcat | grep "screen-on memory reclaim"
07-03 19:53:42.264  1842  1871 D WindowManager: Performing screen-on memory reclaim.
07-03 19:53:42.265  1842  1908 I ActivityManager: Killing 12569:com.android.deskclock/u0a393 (adj 945): screen-on memory reclaim
07-03 19:53:42.267  1842  1908 I ActivityManager: Killing 10731:com.android.permissioncontroller/u0a449 (adj 945): screen-on memory reclaim
07-03 19:53:42.270  1842  1908 I ActivityManager: Killing 13346:org.ironfoxoss.ironfox:tab_disable_art_image_32/u0a453 (adj 930): screen-on memory reclaim
07-03 19:53:42.273  1842  1908 I ActivityManager: Killing 14335:io.homeassistant.companion.android/u0a495 (adj 925): screen-on memory reclaim
07-03 19:53:42.279  1842  1908 I ActivityManager: Killing 10584:org.omnirom.omnijaws/u0a415 (adj 925): screen-on memory reclaim
07-03 19:53:42.282  1842  1908 I ActivityManager: Killing 13221:org.ironfoxoss.ironfox:gpu_disable_art_image_/u0a453 (adj 920): screen-on memory reclaim
07-03 19:53:42.284  1842  1908 I ActivityManager: Killing 5108:com.android.cellbroadcastreceiver.module/u0a440 (adj 915): screen-on memory reclaim
07-03 19:53:42.287  1842  1908 I ActivityManager: Killing 13000:com.android.settings/1000 (adj 915): screen-on memory reclaim
07-03 19:53:42.290  1842  1908 I ActivityManager: Killing 13439:org.ironfoxoss.ironfox:tab_disable_art_image_39/u0a453 (adj 910): screen-on memory reclaim
07-03 19:53:42.292  1842  1908 I ActivityManager: Killing 10151:com.android.providers.calendar/u0a340 (adj 905): screen-on memory reclaim
07-03 19:58:48.594  1842  1871 D WindowManager: Performing screen-on memory reclaim.
07-03 19:58:48.596  1842  1908 I ActivityManager: Killing 14715:org.ironfoxoss.ironfox:gpu_disable_art_image_/u0a453 (adj 930): screen-on memory reclaim
07-03 19:58:48.608  1842  1908 I ActivityManager: Killing 14732:org.ironfoxoss.ironfox:tab_disable_art_image_39/u0a453 (adj 920): screen-on memory reclaim
07-03 19:58:48.612  1842  1908 I ActivityManager: Killing 14748:com.android.providers.calendar/u0a340 (adj 915): screen-on memory reclaim
07-03 19:58:48.617  1842  1908 I ActivityManager: Killing 14781:com.android.settings/1000 (adj 915): screen-on memory reclaim
07-03 19:58:48.622  1842  1908 I ActivityManager: Killing 14765:org.ironfoxoss.ironfox:tab_disable_art_image_32/u0a453 (adj 910): screen-on memory reclaim
07-03 19:58:48.624  1842  1908 I ActivityManager: Killing 14849:com.android.cellbroadcastreceiver.module/u0a440 (adj 905): screen-on memory reclaim

Screenshots or videos

No response

Solution

No response

Additional context

No response

Acknowledgements

• I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
• I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly and understand that not doing so will automatically result in closing of ticket.

[neobuddy89]

This is purposefully added for better UX - it happens after certain interval.

[RiKkzu]

This is purposefully added for better UX - it happens after certain interval.

Is it possible to add a hidden experimental setting that would let me set my own interval (for “infinity” time) or disable it? I suspect this could improve the user experience.