Scanning for too many values causes LMK to kill GG

[r3zaa]

Hi, 

In big games like CSR2 which use 1-2GB of RAM scanning for small values with millions of results causes my phone to run out of memory and close GG. I set Data in RAM to off but it didn't really help.

 

Is there a way around this? Or just the nature of how the program works?

 

Edit: 

Just if needed, I'm on A14, SELinux is enforcing.

Edited January 5 by r3zaa

[kiynox]

[ @r3zaa ]
---

Quote

causes my phone to run out of memory and close GG

It is unlikely because of memory issues, it is caused by Phantom processes that exist in newer Android version (Android 11-14). This is new restriction that Android (the OS itself) will kill/shutdown memory extensive app. You can try to disable it, but it can cause problems, do it at your responsibility:

• - How are phantom processes killed?
• - How to disable the phantom processes killing?

---
I recommend to downgrade your Android to atleast Android 9-11.

[r3zaa]

2 hours ago, kiynox said:

[ @r3zaa ]
---

It is unlikely because of memory issues, it is caused by Phantom processes that exist in newer Android version (Android 11-14). This is new restriction that Android (the OS itself) will kill/shutdown memory extensive app. You can try to disable it, but it can cause problems, do it at your responsibility:

• - How are phantom processes killed?
• - How to disable the phantom processes killing?

---
I recommend to downgrade your Android to atleast Android 9-11.

Thanks for the reply

I tried disabling the flag in Developer Options but it didn't help. 

For example, I searched for DWORD value '10' in CSR 2 and the search reached to about 80-90% before GG got killed.

I did monitor RAM usage with FKM and once it goes above 90% it force closes GG.

Edit: Just to make sure I rebooted after turning the flag. Just in case.

Yeah I remember back in A10-11 didn't have this problem. Good ol' Google back at it again I guess.

Edited January 6 by r3zaa