Timeline for Keeping an app in memory
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 24, 2019 at 19:12 | comment | added | u2n | Upvoted comment of @Michael as this method still does not work (updated to N 7.1). Also tried making oom RO (444), but after the set delay (few minutes), it reverts to previous value. Nothing across the Internet I've found will accomplish the task. | |
| Sep 20, 2013 at 5:28 | vote | accept | Binoy Babu | ||
| Sep 19, 2013 at 22:09 | comment | added | Michael | This seems to work well... at first. but if i watch the oom_adj file i find that pretty soon it is no longer -17, and then my app can be killed again | |
| Jan 31, 2013 at 17:03 | comment | added | t0mm13b | There must be a catch with this? Surely, keeping it in memory will starve other apps of precious RAM and could cause Android to go berserk when trying to manage apps that hit the memory threshold and quite potentially p-off users who are wondering why the app is not loading when that threshold gets reached! | |
| Sep 4, 2012 at 21:34 | history | edited | Ryan Conrad | CC BY-SA 3.0 |
fixed typo
|
| Sep 4, 2012 at 20:00 | comment | added | Izzy | Does that only work if the app is started within that 60s sleep period -- or is this init script run repeatedly? I don't see a loop or anything indicating that this would also work for an app started at a later time. | |
| Aug 25, 2012 at 5:29 | history | answered | Ryan Conrad | CC BY-SA 3.0 |